Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PEP 1: Further clarify PEP-Delegate notification & acceptance process #2273

Merged
merged 2 commits into from
Feb 1, 2022
Merged

PEP 1: Further clarify PEP-Delegate notification & acceptance process #2273

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a187598
PEP 1: Further clarify PEP-Delegate notification & acceptance process
CAM-Gerlach Jan 25, 2022
318a336
PEP 1: Apply suggestions on PEP-Delegate acceptance language
CAM-Gerlach Jan 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 13 additions & 7 deletions pep-0001.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -281,9 +281,10 @@ notifying the PEP author(s) and giving them a chance to make revisions.

The final authority for PEP approval is the Steering Council. However, whenever
a new PEP is put forward, any core developer who believes they are suitably
experienced to make the final decision on that PEP may offer to serve as
the PEP-Delegate for it. If the Steering Council assents to their offer, the
PEP-Delegate will then have the authority to approve or reject that PEP.
experienced to make the final decision on that PEP may offer to serve as its
PEP-Delegate by `notifying the Steering Council <Steering Council issue_>`_
of their intent. If the Steering Council approves their offer,
the PEP-Delegate will then have the authority to approve or reject that PEP.

The term "PEP-Delegate" is used under the Steering Council governance model
for the PEP's designated decision maker,
Expand All @@ -293,14 +294,17 @@ the time when when Python was led by `a BDFL <Python's BDFL_>`_.
Any legacy references to "BDFL-Delegate" should be treated as equivalent to
"PEP-Delegate".

Individuals offering to serve as PEP-Delegate should notify the Steering
Council, PEP authors and PEP sponsor of their intent to self-nominate.
An individual offering to nominate themselves as a PEP-Delegate must notify
the relevant authors and (when present) the sponsor for the PEP, and submit
their request to the Steering Council
(which can be done via a `new issue <Steering Council issue_>`_ ).
AA-Turner marked this conversation as resolved.
Show resolved Hide resolved
Those taking on this responsibility are free to seek
additional guidance from the Steering Council at any time, and are also expected
to take the advice and perspectives of other core developers into account.

Such self-nominations are accepted by default, but may be explicitly declined by
the Steering Council. Possible reasons for the Steering Council declining a
The Steering Council will generally approve such self-nominations by default,
but may choose to decline them.
Possible reasons for the Steering Council declining a
self-nomination as PEP-Delegate include, but are not limited to, perceptions of
a potential conflict of interest (e.g. working for the same organisation as the
PEP submitter), or simply considering another potential PEP-Delegate to be
Expand Down Expand Up @@ -805,6 +809,8 @@ References and Footnotes

.. _`GitHub issue`: https://github.com/python/peps/issues

.. _Steering Council issue: https://github.com/python/steering-council/issues/new/choose
CAM-Gerlach marked this conversation as resolved.
Show resolved Hide resolved


Copyright
=========
Expand Down