Python's PEPs now officially live at https://github.com/python/peps .
Thanks to Donald Stufft for the infrastructure stuff, Kushal Das for
pushing me at the PyCon US sprints to get this going, Senthil Kumaran for
the migration tool, and everyone else who has helped somehow in making this
I'll be updating PEP 512 -- on GitHub! -- to reflect this. That will make
the devguide the next repo to migrate.
This mail is about my progress so far in integrating GitHub and few
doubts/questions about how to do stuff.
*Show GitHub Pull Request comments on b.p.o*.  - Issue and review
comments will be added to the linked b.p.o issue. Only one comment will be
posted over 30 minutes.
*Converting patches to pull requests *- First, let me tell you all my
approach and questions that I have. Please let me know if you have better
ways to do this.
We need to have a git binary on b.p.o server and when a patch is uploaded,
we run a series of git commands from roundup to apply the patch, commit
using contributor's credentials, push the new branch and finally create a
new pull request using GitHub API.
1. How should we inform the contributor about the newly created PR? (S)he
won't get subscribed to it automatically as the PR is created using API.
2. What should we do an issue affects multiple versions? Should we open
multiple pull requests against each branch?
3. There can be different patches for 2.7 and 3.x versions. Currently,
there's no way of determining which patch is for which branch. So, it would
be difficult to create a new pull request.
Looking forward to what you guys think.