From KDE Community Wiki
Revision as of 19:55, 5 August 2023 by Argonel (talk | contribs) (linkify first instance)
Konqi is working the infrastructure!

KDE software is hosted on infrastructure managed by the KDE Sysadmins. If needed, a ticket can be opened on

Identity Accounts

All accounts in the KDE infrastructure are synchronized in a unified system called KDE Identity which is free to use.

Version Control

The KDE projects are mostly using Git. The repositories can be browsed online via our Invent (GitLab).
Find our guidelines and information about the GitHub mirror.
Some projects such as i18n (to localize the programs) or some websites still use SVN. The repository can be browsed on Some guidelines could be found here.
Commit access
Find out how to get commit access.

Content distribution

In order to distribute and spread the software and other data produced by the community, KDE uses mainly two distribution networks.

Code quality

Before pushing code to the repositories, the community has to review it.

The current used system is GitLab. Before May 2020, KDE used Phabricator, and before 2015, KDE used Review Board.
Project Management
Projects are still managed with Phabricator. This functionality will gradually be migrated to GitLab.
Continuous Building - Jenkins
To ensure high-quality, KDE software operates a continuous integration system, namely Jenkins.

Community communication

KDE Developers are encouraged to blog about their actions. More information about blogging here.
KDE provides email aliases in and
Communication channels
Several communication channels are maintained by KDE:
- Matrix
- Mailing Lists
- Jabber


User documentation has KDE user documentation in many languages.
API documentation has documentation generated from source code using the KApiDox framework.
Develop documents the public libraries and scripting utilities for reuse by external developers.


Project Metadata