注意:
The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Help:Funtoo Editing Guidelines"
Jump to navigation
Jump to search
(→Basics) |
|||
Line 23: | Line 23: | ||
{{important|Note that if you experience some problem with Funtoo Linux, during installation or otherwise, the proper course of action is to not add a work-around to our documentation, but to ''open a bug on our bug tracker.'' This is important because the problem you experienced may be a legitimate bug and the solution may be to fix the bug rather than add a work-around to our documentation. We may end up fixing a bug, making a documentation fix, or possibly both.}} | {{important|Note that if you experience some problem with Funtoo Linux, during installation or otherwise, the proper course of action is to not add a work-around to our documentation, but to ''open a bug on our bug tracker.'' This is important because the problem you experienced may be a legitimate bug and the solution may be to fix the bug rather than add a work-around to our documentation. We may end up fixing a bug, making a documentation fix, or possibly both.}} | ||
[[Category:Wiki Development]] | [[Category:Wiki Development]] | ||
[[Category:Official Documentation]] | [[Category:Official Documentation]] |
Revision as of 03:50, February 24, 2019
Description:
This page documents the editing guidelines for the Funtoo Wiki.
Authors:
Subpages:
Thanks for your interest in contributing to the the Funtoo wiki!
Types of Edits
Before we get started, let's review what changes are okay to make, and what changes are not okay:
Type of Change | Okay? |
---|---|
Grammar/spelling fixes | Yes |
New wiki content | Yes |
New package information | Yes |
Adding to existing article | Maybe -- see below |
Adding missing/incomplete information | Yes |
Making corrections | Yes |
Adding work-arounds to problems experienced | No - open bug first on bug tracker. |
Important
Note that if you experience some problem with Funtoo Linux, during installation or otherwise, the proper course of action is to not add a work-around to our documentation, but to open a bug on our bug tracker. This is important because the problem you experienced may be a legitimate bug and the solution may be to fix the bug rather than add a work-around to our documentation. We may end up fixing a bug, making a documentation fix, or possibly both.