WikiGardening

Revision 3 as of 2010-06-07 17:23:11

Clear message

This page aims to guide the creation and style for new Wiki pages in the Kernel/ Documentation section of the page. The currently outstanding gardening tasks can be found on the Kernel/WikiToDo.

Consistency

We should be aiming for a consistent look and feel. At a minimum all pages in the kernel documentation should include the standard Kernel/MenuBar:

  • <<Include(Kernel/MenuBar)>>

Those which are longer should have a floating table of contents:

  • ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>||

Namespace Layout

Pretty much all pages should be placed under the Kernel toplevel directory. Within this we should try and place the pages under the broad topics shown in the menu bar (at the top of this page). Pages which are clearly in a section should be included within that section. Within each section any repeated instructions (see below) should be included in a section specific Action subdirectory.

Section

Description

Prefix

Kernel Debugging

Information and techniques related to diagnosing and debugging kernel issues

Kernel/Debugging

Bug Triage

Information related to how to Triage kernel bugs

Kernel/BugTriage

Kernel Development

Information on how to develop against the Ubuntu kernel

Kernel/Dev

Advanced Topics

Other more esoteric information

Kernel/Advanced

Repeated Instructions

It will often be appropriate to try and include clear instructions on an activity (for example checkout an Ubuntu repository) in more than one place in the documentation. It is imperative that all of these cases have the same instructions and that they are easily maintainable. To allow them to remain within the original flow of the text, these should be pulled out to separate page fragments which can then be included directly. Each should include the title as a second level (==) header:

  • == Obtaining the source for an Ubuntu release ==
    
    The master source for each Ubuntu release is maintained
    in a git repository on the kernel.ubuntu.com, at the
    URL below:
    [...]

These can then be included as required using the incantation below:

  • <<Include Action/ObtainSource>>

Where the title is not appropriate for the flow of your document you could use the following: