Infrastructure: Difference between revisions

From KDE Community Wiki
m (→‎Code quality: Jenkins -> Gitlab CI)
 
(44 intermediate revisions by 14 users not shown)
Line 1: Line 1:
KDE software is hosted on infrastructure managed by the [http://sysadmin.kde.org/ KDE Sysadmins].
[[File:Mascot konqi-app-system.png|thumbnail|right|[[Konqi]] is working the infrastructure!]]
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 ==
== Identity Accounts ==
Every accounts in the KDE infrastructure are synchronized in a same system. It is called KDE Identity.
All accounts in the KDE infrastructure are synchronized in a unified system called [https://identity.kde.org/ KDE Identity] which is free to use.
 
* [[/Get a Contributor Account| Get a Contributor Account]]


== Version Control ==
== Version Control ==
The KDE projects are mostly using [http://git-scm.org Git]. The repositories can be browsed on our [https://quickgit.kde.org QuickGit] and managed on [https://projects.kde.org KDE Projects].
; 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] ([[Infrastructure/GitLab|GitLab]]).
: Find [[/Git | our guidelines]] and information about the [[/Github Mirror | GitHub mirror]].


Find guidelines [[/Git | here]].
; SVN
: Some projects such as i18n (to localize the programs) or some websites still use [http://svnbook.red-bean.com/ SVN]. The repository can be browsed on https://websvn.kde.org/.  Some guidelines could be found [[/Subversion | here]].


Some projects such as i18n (to localize the programs) or some websites still use [http://svnbook.red-bean.com/ SVN]. The repository can be browsed on https://websvn.kde.org/.  Some guidelines could be found [[/Subversion | here]].
; Commit access
: Find out how to [[/Get a Developer Account|get commit access]].


Find out how to [[/Get a Contributor Account|get commit access]].
== Content distribution ==
In order to [[/Content Distribution | distribute]] and spread the software and other data produced by the community, KDE uses mainly two distribution networks.


== Code quality ==
== Code quality ==
Line 19: Line 23:


; Reviews
; Reviews
: The current used system is [[Infrastructure/Review_Board | Review Board]]. However projects are heavily encouraged to move to the new system: [[Infrastructure/Phabricator | Phabricator]].
: The current used system is [[Infrastructure/GitLab | GitLab]]. Before May 2020, KDE used [[Infrastructure/Phabricator | Phabricator]], and before 2015, KDE used [[Infrastructure/Review_Board | Review Board]].


; Project Management
; Project Management
: Projects are now managed with [[Infrastructure/Phabricator | Phabricator]].
: Projects are still managed with [[Infrastructure/Phabricator | Phabricator]]. This functionality will gradually be migrated to GitLab.


; Continuous Building - Jenkins
; Continuous Building - Jenkins
:
: To ensure high-quality,  KDE software operates a [[/Continuous Integration System | continuous integration system]] using Gitlab CI.
 
== Community communication ==
; Blogging
: KDE Developers are encouraged to blog about their actions. More information [[/Blogging |about blogging here]].
 
; Emails
: KDE provides [[/Email | email aliases]] in @kdemail.net and @kde.org.
 
; Communication channels
: Several communication channels are maintained by KDE:
: - [[Matrix | Matrix]]
: - [[/IRC | IRC]]
: - [[/Mailing-Lists | Mailing Lists]]
: - [[/Jabber | 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 [https://api.kde.org/frameworks/kapidox/html/index.html KApiDox framework].


; English Breakfast Network - Static Analysis
; Develop
:
: https://develop.kde.org documents the public libraries and scripting utilities for reuse by external developers.


==Localization ==
==Localization ==
Line 37: Line 62:
* [[Infrastructure/Project_Metadata|Project metadata]], used for various internal and external scripts to aid in source code [http://kdesrc-build.kde.org compilation], [http://sysadmin.kde.org/services/continuous-integration/ continuous integration], translation, and other administrative tasks.
* [[Infrastructure/Project_Metadata|Project metadata]], used for various internal and external scripts to aid in source code [http://kdesrc-build.kde.org compilation], [http://sysadmin.kde.org/services/continuous-integration/ continuous integration], translation, and other administrative tasks.
* [[Infrastructure/Project_Structure|Project structure]]
* [[Infrastructure/Project_Structure|Project structure]]
* [https://projects.kde.org/api/ REST API]
== Misc ==
* [https://geoip.kde.org GeoIP API]

Latest revision as of 14:46, 13 October 2023

Konqi is working the infrastructure!

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

Misc