From owner-cvs-share Sun Oct 6 12:52:50 1996 Return-Path: owner-cvs-share Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA06973 for cvs-share-outgoing; Sun, 6 Oct 1996 12:52:50 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA06966; Sun, 6 Oct 1996 12:52:46 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id OAA09454; Sun, 6 Oct 1996 14:52:28 -0500 (EST) Date: Sun, 6 Oct 1996 14:52:28 -0500 (EST) From: John Fieber To: Joerg Wunsch cc: "Jordan K. Hubbard" , CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-share@freefall.freebsd.org Subject: Re: cvs commit: src/share/doc/FAQ FAQ.sgml In-Reply-To: <199610061422.QAA08205@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-share@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 6 Oct 1996, J Wunsch wrote: > Who guarantees then that the handbook will be maintained on a more > regular basis? Nobody. :( As I've said before (probably in the doc list), I see the ideal FAQ as a dynamic document addressing relatively narrow topics with quick well defined answers. It should be highly responsive to the *current* state of FreeBSD, documenting quirks in particular releases, common pitfalls and the like. The handbook, on the other hand, should be for more in depth topics that cannot adequately be addressed in a 2-5 paragraph FAQ answer. Generally the topics are a bit more stable than FAQ topics, for example the Printing chapter. The FAQ addresses "I've got this little problem" or "Will X work?". The handbook addresses "I want to learn all about Y". Ultimately putting FAQ type material in the handbook would be counterproductive. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================