The CentOS project announced the launch of a collaborative development service based on the GitLab platform. The decision to use GitLab as the primary hosting platform for CentOS and Fedora projects was made last year. It is noteworthy that the infrastructure is raised not on its own servers, but on the basis of the gitlab.com service, in which the gitlab.com/CentOS section is provided for projects related to CentOS.
Currently, work is underway to integrate the section with the user base of the CentOS project, which will enable developers to connect to the Gitlab service using existing accounts. Separately, it is noted that git.centos.org based on the Pagure platform will continue to be considered as a place to host the sources of packages ported from RHEL, as well as the basis for the formation of the CentOS Stream 8 branch. But the CentOS Stream 9 branch is already being developed based on the new repository in GitLab and is distinguished by the ability to connect to the development of members from the community. Other projects hosted on git.centos.org remain in place for now and are not forced to migrate.
Opponents of the transition to the SaaS model in the process of discussing the decision noted that the use of a ready-made service provided by GitLab does not allow full control over the infrastructure, for example, it is impossible to be sure that the server infrastructure is properly maintained, vulnerabilities are eliminated promptly, telemetry and the environment will not begin to be imposed was not compromised as a result of an external attack or the actions of dishonest employees.
When choosing a platform, in addition to typical operations with repositories (merging, creating forks, adding code, etc.), there were such requirements as the ability to send push requests via HTTPS, means of restricting access to branches, support for private branches, separating access from external and internal users (for example, to work on fixing vulnerabilities during a disclosure embargo), familiarity of the interface, unification of subsystems for working with problem reports, code, documentation and planning for new features, availability of tools for IDE integration, support for common workflows, the ability to use a bot for automatic merges (requires CentOS Stream to maintain kernel packages).
Source: opennet.ru