Issue 16746: clarify what should be sent to peps@ (original) (raw)
Created on 2012-12-21 21:27 by chris.jerdonek, last changed 2022-04-11 14:57 by admin. This issue is now closed.
Messages (4)
Author: Chris Jerdonek (chris.jerdonek) * 
Date: 2012-12-21 21:27
Currently, PEP 1 can be read to mean that <peps@python.org> should be CC'ed on all e-mails related to PEPs. However, this isn't the intent because, for example, it is okay to have discussions about PEPs on python-dev or python-ideas without involving <peps@python.org>.
I'm attaching a patch to clarify this language.
[This issue is from: http://mail.python.org/pipermail/python-dev/2012-December/123251.html ]
Author: R. David Murray (r.david.murray) *
Date: 2012-12-21 22:53
The editors do more than your sentence suggests. They also (sometimes) edit peps, (sometimes) provide advice about preparing one, and commit and update peps when the author(s) do not have commit access.
The distinction in the types of email that PEP 1 is attempting to make is the distinction between public discussions of the PEP (which go to python-dev or python-ideas) and semi-private discussions about the mechanics of preparing and posting and updating PEPs, which should go to all the pep editors (thus the instruction to cc the list).
In other words, if you want non-editors involved in the discussion, post to python-dev or whatnot, and do not CC the PEP editors. All other PEP matters should go to the PEP editors, and not be CCed to any other list.
That's what the original text says, but admittedly you have to parse it like a computer would to understand that :)
Author: Chris Jerdonek (chris.jerdonek) *
Date: 2012-12-22 12:42
This issue was just addressed by Nick's fix for issue 16581, specifically the following parts of http://hg.python.org/peps/rev/24d5623ab21e :
+<peps@python.org> is a mailing list consisting of PEP editors. All +email related to PEP administration (such as requesting a PEP number +or providing an updated version of a PEP for posting) should be sent to +this address (no cross-posting please). + + Submitting a PEP
-The PEP editors assign PEP numbers and change their status. Please send
-all PEP-related email to <peps@python.org> (no cross-posting please).
-Also see PEP Editor Responsibilities & Workflow_ below.
A PEP editor must subscribe to the <peps@python.org> list. All -PEP-related correspondence should be sent (or CC'd) to +correspondence related to PEP administration should be sent (or forwarded) to <peps@python.org> (but please do not cross-post!).
Author: Chris Jerdonek (chris.jerdonek) *
Date: 2012-12-22 12:49
By the way, thanks for the clarifying info, David. Also, I thought I was the one that was going to be accused of reading the original text like a computer. :)
History
Date
User
Action
Args
2022-04-11 14:57:39
admin
set
github: 60950
2012-12-22 12:49:15
chris.jerdonek
set
messages: +
2012-12-22 12:42:55
chris.jerdonek
set
status: open -> closed
nosy: + ncoghlan
messages: +
resolution: fixed
stage: resolved
2012-12-21 22:53:06
r.david.murray
set
priority: low -> normal
nosy: + r.david.murray
messages: +
assignee: brett.cannon ->
stage: patch review -> (no value)
2012-12-21 22:50:31
brett.cannon
set
priority: normal -> low
assignee: brett.cannon
nosy: + brett.cannon
stage: patch review
2012-12-21 21:29:35
chris.jerdonek
set
files: + issue-16746-1.patch
keywords: + patch
2012-12-21 21:27:03
chris.jerdonek
create