Note

The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.

Difference between revisions of "Help:Funtoo Editing Guidelines"

From Funtoo
Jump to navigation Jump to search
Line 5: Line 5:
|description=This page documents the editing guidelines for the Funtoo Wiki.}}
|description=This page documents the editing guidelines for the Funtoo Wiki.}}
{{Subpages|Basics,Images,Headings,Inline Code,Tables,Page Tools,Tips and Warnings,Source Code,Text Files,ConsoleOutput,Packages,Kernel,Translations,User Pages}}
{{Subpages|Basics,Images,Headings,Inline Code,Tables,Page Tools,Tips and Warnings,Source Code,Text Files,ConsoleOutput,Packages,Kernel,Translations,User Pages}}


'''Thanks for your interest in contributing to the the Funtoo wiki!'''  
'''Thanks for your interest in contributing to the the Funtoo wiki!'''  

Revision as of 03:55, February 24, 2019

Description:
This page documents the editing guidelines for the Funtoo Wiki.


Thanks for your interest in contributing to the the Funtoo wiki!

Before we get started, it's a good idea to review what kinds of changes to the wiki we're looking for, and what kind of changes we're not looking for. While we love wiki contributions, the wiki can be used in a way that is not ideal. Generally, anything that isn't a workaround for a problem you are experiencing is generally fair game for the wiki. Here are the types of changes that are OK and not OK:

Type of ChangeOkay?
Grammar/spelling fixesYes
New wiki contentYes
New package informationYes
Adding to existing articleMaybe -- see below
Adding missing/incomplete informationYes
Making correctionsYes
Adding work-arounds to problems experiencedNo - open bug first on bug tracker.

So, make a mental note -- 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, or if your problem is potentially a support issue, ask for help on IRC or our forums. 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, or the problem may be an issue that requires support rather than an actual documentation fix.