Infrastructure: Difference between revisions
No edit summary |
(→Documentation: mention https://docs.kde.org , use active voice, link KApiDox) |
||
| (36 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
KDE software is hosted on infrastructure managed by the | [[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 == | ||
* [[/Get a Contributor Account| Get a | All accounts in the KDE infrastructure are synchronized in a unified system called KDE Identity. | ||
* [[/Get a Contributor Account| Get a Developer Account]] | |||
== Version Control == | == Version Control == | ||
The KDE projects are mostly using [http://git-scm.org Git]. The repositories can be browsed | ; 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]]. | |||
; 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]]. | |||
; 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 == | |||
Before pushing code to the repositories, the community has to review it. | |||
; Reviews | |||
: 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 | |||
: Projects are still managed with [[Infrastructure/Phabricator | Phabricator]]. This functionality will gradually be migrated to GitLab. | |||
; Continuous Building - Jenkins | |||
: To ensure high-quality, KDE software operates a [[/Continuous Integration System | continuous integration system]], namely Jenkins. | |||
;[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 == | |||
; 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: | |||
: - [[/IRC |IRC]] | |||
: - [[/Mailing-Lists | Mailing Lists]] | |||
: - [[/Jabber | Jabber]] | |||
== Documentation == | |||
; User documentation | |||
: https://docs.kde.org has KDE user documentation in many la 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]. | |||
; Techbase | |||
: https://techbase.kde.org documents the public libraries and scripting utilities for reuse by external developers. | |||
==Localization == | ==Localization == | ||
| Line 24: | Line 68: | ||
* [[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 11:01, 2 June 2020
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
- User documentation
- https://docs.kde.org has KDE user documentation in many la languages.
- API documentation
- https://api.kde.org has documentation generated from source code using the KApiDox framework.
- Techbase
- https://techbase.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