On Thu, May 27, 2010 at 10:37 AM, Bruce Southey
2010/5/26 Stéfan van der Walt
: On 26 May 2010 16:12, Travis Oliphant
wrote: I changed the subject line for this thread, since I didn't want to hijack another thread. Anyway, I am not proposing that we actually decide whether to move to git and github now, but I am just curious how people would feel. We had a conversation about this a few years ago and it was quite contentious at the time. Since then, I believe a number of us have started using git and github for most of our work. And there are a number of developers using git-svn to develop numpy now. So I was curious to get a feeling for what people would think about it, if we moved to git. (I don't want to rehash the arguments for the move.)
I think we are ready for such a move. Someone should think about the implications, though (with Trac integration, check-in mailings, etc.) and make sure we get something we all like. Somebody probably has thought through all of these things already, though.
Awesome, if there's enough interest I'll help Jarrod out on the NEP. I've been looking at GitHub's Trac integration, and it seems that we should be able to have the same level of integration with the bugtracker as we currently do. Their plugin is available here:
http://github.com/davglass/github-trac/
The SVN-checkout functionality should take care of the build bot. As a bonus, we no longer have to administrate user accounts. Converting the SVN repo to Git should pose no problem.
Regards Stéfan _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
You are all probably aware of this, but I just wanted it said. I do understand the advantage of being able to pull from someone's Python 3 branch (like scipy) as well as some of the more experimental side like the proposed refactoring.
There could (and should) be a github repo on scipy.org. This would be used as the "reference". Something that needs being discussed on is how people will work together - going to "fulltime" git means a change in how to interact compared to git-svn (no more rebase to make changes visible, etc...). I am wondering whether we should follow the pull model - maybe through a gateway, I am not sure: http://www.selenic.com/pipermail/mercurial/2008-July/020116.html
It also provides a common foundation to troubleshoot problems (of course you don't see it because you don't have that branch...). Yet I do understand that any release candidate can be pulled from any tree (as happens with the Linux kernel) and that this should be more of guide than a fixed rule.
The whole point of DVCS is that it is trivial to set up an official repo where the releases are done from, without preventing people to work as they see fit. cheers, David