KDE project completes first phase of migration to GitLab

Announced about the completion of the first phase of the transition of KDE development to GitLab and the beginning of the use of this platform in daily practice on the site invent.kde.org. The first phase of the migration covered the translation of all KDE code repositories and review processes. In the second phase, it is planned to use the capabilities of continuous integration, and in the third phase, we will switch to using GitLab to manage problem resolution and task scheduling.

The use of GitLab is expected to lower the barrier to entry, make participation in KDE development more familiar, and empower tools for development, development cycle maintenance, continuous integration, and change review. Previously, the project used a bunch of Pharmacist ΠΈ cgit, which is perceived by many new developers as unusual. GitLab is pretty close in features to GitHub, is free software, and is already used by many related open source projects such as GNOME, Wayland, Debian, and FreeDesktop.org.

The migration was carried out in stages - at first, the capabilities of GitLab were compared with the needs of developers and a test environment was launched in which small and active KDE projects that agreed to the experiment could try out the new infrastructure. Based on the feedback received, work began to eliminate identified deficiencies and preparing the infrastructure for translating larger repositories and development teams. Together with GitLab was held work on adding to the free edition of the platform (Community Edition) features that the KDE community lacked.

The project has about 1200 repositories with their own specifics, to automate the transfer of which the KDE developers wrote utilities for data migration with the preservation of descriptions, avatars and individual settings (for example, the use of protected branches and specific merge methods). We also ported the existing Git hooks used to check whether file encodings and other parameters match KDE requirements, as well as to automate the closing of problem reports in Bugzilla. In order to make it easier to navigate through over a thousand repositories, the repositories and commands have been broken down into Group and categorized in GitLab (desktop, utilities, graphics, sound, libraries, games, system components, PIMs, frameworks, etc.).

Source: opennet.ru

Add a comment