From owner-freebsd-doc@FreeBSD.ORG Fri Dec 3 18:30:09 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 1582D16A4D1; Fri, 3 Dec 2004 18:30:09 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43D7B43D1F; Fri, 3 Dec 2004 18:30:06 +0000 (GMT) (envelope-from zettel@acm.org) Received: from [192.168.0.2] (bgp966574bgs.derbrn01.mi.comcast.net[68.41.108.205]) by comcast.net (sccrmhc13) with ESMTP id <2004120318300501600be6ofe>; Fri, 3 Dec 2004 18:30:05 +0000 From: Len Zettel To: freebsd-doc@freebsd.org Date: Fri, 3 Dec 2004 13:29:34 +0000 User-Agent: KMail/1.6.2 References: <20041128202656.GL750@zaphod.nitro.dk> <20041202221228.GG78684@abigail.blackend.org> <20041203123606.100fa863@localhost> In-Reply-To: <20041203123606.100fa863@localhost> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412031329.34102.zettel@acm.org> cc: Tom Rhodes cc: Nik Clayton cc: Murray Stokely cc: "Simon L. Nielsen" Subject: Re: Doc BoF at EuroBSDCon 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 18:30:09 -0000 On Friday 03 December 2004 05:36 pm, Tom Rhodes wrote: > On Thu, 2 Dec 2004 23:12:28 +0100 > > Marc Fonvieille wrote: > > On Thu, Dec 02, 2004 at 04:43:45PM -0500, Tom Rhodes wrote: > > > Would be nice, but are you sure you can't come up with a better > > > solution? > > > > I wrote the thing in 2001, I committed it in late 2002 (I think, I > > should check the CVS), so my memories are not really good. I remember I > > did not chose some solutions cause of the jadetex part, the fact > > make(1) should be able to build en_US images mixed with localized one > > (different path), the fact we should avoid to use too much disk spaces > > (copying images), etc. It's quite complex because you have to take care > > about many things at same time. > > Leave it in there for now. We'll cross this bridge when we > come to it. Lets not go off in a million directions at once, > that'll just get us in the mess we have now. If you don't mind an ignorant outsider butting in here.... It seems plain to me that the guys doing the doc project are overworked and underappreciated. It would help a lot if there were more hands and minds doing all the things that need to be done. It would help if it were easier to join the doc project. I don't claim that you guys have barricades and machine guns mowing down prospective newcomers. I mean it is downright difficult to gain the knowledge and expertrise that would let one become a really productive member of the team. This could change if three things moved up the priority list. 1) Fixing the doc infrastructure so it worked as advertised. 2) Updating the advertising so a newbie could find out how it worked without a lot of thrashing around. 3) Laying out a systematic plan to accomplish 1) and 2) that had realistic time shedules. Said plan, as far as possible, should go for incremental steps rather than a massive change all in one blast, but each step should clearly lead to the overall goal. Easy to say, isn't it? ;-) -LenZ-