Mailman 3 July 2016 - core-workflow

GitHub reviews comments on b.p.o
by Anish Shah 12 Aug '16

12 Aug '16

Hello everyone, I'm working on GitHub integration as a part of GSoC. One of my tasks was to show GitHub review comments on b.p.o. Here is how I did it :- I wrote a handler to handle GitHub PR review/diff comments event using webhooks. If a b.p.o issue is linked to a PR, then it checks if any "GitHub" comment was added in last "X" minutes. If no GitHub comments were added, then it adds that comment to the linked issue. This way there will be fewer emails and also developers who are in the nosy list but are not subscribed to GitHub PR will get notified about the progress/review comments on PR. You can check the patch here <http://psf.upfronthosting.co.za/roundup/meta/issue592>. I wanted to know from you all if this is the right approach. If not, then what should be changed? Thank you, Anish Shah

6 12

Devguide migrated and next steps
by Brett Cannon 22 Jul '16

22 Jul '16

The devguide is now at https://github.com/python/devguide! Since I'm not waiting on the benchmarks repo while Victor Stinner does some perf measuring work, that means the cpython repo is next <queue dramatic music />. If you look at https://www.python.org/dev/peps/pep-0512/#status you will see the list of issues that have to occur in order to migrate the cpython repo: 1. Update the devguide to document how we want to use git and GitHub ( https://github.com/python/devguide/milestone/1) 2. Link a PR to an issue (see http://psf.upfronthosting.co.za/roundup/meta/issue589) 3. Update an issue when a PR is closed (I believe http://psf.upfronthosting.co.za/roundup/meta/issue590 covers this) 4. Update hg.python.org/lookup to work with git hashes 5. Deprecate sys._mercurial and create sys._git ( http://bugs.python.org/issue27593) 6. Update PEP 101 Obviously help with any and all of this is appreciated and if you feel anything needs discussion then please start a new thread on the topic (and don't simply reply to this email so we can keep discussions separate).

1 0

What would it take to split the stdlib out into its own git repo?
by Brett Cannon 17 Jul '16

17 Jul '16

What would be involved in making the stdlib its own repo, separate from CPython itself? Now I'm not suggesting making sure it fully functions on its own, but more of what would need to happen if we decided that the stdlib should be its own git repo so that any Python implementation -- including CPython -- would include the stdlib as e.g. a git submodule? For instance, would we be able to split the history, or would the original history stay in the CPython repo and we would start from scratch in the stdlib repo and `git log` would hopefully be smart enough to merge the two histories? How bad is it to work in a repo with a submodule where you will be making changes to submodules regularly? And are there benefits? My hope/hunch is that if we make the stdlib its own repo then other implementations could include the stdlib as a submodule or something, making it easier for them to not only keep up-to-date with fixes to the stdlib, but also make it easier for them to push changes upstream that everyone would benefit from instead of having any changes silo-ed off in their own repo. Am I nuts, or is this something reasonable to consider doing as part of the GitHub migration?

8 10

Github Mirrors - Should Disallow Pull Request / Issue Creation Until the migration
by Senthil Kumaran 11 Jul '16

11 Jul '16

I noticed two issues wherein the reporters were confused with the github mirrors of cpython. 1. http://bugs.python.org/issue25435#msg253159 A pull request was raised against the github mirror. 2. http://bugs.python.org/issue27466 Issue was raised against a github mirror: https://github.com/python-git/python/issues/6 This project, https://github.com/python-git should either redirect to github.com/python or shutdown. And the github.com/python project should disallow Pull Request / Issue Creation. Who can I work with (in the python infra team) to accomplish these things? Also if anyone else has suggestions please share it in this email thread. Thank you, Senthil

8 15