From a3eede85c3a518a7f900b94b522eea8cf5fa32ea Mon Sep 17 00:00:00 2001 From: Carol Willing Date: Mon, 22 Jun 2020 07:20:41 -0700 Subject: [PATCH] Update language on PEP-Delegate --- pep-0001.txt | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/pep-0001.txt b/pep-0001.txt index 7238b7caab0..4fe6e6a328f 100644 --- a/pep-0001.txt +++ b/pep-0001.txt @@ -275,12 +275,17 @@ 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 BDFL-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 +(or reject) that PEP. Under the Steering Council governance, the terms, +PEP-Delegate (preferred) and BDFL-Delegate, may be used 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. +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 "BDFL-Delegate" -header in the PEP. +header in the PEP. The term "PEP-Delegate" will be used under the Steering +Council governance model. Such self-nominations are accepted by default, but may be explicitly declined by the Steering Council. Possible reasons for the Steering Council declining a