The KDE project implements GitLab. GitLab EE and CE development moved to shared repository

KDE Project commissioned collaborative development infrastructure based on an open platform GitLab, which will lower the entry barrier, make participation in KDE development more familiar, and empower tools for development, development cycle maintenance, continuous integration, and change review. Previously, the project used the platform Pharmacist (And 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.

Phabricator support remains in service for now, and a separate service has been launched for GitLab supporters invent.kde.org... Platform Pharmacist is mainly focused on project management and code reviews, but lags behind in areas such as continuous integration, working with repositories and the web interface. GitLab is written in Ruby and Go, while Phabricator is written in PHP. KDE developers needed to switch to GitLab some possibilities, which are partially already implemented in response to their request.

Additionally, we can note the ongoing GitLab company work by merger commercial and community branches of the project, which will greatly simplify development, make processes more transparent and explicitly separate proprietary code into separate modules. Instead of different repositories gitlab-ee ΠΈ gitlab-se, which caused double work to be maintained, the codebase for both editions will now be developed in the same shared repository, and the Enterprise Edition (EE) and Community Edition (CE) products will be built from the same codebase. The proprietary code has been separated from the open source code and moved to the "ee/Β«.

The gitlab-ce repository that does not contain proprietary code will remain available in mirror form gitlab-fossrunning in read-only mode. The new single repository for active development is built on top of the current gitlab-ee repository, which has been renamed to the "gitlab". Currently, the migration is at the final stage - the repositories have been renamed, the merger has taken place, and almost all the tasks associated with it have already been resolved.

GitLab developers also presented patch releases 12.3.2, 12.2.6, and 12.1.12, which fixed 14 vulnerabilities, including the ability to inject arbitrary git commands through the API, bypass email confirmation when using the authentication module through Salesforce, JavaScript inline in the Markdown preview interface, capture control over other people's accounts when using the SAML module, bypassing user blocking, denial of service and leakage of confidential information about the project.

Source: opennet.ru

Add a comment