On 01/10/2016 03:54 AM, Brett Cannon wrote:
I'm developing it at https://github.com/brettcannon/github-transition-pep/blob/master/pep-NNNN.rs... . I'm not posting it here as I'm still actively writing it. The only reason I'm mentioning it now is because the migration plan has been very roughly outlined, so if it looks like I'm missing something, please let me know.
my two cents (on changeset 92afd4a90f56a8caa2cf0620cedc2c20b8c0e0d0):
""" While hg.python.org  hosts many repositories, there are onlyfive key repositories that must move: """ Decide what should happen to the rest of the repos? (or ist under the fait of hg.python.org?) Why is devinabox grey marked, means that something special?
""" Define commands to migrate from Mercurial to Git Converting a Mercurial repository to Git """
Aren't both equivalent (or doesn't you need to define the command to be able to convert the repos?). Or you mean write the script for the migration and then do the migration?
""" Document steps to commit a pull request Handling Misc/NEWS Handling Misc/ACKS ... """ Couldn't be also part of "Requirements for Code-Only Repositories"? Why only Code-Only repos hasn't Misc/NEWS or Miscs/ACKS? (yes, well those are code only per your definition? :-) )
""" Linking pull requests to issues Notify the issue if the pull request is committed """ There can be more than a pull request to one issue (e.g. an alternative patch), should "the not commited ones" be automaticaly rejected (?)
""" Splitting out parts of the documentation into their own repositories """ If those are split, shouldn't exist a mechanism to deploy a consistent release (docs <-> code)?
Bot to deploy a release (tagging, building, ...) or at least the steps need to be documented (or will exist a potentially releaseable branch?).
Decide and document how the python services map into python.org (e.g. git.python.org)