Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 97318 invoked by uid 500); 9 Nov 2001 06:52:06 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 97295 invoked from network); 9 Nov 2001 06:52:06 -0000 From: "Carsten Ziegeler" To: Subject: RE: [Proposal] xdocs for planning notes Date: Fri, 9 Nov 2001 07:53:27 +0100 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <01110912200300.17357@igacer> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 09.11.2001 07:52:15, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.8 |June 18, 2001) at 09.11.2001 07:52:16, Serialize complete at 09.11.2001 07:52:16 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This a very good idea. We are often discussing but never keep a summary or a result anywhere. Using the approach you proposed is fine. We could also link from the todo documentation to such documents. Carsten > -----Original Message----- > From: David Crossley [mailto:crossley@indexgeo.com.au] > Sent: Friday, November 09, 2001 7:48 AM > To: cocoon-dev@xml.apache.org > Subject: [Proposal] xdocs for planning notes > > > There is various long-term planning required, > e.g. moving components to Avalon > e.g. enabling new and complex capabilities > Much gets discussed in RT threads and elsewhere. > However, details get lost in the noise. > > Would it be appropriate to create an xdocs collection > of simple planning notes in the head of CVS? > > Probably a flat directory layout with an index page > linking to topic-based docs would suffice > e.g. xdocs/plan/entity-resolver.xml > e.g. xdocs/plan/validate-docs.xml > > In this way the notes would get built along with the rest > of 2.1 'build docs'. When each functionality is implemented > then the note could be archived. > > --David Crossley > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org