[Python-Dev] Move selected documentation repos to PSF BitBucket account?

[Demian Brecht]

On Tue, Nov 25, 2014 at 6:52 AM, Brett Cannon <brett at python.org> wrote:
>
> I suspect if we make sure we add Bitbucket and GitHub login support to the issue tracker then that would help go a fair distance to helping with the GitHub pull of reach (and if we make it so people can simply paste in their fork's URL into the issue tracker and we simply grab a new patch for review that would go even farther).

Chiming in horribly late, so hopefully this hasn't already been
mentioned (I've only loosely been following this thread).

In addition to the login support (I'm not sold on how much that would
help the reach), I think it would be really beneficial to have some
documentation on either emulating git-style workflow in hg or
detailing a git fork workflow while working on multiple patches
concurrently and keeping master in sync with hg default (or perhaps
even both).

I primarily use git for development. Having little or no effort to
context switch to work on CPython in any capacity (PEPs, code, etc)
would be hugely beneficial for me. Having a well defined workflow in
the docs (perhaps alongside "Lifecycle of a patch"?) would have
significantly lowered the initial barrier of entry for me. Given the
amount of time I put into that initially, I can only imagine how many
people it's entirely turned away from contributing. I'd definitely be
interested in contributing documentation around this (I've written up
something similar here
http://demianbrecht.github.io/vcs/2014/07/31/from-git-to-hg/) if
others feel that it would be valuable.

IMHO, you don't want to limit submissions due to the tech stack (one
of the arguments I've seen for not moving to Github was quality of
submissions). This will also limit high quality work from those who
simply don't have time to adopt new tech and workflows when they're
not being paid to do so. I have no strong opinion of where and how the
official repos are stored so long as I can work on them and contribute
to them in the way that's most efficient for me. I imagine that
statement would also hold true for most.