From owner-freebsd-doc@FreeBSD.ORG Mon Dec 6 19:26:22 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 9B1A216A4CE; Mon, 6 Dec 2004 19:26:22 +0000 (GMT) Received: from mail.elvandar.org (redqueen.elvandar.org [217.148.169.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E2B143D55; Mon, 6 Dec 2004 19:26:22 +0000 (GMT) (envelope-from remko@freebsd.org) Received: from localhost (localhost [127.0.0.1]) by mail.elvandar.org (Postfix) with ESMTP id 6FABE295449; Mon, 6 Dec 2004 20:26:21 +0100 (CET) Received: from mail.elvandar.org ([127.0.0.1]) by localhost (redqueen.elvandar.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41205-18; Mon, 6 Dec 2004 20:26:20 +0100 (CET) Message-ID: <41B4B263.7060804@FreeBSD.org> Date: Mon, 06 Dec 2004 20:26:27 +0100 From: Remko Lodder User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nik Clayton References: <20041205114254.GD23252@clan.nothing-going-on.org> <41B3617B.3080507@centtech.com> <20041206192017.GE72462@clan.nothing-going-on.org> In-Reply-To: <20041206192017.GE72462@clan.nothing-going-on.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at elvandar.org cc: doc@freebsd.org 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:26:22 -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. > > N I like the entire idea :-) The Dutch team will proudly follow translating the stuff when it's available :-) -- Kind regards, Remko Lodder FreeBSD (Dutch) Documentation Team