From acffe50fdffa3fcbf6fc2514b1a38d4e8b27c12e Mon Sep 17 00:00:00 2001 From: Pradyun Gedam Date: Thu, 25 Jun 2020 00:25:31 +0000 Subject: [PATCH] PEP 609: Clarify expectations around PEP sponsors (#1425) --- pep-0609.rst | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/pep-0609.rst b/pep-0609.rst index 4a75757a1..6290d8785 100644 --- a/pep-0609.rst +++ b/pep-0609.rst @@ -172,10 +172,11 @@ Python Steering Council has the final say in the acceptance of these interoperability specifications. It is expected (but not required) that the Python Steering Council -delegates the authority to approve or reject PEPs to individuals -within the PyPA community. At the time of writing (November 2019), the -Python Steering Council has `standing delegations`_ for currently -active packaging interoperability specifications. +would delegate authority to sponsor and/or approve/reject PEPs related +to packaging interoperability specifications, to individuals within the +PyPA community. At the time of writing (June 2020), the Python Steering +Council has `standing delegations`_ for currently active packaging +interoperability specifications. The details of the process of proposing and updating the interoperability specifications are described in the `PyPA