Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 62667 invoked from network); 6 Jun 2005 14:02:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Jun 2005 14:02:53 -0000 Received: (qmail 39078 invoked by uid 500); 6 Jun 2005 14:02:52 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 39027 invoked by uid 500); 6 Jun 2005 14:02:52 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 39001 invoked by uid 99); 6 Jun 2005 14:02:52 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from www2.kc.aoindustries.com (HELO www2.kc.aoindustries.com) (65.77.211.84) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 06 Jun 2005 07:02:51 -0700 Received: from www2.kc.aoindustries.com (www2.kc.aoindustries.com [65.77.211.84]) by www2.kc.aoindustries.com (8.13.1/8.13.1) with ESMTP id j56E2VNV026852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 6 Jun 2005 09:02:31 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by www2.kc.aoindustries.com (8.13.1/8.13.1/Submit) id j56E2VxF026810 for dev@forrest.apache.org; Mon, 6 Jun 2005 09:02:31 -0500 X-Authentication-Warning: www2.kc.aoindustries.com: indexgeo set sender to crossley@apache.org using -f Date: Tue, 7 Jun 2005 00:02:26 +1000 From: David Crossley To: dev@forrest.apache.org Subject: Re: [PROPOSAL] A CMS for our Docs Message-ID: <20050606140226.GA21253@igg.indexgeo.com.au> References: <42A42ADD.7060103@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42A42ADD.7060103@apache.org> User-Agent: Mutt/1.4i X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Ross Gardler wrote: > Over at Cocoon they are starting to use Daisy for their docs. I propose > we do the same. I have too many questions at this stage. How will the changed content get back into our SVN? How is the workflow managed to get the content reviewed and then published onto the website? At the moment we do have a workflow of sorts. I also agree with Ferdinand. We would need a structure to add these docs, or we end up with the un-manageable mess that they call Wiki. Will we see sensible diffs, so that the committers can oversee the content or do we get the voluminous diffs like wiki where you cannot see what has been changed? e.g. most paragraphs are one long line, so diffs are useless. Who will be able to add content? Anyone? Do they need to be a committer? Do they need to be on forrest-dev? Are the contributions assigned copyright to ASF? I actually far prefer the current process where people need to send patches. That way they get reviewed by a committer. Who will manage this Daisy installation? We cannot be stuck with one person who knows a bit about it. We would need a management plan. Same applies if we use Lenya. I find this very alarming. Some people at Infrastructure are trying to get a cross-project environment established for managing documentation tools and site-building. All PMCs were asked to join and discuss this. Some people have, but mainly the process has stalled again. Instead we see projects like Cocoon rushing off to do their own thing. Now we will get duplicate instances of Daisy/Forrest. Sorry, i am not trying to be obstructive, just that i see too many unanswered issues. --David