Add a note about how PEPs should really be more focussed, and contain

a single core idea.
This commit is contained in:
Barry Warsaw 2002-04-02 03:20:07 +00:00
parent 91e98eae56
commit 6644dcee69
1 changed files with 10 additions and 4 deletions

View File

@ -43,10 +43,16 @@ PEP Work Flow
The PEP editor, Barry Warsaw <barry@zope.com>, assigns numbers
for each PEP and changes its status.
The PEP process begins with a new idea for Python. Each PEP must
have a champion -- someone who writes the PEP using the style and
format described below, shepherds the discussions in the
appropriate forums, and attempts to build community consensus
The PEP process begins with a new idea for Python. It is highly
recommended that a single PEP contain a single key proposal or new
idea. The more focussed the PEP, the more successfully it tends
to be. The PEP editor reserves the right to reject PEP proposals
if they appear to unfocussed or too broad. If in doubt, split
your PEP into several well-focussed ones.
Each PEP must have a champion -- someone who writes the PEP using
the style and format described below, shepherds the discussions in
the appropriate forums, and attempts to build community consensus
around the idea. The PEP champion (a.k.a. Author) should first
attempt to ascertain whether the idea is PEP-able. Small
enhancements or patches often don't need a PEP and can be injected