Summit workflow - git migration

Yaron Shahrabani sh.yaron at gmail.com
Tue Aug 26 14:25:23 BST 2025


Since Hebrew has mixed plural forms I can't use summit anyway so my work
routine is VSCode-Lokalize, this way I can fetch the templates and the
updates and see the list of files and changes like when I'm pushing the
files.
I wish I had more time for scripts and tricks but I'm just trying to do the
minimum possible effort to get the job done and I'm hoping that Lokalize is
good enough for keeping everything synced with my config.

So this change had minimal effect on my workflow, thanks.

Yaron Shahrabani

<DevOps - Hebrew translator>


On Tue, 26 Aug 2025, 06:21 Zayed Al-Saidi, <zayed.alsaidi at gmail.com> wrote:

> Hi,
>
> For the Arabic team (one person having svn access), I used a bash script
> (I took it from the French team). After setting up the initial repository,
> I made two scripts and bookmarked them in Konsole. One for Update
> translation repos and Merging messages. The second one to Scattering
> messages and committing the change if any.
>
> Then, I run the first script in one click in Konsole. After that I updated
> the translation. Finally I scatter the messages and commit the changes by
> clicking the second bookmarked script.
>
> If we can use one common tool for all the languages, it will be a great
> help for newcomers and less technical people.
>
> Regards,
> Zayed
>
>
> On Tue, Aug 26, 2025 at 12:43 AM Johnny Jazeix <jazeix at gmail.com> 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
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20250826/ce1fd853/attachment.htm>


More information about the kde-i18n-doc mailing list