Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 3e45e17

Browse filesBrowse files
authored
A few minor clarifications about the new developer process (#1539)
1 parent c696ab5 commit 3e45e17
Copy full SHA for 3e45e17

File tree

1 file changed

+5
-3
lines changed
Filter options

1 file changed

+5
-3
lines changed

‎core-developers/become-core-developer.rst

Copy file name to clipboardExpand all lines: core-developers/become-core-developer.rst
+5-3Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,10 +38,12 @@ are granted through these steps:
3838
#. If the candidate receives at least two-thirds positive votes when the poll closes
3939
(as per :pep:`13`), the submitter `emails the steering council
4040
<mailto:steering-council@python.org>`_ with the candidate's email address
41-
requesting that the council either accept or reject the proposed membership.
41+
requesting that the council either accept or reject the proposed membership. Technically, the
42+
council may only `veto a positive vote <https://peps.python.org/pep-0013/#membership>`_.
4243

43-
#. Assuming the steering council does not object, a member of the council or delegate
44-
(approver) will email the candidate:
44+
#. Assuming the steering council does not veto the positive vote, a member of the council or its
45+
delegate (approver, usually in practice a :ref:`Developer-in-Residence <current owners>`) will
46+
email the candidate:
4547

4648
- A request for account details as required by
4749
`🔒 python/voters <https://github.com/python/voters>`_.

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.