iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 1: Further refine phrasing and organization of PEP-Delegate description (#2257) 

* PEP 1: Refine phrasing and organization of PEP-delegate description

* PEP 1: Further tweak phrasing of PEP delegate description

* PEP 1: Incorporate further reviewer suggestions on PEP-Delegate section

Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>

Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
This commit is contained in:
CAM Gerlach 2022-01-21 23:41:51 -06:00 committed by GitHub
parent da9bf5f9a1
commit a79ef202bc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
pep-0001.txt
View File

@ -271,7 +271,7 @@ PEP Review & Resolution
Once the authors have completed a PEP, they may request a review for
style and consistency from the PEP editors.
However, content review and final acceptance of the PEP must be requested of the
However, content review of the PEP must be requested of the
core developers, usually via an email to the python-dev mailing list.
To expedite the process in selected cases (e.g. when a change is clearly
@ -280,24 +280,22 @@ for review yet), the Steering Council may also initiate a PEP review, first
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 that believes they are suitably
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 that PEP, and they will then have the
authority to approve (or reject) that PEP.
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.
The term "PEP-Delegate" is used under the Steering
Council governance model. The PEP's designated decision maker,
the "PEP-Delegate" with the Steering Council's support, is
recorded in the "PEP-Delegate" field in the PEP's header. For
PEPs written prior to the Steering Council's governance model, the field name
"BDFL-Delegate" will still be kept.
The terms PEP-Delegate and BDFL-Delegate may be used interchangeably in
discussion. PEP-Delegate is the preferred term under the Steering Council
governance model.
The term "PEP-Delegate" is used under the Steering Council governance model
for the PEP's designated decision maker,
who is recorded in the "PEP-Delegate" field in the PEP's header.
The term "BDFL-Delegate" is a deprecated alias for PEP-Delegate, a legacy of
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.
Individuals taking on this responsibility are free to seek
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.