From owner-freebsd-doc Wed Mar 18 15:16:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19216 for freebsd-doc-outgoing; Wed, 18 Mar 1998 15:16:03 -0800 (PST) (envelope-from owner-freebsd-doc@FreeBSD.ORG) Received: from phoenix.welearn.com.au (suebla.lnk.telstra.net [139.130.44.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19172 for ; Wed, 18 Mar 1998 15:15:55 -0800 (PST) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.8.5/8.8.5) id KAA15540; Thu, 19 Mar 1998 10:15:40 +1100 (EST) Message-ID: <19980319101535.32386@welearn.com.au> Date: Thu, 19 Mar 1998 10:15:35 +1100 From: Sue Blake To: freebsd-doc@FreeBSD.ORG Subject: what where when how who Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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