cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vadim.gritse...@verizon.net>
Subject RE: [CLEANCOON] Let's clean Cocoon and modularize it (was: Cocoon Organization (Cocoon plugins))
Date Mon, 05 Aug 2002 12:54:29 GMT
> From: Andrew C. Oliver [mailto:acoliver@apache.org]
> 
> >
> > If nobody objects, I will branch on 7 August 2002 and start
refactoring.
> >
> Not that my opinion should count for much, but I object. 

I'm with you, we are -1.5 now.

Ken, shall we do one step at a time, please?
(seems that I'm in favor of evolution)


> 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. "Cocoon
Organization" thread was exactly about this.


> Secondly,
> I'd like to see something that explains how a common person will go
> about installing Cocoon with *feature X* once its split into a billion
> complex pieces with UNKNOWN dependancies.  Modularization will only
work
> if the modules are defined in a human language.  So far I see a
million
> "lets fix it via just hacking at it" approaches, no definitions, and
> still inadequate documentation.  Personally, I feel the documentation
is
> FAR more important than ANY refactoring at helping users understand
Cocoon.

+1.

Vadim 

> -Andy


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message