Sure, I can drop a note. As for python-dev not being involved, that was somewhat on purpose. I said at the beginning of this process, the switch is geared towards making things easier for core developers while not making things worse for external contributors, and so I focused on python-committers as the most affected group (bringing the whole community in would have just made the process too draining for me). And with Ezio and others planning to put the work in to make sure that non-GitHub contributions are still serviceable I think that goal has been met. On Sun, 10 Jan 2016 at 01:56 Victor Stinner wrote:

Hi,

It looks like there no email to python-dev. Can you please sometimes communicate status on python-dev (and maybe other python mailing list) to keep people aware of what is happening?

For example, I don't think that python-dev was involved in the final choice of github.

Victor

Le dimanche 10 janvier 2016, Brett Cannon a écrit :

...

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.

On Mon, 11 Jan 2016 at 12:42 francismb wrote:

Hi,

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 [1] 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?)

Part of what happens to hg.python.org since they are all personal repos.

Why is devinabox grey marked, means that something special?

Just that the repo name matches the project name.

""" 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?

Accidental duplication.

""" 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? :-) )

Only the cpython repos have an ACKS and NEWS file and all the other repos can just use the merge button in a GitHub PR (that will be pointed out in the cpython section).

""" 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 committed ones" be automatically rejected (?)

No, because sometimes an issue involves multiple patches legitimately.

""" 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)?

People are talking about things like the HOWTOs, tutorial, etc. And they can be made to be subrepos of the cpython repo if we want.

Bot to deploy a release (tagging, building, ...) or at least the steps need to be documented (or will exist a potentially releaseable branch?).

There's too much specifically for a bot to do, plus the release process is documented in another PEP.

Decide and document how the python services map into python.org (e.g. git.python.org)

Added a section on creating git.python.org. -Brett

Regards, francis

_______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct

Hi! On Tue, Jan 12, 2016 at 12:25:06AM +0000, Brett Cannon wrote:

PEP is still not done, but I have at least fleshed out the parts required to migrate the code-only and web-related repositories: https://github.com/brettcannon/github-transition-pep/blob/master/pep-NNNN.rs... .

Continuous integration per pull request XXX https://travis-ci.org/ https://codeship.com/ https://circleci.com/

No buildbot?

Tools and commands to move from Mercurial to Git A decision needs to be made on exactly what tooling and what commands involving those tools will be used to convert a Mercurial repository to Git. Currently a suggestion has been made to use https://github.com/frej/fast-export.

My personal experience with fast-export was a bit negative when I tried to convert a repository for a complex project with a number of branches and a lot of tags. I switched to git-remote-hg [1] and found it much better for my needs. See Comparison [2]. 1. https://github.com/felipec/git-remote-hg 2. https://github.com/felipec/git/wiki/Comparison-of-git-remote-hg-alternatives Oleg. -- Oleg Broytman http://phdru.name/ phd@phdru.name Programmers don't die, they just GOSUB without RETURN.