Home Original page

[Python-Dev] PEP process entry point and ill fated initiatives

Kristján Valur Jónsson kristjan at ccpgames.com
Fri Nov 29 10:16:38 CET 2013 
Reading the defect, I find people being unnecessarily obstructive.
Closing the ticket, twice, is a rude, and unnecessary action.  How about acknowledging that these waters are dark and murky and help making things better?
Surely, documenting processes can only be an improvement?
A lot has changed in open source development in the last 10 years.  The processes we have are starting to have the air of cathedral around them.

K

From: Python-Dev [mailto:python-dev-bounces+kristjan=ccpgames.com at python.org] On Behalf Of Guido van Rossum
Sent: 28. nóvember 2013 18:40
To: anatoly techtonik
Cc: python-dev
Subject: Re: [Python-Dev] PEP process entry point and ill fated initiatives

Anatoly, the Python community is a lot more diverse than you think. "Pull requests" (whatever that means) are not the way to start a PEP. You should start by focusing on the contents, and the mechanics of editing it and getting it formatted properly are secondary. The process is explained in PEP one. Your bug report would have gotten a much better response if you had simply asked "what is the process, I can't figure it out from the repo's README" rather that (again) complaining that the core developers don't care. Offending people is not the way to get them to help you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20131129/04591ac8/attachment.html>
More information about the Python-Dev mailing list