Addeda paragraph about transferring ownership of the PEP.
This commit is contained in:
parent
80093461c0
commit
83614f97e5
22
pep-0001.txt
22
pep-0001.txt
|
@ -333,6 +333,28 @@ Reporting PEP Bugs, or Submitting PEP Updates
|
|||
for details.
|
||||
|
||||
|
||||
Transferring PEP Ownership
|
||||
|
||||
It occasionally becomes necessary to transfer ownership of PEPs to
|
||||
a new champion. In general, we'd like to retain the original
|
||||
author as a co-author of the transferred PEP, but that's really up
|
||||
to the original author. A good reason to transfer ownership is
|
||||
because the original author no longer has the time or interest in
|
||||
updating it or following through with the PEP process, or has
|
||||
fallen off the face of the 'net (i.e. is unreachable or not
|
||||
responding to email). A bad reason to transfer ownership is
|
||||
because you don't agree with the direction of the PEP. We try to
|
||||
build consensus around a PEP, but if that's not possible, you can
|
||||
always submit a competing PEP.
|
||||
|
||||
If you are interested assuming ownership of a PEP, send a message
|
||||
asking to take over, addressed to both the original author and the
|
||||
PEP editor <peps@python.org>. If the original author doesn't
|
||||
respond to email in a timely manner, the PEP editor will make a
|
||||
unilateral decision (it's not like such decisions can be
|
||||
reversed. :).
|
||||
|
||||
|
||||
References and Footnotes
|
||||
|
||||
[1] This historical record is available by the normal CVS commands
|
||||
|
|
Loading…
Reference in New Issue