I'd also like to follow the same model Zones has -- contributions to a
maintainer or set of maintainers, a review period, then incorporation
into the 'official' FAQ, hosted on the community site.
This will become easier once we've got Subversion support, as putting
back changes to the FAQ can be like putting back changes for code.
(I'm probably repeating what I said last week -- apologies for that.)
It'd be awesome if there was a S10 'collector' FAQ which pointed to
some of the most frequent of the frequently asked questions, but lets'
figure out how to do that by storing the component-specific information
in the component-specific FAQs and linking, rather than diverging
information and forcing folks to do reviews of many different
'official' sources, and reconcile conflicting information on their own.
My specific proposal for movement forward with an official SMF
community FAQ:
- Kathy, Christine, and Bernd (if you guys want, and anyone
else who wants to join the effort) take a first pass at combining
and organizing the two current disparate SMF FAQs. Kathy, do
you have time to take the lead on the organization? The format
would need to be in something we can easily format as HTML: perhaps
the stuff the docs community has published might be useful, as
it can convert to all sorts of interesting output formats:
http://www.opensolaris.org/os/community/documentation/doc_collab/tools/asciidocqsg/
- Publish a combined version for review, and drive review to
completion on smf-discuss. (I'm happy if you guys decide that this
first version is one of the existing FAQs. I'd just love to leave
it for you guys to decide, as you've put energy into it.)
- Once the review is complete, we'll host the source and post
prominently on the SMF community.
liane
--
Liane Praza, Solaris Kernel Development
liane.praza at sun.com - http://blogs.sun.com/lianep
