Re: Git migration plan

Hi,

thanks to all of you who replied to me for their coordinator roles.

Le lun. 24 août 2026 à 20:11, Kisaragi Hiu <[email protected]> a écrit :
>
> Hello,
>
> I'm looking forward to this, thank you so much. Hopefully this will allow us to even use MRs (easier submission for new translators, easier / more public review even for existing translators)!
>
> > If you are coordinating a language, can you please reply in private so
> > I know who to contact when I will want to handle your language (I
> > don't think we have a list of coordinators somewhere)?
>
> (Since I'm already asking things below I'll just include this here.)
>
> I coordinate Min Nan Chinese (aka Taiwanese Hokkien, code nan_TW & nan_TW@latin). The history should be quite thin because it's only just been created in June. We have a lokalize-files subdirectory since I decided to colocate the glossary with the translations, which I hope is fine.
>
> I also actively translate Traditional Chinese (aka Taiwnese Mandarin, code zh_TW). I'm not sure if I would have the title of a coordinator, but I am the most active person in the team with commit access.
>
> > An important part (I'm directly quoting Karl from the discussion):
> > "What I think is really important, is to have a good, clear
> > documentation for the translators before the actual migration.
> > Basically, we’ll need a ‘KDE L10N SVN user to Git user’ guide (for
> > existing translators) and a ‘KDE L10N Git user’ guide (for new
> > translators)."
> > So we would also like, if we have a volunteer team to test the git
> > workflow, that they help to write this guide to help the translators
> > who are not familiar with Git.
>
> I tried writing a rough outline of a migration guide for an existing translator with commit access. I found some questions that I'd like to know as well (currently 3), which are interspersed in the rough draft below.
>
> (I don't think it's useful to focus on teaching Git ("use git pull instead of svn update" etc.). This is because (a) the need is low, because it seems unlikely someone would know svn yet still don't know git in 2026, and (b) even if someone does need to learn Git, Git can be learned elsewhere but details about our new workflow can't, so it's still the latter that should be focused on. Touching on it is fine but it shouldn't be the main purpose of the guide)
>

Some translators don't know git, I guess having the basics are still
essential (just "git add/commit/push" replace "svn add/commit" + a
link to a git doc).


> Existing translators:
> - Each language team has one Git repository at https://invent.kde.org/localization/l10n-CODE
>   - Q: this is my guess based on how l10n-templates and l10n-umbrella are named. Is this correct?

yes

>   - All (essentially) history has been preserved

yes

>   - The total size is reasonable even for languages with a long history & lots of translations

The worse last year when Karl created the repos was  787M for the French team.

> - Directories are just like the migrated-to-git templates
>   - namely: trunk5, trunk6, stable5, stable6, summit
>   - files and paths within are unchanged

yes

>   - Q: can translators with commit access put other stuff (like a common glossary, a team's own README, or even a team's setup code for their own Weblate / Crowdin / etc. instance) in this repository? My guess is yes for small files (what was already acceptable to commit into SVN like glossary, README files...), but no for large / complex things (since that's a burden to clone or host).

There is git-lfs for the binary files but to be checked with sysadmin
for large/complex things, I guess it depends on what and size. It may
make more sense to have them on a separate repo.

> - Q: What about teams that use summit? Does posummit just work, what config changes might be needed, etc.
>

config will need to be changed. As we don't use the same tool across
the different languages, each team will have to handle theirs.
For French, I had done
https://invent.kde.org/jjazeix/kde-l10n-parent/-/tree/master/summit?ref_type=heads
last year (note that some paths are incorrect, I expected kde-l10n-xx
instead of l10n-xx

> Best regards,
> Kisaragi Hiu

Cheers,
Johnny