Summit workflow - git migration

[Johnny Jazeix]

Thank you for your answers,

the script we use for French also checkout/clone all the folders
needed (pology, scripty, languages...), update them then run the
posummit merge/scatter for both messages and docmessages and also
generate the docbook for the 4 branches (stable/trunk, kf5/kf6). Maybe
it can be split to multiple scripts, each one with a precise goal.

Cheers,

Johnny

Le mar. 26 août 2025 à 17:39, Łukasz Wojniłowicz
<lukasz.wojnilowicz at gmail.com> a écrit :
>
> On 25-08-25 22:43, Johnny Jazeix wrote:
> >Hi,
> >
> >as you may know, there is some work in progress to migrate the
> >translation files from svn to git
> >(https://invent.kde.org/teams/localization/issues/-/issues/1). This
> >thread is focused on the summit workflow.
> >
> >One major point of it will be the folders structure will not be the
> >same as before.
> >In svn we have a common svn repository and in it:
> >[branches/stable | trunk] / [l10n-kf5 | l10n-kf6] / {lang}
> >where with git, we will have a kde-l10n-{lang} repository and in it:
> >[ stable5 | stable6 | trunk5 | trunk6 | summit ]
> >
> >I would like to start this discussion to know how teams run the summit
> >scripts. I know for French we use a bash script (that I ported to work
> >with the git structure):
> >https://invent.kde.org/jjazeix/kde-l10n-parent/-/blob/master/summit/sync_summit_branches.sh?ref_type=heads),
> >for German, klash (https://invent.kde.org/schwarzer/klash) and I don't
> >know for other...
> >
> >If you are a summit user:
> >* which tool do you use?
> >* What are the pros/cons of your tool?
> >* can we agree to use one common tool for all the languages and
> >enforce it in KDE?
> >
> >I guess all the tools call pology for the different steps, so it's
> >mostly a choice of language?
> >
> >Cheers,
> >
> >Johnny
>
> Hi,
>
> I use just:
> posummit scripts/messages.summit $L10NLANG merge
> posummit scripts/messages.summit $L10NLANG scatter
> --
> Cheers,
> Łukasz