Yes, we are working on fixing the Doc Guide and Quick Start Guide to be
better. Let's keep that discussion separate. Same for the processes.
First, our process for taking submissions and turning them into docs is
entirely separate from the tool used to generate the docs.
As a project, we are centered around DocBook and XML. I think this is
the right thing to do, to have a single source for documentation that
can generate _all_ formats.
So, it should be our goal to move all _appropriate_ documentation into
that format and work from there. Eventually.
Because of the existence of tools such as DocBook Wiki, we may be able
to author bi-directionally with a Wiki. Until that is in place, Wiki
authoring is a one-time conversion to DocBook.
We will take a new doc in any format.
We will help to convert it to DocBook XML.
All new documents _must_ have a maintainer who commits to keeping the
doc up to date. That person doesn't have to be the original author.
If you have a doc that is _already_ in a Wiki and an argument why it
should stay there, let's consider it.
If you can only write in {Wiki, HTML, plain text, RTF, troff, LaTeX},
then go ahead. After we convert it for you for maintenance, you can
learn the DocBook. It's just not that hard. Really. And you can use
vi, jedit, Conglomerate, or whatever you choose. You can even use
Notepad under Windows, just don't come here complaining about getting
the toolchain to work under Cygwin. :)
- Karsten
--
Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/
gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41
Red Hat SELinux Guide
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-docs-list
