summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--code/sc-email.txt85
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 @@
1To: maintainer@example.org
2
3Dear GNU maintainer,
4
5You are receiving this message because you are listed as responsible for
6a GNU package in the ‘maintainers’ file on fencepost.gnu.org. If you
7think this is inaccurate, or if you no longer want to be contacted about
8this initiative, please let us know about it.
9
10The authors of this message have started an effort to devise a GNU
11“social contract”. We hope the social contract will help build a shared
12understanding of our mission as part of GNU.
13
14Work has been on-going on the public gnu-misc-discuss mailing list since
15October 2019, with comments from several GNU volunteers, in the “GNU
16social contract” threads below:
17
18 https://lists.gnu.org/archive/html/gnu-misc-discuss/2019-10/threads.html
19 https://lists.gnu.org/archive/html/gnu-misc-discuss/2019-11/threads.html
20 https://lists.gnu.org/archive/html/gnu-misc-discuss/2019-12/threads.html
21 https://lists.gnu.org/archive/html/gnu-misc-discuss/2020-01/threads.html
22
23A first draft resulting from these discussions is attached below and can
24be seen at:
25
26 XXX (meta.gnu.tools URL)
27
28The goal of this document is to state the core values GNU maintainers
29and uploaders and contributors who have endorsed it are committed to
30uphold. It is both an agreement among us, GNU contributors, and a
31pledge to the broader free software community. Additionally, we think
32it can be a first step towards formalizing a transparent and collective
33governance of the GNU Project.
34
35We are sending this message to all the GNU volunteers responsible for a
36GNU package for which we have the contact information so that they can
37take part in the making of the GNU Social Contract. We hope you can
38share this with other members of your project for the next step (see
39below). The proposed timeline is the following:
40
41 1. By February 9th, 2020, we invite you to send feedback about the
42 draft GNU Social Contract to gnu-misc-discuss@gnu.org (you first
43 need to subscribe at
44 <https://lists.gnu.org/mailman/listinfo/gnu-misc-discuss>).
45
46 Please introduce yourself as GNU maintainer. Note that up to XXX
47 maintainers might contribute to the discussions; make sure that
48 your contributions are focused and to-the-point. Alternately, you
49 can choose to email your feedback privately to <XXX@gnu.tools>.
50
51 We also encourage you to discuss this topic on your project’s
52 channels during that time to get some feedback whether other
53 members would be willing to endorse the GNU Social Contract or
54 would like improvements to the text before doing so.
55
56 2. On February 10th, we will upload an updated version of the Social
57 Contract, version 1.0, to XXX (meta.gnu.tools URL).
58
59 3. We ask you to send a message, by February 24th, preferably signed
60 with your OpenPGP key, to gnu-misc-discuss@gnu.org and
61 XXX@gnu.tools, containing one of the following statements:
62
63 • I, maintainer of package X, endorse version 1.0 of the GNU
64 Social Contract, available at XXX (meta.gnu.tools URL).
65
66 • I, maintainer of package X, do not adhere to version 1.0 of the
67 GNU Social Contract, available at XXX.
68
69 4. In the following days, we will publish at XXX the list of GNU
70 package maintainers who endorse as well as those who reject version
71 1.0 of the GNU Social Contract.
72
73One of the next action items we may collectively undertake at the end
74of this process is defining “membership” in the GNU Project. This, in
75turn, will allow us to ask all the project members (including sysadmins,
76web masters, developers) whether they would endorse the GNU Social
77Contract.
78
79Thanks in advance for your participation!
80
81 - Ludovic Courtès
82 - Andreas Enge
83 - Carlos O’Donell
84 - Mark Wielaard
85 - Andy Wingo