[Kde-scm-interest] Minutes from Today's KDE -> Git BoF

Andrius Štikonas stikonas at gmail.com
Mon Jul 13 18:30:07 CEST 2009

2009/7/9 Leo Franchi <lfranchi at kde.org>

> On 9 Jul 2009, at 02:08, Ian Monroe wrote:
>  2009/7/8 Andrius Štikonas <stikonas at gmail.com>:
>>> yeah.. it was mentioned and got lost in the noise I guess. or maybe it
>>>> was
>>>> that the po files are staying in svn for however long the translators
>>>> stay
>>>> there.
>>>> in any case, we have pre-commit hooks and they're important and the
>>>> gitorious
>>>  guys said they'll make it possible to add them.
>>> Git offers many benefits to translators too. Now ordinary translators do
>>> not
>>> have any commit access at all
>>> and they send their translations to maintainer and maintainer uploads
>>> large
>>> commits that are hard to review.
>>> With git it is possible to use workflow where every translator can commit
>>> to
>>> some git repository and later translation maintainer pushes translations
>>> into main repo. This workflow allows better review of translations by
>>> ordinary translators
>> Yea I agree, that makes a lot of sense, but given that translators had
>> more issues with the cvs->svn transition (according to conventional
>> wisdom) I really like the idea of translators moving or not moving to
>> Git on their own schedule and not one imposed by the likes of us.
> The translators have stated their complete non-desire to deal with
> switching to Git right now---our goal is to make this as faultless a
> transition as possible, and this includes not making the translators want to
> kill us. So we're not going to change their workflow underneath their feet
> :)
> leo
> ---
> Leo Franchi                             (650) 704 3680
> Tufts University 2010
> lfranchi at kde.org
> leonardo.franchi at tufts.edu
Ok, let's leave translations in svn for now. But later we can do the same
thing for translations that is being done for software repositories: migrate
only one or two teams to find all rough edges (for example Lithuanian team
will be willing to test) while all other teams remain in svn. After that,
migration for other teams should be relatively painless.
Since we had large cvs and svn repositories that contained all modules, such
testing with 1 or 2 teams was not possible with cvs->svn migration.

Andrius Štikonas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-scm-interest/attachments/20090713/a8dc0836/attachment.htm 

More information about the Kde-scm-interest mailing list