cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <>
Subject RE: [CLEANCOON] Let's clean Cocoon and modularize it (was: Cocoon Organization (Cocoon plugins))
Date Mon, 05 Aug 2002 14:33:26 GMT
> From: Nicola Ken Barozzi []
> Vadim Gritsenko wrote:
> >>From: Andrew C. Oliver []
> >>My objection
> >>is this.  Before there is an agreement and set of documentation
> >>explaining "WHAT goes WHERE" then this will be contentious.
> >
> > +1. Before we start branching CVS, let's define what goes where.
> > Organization" thread was exactly about this.
> Why?
> The branch is a playground, where many can *see* the difference
> of just trying to understand it.
> If you prefer I can just write the things I will move, but it just
> easier to me to move them and have all evaluate it.

My main concern about Cocoon health is that it grows with features which
are *not* integrated with each other. Examples are:

1. CInclude vs XInclude
2. ESQL vs SQLTransformer
3. xscript vs session context 
4. ProgrammingLanguage vs Interpreter

All these features should be better integrated with each other, should
be built on common code and share that common code. The resulting shared
code base among features will easy maintenance burden, reduce amount of
code, and will give better integrated Cocoon, where features are work
with each other seamlessly.

If you to break up things into several packages, it will be much harder
to do integration work (if possible at all).

Also, can you comment on Andrew's suggestion:

And Konstantin's:

And Berin's:

> AFAIK there doesn't have to be a vote to branch, but there is to be a
> vote to switch codebases or to switch back.
> For now, I haven't heard compelling reasons not to.

My other reason is: the more (playground) directories we create, the
more messy MAIN becomes. And, one cannot work with HEAD, because you
cannot commit to HEAD.


To unsubscribe, e-mail:
For additional commands, email:

View raw message