On Amarok Switching to Git

[Ian Monroe]

So most Amarok devs use git-svn now, and there's a growing consensus
that switching to Git would make life easier. So I'd like to request
assistance and pointers on how to actually go about doing this.

I understand from reading the archives that one thing holding the
switch to Git back is that its hard to keep track of history of files
that are copied across projects. Outside of our file browser from
Kate, Amarok doesn't really have any such files that I know of and
this isn't important to us. So I don't think this is an issue. I
understand that otherwise the actual svn->git conversion is a solved
issue.

Issues that need to be solved:
* Scripty. Its somewhat of a mystery where it is and how this thing
works. :) So it just needs to clone the central git repo, and perhaps
use a stable branch in the future. It should commit the translation
files back into SVN like it does currently, and make the commits with
.desktop files available somewhere.
*svn externs. We currently have a couple: one is Plasma (which we'll
remove once we depend on KDE 4.3 I think) and the other is a library
written by an Amarok dev that could probably be converted into a git
repo as well. It'd be nice to at least record the history of svn
externs.
*Other problems that I don't know about.

So for the first issue I'm guessing I will have to ask the sysadmin
team. Similarly I'd like to be hosted at git.kde.org; I want to keep
it very clear that we're still "in KDE."

Hello to folks in Jamaica! :)

Ian