[Python-checkins] python/nondist/peps pep-0001.txt,1.34,1.35

bwarsaw@users.sourceforge.net bwarsaw@users.sourceforge.net
Fri, 12 Jul 2002 09:39:51 -0700


Update of /cvsroot/python/python/nondist/peps
In directory usw-pr-cvs1:/tmp/cvs-serv32562

Modified Files:
	pep-0001.txt 
Log Message:
Addeda paragraph about transferring ownership of the PEP.


Index: pep-0001.txt
===================================================================
RCS file: /cvsroot/python/python/nondist/peps/pep-0001.txt,v
retrieving revision 1.34
retrieving revision 1.35
diff -C2 -d -r1.34 -r1.35
*** pep-0001.txt	28 May 2002 15:20:17 -0000	1.34
--- pep-0001.txt	12 Jul 2002 16:39:49 -0000	1.35
***************
*** 334,337 ****
--- 334,359 ----
  
  
+ 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