From Fedora Project Wiki

Revision as of 00:45, 27 May 2008 by Ylynfatt (talk | contribs) (added DocsProject header)

DocsProject Header docTeam1.png

Documentation Project Workflow

Release Notes

DocsProject/ReleaseNotes/Process,, from="^

Wiki - Writing/Drafting

  1. Read DocsProject/WritingUsingTheWiki tells how to structure a document on the Wiki for portability
  2. Know the rules for WikiEditing , and especially the markup rules
  3. Use the writing draft documents page as a reference
  4. Read and understand the style guidelines

Wiki - Publication Method for Formal Documentation

  1. Content is created, worked, and edited for approval in Docs/Drafts/FooGuide as per the flow in Wiki - Writing/Drafting .
    • Editor must be a different person than the writer(s)
  2. Publication editor finalizes, copies to Docs/FooGuide.
  3. Writing team creates Docs/Drafts/<Fedora Ver Num>/FooGuide to work on branch drafts.
  4. Wiki is edited live before conversion to DocBook
  5. Conversion is conducted as per Wiki to DocBook XML
  6. Work for next release continues in Docs/Drafts/.
  7. Request peer review and editing on list.

Wiki to DocBook XML

  1. Document has completed steps in Wiki - Publication Method for Formal Documentation
  2. Edit document to confirm it matches:
  3. Use native MoinMoin tools convert the document to XML and edit the resulting work for DocBook compliance and project norms, as per the wiki to XML conversion how-to .
  4. Follow [#Full_Process_Flow full steps for getting a CVS module] for a Docbook document.

Wiki - Docs Project (e.g. DocsProject/*) Content

  1. Work live in DocsProject/* or in your UserName/ structure
  2. If working in private space, copy over content when ready

There is not much formal process around this. Projects handle this internally, and we trust our own project members to do The Right Thing. Of course, all project members should be watching each other by subscribing to Docs.*.


Project in limbo -- 2007-10-23

For details, read DocsProject/Magazine .

To write for the magazine:

  1. Designate one or more content flows or pieces of content as being under the vanilla OPL .
  2. All new submissions must have the standard OPL reference at the end of the article.
  3. If you do not have one, sign up for an account on . The Firefox plug-in made by is highly recommended.
  4. After you have written a piece of content following the guidelines, view the page in Firefox and tag the page using . Amongst any other tags you wish, be sure to use:
    • 'for:fedoradocs' as one of the tags.
    • 'fedorabeats' as another tag, if you are designating it as for the special content feed. The extension has tab-complete for tags, so you will only have to type it one time. :)
  5. Designated editors log in to the fedoradocs account and retag content suggestions that have arrived via the 'for:' tag. Content may be designated as going into one or more feeds, be linked from a Docs/Beats page, or even be the source of content for a new entry in the relnotes via Docs/Beats .

Full Process Flow, AKA 'From Idea to Document'

  1. A writer posts to fedora-docs-list with an idea or document, and the willingness to maintain it.
  2. If the consensus of the list is that the proposal is feasible, then the writer is assigned an editor and the proposal is registered on the the DocsProject/EditorAssignments Wiki page.
  3. The writer produces an initial draft and submits it to fedora-docs-list . The writer directs any queries or questions either to the mailing list or to the assigned editor. The FDP encourages writers to participate on the mailing list, which is an active forum for help and debate.
    • If the draft is Wiki-based, it should be in Docs/Drafts/ .
    • If the draft is XML-based, it needs a new module in CVS; base the draft on the template in example-tutorial and write to the list when it is ready, so that a CVS admin can respond. Making a module includes creating a bugzilla component for it.
    • In the future, drafts may also be submitted through Plone (CMS) in XHTML or other acceptable formats.
  4. A manager with access-granting privilege creates a container in CVS for the document in progress, and gives the writer CVS access. The assigned manager can assist the writer and editor in ensuring that the document is compatible with the technical requirements of Fedora.
  5. The editor negotiates any work schedule with the writer if necessary. Both may commit revisions during the editorial process, subject to the FDP document lifecycle guidance.
  6. The assigned editor notifies the assigned manager when the document is ready for final review for publication.
  7. Once the writer, editor, and manager agree that the document is complete, it is published on the official Documentation Website .

This process promotes an extremely low barrier to entry. The writer's work may be in any format desired (including plain text) up to the point of final markup, as agreed upon by the editor. The final markup will be in DocBook XML as required in the Documentation Guide. In this way, the writer and the editor form a team with a mentorship aspect, so that the writer learns DocBook XML markup (and hopefully style as well) for more effective document maintenance later.

The Wiki is used as either an interim drafting tool or as a final publishing location. The Wiki is good for very short, one-page how-to pieces, but is not used for maintaining full-length tutorials or guides. If you want to author in the Wiki, you need to use the rules at WikiEditing and WritingUsingTheWiki .

Writers may gain access to additional document containers by providing substantial improvements to those documents in association with their writers, editors, and managers. The definition of substantial is left to the editors and managers for each document, to provide maximum fluidity. Regular contributors may be added to a list of "power writers/editors" with access to all other containers.

Withdrawing a Proposed Document

A writer may email their editor and withdraw proposals or documents in progress without any prejudice. The FDP recognizes that sometimes changing circumstances result in work delays or cancellations, through no fault of the writer. It is far better to cancel than to just drop the work or disappear. The first shows maturity as a contributor, the second and third make people not willing to trust you in the future.

Fedora is a dynamic project that aims for both open participation and high standards. For these reasons, editors and managers may ask writers to amend their drafts before accepting them. If the writer does not respond, or no agreement can be reached, then the editor may request that the proposal or documents in progress be withdrawn.

The FDSCo must be made aware of withdrawals. Once a withdrawal is known, the editor then moves to close the bug component and informs the writer by email. Once a proposal or document in progress has been withdrawn, other writers may submit their own proposals for the same subject. Naturally, anyone is welcome to use the in-progress work and continue with it, as long as the work has been correctly contributed to the project and is therefore under the OPL

Stop (medium size).png Canonical documents, such as the Documentation Guide, or other high-risk content areas are somewhat more closely controlled.

Other Projects

Other projects are welcome to use these methodologies/workflows. Any that wish to have their documentation be formally part of the FDP set should contact [] .

XML - DocBook Publication Method


Getting a Document Translated

  1. Author or convert guide to XML
  2. Use XML toolchain to generate the PO file (make po)
  3. Refer to fedora-docs-list for latest process to get PO files into L10n channels .

Orphaning Documents

Refer to Full Process Flow for a complete explanation.

Wiki-based Orphans

Empty, fill me

CVS-based Orphans

Empty, fill me

Plone-based Orphans

Empty, fill me

Further Considerations

Empty, fill me