Skip to content

PEP 541: Make the Packaging WG the approval authority #566

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 7, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion pep-0541.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
=============

Expand Down