emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#53464: closed ([PATCH] doc: Add a rule of thumb to guide enabling ne


From: GNU bug Tracking System
Subject: bug#53464: closed ([PATCH] doc: Add a rule of thumb to guide enabling new committers.)
Date: Tue, 01 Feb 2022 04:45:02 +0000

Your message dated Mon, 31 Jan 2022 23:44:23 -0500
with message-id <878ruvfb6g.fsf@gmail.com>
and subject line Re: bug#53464: [PATCH] doc: Add a rule of thumb to guide 
enabling new committers.
has caused the debbugs.gnu.org bug report #53464,
regarding [PATCH] doc: Add a rule of thumb to guide enabling new committers.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53464: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53464
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH] doc: Add a rule of thumb to guide enabling new committers. Date: Sat, 22 Jan 2022 22:25:47 -0500
* 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
+the contributor, which is essential for mentoring and assessing whether
+they are ready to become a committer.  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.
 
 The following sections explain how to get commit access, how to be ready
 to push commits, and the policies and community expectations for commits
-- 
2.34.0




--- End Message ---
--- Begin Message --- Subject: Re: bug#53464: [PATCH] doc: Add a rule of thumb to guide enabling new committers. Date: Mon, 31 Jan 2022 23:44:23 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Hi!

Ludovic Courtès <ludo@gnu.org> writes:

> 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.

Pushed as c1043fd60d273c61c80ecfd31fa3a4ea1b24639a.

Thank you for having a look!

Maxim


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]