Infrastructure: Difference between revisions

From KDE Community Wiki
No edit summary
(17 intermediate revisions by 3 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 (or http://sysadmin.kde.org/tickets).


== Identity Accounts ==
== Identity Accounts ==
Line 7: Line 8:


== 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://commits.kde.org web interface].
:  Find [[/Git | our guidelines]] and informations 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 Contributor 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 32: Line 38:
== Community communication ==
== Community communication ==
; Blogging
; Blogging
: KDE Developers are encourage to blog about their actions. More information [[/Blogging about blogging here]].
: 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:
: - [[/IRC |IRC]]
: - [[/Mailing-Lists | Mailing Lists]]
: - [[/Jabber | Jabber]]


== Documentation ==
== Documentation ==
Line 50: Line 63:
* [[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]

Revision as of 10:46, 4 December 2018

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

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