[Kde-scm-interest] On Amarok Switching to Git

[Ian Monroe]

On Sat, Jan 17, 2009 at 5:17 PM, Thiago Macieira <thiago at kde.org> wrote:
> Ian Monroe wrote:
>>* 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.
>
> SVN externs are not a problem. They just die. Get rid of them right now,
> on SVN (they are hurting you now because you're using git-svn). SVN and
> Git users will thank you.

Actually we already got rid of them. I was confused. :)

Still we need to have this info recorded somewhere. I suppose having
it in a deep freezed SVN server somewhere is good enough.

>>*Other problems that I don't know about.
>
> Other problems that come to mind:
>
>  * infra-structure (must convince sysadmins to host and maintain
> git.kde.org)

Indeed.

>  * how to create personal or group repositories. Should we use Gitorious
> or GitHub?

We don't have to decide this. People can do what they want. Some
standard solution is a good idea though.

>  * the unresolved issue of accountability

This is the main issue I see. I hear there are solutions though?

>  * who will have push rights? To which branches? Who can create branches?
> Which branches/repos will allow force-pushes?

Well everyone will have push rights. I don't know what a force push is.

>  * SSH accounts for the Git server
>    (every single KDE contributor using HTTPS must mail an SSH key)

s/everyone/everyone who wants to develop Amarok/

>  * the general layout of the server hierarchy (Amarok may be the first,
> but we hope it's not the last, so we need some future-proofing)

I don't understand why? The Amarok git repo can move around in future.

>  * should we use supermodule/supermodule? Should we use repo?

Again we don't need to decide this. (assuming I understand what you're saying).

>  * should we use a patch-submission-and-review system? (probably not)

no.

> And most importantly:
>  * who is going to do all this work?
>
> I'm not volunteering.

Well I did... though obviously I can't volunteer the sysadmins and
will need some help. Why I sent this email. :)

Ian