doc: Add a rule of thumb to guide enabling new committers.base-for-series-11226base-for-series-11225base-for-series-11224base-for-series-11223base-for-series-11221base-for-series-11219base-for-series-11218base-for-series-11217base-for-series-11216base-for-series-11215base-for-series-11214base-for-series-11213base-for-series-11212base-for-series-11211base-for-series-11210base-for-series-11209base-for-series-11208base-for-series-11206base-for-series-11205

* doc/contributing.texi (Commit Access): Introduce a new rule of thumb to
determine if a contributor should be considered to become a committer.

1 files changed, 8 insertions, 3 deletions

diff --git a/doc/contributing.texi b/doc/contributing.texi
index 196ac48879..c3d41e231f 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1416,9 +1416,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