Back in November, KDE introduced that it will be transferring to GitLab as a part of an enormous migration, and immediately the corporate confirmed that the primary part of the method is lastly full.
In different phrases, the KDE neighborhood can now use GitLab on a standard foundation to contribute to the challenge and assist enhance the challenge total.
The migration to GitLab wasn’t by any means one thing that may simply occur in a single day, as greater than 1,000 repositories have been migrated.
And that is the explanation KDE wished to do the entire thing in phases, utilizing customized instruments for bulk updates that have been supposed to assist through the course of.
“The migration started by moving some smaller and more agile KDE teams that were very interested in testing and providing feedback,” Nuritzi Sanchez of GitLab explains in an in depth submit about KDE’s migration.
“After this cycle was completed successfully, KDE started migrating teams with a larger codebase and more contributors. Once all of the major issues were resolved, they made the final switch for all remaining projects they planned to move. The sysadmin team documented the results after each step and shared them directly with the KDE community to receive feedback and gather consensus on how to proceed.”
Next cease: part two
According to the official stats, the KDE challenge is at present the house of over 200 functions, with greater than 2,700 artists, designers, builders, and contributors engaged on bettering the expertise total for everybody that’s a part of the neighborhood.
Before the migration to GitLab might be thought-about full, KDE nonetheless has two extra phases to finalize. They embody CI and job administration for builders, and as soon as once more, this is able to happen regularly to verify the whole lot goes as deliberate.
A extra technical overview of the migration is offered in GitLab’s personal submit here.