You're right Chris, some things need to be clarified before we can move on with the discussion. To get a better picture of what is affected by a VCS switch we should compile a list to get an overview. Based on this list we then can estimate how much work it will be and who is able to contribute. Then we should get a clearer picture if we can accomplish switching.
I've started a list on the wiki here http://opencast.jira.com/wiki/display/MH/Switching+to+Git - Jira - Bamboo - Crucible - install scripts - release scripts - branch mapping SVN -> git - SVN tags - does the MH repo use SVN externals? - where to host the git repo Please amend to this list whatever is missing. Christoph Am 28.03.2012 um 17:20 schrieb Christopher Brooks: > I'm a -0 if you or others reconfigure our jira instance, hooks to > bamboo, cru instance, install scripts, release scripts, etc. before we > switch the code over. > > If this has not been done, then I'm a -1 on the grounds that something > that works now is better than something that sounds like it might work. > > In short: I won't stand in the way but someone who really wants git has > to do the leg work of getting things up and running. > > Chris > >> 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] >> http://lists.opencastproject.org/mailman/listinfo/matterhorn >> >> >> To unsubscribe please email >> [email protected] >> _______________________________________________ > > > > -- > Christopher Brooks, BSc, MSc > ARIES Laboratory, University of Saskatchewan > > Web: http://www.cs.usask.ca/~cab938 > Phone: 1.306.966.1442 > Mail: Advanced Research in Intelligent Educational Systems Laboratory > Department of Computer Science > University of Saskatchewan > 176 Thorvaldson Building > 110 Science Place > Saskatoon, SK > S7N 5C9 _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
