From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 53464@debbugs.gnu.org
Subject: [bug#53464] [PATCH] doc: Add a rule of thumb to guide enabling new committers.
Date: Mon, 31 Jan 2022 23:46:21 +0100 [thread overview]
Message-ID: <87zgnb8qwy.fsf@gnu.org> (raw)
In-Reply-To: <20220123032547.9635-1-maxim.cournoyer@gmail.com> (Maxim Cournoyer's message of "Sat, 22 Jan 2022 22:25:47 -0500")
Hello!
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> * doc/contributing.texi (Commit Access): Introduce a new rule of thumb to
> determine if a contributor should be considered to become a committer.
> ---
> doc/contributing.texi | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/doc/contributing.texi b/doc/contributing.texi
> index 9f97788c0b..321d496739 100644
> --- a/doc/contributing.texi
> +++ b/doc/contributing.texi
> @@ -1386,9 +1386,14 @@ what your usertag means.
> @cindex commit access, for developers
> Everyone can contribute to Guix without having commit access
> (@pxref{Submitting Patches}). However, for frequent contributors,
> -having write access to the repository can be convenient. Commit access
> -should not be thought of as a ``badge of honor'' but rather as a
> -responsibility a contributor is willing to take to help the project.
> +having write access to the repository can be convenient. As a rule of
> +thumb, a contributor should have accumulated fifty (50) reviewed commits
> +to be considered as a committer and have sustained their activity in the
> +project for at least 6 months. This ensures enough interactions with
That sounds reasonable to me.
Thanks!
Ludo’.
next prev parent reply other threads:[~2022-01-31 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 3:25 [bug#53464] [PATCH] doc: Add a rule of thumb to guide enabling new committers Maxim Cournoyer
2022-01-31 22:46 ` Ludovic Courtès [this message]
2022-02-01 4:44 ` bug#53464: " Maxim Cournoyer
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=87zgnb8qwy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53464@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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).