Refine 'gaining commit privileges'. (#969)

* Refine 'gaining commit privileges'.

- Allow the audience to be anybody (not just an individual seeking commit privileges). Avoids use of second-person language.
- Provide guidance for all involved.
- Refer to the various actors directly, avoiding passive language. Use 'candidate', 'submitter', and 'approver' to represent the key actors.
- Move the "cross-post" action into step 1 to indicate better the temporal positition of the action.
- Summarize the confirmation criterion (2/3 vote) rather than make the reader go to the PEP, which basically indicates 2/3 vote.
- Include the steering council email, because the submitter may not know it.
- Normalize the initial approver actions. Previously, council was directed to be "asking for ... a reminder about the Code of Conduct and to report issues to the PSF WG". Now it's two requests and a reminder.
- Hyperlink "python/voters" instead of the full URL.

* Combine steps

Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>

* Consolidate steps 5-8 into one.

Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>

* Update number.

Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>

* Link python-committers mailing list.

Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>

* Remove unnecessary hostname.

Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>

* Move cross-post instruction to step 1.

* Auto number

* Fix syntax.

* Apply suggestions from code review

Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>

Co-authored-by: Ezio Melotti <ezio.melotti@gmail.com>
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>

Author: 4 people

core-developers/become-core-developer.rst

@@ -25,37 +25,39 @@ an official offer. How core developers come to that agreement are outlined in
 Gaining Commit Privileges
 =========================
 
-The steps to gaining commit privileges are:
+After a candidate has demonstrated consistent contributions, commit privileges
+are granted through these steps:
 
-1. A core developer starts a poll in the
-   `Committers category`_ on the `Python Discourse`_ (``discuss.python.org``)
+#. A core developer (submitter, usually the mentor) starts a poll in the
+   `Committers category`_ on the `Python Discourse`_ and cross-posts it to
+   the `python-committers mailing list`_.
 
    - Open for 7 days
    - Results shown upon close
 
-2. The poll is announced on the `python-committers mailing list`_
-3. Wait for the poll to close and see if the results confirm your membership
-   as per the voting results required by :pep:`13`
-4. The person who nominated you emails the steering council with your email
-   address and a request that the council either accept or reject the proposed
-   membership
-5. Assuming the steering council does not object, a member of the council will
-   email you asking for:
-
-   - Account details as required by
-     🔒 https://github.com/python/voters/
-   - Your preferred email address to
-     subscribe to the python-committers mailing list with
-   - A reminder about the `Code of Conduct`_ and to report issues to the PSF
-     Conduct WG
-
-6. Once you have provided the pertinent details, your various new privileges
-   will be turned on
-7. Your details will be added to 🔒 https://github.com/python/voters/
-8. They will update the devguide to publicly list your team membership at
-   :ref:`developers`
-9. An announcement email by the steering council member handling your new
-   membership will be sent to the Committers Discourse category
+#. If the candidate receives at least two-thirds positive votes when the poll closes
+   (as per :pep:`13`), the submitter `emails the steering council
+   <mailto:steering-council@python.org>`_ with the candidate's email address
+   requesting that the council either accept or reject the proposed membership.
+
+#. Assuming the steering council does not object, a member of the council or delegate
+   (approver) will email the candidate:
+
+   - A request for account details as required by
+     `🔒 python/voters <https://github.com/python/voters>`_
+   - A request for the committer's preferred address for subscription to
+     the `python-committers mailing list`_
+   - A reminder about the `Code of Conduct`_ and guidance on reporting issues
+     to the PSF Conduct WG
+
+#. Once the candidate has provided the pertinent details, the approver will:
+
+   - enable the various new privileges;
+   - add the new committer's details to
+     `🔒 python/voters <https://github.com/python/voters>`_;
+   - update the devguide to publicly list the new committer's team membership
+     at :ref:`developers`;
+   - send an announcement email to the Committers Discourse category.
 
 .. _Code of Conduct: https://www.python.org/psf/conduct/
 .. _Committers category: https://discuss.python.org/c/committers/5