> -----Original Message-----
> From: Christian Haul [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 19, 2002 2:42 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [VOTE] RE: New "module" terminology: WAS: Extending the
> build system for modules
>
>
> On 19.Aug.2002 -- 02:11 PM, Stephan Michels wrote:
> >
> >
> > On Mon, 19 Aug 2002, Carsten Ziegeler wrote:
> >
> > > Stephan Michels wrote:
> > > >
> > > > On Mon, 19 Aug 2002, Carsten Ziegeler wrote:
>
> > > > > Putting it very simple, blocks are a plug-in mechanism for
> > > > Cocoon and the
> > > > > modules concept is only a better cvs structure for Cocoon.
> > > > > So modules is only about organizing things and can be
> done by simply
> > > > > restructuring the cvs and change minor parts of the build
> system. So,
> > > > > these modules are possible today.
>
> Yup, but we're not talking about cvs modules, are we. And we are not
> talking about org.apache.cocoon.components nor
> org.apache.cocoon.components.modules but about something that avalon
> calls "sub-project".
>
Ok, and we rename our Request class to something else because it's already
used somewhere etc ;)
I suggest, that a volunteer starting with implementing it, chooses the
name. That's simple, requires no vote and no other activities.
So, any volunteers?
Carsten
> -100 for 'module' because of the above
>
> > +1 for 'extension' (short 'ext'). (But 'module' also okay).
>
> +1 for 'extension' or anything else, that doesn't conflict with
> existing naming.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
