Git migration plan

[Luigi Toscano]

Hi,

Kisaragi Hiu ha scritto:
> 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?
>   - All (essentially) history has been preserved
>   - The total size is reasonable even for languages with a long history & lots
> of translations
> - Directories are just like the migrated-to-git templates
>   - namely: trunk5, trunk6, stable5, stable6, summit
>   - files and paths within are unchanged
>   - 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).

You can have files (it is already the case, if you browse around) but please
PLEASE don't set your own weblate/crowdin. And if you have to chose, don't use
crowdin, which has no tracking of who contributed what. Let's work together
when this migration is done to setup a global service for everyone.

-- 
Luigi