From owner-freebsd-doc Thu Jan 6 17:12:51 2000 Delivered-To: freebsd-doc@freebsd.org Received: from mailgw01.execpc.com (mailgw01.execpc.com [169.207.2.78]) by hub.freebsd.org (Postfix) with ESMTP id F1B071501B; Thu, 6 Jan 2000 17:12:40 -0800 (PST) (envelope-from acadix@execpc.com) Received: from earth.execpc.com (acadix@earth.execpc.com [169.207.16.1]) by mailgw01.execpc.com (8.9.1) id TAA16970; Thu, 6 Jan 2000 19:10:50 -0600 Received: (from acadix@localhost) by earth.execpc.com (8.9.0) id TAA22445; Thu, 6 Jan 2000 19:10:50 -0600 (CST) Message-Id: <200001070110.TAA22445@earth.execpc.com> Subject: Re: ZIP Drive doc for handbook To: ean@korax.net (Ean Kingston) Date: Thu, 6 Jan 100 19:10:50 -0600 (CST) From: "Acadix Software Systems" Cc: nik@freebsd.org, acadix@execpc.com, freebsd-doc@freebsd.org In-Reply-To: from "Ean Kingston" at Jan 6, 0 04:44:00 pm X-Mailer: ELM [version 2.4 PL25-execpc] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On Thu, 6 Jan 2000, Nik Clayton wrote: > > > On Thu, Jan 06, 2000 at 09:54:34AM -0500, Ean Kingston wrote: > > > I recently started working on the Zip drive part of the handbook. This > > > does not prevent anyone else from writing for that section of the book. > > > Since you certainly had more problems getting your Zip drive to work then > > > I did mine, you have much more information on what can go wrong and how to > > > fix it then I do. At the very least I will be using your paper as a > > > reference (and giving you credit) and with your permission I will > > > integrate my efforts with yours for the final Zip drive section. Of Sure, that would be fine. Use it as a reference, plagerize it, whatever gets the job done best. > > > course, if you give that permission, you would then be associated with the > > > FreeBSD Documentation project :-) Ooh, well... I'll have to discuss this with my attorneys Murmurmurmurmur... OK, it's a go. > > FWIW, I think there can be room for both kinds of document. As well as > > 'cannabilising' it for parts, as it were, it could pretty much move > > wholesale in to the tutorials section. > > Absolutely. It's just a question of how to go about cannabilising it. > The more documentation there is in the more places the easier it is to > find. First I'm going to have to learn docbook. If there's a practical reason to have two separate documents, go ahead, but don't do it for the sake of my ego. I'd much rather see one coherent doc with "portions contributed by some guy named after a breakfast food..." in the fine print. That's one reason I prefer FreeBSD - if I wanted to get protectionist about my work, I'd just start my own distribution. :-) -Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message