Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: "Cocoon-Dev" <cocoon-dev@xml.apache.org>
Subject: What Cocoon is really doing wrong [was: CVS repository changes...
 (and what's left to do)]
Date: Thu, 27 Feb 2003 09:12:26 +0100
Message-ID: <LKENJPKDAIKAPKHEOCMMIEDHCNAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="iso-8859-1"

I just want to keep on the tradition of writing mails
that explain what cocoon is doing wrong :(

We really should avoid "action fast" when this has a great impact
on all developers and all users of cocoon, like renaming cvs repositories
etc. Reverting things like these is more than a pita.

So, we really should come back to the usual open source handling
of things: first a proposal, than a vote, than the action.
And not: making a proposal and during the proposal doing the
action only because one committer that "great". All the other
committers had even no chance to say their opinion. 
You have to give other committers at least one day time, because
we don't live all on the same site of the world, but I guess for
such important isuess one week (as it is handled e.g. by the
avalon group) is much better.

Sorry Pier that this time it hits you, but I hope you feel better
when you know that you are not the only one doing things in cocoon
this way. Even I do it sometimes...but it really depends on the
impact of the change. If the change can be simply reverted it might
be seen as "ok".

So as a personal consequence, I will stop my work on cocoon until 
this is sorted out, because I'm feeling really unsure on how to 
handle any committs and how it will go on.
(The good thing about it is that it gives me some time to finish
things in avalon).

Thanks
Carsten 

Carsten Ziegeler 
Open Source Group, S&N AG