From owner-freebsd-doc Wed Apr 7 8: 0:40 1999 Delivered-To: freebsd-doc@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id E8489157DB for ; Wed, 7 Apr 1999 08:00:29 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id AAA15043; Thu, 8 Apr 1999 00:58:15 +1000 (EST) Message-ID: <19990408005810.34644@welearn.com.au> Date: Thu, 8 Apr 1999 00:58:10 +1000 From: Sue Blake To: Bill Fumerola Cc: Nik Clayton , Duncan Barclay , doc@FreeBSD.ORG Subject: Re: Organisation change for the Handbook References: <19990406190353.C6083@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Bill Fumerola on Wed, Apr 07, 1999 at 10:31:24AM -0400 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Apr 07, 1999 at 10:31:24AM -0400, Bill Fumerola wrote: > On Tue, 6 Apr 1999, Nik Clayton wrote: > > > Yeah. One of the benefits of this approach is that it makes it easier > > to slot new material in, and at the same time simpler to hand off > > chunks to volunteers and say "Here's a complete framework, all it needs > > is content". > > And the advocates of the lesser-known-but-loved-by-those-who-use-it > software would probably love to have something to dock their documentation > into. Wow! Here's my big chance to write a "book" on ed :-) But how do we induce people to fill in the old ignored bits, like the missing X section? Would it help to have a monthly posting to -doc listing what documentation is sorely lacking and what's currently being worked on? -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message