Skip to content

Commit

Permalink
PEP 1: Refine phrasing and organization of PEP-delegate description
Browse files Browse the repository at this point in the history
  • Loading branch information
CAM-Gerlach committed Jan 22, 2022
1 parent da9bf5f commit e200328
Showing 1 changed file with 13 additions and 13 deletions.
26 changes: 13 additions & 13 deletions pep-0001.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -282,22 +282,22 @@ 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
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 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
the PEP-Delegate for that PEP, and not declined by the Steering Council,
they 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,
and recorded in the "PEP-Delegate" field in the PEP's header.
For PEPs written prior to the Steering Council 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 "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.

Expand Down

0 comments on commit e200328

Please sign in to comment.