Date: Thu, 19 Mar 1998 10:15:35 +1100 From: Sue Blake <sue@welearn.com.au> To: freebsd-doc@FreeBSD.ORG Subject: what where when how who Message-ID: <19980319101535.32386@welearn.com.au>
next in thread | raw e-mail | index | archive | help
I don't know if anyone else is as confused as I am, but it sure looks that
way. We've been cross-posting willy-nilly and dragging in people who haven't
seen what's going on, and then talking about various things all at once:
Problems for people (not) trying to follow -stable, and the practicalities
of providing alternative information sources for them.
Demonstrated support implications of possible changes in 2.2.6 and how
documentation could be used to help if they happen.
Both of these might be best left on -stable?
Quick urgent documentation changes to be included in 2.2.6.
The process of conversion to DocBook, and retraining in its use.
Longer term improvements to Handbook and FAQ:
- restructuring (and/or rewriting)
- filling out what's obviously missing; asking what's wanted
- editing, testing, and selecting from what is written
Have I left anything out?
It makes it a lot easier to follow what's being addressed if only one of
these (and its implications for the others) is dealt with in a single post.
Even though (or because?) I've been watching everything, the writer's focus
is seldom clear to me.
Also, if newcomers are going to keep trickling in, maybe we need something
like a mini FAQ to explain in simple terms how all this documentation work
gets done, who does it, how, what happens to it, and what the correct
procedures are. Until now it's tended to be only those who know everything
who have contributed anything, but that's changing. The outcomes will be
good but the transition might be be rocky.
--
Regards,
-*Sue*-
find / -name "*.conf" |more
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980319101535.32386>