Add Social Contract email.

* code/sc-email.txt: New file.

1 files changed, 85 insertions, 0 deletions

diff --git a/code/sc-email.txt b/code/sc-email.txt
new file mode 100644
index 0000000..4433d08
--- /dev/null
+++ b/code/sc-email.txt
@@ -0,0 +1,85 @@
+To: maintainer@example.org
+
+Dear GNU maintainer,
+
+You are receiving this message because you are listed as responsible for
+a GNU package in the ‘maintainers’ file on fencepost.gnu.org. If you
+think this is inaccurate, or if you no longer want to be contacted about
+this initiative, please let us know about it.
+
+The authors of this message have started an effort to devise a GNU
+“social contract”.  We hope the social contract will help build a shared
+understanding of our mission as part of GNU.
+
+Work has been on-going on the public gnu-misc-discuss mailing list since
+October 2019, with comments from several GNU volunteers, in the “GNU
+social contract” threads below:
+
+  https://lists.gnu.org/archive/html/gnu-misc-discuss/2019-10/threads.html
+  https://lists.gnu.org/archive/html/gnu-misc-discuss/2019-11/threads.html
+  https://lists.gnu.org/archive/html/gnu-misc-discuss/2019-12/threads.html
+  https://lists.gnu.org/archive/html/gnu-misc-discuss/2020-01/threads.html
+
+A first draft resulting from these discussions is attached below and can
+be seen at:
+
+  XXX (meta.gnu.tools URL)
+
+The goal of this document is to state the core values GNU maintainers
+and uploaders and contributors who have endorsed it are committed to
+uphold.  It is both an agreement among us, GNU contributors, and a
+pledge to the broader free software community.  Additionally, we think
+it can be a first step towards formalizing a transparent and collective
+governance of the GNU Project.
+
+We are sending this message to all the GNU volunteers responsible for a
+GNU package for which we have the contact information so that they can
+take part in the making of the GNU Social Contract.  We hope you can
+share this with other members of your project for the next step (see
+below).  The proposed timeline is the following:
+
+  1. By February 9th, 2020, we invite you to send feedback about the
+     draft GNU Social Contract to gnu-misc-discuss@gnu.org (you first
+     need to subscribe at
+     <https://lists.gnu.org/mailman/listinfo/gnu-misc-discuss>).
+
+     Please introduce yourself as GNU maintainer.  Note that up to XXX
+     maintainers might contribute to the discussions; make sure that
+     your contributions are focused and to-the-point.  Alternately, you
+     can choose to email your feedback privately to <XXX@gnu.tools>.
+
+     We also encourage you to discuss this topic on your project’s
+     channels during that time to get some feedback whether other
+     members would be willing to endorse the GNU Social Contract or
+     would like improvements to the text before doing so.
+
+  2. On February 10th, we will upload an updated version of the Social
+     Contract, version 1.0, to XXX (meta.gnu.tools URL).
+
+  3. We ask you to send a message, by February 24th, preferably signed
+     with your OpenPGP key, to gnu-misc-discuss@gnu.org and
+     XXX@gnu.tools, containing one of the following statements:
+
+       • I, maintainer of package X, endorse version 1.0 of the GNU
+         Social Contract, available at XXX (meta.gnu.tools URL).
+
+       • I, maintainer of package X, do not adhere to version 1.0 of the
+         GNU Social Contract, available at XXX.
+
+  4. In the following days, we will publish at XXX the list of GNU
+     package maintainers who endorse as well as those who reject version
+     1.0 of the GNU Social Contract.
+
+One of the next action items we may collectively undertake at the end
+of this process is defining “membership” in the GNU Project.  This, in
+turn, will allow us to ask all the project members (including sysadmins,
+web masters, developers) whether they would endorse the GNU Social
+Contract.
+
+Thanks in advance for your participation!
+
+  - Ludovic Courtès
+  - Andreas Enge
+  - Carlos O’Donell
+  - Mark Wielaard
+  - Andy Wingo