diff --git a/pep-0001.txt b/pep-0001.txt --- a/pep-0001.txt +++ b/pep-0001.txt @@ -73,8 +73,8 @@ Submitting a PEP ---------------- -The PEP editors assign PEP numbers and change their status. Please send -all PEP-related email to (no cross-posting please). +The PEP editors assign PEP numbers and change their status. To email the +editors, send email to (but no cross-posting please). Also see `PEP Editor Responsibilities & Workflow`_ below. The PEP process begins with a new idea for Python. It is highly @@ -152,7 +152,7 @@ PEP authors are responsible for collecting community feedback on a PEP before submitting it for review. However, wherever possible, long open-ended discussions on public mailing lists should be avoided. -Strategies to keep the discussions efficient include: setting up a +Strategies to keep the discussions efficient include: setting up a separate SIG mailing list for the topic, having the PEP author accept private comments in the early design phases, setting up a wiki page, etc. PEP authors should use their discretion here. @@ -462,9 +462,9 @@ PEP Editor Responsibilities & Workflow ====================================== -A PEP editor must subscribe to the list. All -PEP-related correspondence should be sent (or CC'd) to - (but please do not cross-post!). +A PEP editor must subscribe to the list. All correspondence +intended for the editors should be sent (or CC'd) to (but +please do not cross-post!). For each new PEP that comes in an editor does the following: @@ -502,7 +502,7 @@ will not be updated to reflect the PEP changes. * Commit and push the new (or updated) PEP - + * Monitor python.org to make sure the PEP gets added to the site properly.