Return-Path: Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 42772 invoked from network); 12 Jul 2002 16:11:33 -0000 Received: from otsrv1.iic.rug.ac.be (157.193.121.51) by daedalus.apache.org with SMTP; 12 Jul 2002 16:11:33 -0000 Received: from outerthought.org ([192.168.123.104]) by otsrv1.iic.rug.ac.be (8.11.6/8.11.6) with ESMTP id g6CGBaj28374 for ; Fri, 12 Jul 2002 18:11:36 +0200 Message-ID: <3D2EFFB7.60900@outerthought.org> Date: Fri, 12 Jul 2002 18:11:35 +0200 From: Steven Noels Organization: Outerthought User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en MIME-Version: 1.0 To: forrest-dev@xml.apache.org Subject: Re: Separate CVS module for docs? References: <79C5D134-95B0-11D6-9267-0030653FE818@apache.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 160 Diana Shannon wrote: > I'm ***not*** trying to start a separate thought train. Forrest > transition for Cocoon is an ongoing issue, not a new thread. my entire mail was written with the assumption this new module would not only be containing Cocoon docs, but also other projects docs - an idea which I don't particularly like due to the abysmal state of xml-site which is such a 'shared module' ownership of docs should reside in the hands of per-project appointed code/docs committers, not centralized in some xml.apache.org-docs module if my assumption is wrong (apparently) - sorry about it - I'm bad with assumptions these days... :-( > I'm proposing this as a more efficient path of Forrest transition > speaking on behalf of someone who is working hard to make that happen > as well as support Forrest in the process. I know, Diana. We all know. If you prefer to have a separate module for cocoon-docs, I can agree with you. I'm not so sure (from a community perspective) whether creating subcommunities is efficient, however, but that's my personal opinion. We are actively thinking about some form of forrest.jar/.war/.cent that projects depending on Forrest need to include inside their CVS module for local builds - it's just that I haven't quite wrapped my brain around it - anyone an idea? Cocoon always will be a special case, I reckon, since most of what powers Forrest is born over there :-D Friends again? -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center stevenn@outerthought.org stevenn@apache.org