From owner-freebsd-doc@FreeBSD.ORG Fri Dec 3 19:02:13 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3732C16A4CE; Fri, 3 Dec 2004 19:02:13 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1858843D48; Fri, 3 Dec 2004 19:02:13 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id B1577148F5; Fri, 3 Dec 2004 13:02:12 -0600 (CST) Date: Fri, 3 Dec 2004 13:02:12 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: Tom Rhodes In-Reply-To: <20041203125024.31182375@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Mark Linimon cc: FreeBSD-doc@FreeBSD.org Subject: Re: Merging the FAQ -> handbook, build time options, proof ofconcept patch X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 19:02:13 -0000 I agree that we don't want any overlap in the FAQ and the handbook, or frankly for anyplace else for that matter. The overlap causes confusion for both users and doc committers. That's one of the reasons that the FAQ has rotted so badly. I see the FAQ serving as a "Start Here" document for people who are not familiar with FreeBSD; as a place for "what is it/why should I care/why did you do XYZ" thing. I see the handbook as "now that I have FreeBSD installed, how do I do XYZ". The timeslice I had to do the hackup job was insufficient to have gotten that across. So I don't see having the "include the text here or include the text there" knobs as doing anything other than perpetuating the bad current practice. I'm waving my hands at the "I tried to do XYZ and it didn't work" questions which I think are different from the "how do I do XYZ" questions. The latter belong in the handbook, the former I'm not so sure of. Anyone have any experience in setting up a knowledge- base app? I'd accept the argument that that's really where those kinds of answers belong. mcl