@@ -16,7 +16,8 @@ Typically a core developer will offer you the chance to gain commit privilege.
1616The person making the offer will become your mentor and watch your commits for
1717a while to make sure you understand the development process. If other core
1818developers agree that you should gain commit privileges you are then extended
19- an official offer.
19+ an official offer. How core developers come to that agreement are outlined in
20+ :pep: `13 `.
2021
2122What it Means
2223-------------
@@ -61,7 +62,22 @@ Gaining Commit Privileges
6162-------------------------
6263
6364When you have been extended an official offer to become a Python core
64- developer, there are several things you must do.
65+ developer, there are several things you and the person handling your onboarding
66+ must do.
67+
68+ 1. Find out who is handling your onboarding (your mentor should know who this
69+ is; at worst ask the steering council)
70+ 2. Email the person handling your onboarding
71+ 3. The person onboarding you will ask you for various account details to record
72+ them at https://github.com/python/voters/
73+ 4. They will ask what email address you would like to subscribe to
74+ python-committers with
75+ 5. They will turn on various permissions based on the information you provided
76+ in the previous steps
77+ 6. They will update the devguide to publicly list your team membership at
78+ :ref: `developers `
79+ 7. They will announce your membership to python-committers
80+
6581
6682Mailing Lists
6783'''''''''''''
@@ -71,39 +87,6 @@ python-checkins, and one of new-bugs-announce or python-bugs-list. See
7187:ref: `communication ` for links to these mailing lists.
7288
7389
74- Issue Tracker
75- '''''''''''''
76-
77- If you did not gain the Developer role in the `issue tracker `_ before gaining
78- commit privileges, please say so. The role allows issues to be assigned to you,
79- and it allows you to triage (e.g. close or reassign) issues.
80-
81- A tracker admin should also flip your "is committer" bit in the tracker's
82- account screen. This will add the Python logo next to your name in discussions
83- on the tracker. Note that this is separate from the Developer role.
84-
85- It is expected that on the issue tracker you have a username in the form of
86- "first_name.last_name". If your initial issue tracker username is not of this
87- form, please change it. This is so that it is easier to assign issues to the
88- right person.
89-
90-
91- GitHub
92- ''''''
93-
94- You will be added to the ``Python core team `` on GitHub. This will give you
95- rights to commit to various repositories under the `Python organization `_
96- on GitHub. When you are initially added you will be emailed by GitHub with
97- an invitation to join the team. Please accept the invite in the email or
98- go to https://github.com/python and accept the invite there.
99-
100- An entry in the :ref: `developers ` should also be entered for you.
101- Typically the person who sponsored your application to become a core developer
102- makes sure an entry is created for you.
103-
104- .. _Python organization : https://github.com/python
105-
106-
10790.. _contributor_agreement :
10891
10992Sign a Contributor Agreement
0 commit comments