Albert Astals Cid wrote:
>A Dimarts, 26 de maig de 2009, Ian Monroe va escriure:
>> 2009/5/26 Chusslove Illich <caslav.i...@gmx.net>:
>> >> [: Ian Monroe :]
>> >> I agree that there's no reason translators and programmers should
>> >> use the same system. However I don't think letting individual
>> >> projects in KDE pick their own VCS is a good idea. Amarok is
>> >> probably going to switch before the rest, but this is purely
>> >> transitional. Keeping all the developers in KDE on the same
>> >> technological ship is important to the culture, and there's no
>> >> technology more critical to development then VCS.
>> >
>> > This depends on definition of "in KDE" :) If that means "presently
>> > in central KDE repo", then, well, such definition is obviously going
>> > to be made void. While (just giving examples, not a policy opinion)
>> > core modules may all use same VCS, some extragear apps may not.
>>
>> Well I think all extragear apps are in KDE and should use the same
>> VCS. :)
>>
>> > For random KDE apps presently
>> > not in KDE repo (Krusader comes to mind as prominent example), there
>> > is neither a way (nor the need) to enforce a given VCS. But there is
>> > no reason for a random KDE app not to be able to benefit from KDE
>> > Translation Project (KTP), should they want so and agree to terms
>> > established by KTP.
>>
>> Translation is one of the major benefits in having your app join the
>> KDE project. I don't like the idea of extending it to others.
>
>But i'm sure "KDE project" translators would be more than happy if we
> extended the benefits of our powerful infrastructure to other "KDE but
> not KDE project " programs because if they don't translate them it's
> just because it's more difficult to handle them.

Once Git support is added to scripty, we could extend our translation 
services to projects hosted outside the KDE servers.

I don't know which applications may want that, but I'm sure there will be 
some.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest

Reply via email to