> On Nov 23, 2014, at 12:59 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > > On 23 November 2014 at 15:19, Guido van Rossum <gu...@python.org> wrote: >> This thread seems to beg for a decision. I think Donald Stufft has it >> exactly right: we should move to GitHub, because it is the easiest to use >> and most contributors already know it (or are eager to learn thee). >> Honestly, the time for core devs (or some other elite corps of dedicated >> volunteers) to sysadmin their own machines (virtual or not) is over. We've >> never been particularly good at this, and I don't see us getting better or >> more efficient. > > The learning curve on git is still awful - it offers no compelling > advantages over hg, and GitHub doesn't offer any huge benefits over > BitBucket for Sphinx based documentation (ReadTheDocs works just as > well with either service).
It does have one very big compelling advantage. It’s way more popular. Besides, the learning curve on hg isn’t any better, it’s just differently hard. > >> Moving the CPython code and docs is not a priority, but everything else >> (PEPs, HOWTOs etc.) can be moved easily and I am in favor of moving to >> GitHub. For PEPs I've noticed that for most PEPs these days (unless the >> primary author is a core dev) the author sets up a git repo first anyway, >> and the friction of moving between such repos and the "official" repo is a >> pain. > > Note that if folks prefer Git, BitBucket supports both. I would object > strongly to unilaterally forcing existing contributors to switch from > Mercurial to git. Going to all the trouble to move to an external repository and choosing the least popular option out of the two main ones seems like a bad idea in general. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com