Guidelines and HOWTOs/Documentation in wikis: Difference between revisions
| Line 37: | Line 37: | ||
; What it is | ; What it is | ||
For instance, you wrote a library to deal with maps: you might want to write some tutorials of how to link to the library, get in touch with other users of the library, find the tarballs, etc... | For instance, you wrote a library to deal with maps: you might want to write some tutorials of how to link to the library, get in touch with other users of the library, find the tarballs, etc... | ||
Another example would be Plasma writing there how to write a plasmoid based their tools or Kirigami describing how to get started with the kirigami libs. | |||
; What it is NOT | ; What it is NOT | ||
Revision as of 18:28, 27 February 2017
At KDE we have 3 wikis:
- Community: it contains everything for your team work and the resources for the KDE community. (more on this in the Community chapter
- Techbase: it contains the documentation, links and tutorial for your libraries. This is aimed for external developers that use your products. (more on this in the Techbase chapter)
- Userbase: it contains the user manuals. How to use your application? What does which button? How to achieve a given operation? Theses are all questions to be answered there.
Community
https://community.kde.org has two focuses:
- centralizing the KDE resources
- organizing the teamwork on your Project.
Community Resources
All the KDE resources are documented here.
If you are looking for (or want to add) a tutorial about general procedures in KDE, go under Guidelines and HOWTOs. You'll find useful information about our Infrastructure, Schedules and other ways to Get Involved
Projects
- Structure
Your project should have a page at https://community.kde.org/Your_Project_Name. This is the entry point of your internal resources. All your page should have the format https://community.kde.org/Your_Project_Name/XXX, with the depth you find relevant. We do not enforce any structure as you can see in the examples below.
- Content
You have to think about it as the resource for your fellow contributors. What development environment do I need? or How do I compile the source or What are the code guidelines or What are the contact channel to get started are all valid questions to be answered here.
You can put add your schedules, your meeting minutes, the architecture of your program and everything you find relevant. Don't forget to use Phabricator do organize your tasks and todos !
- Examples
Techbase
https://techbase.kde.org is like Userbase but for external developers.
- What it is
For instance, you wrote a library to deal with maps: you might want to write some tutorials of how to link to the library, get in touch with other users of the library, find the tarballs, etc...
Another example would be Plasma writing there how to write a plasmoid based their tools or Kirigami describing how to get started with the kirigami libs.
- What it is NOT
- Tutorial about general How-Tos in KDE are not supposed to be there => https://community.kde.org
- Team work and bugs to fix are not supposed to be there => https://community.kde.org, https://phabricator.kde.org or https://bugs.kde.org
- Good Examples
Userbase
https://userbase.kde.org contains your user documentation, the same that should appear when the user asks for About>Help