Gardening/docwebsites: Difference between revisions
Appearance
Jeremy Paul (talk | contribs) Add docwebsites love project objectives |
No edit summary |
||
Line 3: | Line 3: | ||
=== Practicalities === | === Practicalities === | ||
* Code is at | * Code is at: | ||
** englishbreakfastnetwork.org: https://projects.kde.org/projects/websites/quality-kde-org/repository | |||
** docs.kde.org: https://projects.kde.org/projects/websites/docs-kde-org/repository | |||
* We will be working on the master branch | * We will be working on the master branch | ||
* For patches: | * For patches: |
Revision as of 07:37, 27 March 2015
Gardening Day
One saturday in May 2015 we will hold a Gardening Day for documentation websites on #kde-devel
Practicalities
- Code is at:
- englishbreakfastnetwork.org: https://projects.kde.org/projects/websites/quality-kde-org/repository
- docs.kde.org: https://projects.kde.org/projects/websites/docs-kde-org/repository
- We will be working on the master branch
- For patches:
- Smaller ones use http://paste.kde.org/ and seek approval in IRC
- Bigger ones please use http://reviewboard.kde.org/
- For bug triaging use the gardening field
- + for really critical bugs that should be fixed as part of gardening
- ? for easy bugs
- - for out of scope (doesn't mean they are not important nor real, just that are not in scope for the gardening, i.e. they may be very corner case or need deep knowledge of the code base)
Objectives
- Test/discover/file bugs against issues on api.kde.org, englishbreakfastnetwork.org and docs.kde.org
- api.kde.org and englishbreakfastnetwork.org are not showing api for kf5 based applications and libraries or running kf5 based checks on kf5 based applications (and they are shown under KDE 4.latest which is incorrect). Thus the next 3 objectives.
- Add kf5 based application and library apidocs to api.kde.org
- Add kf5 based application and library code checks to ebn
- Add kf5 based application and library documentation to docs.kde.org
- Improve api.kde.org, ebn, and docs.kde.org to only update what has changed rather than everything (which takes up to 30 hours)
- Create bug products for each of the above sites (or one product for websites with a subproject for each)