On Tue, 13 Nov 2001, David Crossley wrote:

Hey, David, good work. We need a can like this to place our RTs into and
to save them somewhere. Stuff from the "Stefano and Giacomo got together
for a week" theme someone mentioned recently will go there soon :)

Giacomo

> I have checked-in the initial set of planning notes to
> documentation/xdocs/plan/ in the head of CVS only.
> The first important document is a summary of the recent
> thread "Identifying Components for Avalon".
> There are also some other initial documents to get the
> process started.
> --David
>
> > Date: Fri, 9 Nov 2001 07:53:27 +0100
> > Subject: Re: [Proposal] xdocs for planning notes
> > From: "Carsten Ziegeler" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> >
> > 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:[EMAIL PROTECTED]]
> > > Sent: Friday, November 09, 2001 7:48 AM
> > > To: [EMAIL PROTECTED]
> > > 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: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to