On Thu, 2005-12-01 at 10:23 -0500, Chad Sellers wrote: > We definitely want to make sure that many of the changes (move to reference > policy/policy v2, move to managed policy, move to policy modules, etc.) get > into the FAQ. Let me know what I can do to help. The main thing is to review the current content and make the following changes: * Remove out-of-date information * Update FAQs to reflect current reality * Add new content The best and fastest way to do this is directly in the XML in CVS. The FAQ is written in DocBook, and is very straightforward. If you haven't written in DocBook before, it is about 10% more difficult than HTML, and 100% more rewarding. To set this up, go through this page ... you want to follow the steps in "Signing Up". The most important step is 4., where you sign up for CVS access. "Submitting Your Own Documentation" covers the details of using DocBook and CVS in this project. http://fedoraproject.org/wiki/DocsProject/NewWriters If you cannot take that route, people in the Fedora Documentation Project can take your changes and incorporate them ourselves. For simplicity sake, I recommend that you use a plain text output of the FAQ to edit. We can then run a diff against another plain text output, and manually make the changes in the XML. Here is a plain text output of the latest (1.3-8): http://people.redhat.com/kwade/fedora-docs/selinux-faq-en-1.3-8.txt The next version starts at 1.5, as I've been using the minor release to indicate which version of Fedora Core this version of the FAQ relates to. Thanks very much for your interest, - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
