[Python-Dev] PEP 481 - Migrate Some Supporting Repositories to Git and Github

[Antoine Pitrou]

On Sun, 30 Nov 2014 00:15:55 +0000 (UTC)
Alex Gaynor <alex.gaynor at gmail.com> wrote:
> 
> The seconds experience I have is that of Django's migration to git and github.
> For a long time we were on SVN, and we were very resistant to moving to 
> DVCS in
> general, and github in particular. Multiple times I said that I didn't see how
> exporting a patch and uploading it to trac was more difficult than sending a
> pull request. That was very wrong on my part.
> 
> My primary observation is not about new contributors though, it's actually
> about the behavior of core developers. Before we were on github, it was fairly
> rare for core developers to ask for reviews for anything besides *gigantic*
> patches, we'd mostly just commit stuff to trunk. Since the switch to github,
> I've seen that core developers are *far* more likely to ask for reviews of
> their work before merging.

I don't know anything about Django's old SVN setup, but our code review
tool (Rietveld) is actually quite good at that, and IMHO slightly
better than github, since it will only send an e-mail at the final
submission - by contrast, each individual comment you leave on github
fires a separate notification, which can feel like spam.

Our main problem for reviews these days is the lack of core developer
time. For example, Serhiy often asks for reviews (he has many patches
pending), which I personally don't have a lot of time to provide.

Regards

Antoine.