user/dev discussion of public-inbox itself
 help / color / Atom feed
* [RFC] doc: start reproducibility document
@ 2020-04-07  9:37 Eric Wong
  2020-04-08  0:24 ` Kyle Meyer
  0 siblings, 1 reply; 2+ messages in thread
From: Eric Wong @ 2020-04-07  9:37 UTC (permalink / raw)
  To: meta

Not new ideas, just gathering thoughts.
---
 Documentation/reproducibility.txt | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 Documentation/reproducibility.txt

diff --git a/Documentation/reproducibility.txt b/Documentation/reproducibility.txt
new file mode 100644
index 00000000..4e56ada4
--- /dev/null
+++ b/Documentation/reproducibility.txt
@@ -0,0 +1,29 @@
+reproducibility => forkability
+------------------------------
+
+The ability to fork a project is a checks and balances
+system for free software projects.  Reproducibility is key
+to forkability since every mirror is potential fork.
+
+git makes the code history of projects fully reproducible.
+public-inbox uses git to make the email history of projects
+reproducible.
+
+Keeping all communications as email ensures the full history
+of the entire project can be mirrored by anyone with the
+resources to do so.  Compact, low-complexity data requires
+less resources to mirror, so sticking with plain-text
+ensures more parties can mirror and potentially fork the
+project with all its data.
+
+Any private or irreproducible data is a barrier to forking.
+These include mailing list subscriber information and
+non-federated user identities.  The "pull" subscriber model
+of NNTP and Atom feeds combined with open-to-all posting
+means there's no need for private data.
+
+If these things make power hungry project leaders and admins
+uncomfortable, good.  That was the point.  It's how checks
+and balances ought to work.
+
+Comments, corrections, etc welcome: meta@public-inbox.org

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [RFC] doc: start reproducibility document
  2020-04-07  9:37 [RFC] doc: start reproducibility document Eric Wong
@ 2020-04-08  0:24 ` Kyle Meyer
  0 siblings, 0 replies; 2+ messages in thread
From: Kyle Meyer @ 2020-04-08  0:24 UTC (permalink / raw)
  To: Eric Wong; +Cc: meta

Eric Wong <e@yhbt.net> writes:

> Not new ideas, just gathering thoughts.

Thanks.  Ideas will are always be new to some :)  It's nice to make them
easy to discover for someone exploring the project tree.

It reads well to me.

> +The ability to fork a project is a checks and balances
> +system for free software projects.  Reproducibility is key
> +to forkability since every mirror is potential fork.

Missing an "a" in front of "potential".

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-07  9:37 [RFC] doc: start reproducibility document Eric Wong
2020-04-08  0:24 ` Kyle Meyer

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror http://public-inbox.org/meta
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Example config snippet for mirrors

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta
	nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta
	nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta
	nntp://news.gmane.io/gmane.mail.public-inbox.general

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git