From owner-freebsd-doc Mon Jan 21 16:50:47 2002 Delivered-To: freebsd-doc@freebsd.org Received: from guppy.vub.ac.be (guppy.vub.ac.be [134.184.129.2]) by hub.freebsd.org (Postfix) with ESMTP id E660637B42A for ; Mon, 21 Jan 2002 16:50:30 -0800 (PST) Received: from fort-knox.rave.org (igwe15.vub.ac.be [134.184.49.15]) by guppy.vub.ac.be (8.9.1b+Sun/3.17.1.ap (guppy)) id BAA11793; Tue, 22 Jan 2002 01:49:56 +0100 (MET) for Received: (qmail 1548 invoked by uid 1979); 22 Jan 2002 00:50:00 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Jan 2002 00:50:00 -0000 Date: Tue, 22 Jan 2002 01:50:00 +0100 (CET) From: Wouter Van Hemel To: Michael Lucas Cc: Tom Rhodes , Subject: Re: Practicalities of FAQ->Handbook migrations In-Reply-To: <20020121180114.A56458@blackhelicopters.org> Message-ID: PGP: 0B B4 BC 28 53 62 FE 94 6A 57 EE B8 A6 E2 1B E4 (0xAA5412F0) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 21 Jan 2002, Michael Lucas wrote: > On Mon, Jan 21, 2002 at 03:45:55PM -0500, Tom Rhodes wrote: > > Anyways, a quick question, quick answer chapter would be nice, but do you > > have a vision > > I had visions, but the little white pills stopped most of them. Now > if I could only do something about the voices, I'd be all set. > Set for what? :) > of "one line question 2-3 line answer" type of chapter, or > > would you like the answers to be a bit more broad than what the FAQ currently > > carries? This is your started project, but I would be more than happy to > > lend a hand (no cutting off jokes pls :) I'm rather attached to them) > > Seriously, I don't have much in the way of vision here. > > We have some entries in the FAQ that really aren't frequently asked. > In practical terms, our FAQ is "short bits of documentation, plus > FAQs" while the Handbook is "long bits of documentation." > > We want to make the FAQ just FAQs, fine. But what do we do with short > bits? > > I'll ponder for a bit. Perhaps a new book would be the best thing. > What if it's just done the way the handbook's done? Divide it in chapters, group contents in categories so it's easy to find... Then we'd have the handbook, with all theory and "long bits of documentation", and the faq-book, which would have smaller, more practical and specific topics... So people can follow the handbook if they don't know the _how_, and read the problem-book if the _how_ doesn't work out quite as good as it says. I admit I have to read up a bit on the recent form of e.g. the handbook, but maybe the "chapters" could be just the same in both books, what could make linking from the more theorical to the more practical pretty transparent. That only works if the faq's really too big. Either it isn't, and then it doesn't need to be cut up, or it is, and the proper form needs to be established... About 2.x specific faq's: if you ask me, forget them, if they are really only valuable for those releases. Let's focus on the future, and not try to spend too much time into supporting the stone-age. A faq is only a faq if it's fa'd... If nobody asks anymore, throw it out. There still is -questions@, just like for all the lesser asked questions. That's ofcourse my opinion. ;) Kind regards, wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message