Infrastructure: Difference between revisions

From KDE Community Wiki
(Added EBN links from Techbases)
(Fix EBN links)
Line 33: Line 33:
: 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]], namely Jenkins.


;[http://englishbreakfastnetwork.org/ English Breakfast Network] - Static Analysis
;[http://ebn.kde.org/ English Breakfast Network] - Static Analysis
: [http://www.englishbreakfastnetwork.org/krazy/ Krazy ] - Code Analysis, [https://community.kde.org/Guidelines_and_HOWTOs/Code_Checking Usage Tutorial]
: [http://ebn.kde.org/krazy/ Krazy ] - Code Analysis, [https://community.kde.org/Guidelines_and_HOWTOs/Code_Checking Usage Tutorial]
: [http://www.englishbreakfastnetwork.org/apidocs/ APIDOX] - API Documentation Statistics
: [http://ebn.kde.org/apidocs/ APIDOX] - API Documentation Statistics
: [http://www.englishbreakfastnetwork.org/sanitizer/ Sanitizer] - DocBook Checker
: [http://ebn.kde.org/sanitizer/ Sanitizer] - DocBook Checker
: [http://www.englishbreakfastnetwork.org/usability/ Usability Checks]
: [http://ebn.kde.org/usability/ Usability Checks]


== Community communication ==
== Community communication ==

Revision as of 05:47, 2 June 2019

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

Every accounts in the KDE infrastructure are synchronized in a same system. It is 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 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
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