From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: [PATCH v2 2/2] doc: start reproducibility document
Date: Mon, 13 Apr 2020 11:32:45 +0000 [thread overview]
Message-ID: <20200413113245.9282-3-e@yhbt.net> (raw)
In-Reply-To: <20200413113245.9282-1-e@yhbt.net>
Not new ideas, just gathering thoughts.
Thanks to Kyle Meyer for a grammar fix.
---
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..af3e5366
--- /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 a 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
prev parent reply other threads:[~2020-04-13 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 11:32 [PATCH v2 0/2] rerolled doc updates Eric Wong
2020-04-13 11:32 ` [PATCH v2 1/2] doc: add technical/whyperl Eric Wong
2020-04-13 11:32 ` Eric Wong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200413113245.9282-3-e@yhbt.net \
--to=e@yhbt.net \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).