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

[Ian Monroe]

On Sun, Jan 18, 2009 at 10:15 AM, Robert Wohlrab <robert.wohlrab at gmx.de> wrote:
> On Sunday 18 January 2009 16:52:18 Ian Monroe wrote:
> [..]
>> >  * 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.
> Normally you can only push if you do a fast forward push (I know that your
> local branch can have names you want but I assume in this example that
> branches on server and your branches have the same name and your branches
> track the branches on the server)
[snip, thanks]
>
> Please note that git tracks everything by its sha1. So rebasing a branch will
> change its sha1's and you will get the same stuff as above. So I would say
> nobody should have forced push rights access to the official branches. But
> this is something your guys have to "auskaspern" (sry, don't know an
> equivalent word in english - just speak with other amarok devs what they think
> about forced pushs)

Yes no force pushes I think. :) Central repos aren't meant for that
sort of thing.

>> >  * 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.
> But good designs will not move around. We can do the "lets just do it and
> change it in the future sometimes" or the "lets design it in a sane way so we
> can build on it" approach. I dont know which one is the right solution but one
> of them is the definitely the wrong.

Err I don't get this. "Good designs will not move around". Its really
no hassle to move around a git repo.  I still see no need for future
proofing. We have plenty of problems to solve we don't need to create
new ones! Part of the point in moving a one or two KDE project's first
is that we don't have to solve everything.

>> > 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. :)
> Did you try to convert the whole/partial/whatever repo of amarok and checked
> if it you get a good result (checked with graphical tools and give the repo to
> a guy with more experience(tm)?).

Well plain ole git-svn looks just fine. I figure the next step is
figuring out authentication and scripty. I plain on poking aacid and
kde-i18n and can start working on that. Authentication I don't know!

Ian