Jump to content

Infrastructure: Difference between revisions

From KDE Community Wiki
m add link
Ngraham (talk | contribs)
Phab -> GitLab
Line 24: Line 24:


; Reviews
; Reviews
: The current used system is [[Infrastructure/Phabricator | Phabricator]]. However projects are gradually moving to GitLab at [https://invent.kde.org invent.kde.org] that replaces Phabricator's code review functionality. Before introduction of Phabricator in 2015, the main review tool used to be [[Infrastructure/Review_Board | Review Board]].
: 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

Revision as of 15:11, 18 May 2020

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 (or http://sysadmin.kde.org/tickets).

Identity Accounts

All accounts in the KDE infrastructure are synchronized in a unified system called KDE Identity.

Version Control

Git
The KDE projects are mostly using Git. The repositories can be browsed online via our web interface.
Find our guidelines and informations 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, namely Jenkins.
English Breakfast Network - Static Analysis
Krazy - Code Analysis, Usage Tutorial
APIDOX - API Documentation Statistics
Sanitizer - DocBook Checker
Usability Checks

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

Localization

Project Metadata

Misc