Sam Folk-Williams wrote:
On Tue, 2006-11-07 at 05:58 -0800, Karsten Wade wrote:
But ... hmm ... there has been discussion in the past of having a
kbase.fedoraproject.org that is a stand-alone knowledgebase. If we
opened it to all Fedora account holders and had kbase articles queued
for this team to edit (part of a workflow), maybe we could build up
something very useful. I could see many discussions on e.g. fedora-list
or fedoraforum.org being worth migrating into a kbase article.
+1 on this. I would really like to see a kbase for Fedora. I think it's
an excellent way to organize a large number of targeted how-to articles.
It can also be a lot easier for a contributor to write a brief kbase
than to get involved with a larger "guide" type of document. Then, guide
writers can pull from the kbase for ideas as well.
I think it would be better to avoid having too much information in
FAQ-style, since although referencable, they are not very readable or
usable as a manual.
On the other hand, it would be great if we had that information in the
guides/chapters and compile a set of FAQ that the answer is like "More
information for this can be found <there>. For customizing it, see
Chapter <Foo>, paragraph <Bar>".
I believe the most difficult part of doing the Handbook would be to
decide on a good hierarchy that strikes a good balance between
usability/quality and reference-able.
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/ref-guide/
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/security-guide/
(e.g. the vpn question)
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/step-guide/
Heh, I could never forget those. :)
Obviously these are not fedora docs and most people using fedora know
about them, however not everybody, and these are not compatible
everywhere, but I am sure there are some useful peaces. So they should
be referenced somehow. (sometimes better than empty wiki pages)
We may be able to fold some of that content directly in, rewritten to
match Fedora. Let's not make any plans that require that content, which
is too bad since it would provide such a huge base to work from :(, but
let's be prepared to be surprised.
Who should we contact to move some strings to free those docs? It would
be *great* if we could use them.
-d
--
Dimitris Glezos
Jabber ID: glezos@xxxxxxxxxx, PGP: 0xA5A04C3B
http://dimitris.glezos.com/
"He who gives up functionality for ease of use
loses both and deserves neither." (Anonymous)
--
--
fedora-docs-list mailing list
fedora-docs-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-docs-list
