Revise guidelines for discussion of PEP before draft exists. The goal
is to limit needless and uninformed discussion of an issue, not to prevent all discussion.
This commit is contained in:
parent
cddd347814
commit
5b4565c9b8
|
@ -61,10 +61,10 @@ PEP Workflow
|
|||
Dictator for Life, Guido van Rossum <guido@beopen.com>) is the
|
||||
final arbitrator of the latter.
|
||||
|
||||
Discussion concerning a PEP should initially be kept out of the
|
||||
python-dev and python-list mailing lists. Instead, comments
|
||||
should be sent to, and collected by, the PEP owner, who has the
|
||||
responsibility to incorporate these comments into the document.
|
||||
In general, an initial draft of the PEP should be prepared before
|
||||
discussion occurs on the python-dev and pyton-list mailing lists.
|
||||
The author should incorporate comments and feedback into this
|
||||
initial draft when possible.
|
||||
|
||||
The authors of the PEP are then responsible for writing the PEP
|
||||
and marshaling community support for it. The structure of a PEP
|
||||
|
|
Loading…
Reference in New Issue