From e2003285df7cfe1f5d32f7d61c7ce37dfcc99163 Mon Sep 17 00:00:00 2001 From: "C.A.M. Gerlach" Date: Thu, 20 Jan 2022 19:40:02 -0600 Subject: [PATCH 1/3] PEP 1: Refine phrasing and organization of PEP-delegate description --- pep-0001.txt | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index b75f0a350cf..6f178f95df9 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -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 @@ -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 `_. +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. From c03489b23483484cf1dd5b2876ca104e4b2222d2 Mon Sep 17 00:00:00 2001 From: "C.A.M. Gerlach" Date: Fri, 21 Jan 2022 01:39:13 -0600 Subject: [PATCH 2/3] PEP 1: Further tweak phrasing of PEP delegate description --- pep-0001.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 6f178f95df9..1ec85fa8f45 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -282,8 +282,8 @@ 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 not declined by the Steering Council, -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 for the PEP's designated decision maker, From 409946e40d7f79b263a080b98365630dae56c842 Mon Sep 17 00:00:00 2001 From: CAM Gerlach Date: Fri, 21 Jan 2022 20:35:30 -0600 Subject: [PATCH 3/3] PEP 1: Incorporate further reviewer suggestions on PEP-Delegate section Co-authored-by: Jelle Zijlstra --- pep-0001.txt | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 1ec85fa8f45..ffdda84092f 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -280,16 +280,14 @@ 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 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 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. +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 `_. Any legacy references to "BDFL-Delegate" should be treated as equivalent to