Infrastructure

KDE software is hosted on infrastructure managed by the KDE Sysadmins.

Identity Accounts

Every accounts in the KDE infrastructure are synchronized in a same system. It is called KDE Identity.

• Get a Developer Account

Version Control

The KDE projects are mostly using Git. The repositories can be browsed on our QuickGit and managed on KDE Projects.

Find guidelines here.

Some projects such as i18n (to localize the programs) or some websites still use SVN. The repository can be browsed on https://websvn.kde.org/. Some guidelines could be found here.

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.

Reviews

The current used system is Review Board. However projects are heavily encouraged to move to the new system: Phabricator.

Project Management

Projects are now managed with Phabricator.

Continuous Building - Jenkins

To ensure high-quality, KDE software operates a continuous integration system, namely Jenkins.

English Breakfast Network - Static Analysis

Community communication

Blogging

KDE Developers are encouraged to blog about their actions. More information about blogging here.

Emails

KDE provides email aliases in @kdemail.net and @kde.org.

Communication channels

Several communication channels are maintained by KDE:

- IRC

- Mailing Lists

- Jabber

Documentation

API documentation

https://api.kde.org, where the kapidox documention can be found.

Techbase

https://techbase.kde.org, where the public libraries and scripting utilities are documented to be reused by external developers

Project Metadata

• Project metadata, used for various internal and external scripts to aid in source code compilation, continuous integration, translation, and other administrative tasks.
• Project structure