From b6505ed84694baa99650babe2de507fcf5f4f490 Mon Sep 17 00:00:00 2001 From: Carol Willing Date: Mon, 22 Jun 2020 07:20:41 -0700 Subject: [PATCH 1/5] Update language on PEP-Delegate --- pep-0001.txt | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index af34fdea5e4..fb07c428f77 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -281,14 +281,24 @@ 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. Individuals taking on this responsibility are free to seek +the PEP-Delegate (BDFL-Delegate) for that PEP, and they will then have the +authority to approve (or reject) that PEP. + +The terms, PEP-Delegate (preferred term under the Steering Council governance +model) and BDFL-Delegate, may be used interchangeably in discussion. +The term "PEP-Delegate" will be 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 "BDFL-Delegate" field in the PEP's header. For consistency with +PEPs written prior to the Steering Council's governance model, the field name, +"BDFL-Delegate" will still be kept but the field means "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 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. -The designated decision maker for each PEP is recorded in the "PEP-Delegate" -header in the PEP. - Such self-nominations are accepted by default, but may be explicitly declined by the Steering Council. Possible reasons for the Steering Council declining a self-nomination as PEP-Delegate include, but are not limited to, perceptions of From 96c0efbba4b7cf8681f4b49e50121f9d9f192c88 Mon Sep 17 00:00:00 2001 From: Carol Willing Date: Thu, 20 Jan 2022 07:59:26 -0800 Subject: [PATCH 2/5] Add review feedback from @JelleZijlstra and @AA-Turner --- pep-0001.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index fb07c428f77..523300cb5e8 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -281,17 +281,17 @@ 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 (BDFL-Delegate) for that PEP, and they will then have the +the PEP-Delegate for that PEP, and they will then have the authority to approve (or reject) that PEP. -The terms, PEP-Delegate (preferred term under the Steering Council governance -model) and BDFL-Delegate, may be used interchangeably in discussion. The term "PEP-Delegate" will be 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 "BDFL-Delegate" field in the PEP's header. For consistency with +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 but the field means "PEP-Delegate". +"BDFL-Delegate" will still be kept. +The terms, PEP-Delegate (preferred term under the Steering Council governance +model) and BDFL-Delegate, may be used interchangeably in discussion. Individuals offering to serve as PEP-Delegate should notify the Steering Council, PEP authors and PEP sponsor of their intent to self-nominate. From 1abf29bfb1aca5057c052319e144065f533205ce Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Thu, 20 Jan 2022 13:50:28 -0800 Subject: [PATCH 3/5] Update pep-0001.txt Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> --- pep-0001.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pep-0001.txt b/pep-0001.txt index 523300cb5e8..63043f5fe68 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -288,7 +288,7 @@ The term "PEP-Delegate" will be 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, +PEPs written prior to the Steering Council's governance model, the field name "BDFL-Delegate" will still be kept. The terms, PEP-Delegate (preferred term under the Steering Council governance model) and BDFL-Delegate, may be used interchangeably in discussion. From d2fd3ae511aecb97de2691b3dac723c7ac46b459 Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Thu, 20 Jan 2022 13:51:15 -0800 Subject: [PATCH 4/5] Update pep-0001.txt Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> --- pep-0001.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 63043f5fe68..ed0e03d036c 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -290,8 +290,9 @@ 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 (preferred term under the Steering Council governance -model) and BDFL-Delegate, may be used interchangeably in discussion. +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. Individuals offering to serve as PEP-Delegate should notify the Steering Council, PEP authors and PEP sponsor of their intent to self-nominate. From 92f207d6c77c198d8e245d98a013da0f5e003a09 Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Thu, 20 Jan 2022 13:51:39 -0800 Subject: [PATCH 5/5] Update pep-0001.txt Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com> --- pep-0001.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pep-0001.txt b/pep-0001.txt index ed0e03d036c..b70871c544e 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -284,7 +284,7 @@ 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" will be used under the Steering +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