+1 for git. We use it for the rest of our project—would be nice to not have to use two different systems.
Mark From: [email protected] [mailto:[email protected]] On Behalf Of Denis Meyer Sent: Wednesday, March 28, 2012 11:15 AM To: Opencast Matterhorn Subject: Re: [Opencast Matterhorn] git again +1 svn is obsolete and not a good version control tool for so many contributors. I pointed out the many advantages of git already. And right now you all see how "good" svn is at branching/merging back/whatever (just have a look at the broken trunk). I don't want to say "I said it" but... I said it. Denis On Tuesday, 27. March 2012 at 4:55 PM, Christoph Drießen wrote: The question whether the Opencast project should move to git has already been brought to list several times and has each time been rejected due to good reasons. But with all this GSoC discussion going on and having seen multiple people on list who are willing to contribute I find that it's time to bring it up again. I do not want to write about the differences and -- in my opinion -- advantages of using git over svn once more. This can be read in my predecessors posts on the subject and elsewhere. I just would like to emphasize that one point that makes git so outstanding for me. I see more people wanting to work on Matterhorn but do not have commit rights -- and probably won't ever get. But with git this doesn't really matter. It's an easy go: clone, branch, fetch, work. And if your work results in something that should be contributed back, just ask someone to fetch from you. This process of working is inherent to git. Sure, one can achieve something similar using the git svn bridge like we do at Entwine. But this always feels a bit like a hack, not that natural. And then there is this psychological effect you have with a git based project, which invites people to join be just saying: clone me! The second reason why I'm talking about switching to git is the experience we gained at Entwine working with a dual git/svn setup where developers work solely in git but parts of our work repos are connected to the OC SVN. This doesn't work bad but it feels like having MH git based would be much nicer. I think it would be a good idea to switch to git after the 1.4 release and before GSoC to send out a strong signal that we embrace folks who want to work with us on MH. This leaves us some time to plan the migration and for everybody to check out git. Entwine can share their list of resources to get everybody to learn at least the basics to become productive with git soon. Christoph _______________________________________________ Matterhorn mailing list [email protected]<mailto:[email protected]> http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected]<mailto:[email protected]> _______________________________________________
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
