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
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
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
Source: opennet.ru