Archives:Docs release standard operating procedures: Difference between revisions

Revision as of 19:59, 21 November 2009

All guides must be written in DocBook XML and be built by Publican (current version is 1.x). Source for these guides should be done using Fedora Hosted (git (preferred), svn, or cvs).

Build your guides in html, html-single, and PDF. These files should be uploaded to the Fedora CVS to by synced to the http://docs.fedoraproject.org website.

Your guides should be submitted to the translators for translation. When a guide reaches 100% it should be built in html, html-single, and PDF and uploaded to the CVS.

@@ Line 1: / Line 1: @@
+== Official Guides ==
+* All guides must be written in DocBook XML and be built by Publican (current version is 1.x).  Source for these guides should be done using Fedora Hosted (git (preferred), svn, or cvs).
+* Build your guides in html, html-single, and PDF.  These files should be uploaded to the Fedora CVS to by synced to the http://docs.fedoraproject.org website.
+* Your guides should be submitted to the translators for translation.  When a guide reaches 100% it should be built in html, html-single, and PDF and uploaded to the CVS.
+== Draft Documentation ==
+== Wiki Documentation ==
 [[Category:Docs Project SOP]]
-* Single page HTML for each language
-* Downloadable tarballs of HTML
-* Condensed version that is just what is different for the release
-** Perhaps section at the end of each chapter?
-** Avoid interweaving fixed content for new users and new content for old users
-* Update schedule for notes and guides
-* Hold a 'lessons learned' meeting soon after the release