PEP 541: Make the Packaging WG the approval authority (GH-566)

It isn't appropriate for the PSF to ask a single community
volunteer to accept full responsibility for the PSF's
policy on PyPI name management.

Delegating the task to the Packaging Working Group is more
appropriate, since we're already responsible for handling
the PSF's budget in this area, and there's a lot of overlap
between budget management and risk management.

This updates the BDFL-Delegate to be Mark Mangoba (as
the PSF's IT manager), and changes the delegate's role
for this PEP as being to put the policy forward for a vote
in the working group.

Author: ncoghlan

pep-0541.txt

@@ -3,7 +3,7 @@ Title: Package Index Name Retention
 Version: $Revision$
 Last-Modified: $Date$
 Author: Łukasz Langa <[email protected]>
-BDFL-Delegate: Donald Stufft <[email protected]>
+BDFL-Delegate: Mark Mangoba <[email protected]>
 Discussions-To: distutils-sig <[email protected]>
 Status: Draft
 Type: Process
@@ -36,6 +36,22 @@ This document aims to provide general guidelines for solving the
 most typical cases of such conflicts.
 
 
+Approval Process
+================
+
+As the application of this policy has potential legal ramifications for the
+Python Software Foundation, the approval process used is more formal than that
+used for most PEPs.
+
+Rather than accepting the PEP directly, the assigned BDFL-Delegate will instead
+recommend its acceptance to the PSF's Packaging Working Group. After
+consultation with the PSF's General Counsel, adoption of the policy will then
+be subject to a formal vote within the working group.
+
+This formal approval process will be used for both initial adoption of the
+policy, and for adoption of any future amendments.
+
+
 Specification
 =============