From owner-freebsd-doc@FreeBSD.ORG Mon Dec 6 19:58:31 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 6243016A4CE; Mon, 6 Dec 2004 19:58:31 +0000 (GMT) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FC8743D72; Mon, 6 Dec 2004 19:58:30 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost (64-144-75-100.client.dsl.net [64.144.75.100]) (authenticated bits=0) by pittgoth.com (8.12.10/8.12.10) with ESMTP id iB6JwQag089954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Dec 2004 14:58:27 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Mon, 6 Dec 2004 14:58:32 -0500 From: Tom Rhodes To: Nik Clayton Message-ID: <20041206145832.59e143d3@localhost> In-Reply-To: <20041206192017.GE72462@clan.nothing-going-on.org> References: <20041205114254.GD23252@clan.nothing-going-on.org> <41B3617B.3080507@centtech.com> <20041206192017.GE72462@clan.nothing-going-on.org> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: doc@FreeBSD.org cc: Nik Clayton Subject: Re: Time for a Network Handbook? 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: Mon, 06 Dec 2004 19:58:31 -0000 On Mon, 6 Dec 2004 19:20:18 +0000 Nik Clayton wrote: > On Sun, Dec 05, 2004 at 01:28:59PM -0600, Eric Anderson wrote: > > Nik Clayton wrote: > > >Anybody got any strong feelings about moving the existing "Network > > >Communication" out of the Handbook, and using it to seed a new > > >FreeBSD Networking Handbook? > > > > What's the reasoning behind it? I like it in the Handbook personally - > > it fits with the rest of the book. > > Partly to move closer (as others have said) to having a collection of > Handbooks. But mainly because I was glancing over the existing content > and it struck me as odd that mail gets its own chapter while most of the > other network services have to sit in together. > > So the natural thing to do is to give each network service its own > chapter. Which would increase the size of the Handbook somewhat. So > slicing them out in to a separate networking handbook could be > appropriate. > > I also think that giving each service a 'standard' structure: > > Synopsis > Terminology > Client > Server > > will lend some needed uniformity to the content, and make it easier for > someone to start documenting additional services (IMAP? POP3? DAV? ...). > > While I think about it I'm beginning to think that Terminology > ("Glossary"?) might make sense as a 'standard' in all the other > chapters too, in the same way that Synopsis is. This sounds like a good idea. It also shows how much documentation we actually have (and lack). -- Tom Rhodes