Return-Path: Delivered-To: apmail-xml-cocoon-docs-archive@xml.apache.org Received: (qmail 1857 invoked by uid 500); 1 Nov 2002 04:02:11 -0000 Mailing-List: contact cocoon-docs-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-docs@xml.apache.org Delivered-To: mailing list cocoon-docs@xml.apache.org Received: (qmail 1848 invoked from network); 1 Nov 2002 04:02:10 -0000 Received: from ptolemy.goulburn.net.au (203.28.11.5) by daedalus.apache.org with SMTP; 1 Nov 2002 04:02:10 -0000 Received: (qmail 24830 invoked from network); 1 Nov 2002 04:02:18 -0000 Received: from max-02-004.goulburn.net.au (203.28.11.193) by ptolemy.goulburn.net.au with SMTP; 1 Nov 2002 04:02:18 -0000 Subject: Re: [PROPOSAL] Use Forrest to build Cocoon docs From: David Crossley To: cocoon-docs@xml.apache.org In-Reply-To: <3DBE923B.2080605@verizon.net> References: <3DBE923B.2080605@verizon.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 01 Nov 2002 15:02:16 +1100 Message-Id: <1036123338.1245.20210.camel@ighp> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: Vadim Gritsenko wrote: > Diana Shannon wrote: > > David Crossley wrote: > > >> We know that there are > >> varied issues that needed to be addressed. Those issues > >> will only be discovered over time. > > > > But there are many issues we can discuss right now! > > Why can't we draft > > a proposal of how we'd do it right now? > > IMHO, Let's get started. > > Vadim Yes, let us get the proposal happening. Thinking along the lines of Bertrand Delacretaz: "Using the Wiki for concepts and design" http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103607167811513 I have been wondering for some time if Wiki would be a good way to develop a proposal. Perhaps a mix of cocoon-docs discussion and Wiki would work. Another way would be a document in CVS plus the cocoon-docs mailing list. Whichever way, we need a document at the end of the process. --David