[Kde-scm-interest] initial port of scripty to git is ready

[Ian Monroe]

2009/5/21 Thomas Zander <zander at kde.org>:
> On Thursday 21. May 2009 15.16.05 Ian Monroe wrote:
>> > 3. There is no 'git push' back into the main repository from scripty's
>> > clone
>
> That should be added then; ;)
> some algorithm along the lines of
>  while (!git push) {
>    if (!git pull --rebase) { # sorry, not working out...
>     git reset --hard origin/master;
>     quit;
>    }
>  }
>
>> So that we're on the same page... scripty still needs to work with
>> i18n in SVN. I was a little concerned when you said its a "git port"
>> when its really more of a "git feature addition." I guess I should've
>> dented immediately. :)
>>
>> The idea is that for Amarok or Plasma to switch to git tomorrow, i18n
>> needs to stay in SVN. (Possibly i18n could stay in SVN forever, they
>> have a very different way of doing things and switching to git should
>> be up to them.)
>
> It would be great to have the functionality in place for amarok/plasma to go
> git.
> I'm a bit confused about the conclusion we don't want to have i18n in git.

Its more like: I have no opinion on moving i18n to git. I wasn't using
"possibly" as a weasel word, I really don't have a conclusion on the
matter.

> There are loads of solutions to migrate, including having nice GUI tools so
> the user never need to see a command line.
> Keeping svn seems a bit odd to me; an opt-out solution. Not solving the
> problem but avoiding it with the side effect of having to keep an svn server
> up and running :/

The goal isn't to solve the i18n problem, whatever it is.

We should recognize that they have a unique set of issues from coders,
so the question of their VCS should be separate. With the
decentralized method that they already use a DVCS like git might be
great for them. But I dunno, I'm not a translator. I just don't think
"because application code is in git" is much of a reason for them to
use git.

> So, like Matt I was under the impression we wanted to port script to
> basically do exactly what it did before, but now using git.

Well for Amarok to switch 'tomorrow' (while rest of KDE stays in SVN)
obviously i18n needs to stay in SVN. We can't expect translators to
use two VCS's at the same time, given that they deal with multiple
apps in bulk when doing translations.

Ian