On Wed, Oct 09, 2002 at 04:15:57PM -0700, Gordon Messmer wrote:
> On Tue, 2002-10-08 at 15:47, Robert Monical wrote:
> > 
> > (There are valid reasons why RedHat may not
> > want this to happen.)

Like what? I can see they may not want to officially sanction it. 
 
> I've been thinking about doing the same thing.  It'll be a time
> consuming task, however.  If it's going to be any good, you'll need
> a writer who's going to review threads in the Red Hat lists, clearly
> state and organize the problems that people have, and clearly
> document the correct fix.  Pointers to archived threads may be a
> plus.  Outlining what releases of the distribution are likely to be
> affected by a FAQ is pretty much a must, which means that you'll
> have to continue maintaining old items as well.

The maintenance of such efforts is an overlooked aspect of the time
requirements. It is tempting to see all the effort go into the
writing. But many once good docs get broken as the world changes
around them, making once valid content, either broken or muddied. For
small docs not so big a deal, but I can see this as potentially a
monster. For instance, when the rpm people change syntax, this
probably breaks examples in docs all over the place :/ No telling how
many people are scratching their head over things like this from the
RPM HOWTO (copyright Red Hat!):


 7.4. Building the Package with RPM

 Once you have a spec file, you are ready to try and build your
 package. The most useful way to do it is with a command like the
 following:

 rpm -ba foobar-1.0.spec                                                               
         

Last update on this doc is 1999 :(  LDP should pull it.
 
> It'll be an ongoing process to fill out the FAQ, and it's hard to tell
> if it'll plateau off, if ever.

Doubtful, it just grows bigger and more difficult to maintain due to
unforseeable changes.

This would take several people (at least), who not only like the idea,
but have the time to make a commitment. And then a way to collaborate.
One way is cvs, or as a wiki (http://tldp.org/HOWTO/WikiText-HOWTO/).
Sourceforge might make for a good host, which not only provides cvs,
but also a permanent site to host from (important IMO too).

Then the source format needs to be decided. For portability, probably
either sgml or xml. The RH8 help browser actually looks like it takes
Docbook/xml as input (at least for gnome). xml seems to be where
everything is heading.

-- 
Hal Burgiss
 



-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to