On 23 November 2014 at 15:19, Guido van Rossum <guido at 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). > 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. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4