Git migration plan

Wed Oct 28 22:28:08 GMT 2026

Hi,
It happens with each `git push` since I started working with git after the 
migration.

$ git push
Enumerating objects: 33, done.
Counting objects: 100% (33/33), done.
Delta compression using up to 16 threads
Compressing objects: 100% (22/22), done.
Writing objects: 100% (24/24), 7.67 KiB | 7.67 MiB/s, done.
Total 24 (delta 15), reused 0 (delta 0), pack-reused 0
remote: The commits in this series can be viewed at:
remote: https://invent.kde.org/localization/l10n-eu/-/commit/
075ec34ea90b4972ff0389002b77ad8a994bb46d

<stopped for 03:39 minutes>

To invent.kde.org:localization/l10n-eu.git
   966e1e5616..075ec34ea9  master -> master
$

Cheers.
--
Iñigo

2026(e)ko urriaren 28(a), asteazkena 10:51:53 (Europako erdialdeko ordu 
estandarra)(e)tan Ben Cooksley(e)k idatzi zuen:
> On Wed, Oct 28, 2026 at 10:47 AM Johnny Jazeix <jazeix at gmail.com> wrote:
> > Hi,
> 
> Kisaragi tested for zh_TW
> 
> > (https://invent.kde.org/localization/l10n-zh_TW) and it was around 12
> > seconds for a single file.
> > Alexander for German is pushing very often l10n-de
> > (https://invent.kde.org/bxela/l10n-de/-/commits/master?ref_type=HEADS),
> > it is big (1.1GB, only .git folder inside is 812MB) and "git pull
> > first time take long, git push is very quick.".
> > I'm not sure what could impact the duration, I've added the sysadmin
> > in copy who might have more knowledge about it.
> 
> Git pushes should require very little in the way of traffic and certainly
> shouldn't take 4 minutes to complete.
> During the process of running "git push" at which line in the below output
> does it hang?
> 
> Enumerating objects: 10, done.
> Counting objects: 100% (10/10), done.
> Delta compression using up to 8 threads
> Compressing objects: 100% (7/7), done.
> Writing objects: 100% (7/7), 715 bytes | 715.00 KiB/s, done.
> Total 7 (delta 3), reused 0 (delta 0), pack-reused 0 (from 0)
> remote: The commits in this series can be viewed at:
> remote:
> https://invent.kde.org/sysadmin/repo-metadata/-/commit/b3dc34a8504558d83b959
> d02f0fc7788588a9e3d To invent.kde.org:sysadmin/repo-metadata
>   3685fe5f..b3dc34a8  master -> master
> 
> If it takes ages to even start that is indicative of DNS / IPv6 networking
> issues.
> Please try "git push -4" in that case.
> 
> One other possibility is that you had the misfortune of trying to push when
> Invent was being attacked by AI scrapers - this also affects pushes over
> SSH unfortunately.
> If that is the case then the issue will no longer be reproducible.
> 
> > Cheers,
> > Johnny
> 
> Cheers,
> Ben
> 
> > Le mar. 27 oct. 2026 à 22:35, Iñigo Salvador Azurmendi
> > 
> > <xalba at arranoarenkabia.eus> a écrit :
> > > Hello,
> > > When pushing translation commits from local to invent `git push` it
> > 
> > takes up
> > 
> > > to 4+ minutes even when making a one line on one file change. Is it a
> > 
> > normal
> > 
> > > duration?
> > > 
> > > Cheers.
> > > --
> > > Iñigo
> > > 
> > > 2026(e)ko urriaren 17(a), larunbata 16:29:17 (Europako erdialdeko ordu
> > > 
> > > estandarra)(e)tan Johnny Jazeix(e)k idatzi zuen:
> > > > Hi,
> > > > first batch of repositories should be finished tomorrow :).
> > > > I would like to continue with the last unmaintained repositories: my,
> > > > tok, lo, zh_HK, be at latin, sa, kn, uz at cyrillic, ie, vi, ml, ast, mk,
> > > > tg, br, eo, en_GB, et, gl.
> > > > And start with a few maintained ones: th, he, ta, eu, pt.
> > > > I'll contact the maintainers next week to find which day will be the
> > > > best for the migration.
> > > > Please don't hesitate to tell if there is any obstacle to migrate one
> > > > of these repos.
> > > > 
> > > > Karl started this documentation for the svn to git steps for
> > > > maintainers: https://invent.kde.org/-/snippets/3918, please make sure
> > > > to read and comment if you have any doubts, else I'll consider
> > > > coordinators are ready for git.
> > > > 
> > > > Cheers,
> > > > Johnny
> > > > 
> > > > Le ven. 9 oct. 2026 à 14:55, Johnny Jazeix <jazeix at gmail.com> a écrit
> > > > 
> > > > > Hi,
> > > > > 
> > > > > thanks to all the coordinators who replied!
> > > > > We successfully migrated the first language yesterday to git. We
> > > > > will
> > > > > monitor it a few days to ensure the shadowing works fine and all the
> > > > > scripts we use are working as expected.
> > > > > The next step, starting next week will be to migrate more
> > 
> > unmaintained
> > 
> > > > > languages: ky, sw, tn, kab, mi, crh, ss, mn, ps, gd, tt, lb, as, fo,
> > > > > ven, zu, mt, or, bn_IN, nso, te, ha, csb, rw, ku, si, bn, hsb, fy,
> > 
> > uz,
> > 
> > > > > mai, wa, hne, af, mr, oc, ne, cy, xh, kk, hy, ms, bs, km, nds.
> > > > > 
> > > > > Once these are done, I'll refine my list because for sure I missed
> > > > > some unmaintained languages but we will also be able to start
> > > > > migrating maintained languages to work on the documentation for the
> > > > > migration process for other teams.
> > > > > 
> > > > > I confirm that the language is frozen during a full day (I start the
> > > > > migration morning CEST time and I finish it before the night
> > 
> > depending
> > 
> > > > > on my day).
> > > > > 
> > > > > Cheers,
> > > > > Johnny
> > > > > 
> > > > > Le jeu. 20 août 2026 à 18:52, Johnny Jazeix <jazeix at gmail.com> a
> > 
> > écrit :
> > > > > > Hi,
> > > > > > 
> > > > > > here is the global plan I would like to progress for the git
> > 
> > migration
> > 
> > > > > > of the translation files.
> > > > > > The global idea is to migrate language by language with no freeze.
> > 
> > We
> > 
> > > > > > synchronize with the git files prior running scripty and we push
> > 
> > back
> > 
> > > > > > to git after. Once all the languages are migrated, we can migrate
> > > > > > scripty to the git version.
> > > > > > 
> > > > > > The plan with more details is:
> > > > > > * do the prerequisites (create the umbrella repo, make
> > > > > > makemessages
> > > > > > part of scripty + integrate svn/git synchro to the process)
> > > > > > * migrate one language with no active contribution (lg for example
> > 
> > is
> > 
> > > > > > a small one) and test the shadowing
> > > > > > * once we have checked it is fine, we can continue to migrate the
> > > > > > other inactive languages and if we have an active candidate team
> > > > > > to
> > > > > > test the git workflow, we can migrate it in parallel
> > > > > > * once all the inactive languages, we will need to coordinate with
> > 
> > the
> > 
> > > > > > language coordinators to find a good time to migrate their
> > > > > > language
> > > > > > (it should be blocked around half a day, depending on how fast we
> > > > > > handle the process, this will be refined later once we have tested
> > 
> > a
> > 
> > > > > > few languages).
> > > > > > * once all the languages are migrated, we can switch all the
> > 
> > dependant
> > 
> > > > > > scripts to git (scripty -
> > > > > > https://invent.kde.org/sysadmin/l10n-scripty/-/merge_requests/91,
> > > > > > website -
> > > > > > https://invent.kde.org/websites/l10n-kde-org/-/merge_requests/3)
> > > > > > 
> > > > > > There were a lot of discussion in
> > > > > > https://invent.kde.org/teams/localization/issues/-/work_items/1
> > 
> > for
> > 
> > > > > > those interested with all the history and choices.
> > > > > > There are also some remaining questions that can be tackled during
> > 
> > the
> > 
> > > > > > migration (usage of git-lfs, git-graft...).
> > > > > > 
> > > > > > 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.
> > > > > > 
> > > > > > 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)?
> > > > > > 
> > > > > > I don't have a specific time frame to announce, I would like to
> > 
> > start
> > 
> > > > > > as soon as possible, it should be finished the end of year at
> > > > > > worse
> > > > > > and at best I would say doable in 1-2 months (depending on the
> > > > > > time
> > > > > > and coordination needed). I will try to communicate as much as
> > > > > > possible on each step (especially when starting to handle active
> > > > > > languages).
> > > > > > 
> > > > > > Cheers,
> > > > > > 
> > > > > > Johnny