Infrastructure: Difference between revisions

Latest revision as of 14:46, 13 October 2023

KDE software is hosted on infrastructure managed by the KDE Sysadmins. If needed, a ticket can be opened on https://go.kde.org/systickets.

Identity Accounts

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

Version Control

Git: 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.

SVN: 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.

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.

Reviews: 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 using Gitlab CI.

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:; - Matrix; - IRC; - Mailing Lists; - Jabber

Documentation

User documentation: https://docs.kde.org has KDE user documentation in many languages.

API documentation: https://api.kde.org has documentation generated from source code using the KApiDox framework.

Develop: https://develop.kde.org documents the public libraries and scripting utilities for reuse by external developers.

Localization

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
REST API

Misc

GeoIP API

@@ Line 7: / Line 7: @@
 == Version Control ==
 ; Git
-: The KDE projects are mostly using [http://git-scm.org Git]. The repositories can be browsed online via our [https://invent.kde.org Invent] (GitLab).
+: The KDE projects are mostly using [http://git-scm.org Git]. The repositories can be browsed online via our [https://invent.kde.org Invent] ([[Infrastructure/GitLab|GitLab]]).
 :  Find [[/Git | our guidelines]] and information about the [[/Github Mirror | GitHub mirror]].
@@ Line 29: / Line 29: @@
 ; Continuous Building - Jenkins
-: To ensure high-quality,  KDE software operates a [[/Continuous Integration System | continuous integration system]], namely Jenkins.
+: To ensure high-quality,  KDE software operates a [[/Continuous Integration System | continuous integration system]] using Gitlab CI.
-;[http://ebn.kde.org/ English Breakfast Network] - Static Analysis
-: [http://ebn.kde.org/krazy/ Krazy ] - Code Analysis, [https://community.kde.org/Guidelines_and_HOWTOs/Code_Checking Usage Tutorial]
-: [http://ebn.kde.org/apidocs/ APIDOX] - API Documentation Statistics
-: [http://ebn.kde.org/sanitizer/ Sanitizer] - DocBook Checker
-: [http://ebn.kde.org/usability/ Usability Checks]
 == Community communication ==
@@ Line 58: / Line 52: @@
 : https://api.kde.org has documentation generated from source code using the [https://api.kde.org/frameworks/kapidox/html/index.html KApiDox framework].
-; Techbase
+; Develop
-: https://techbase.kde.org documents the public libraries and scripting utilities for reuse by external developers.
+: https://develop.kde.org documents the public libraries and scripting utilities for reuse by external developers.
 ==Localization ==