+1
D
On 09/26/2012 12:08 PM, Lukas Rohner wrote:
+1 from me too
Am 26.09.2012 um 11:09 schrieb Denis Meyer <[email protected]
<mailto:[email protected]>>:
+1 for moving forward to git.
I work with Matterhorn using git (git-svn) as well (manually updated):
Matterhorn 1.4: https://github.com/CallToPower/Opencast-Matterhorn-1.4.x
and
Matterhorn Trunk: https://github.com/CallToPower/Opencast-Matterhorn
Denis
On 25.09.2012, at 7:03 PM, Christoph Drießen
<[email protected] <mailto:[email protected]>> wrote:
As a follow up from today's dev meeting I re-post a mail with the
title "git again" I've sent to list a couple of month ago.
Another good source for getting the advantages of git over svn is
this video of Linus Thorvalds speaking at Google. It's a bit long
but gives great insight and is also fun to watch.
http://www.youtube.com/watch?v=4XpnKHJAok8
Then I'd like to remind that there's a page on the wiki to collect
all issues you see around migrating to git. If we want to make the
transition everyone should contribute.
http://opencast.jira.com/wiki/display/MH/Switching+to+Git
Besides the point I've outlined in my re-post below, I'd like to
emphasize the superior toolset of git when comes to working with
your source code. The fact that everything is local makes it
blazingly fast. Digging around in revisions, picking code from
another branches, doing code analysis, branching and merging really
becomes part of your daily development routine since all those tools
run in fractions of a second.
Since branching and merging is that easy you'll immediately start to
develop in dedicated local development branches. That gives you the
benefit of _always_ having a working version at hand. It's just
switching branches.
There's more to git. Do a bit of googling or just set up a small
test repo for yourself and start working with it. After some time
you'll be asking yourself how development worked without it.
## re-post
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]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected] <mailto:[email protected]>
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
