[Tracker-discuss] [issue655] Migrate to the "python" org on GitHub?

2018-06-15 Thread Eric Snow
Eric Snow added the comment: related: issue635 -- nosy: +eric.snow ___ PSF Meta Tracker ___

[Tracker-discuss] [issue655] Migrate to the "python" org on GitHub?

2018-06-15 Thread Nick Coghlan
Nick Coghlan added the comment: Issue-tracker-only repos technically aren't sourceless, but the trick is that the only file you create is a README, and perhaps some issue templates: https://github.com/python/bugs.python.org Alternatively, they can also be good places to host the source code

[Tracker-discuss] [issue655] Migrate to the "python" org on GitHub?

2018-06-15 Thread Ezio Melotti
Ezio Melotti added the comment: Keep in mind that converting the repo to Git will make it more difficult to upgrade, since our roundup is a clone of the main Roundup repo. So, assuming this issue moves forward, we can either: * start using official Roundup releases (this means no changes to Ro

[Tracker-discuss] [issue655] Migrate to the "python" org on GitHub?

2018-06-15 Thread Nick Coghlan
New submission from Nick Coghlan : Hi folks, bugs.python.org is currently a key piece of CPython workflow automation, but it's relatively difficult to contribute to as it uses a different workflow from both CPython itself *and* the rest of the core workflow projects (cherry picker, blurb, mi