Git migration

[Albert Astals Cid]

El dilluns, 9 de setembre del 2024, a les 16:17:15 (Hora estàndard del Centre 
d’Europa), Albert Astals Cid va escriure:
> El dilluns, 9 de setembre del 2024, a les 15:18:56 (CEST), Johnny Jazeix va
> 
> escriure:
> > Le lun. 9 sept. 2024 à 11:42, Shinjo Park <kde at peremen.name> a écrit :
> > > Dear everyone,
> > > 
> > > Here is minutes from the i18n BoF during Akademy 2024.
> > > 
> > > Migration of translations from SVN to Git
> > > - Blocker: tooling (tosky and tsdgeos) -> renaming of PO files, history
> > > preservation, others
> > > - Wiki page for documentation, statistics webpage needs to point Git
> > > instead - Possibly lower the barrier for new translation teams
> > > ...
> > > Shinjo
> > 
> > Thanks Shinjo,
> > I'm splitting the mail to only focus on the git migration part.
> > Can we do a wiki page or something else (depending on the preference
> > of the maintainers) to list all the blockers/steps to migrate? I know
> > there was a phabricator task but there is more to read on it than in
> > the lord of the rings trilogy...
> 
> I would possibly vote for an issue in
> https://invent.kde.org/groups/teams/localization/-/issues

https://invent.kde.org/teams/localization/issues/-/issues/1

Filled with the plan that Luigi and me came up a few months ago.

The basic idea is we move each team to their own repository and have a global 
repository with git submodules that would be used mainly for making the admins 
life easier.

Each of the team repositories would just have a git branch with the 
"translation branches" just being directories in that git branch. That would 
really keep the workflow/script changes we need to a minimum.

Now what we need is someone to check all the scripts that interact with SVN 
one way or another so we can have an exhaustive list of what needs changing 
once we move to GIT with the suggested architecture.

Cheers,
  Albert

> 
> Cheers,
>   Albert
> 
> > Cheers,
> > 
> > Johnny