From: "Ludovic Courtès" <ludo@gnu.org>
To: 38846@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>, guix-maintainers@gnu.org
Subject: [bug#38846] [PATCH 4/4] DRAFT doc: Add a cooption policy for commit access.
Date: Wed, 1 Jan 2020 17:34:46 +0100 [thread overview]
Message-ID: <20200101163446.5132-4-ludo@gnu.org> (raw)
In-Reply-To: <20200101163446.5132-1-ludo@gnu.org>
DRAFT: Subject to discussion!
* doc/contributing.texi (Commit Access): Draft a cooptation policy.
---
doc/contributing.texi | 48 +++++++++++++++++++++++++++++++++++++++++--
1 file changed, 46 insertions(+), 2 deletions(-)
diff --git a/doc/contributing.texi b/doc/contributing.texi
index 74b4718eb3..6e2cc1a369 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1099,8 +1099,52 @@ this nifty tool!
@cindex commit access, for developers
For frequent contributors, having write access to the repository is
-convenient. When you deem it necessary, feel free to ask for it on the
-mailing list. When you get commit access, please make sure to follow
+convenient. When you deem it necessary, consider applying for commit
+access by following these steps:
+
+@enumerate
+@item
+Find three committers who would vouch for you, emailing a signed
+statement to @email{guix-maintainers@@gnu.org} (a private alias for the
+collective of maintainers). You can view the list of committers at
+@url{https://savannah.gnu.org/project/memberlist.php?group=guix}.
+
+Committers are expected to have had some interactions with you as a
+contributor and to be able to judge whether you are sufficiently
+familiar with the project's practices. It is @emph{not} a judgment on
+the quality of your work, so a refusal should rather be interpreted as
+``let's try again later''.
+
+@item
+Send @email{guix-maintainers@@gnu.org} a signed message stating your
+intent, listing the three committers who support your application, and
+giving the fingerprint of the OpenPGP key you will use to sign commits
+(see below).
+
+@item
+Once you've been given access, please send a message to
+@email{guix-devel@@gnu.org} to say so, again signed with the OpenPGP key
+you will use to sign commits. That way, everyone can notice and ensure
+you control that OpenPGP key.
+
+@c TODO: Add note about adding the fingerprint to the list of authorized
+@c keys once that has stabilized.
+
+@item
+Make sure to read the rest of this section and... profit!
+@end enumerate
+
+@quotation Note
+Maintainers are happy to give commit access to people who have been
+contributing for some time and have a track record---don't be shy and
+don't underestimate your work!
+
+However, note that the project is working towards a more automated patch
+review and merging system, which, as a consequence, may lead us to have
+fewer people with commit access to the main repository. Stay tuned!
+@end quotation
+
+When you get commit access, please make sure to follow
the policy below (discussions of the policy can take place on
@email{guix-devel@@gnu.org}).
--
2.24.1
next prev parent reply other threads:[~2020-01-01 16:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-01 16:29 [bug#38846] [PATCH 0/4] Move 'HACKING' to the manual, and a proposal for commit access Ludovic Courtès
2020-01-01 16:34 ` [bug#38846] [PATCH 1/4] doc: Add "Tracking Bugs and Patches" section Ludovic Courtès
2020-01-01 16:34 ` [bug#38846] [PATCH 2/4] doc: Move "Commit Access" section from 'HACKING' to the manual Ludovic Courtès
2020-01-01 18:08 ` Ricardo Wurmus
2020-01-01 16:34 ` [bug#38846] [PATCH 3/4] doc: Encourage patch review Ludovic Courtès
2020-01-01 18:09 ` Ricardo Wurmus
2020-01-01 16:34 ` Ludovic Courtès [this message]
2020-01-01 18:15 ` [bug#38846] [PATCH 4/4] DRAFT doc: Add a cooption policy for commit access Ricardo Wurmus
2020-01-02 11:20 ` Ludovic Courtès
2020-01-07 22:36 ` Maxim Cournoyer
2020-01-01 18:51 ` zimoun
2020-01-02 11:53 ` Ludovic Courtès
2020-01-02 18:35 ` zimoun
2020-01-06 9:30 ` Ludovic Courtès
2020-01-02 4:09 ` Brett Gilio
2020-01-02 11:15 ` Ricardo Wurmus
2020-01-02 11:59 ` Ludovic Courtès
2020-01-06 23:29 ` Tobias Geerinckx-Rice via Guix-patches via
2020-01-06 23:34 ` Tobias Geerinckx-Rice via Guix-patches via
2020-01-07 0:19 ` Brett Gilio
2020-01-07 11:27 ` zimoun
2020-01-09 22:39 ` bug#38846: " Ludovic Courtès
2020-01-01 18:07 ` [bug#38846] [PATCH 1/4] doc: Add "Tracking Bugs and Patches" section Ricardo Wurmus
2020-01-01 18:18 ` zimoun
2020-01-02 11:51 ` Ludovic Courtès
2020-01-02 18:40 ` zimoun
2020-01-01 18:37 ` [bug#38846] [PATCH 0/4] Move 'HACKING' to the manual, and a proposal for commit access Ricardo Wurmus
2020-01-06 13:13 ` Ludovic Courtès
2020-01-07 22:50 ` Marius Bakke
2020-01-06 21:44 ` zimoun
2020-01-07 11:17 ` Ludovic Courtès
2020-01-09 22:05 ` Ludovic Courtès
2020-01-10 15:49 ` zimoun
2020-01-13 10:01 ` Ludovic Courtès
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200101163446.5132-4-ludo@gnu.org \
--to=ludo@gnu.org \
--cc=38846@debbugs.gnu.org \
--cc=guix-maintainers@gnu.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://git.savannah.gnu.org/cgit/guix.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).