From Fedora Project Wiki

(Announcements)
(Access Control)
 
(26 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
== Docs Projects ==
 
== Docs Projects ==
  
Most of the effort undertaken by the Docs Project is oriented towards
+
The mission of the Fedora Documentation Project is to provide documentation to users and developers to improve the overall usage of Fedora. We do that by explaining the usage of certain pieces of software or systems, provide written accounts of special events (releases, etc), and provide recommendations on setting of software or systems (security, performance, etc).  
producing formal documents. Usually, these are DocBook XML documents
 
rendered in a number of formats using Publican.
 
  
In some cases, a draft is produced on the wiki, or content from various
+
While in [https://fedoraproject.org/wiki/Category:Draft_documentation draft stage], documents are [https://fedoraproject.org/wiki/Writing_for_DocBook_using_the_wiki produced on the wiki.] There material from various subject matter experts is collected.  If the author prefers, a document may be written offline. No matter how the document is drafted, it will always be [https://fedoraproject.org/wiki/Release_notes_wiki_to_XML_conversion_process converted into XML.]
subject matter experts is collected on the wikiIn some cases, writers
 
collect data (or perhaps have the expertise or otherwise do research)
 
and write directly to XML.
 
  
Documents usually end up being published to http://docs.fedoraproject.org
+
Release notes, guides, and formal documents on a specific piece of software are published in [https://fedoraproject.org/wiki/DocBook_Editor DocBook XML.] Published XML documents are converted into html, pdf, and other formats [https://fedoraproject.org/wiki/Publishing_draft_documentation_using_Publican using Publican.]
although often they are also packaged and made available through the Fedora
 
repositories.
 
  
<center>[[Image:{{{image|TLflow2.png}}}]]</center>
+
Once in the XML format, the document is checked into a [https://fedoraproject.org/wiki/Branching_a_document_in_git git branch] where it may be further edited.
 +
 
 +
Finished product is available at [http://docs.fedoraproject.org docs.fp.o] and sometimes [https://fedoraproject.org/wiki/Package_Review_Process packaged] for the Fedora [http://koji.fedoraproject.org/koji/packages?tagID=108 repositories.]
 +
 
 +
<!-- <center>[[Image:{{{image|TLflow2.png}}}]]</center> -->
 +
<center>[[Image:{{{image|TLflowLR.png}}}]]</center>
  
 
== Announcements ==
 
== Announcements ==
  
The Docs Project often works with marketing to produce announcements.
+
The Docs Project often works with [https://fedoraproject.org/wiki/Marketing marketing] to produce [https://fedoraproject.org/wiki/Final_announcement_SOP announcements.]
 
This work tends to be done almost entirely within the wiki, and rarely,
 
This work tends to be done almost entirely within the wiki, and rarely,
 
if ever is a formal document produced.  Occasionally, the Fedora Design
 
if ever is a formal document produced.  Occasionally, the Fedora Design
Line 29: Line 27:
 
Project procedures or policies.
 
Project procedures or policies.
  
<center>[[Image:{{{image|flo-announce.png}}}]]</center>
+
<!-- <center>[[Image:{{{image|flo-announce.png}}}]]</center> -->
 +
<center>[[Image:{{{image|flo-announceLR.png}}}]]</center>
  
 
== Release Notes ==
 
== Release Notes ==
  
Release notes, on the other hand, almost always follow the complete
+
[https://fedoraproject.org/wiki/Category:Release_Notes Release notes,] on the other hand, almost always follow the complete
process.  The only unexploited path is directly writing to DocBook;  
+
process.  The only unfrequented path is directly writing to DocBook;  
 
Release Notes are always developed in the wiki first.
 
Release Notes are always developed in the wiki first.
  
<center>[[Image:{{{image|flo-relnotes.png}}}]]</center>
+
<!-- <center>[[Image:{{{image|flo-relnotes.png}}}]]</center> -->
 +
<center>[[Image:{{{image|flo-relnotesLR.png}}}]]</center>
 +
 
 +
Step details:
 +
 
 +
* '''[1]''' - [[Docs Project workflow - beat writing]]
 +
 
 +
* '''[2]''' - Wiki review
 +
 
 +
* '''[3]''' - [[Converting wiki to DocBook XML]]
 +
 
 +
* '''[4]''' - Managing the document in git
 +
 
 +
* '''[5]''' - Reviewing/Editing the XML Document
 +
 
 +
* '''[6]''' - Building a document from git
 +
 
 +
* '''[7]''' - Packaging a Publican document
 +
 
 +
* '''[8]''' - [[Publishing a document with Publican]]
 +
 
 +
* '''[9]''' - [[Getting the release notes to Bodhi]]
 +
 
 +
* '''[10]''' - [[Giving_a_document_karma]]
  
 
== Guides ==
 
== Guides ==
Line 46: Line 68:
 
and there is no reason input cannot be collected on the wiki.
 
and there is no reason input cannot be collected on the wiki.
  
<center>[[Image:{{{image|flo-guides.png}}}]]</center>
+
<!-- <center>[[Image:{{{image|flo-guides.png}}}]]</center> -->
 +
<center>[[Image:{{{image|flo-guidesLR.png}}}]]</center>
  
 
== Access Control ==
 
== Access Control ==
  
Each of the various repositories has access controlled by some FAS group.  Access to the
+
The Fedora Docs Project has three access groups for contributors: '''Docs, Doc-Writers, and Doc-Publishers.'''
wiki is encouraged, rather than controlled, so access to the wiki is available to anyone who
 
has signed the contributor agreement.
 
  
Contributors who have learned to write XML and become familiar with git are entered
+
1. Members of '''Docs''' are part of the Fedora Docs Project as voting contributors. They get write access to the wiki, as does everyone with a [https://admin.fedoraproject.org/accounts Fedora Access Account.] To become a member of '''Docs''', [https://fedoraproject.org/wiki/Join_the_Docs_Project Join the Docs Project] and you will be 'sponsored' by someone in the The Fedora Docs Project leadership. Then you may work on writing projects on the wiki or 'garden' existing pages.
into the Docs writers group, allowing access to the git repositories. Each document is
 
maintained in a git repository, and the writer group grants access to all of these.
 
  
When a contributor has developed the skills necessary to prepare documents for docs.fp.o
+
2. Members of '''Doc-Writers''' are part of the Fedora Docs as voting contributors who have a document to commit and maintain in the git repository. Each guide is managed in [https://fedoraproject.org/wiki/Docs_Project_guides_table various repositories] by members of this group.  Promotion from Docs to Doc-Writers requires application on FAS and a sponsor. Contributors who have learned to write XML and become familiar with git are entered into the Docs writers group, allowing access to the git repositories. Each document is maintained in a git repository, and the writer group grants access to all of these.  
he is given entry to the publisher's group, which permits committing changes to the
 
Fedora documentation website. If a contributor needs to package a document, the packaged
 
document is submitted for review, and once successfully reviewed, the contributor gets
 
packager privilege, and may
 
push that package to the Fedora repositories.
 
  
<center>[[Image:{{{image|docs-permissions.png}}}]]</center>
+
 
 +
3. Members of '''Doc-Publishers''' are part of the Fedora Docs as voting contributors who have a document to commit and maintain in the docs.fp.o hich permits committing changes to the
 +
Fedora documentation website. Promotion from Docs to Doc-Publishers requires application on FAS and a sponsor.
 +
 
 +
 
 +
Other: If a contributor needs to package a document, the packaged document is submitted for review, and once successfully reviewed, the contributor gets packager privilege, and may push that package to the Fedora repositories.
 +
 
 +
<!-- <center>[[Image:{{{image|docs-permissions.png}}}]]</center> -->
 +
<center>[[Image:{{{image|docs-permissionsLR.png}}}]]</center>
 +
 
 +
==Translations==
 +
 
 +
The following page details the translation process:
 +
 
 +
[[Docs_Project_workflow - translations]]
  
 
== Note: Source ==
 
== Note: Source ==
Line 71: Line 99:
 
The sources for the above images are text:
 
The sources for the above images are text:
  
* [[Docs_Workflow_TLflow2.dot]]
+
<!--* [[Docs_Workflow_TLflow2.dot]]
 
* [[Docs_Workflow_flo-announce.dot]]
 
* [[Docs_Workflow_flo-announce.dot]]
 
* [[Docs_Workflow_flo-relnotes.dot]]
 
* [[Docs_Workflow_flo-relnotes.dot]]
 
* [[Docs_Workflow_flo-guide.dot]]
 
* [[Docs_Workflow_flo-guide.dot]]
 +
* [[Docs_Workflow_docs-permissions.dot]]-->
 +
* [[Docs_Workflow_TLflowLR.dot]]
 +
* [[Docs_Workflow_flo-announceLR.dot]]
 +
* [[Docs_Workflow_flo-relnotesLR.dot]]
 +
* [[Docs_Workflow_flo-guideLR.dot]]
 +
* [[Docs_Workflow_docs-permissionsLR.dot]]
 +
 +
If you wish to edit the above images, install the {{Package|graphiz}} package and save the text on one of the above pages to a text file.  Then execute the command:
 +
 +
  dot -Tpng -o TLflow2.png TLflow2.dot
  
 +
(or whichever file you select).  Edit the source and repeat until the image is how you desire. Note that the various flow- files are copies of TLflow2 with various sections grayed and the size reduced.  Then update the source wiki page for those following you, and upload the png to the wiki.  Refresh this page and be sure it appears in context correctly.
  
 
= Old Material still to be incorporated =
 
= Old Material still to be incorporated =
 +
 +
{{admon/note| Out of date | Much of the material below is badly out of date or in need of considerable editing.  It has been commented out for now.}}
 +
 +
<!--
  
 
{{Anchor|WikiWritingDrafting}}
 
{{Anchor|WikiWritingDrafting}}
Line 179: Line 222:
  
 
Refer to [[#Full_Process_Flow| Full Process Flow]]  for a complete explanation.
 
Refer to [[#Full_Process_Flow| Full Process Flow]]  for a complete explanation.
 +
 +
-->
  
 
[[Category:Docs Project process]]
 
[[Category:Docs Project process]]

Latest revision as of 20:02, 27 October 2010

Cog.png
This page needs some love
This page should be revised or reconstructed to be more helpful. Problems may include being out of step with current team or project status or process.
DocsProject Header docTeam1.png


Docs Projects

The mission of the Fedora Documentation Project is to provide documentation to users and developers to improve the overall usage of Fedora. We do that by explaining the usage of certain pieces of software or systems, provide written accounts of special events (releases, etc), and provide recommendations on setting of software or systems (security, performance, etc).

While in draft stage, documents are produced on the wiki. There material from various subject matter experts is collected. If the author prefers, a document may be written offline. No matter how the document is drafted, it will always be converted into XML.

Release notes, guides, and formal documents on a specific piece of software are published in DocBook XML. Published XML documents are converted into html, pdf, and other formats using Publican.

Once in the XML format, the document is checked into a git branch where it may be further edited.

Finished product is available at docs.fp.o and sometimes packaged for the Fedora repositories.

TLflowLR.png

Announcements

The Docs Project often works with marketing to produce announcements. This work tends to be done almost entirely within the wiki, and rarely, if ever is a formal document produced. Occasionally, the Fedora Design Team will take the wiki document and use it as the basis for a glossy document or brochure. A similar process, obviously without the engagement of Marketing, is used when documenting Docs Project procedures or policies.

Flo-announceLR.png

Release Notes

Release notes, on the other hand, almost always follow the complete process. The only unfrequented path is directly writing to DocBook; Release Notes are always developed in the wiki first.

Flo-relnotesLR.png

Step details:

  • [2] - Wiki review
  • [4] - Managing the document in git
  • [5] - Reviewing/Editing the XML Document
  • [6] - Building a document from git
  • [7] - Packaging a Publican document

Guides

Guides are typically not developed in the wiki but rather written straight to DocBook. In addition, Guides are typically not packaged. The emphasis here is on typical, Guides are sometimes packaged and there is no reason input cannot be collected on the wiki.

Flo-guidesLR.png

Access Control

The Fedora Docs Project has three access groups for contributors: Docs, Doc-Writers, and Doc-Publishers.

1. Members of Docs are part of the Fedora Docs Project as voting contributors. They get write access to the wiki, as does everyone with a Fedora Access Account. To become a member of Docs, Join the Docs Project and you will be 'sponsored' by someone in the The Fedora Docs Project leadership. Then you may work on writing projects on the wiki or 'garden' existing pages.

2. Members of Doc-Writers are part of the Fedora Docs as voting contributors who have a document to commit and maintain in the git repository. Each guide is managed in various repositories by members of this group. Promotion from Docs to Doc-Writers requires application on FAS and a sponsor. Contributors who have learned to write XML and become familiar with git are entered into the Docs writers group, allowing access to the git repositories. Each document is maintained in a git repository, and the writer group grants access to all of these.


3. Members of Doc-Publishers are part of the Fedora Docs as voting contributors who have a document to commit and maintain in the docs.fp.o hich permits committing changes to the Fedora documentation website. Promotion from Docs to Doc-Publishers requires application on FAS and a sponsor.


Other: If a contributor needs to package a document, the packaged document is submitted for review, and once successfully reviewed, the contributor gets packager privilege, and may push that package to the Fedora repositories.

Docs-permissionsLR.png

Translations

The following page details the translation process:

Docs_Project_workflow - translations

Note: Source

The sources for the above images are text:

If you wish to edit the above images, install the Package-x-generic-16.pnggraphiz package and save the text on one of the above pages to a text file. Then execute the command:

  dot -Tpng -o TLflow2.png TLflow2.dot

(or whichever file you select). Edit the source and repeat until the image is how you desire. Note that the various flow- files are copies of TLflow2 with various sections grayed and the size reduced. Then update the source wiki page for those following you, and upload the png to the wiki. Refresh this page and be sure it appears in context correctly.

Old Material still to be incorporated

Note.png
Out of date
Much of the material below is badly out of date or in need of considerable editing. It has been commented out for now.