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

[Nick Coghlan]

New submission from Nick Coghlan <ncoghlan at gmail.com>:

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, miss-islington, the knights-who-say-ni, etc). It also uses a workflow different from that of the main python.org website, as well as that of PyPI.

Accordingly, I'd like to propose that we start migrating the tracker's development processes to a new "python/bugs.python.org" repo on Github via the following process:

1. Create the project repo immediately, and start using its issue tracker for new issues in preference to the current metatracker. (I'd migrate this issue over there, and turn these bullet points into a task list)
2. Prepare to migrate the Mercurial repo to GitHub, using the CPython repo migration PEP as a guide
3. Actually migrate the source repo
4. Update the links in the b.p.o service accordingly

In parallel with 2-4, the fate of the meta-tracker could be determined (either bulk closing all issues, and requesting they be reopened in GitHub if they're still relevant, or else figuring out a way to migrate them automatically)

(I know I'm glossing over a lot of steps there, but I'd elaborate on them more in a GitHub task list assuming the idea is accepted by the current maintainers as acceptable-in-principle)

----------
messages: 3505
nosy: ncoghlan
priority: wish
status: unread
title: Migrate to the "python" org on GitHub?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue655>
_______________________________________________________