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

[Thiago Macieira]

Ian Monroe wrote:
>> I see both reasons as valid.  However, I thought being "part of KDE"
>> meant being maintained under the same source control.  That said,
>> Amarok survived fine being not "part of KDE" in the past and I think
>> it could flourish there again.
>
>Amarok has been in KDE SVN since 2003, before version 0.6 which is
> pre-historic.
>
>But being "part of kde" is mostly a social and political thing. So
>like Amarok could just use github, but it'd probably be nice to use
>git.kde.org and have the user list be synced with at least all the
>svn+ssh users.

I don't see the problem here. We can move the modules one by one.

But we should have a consensus on doing so. I'd hate to have only Amarok 
on Git, plus smaller, new projects that people start, while the majority 
of the projects remains on SVN.

I, for one, would advocate for kdelibs to switch to Git[*]. That way, we 
force everyone to start using it and learning it. Eventually, everything 
would follow suit.

[*] This is my selfish reason. And I've said more than once that I will 
not backport my commits until we switch to Git.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20090118/cbb2d463/attachment-0001.sig