Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Vadim Gritsenko" <vadim.gritsenko@verizon.net>
To: <cocoon-dev@xml.apache.org>,
	<nicolaken@apache.org>
Subject: RE: [RACOON] Let's clean Cocoon and modularize it  (was: Cocoon
 Organization(Cocoonplugins))
Date: Mon, 5 Aug 2002 10:37:15 -0400
Message-ID: <011901c23c8d$97cbb400$df74558b@vgritsenkopc>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3D4E8A66.3060204@apache.org>
Importance: Normal

> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
> 
> Leigh Dodds wrote:
> >>Since we are talking about code, CVS logs are our WIKI.
> >>That's the intention.
> >
> >
> > You're not serious?
> >
> > I'm not talking about file level changes, I'm talking about design
> documents,
> > project roadmaps, proposals, etc. How do they get put into a CVS
log?
> 
> I commit the change, it gets reviewed there, live.
> If I want to make a document I commit it, and others change it, I get
> notified via log, I change again or discuss, etc.
> 
> I don't see what a WIKI brings developers more than VCSes.

Nicola,

I think you missed the point. We have lots of RTs, discussions, etc, and
the only way to get them is through archives, or sometimes some good
soul [summary]izes them, and again, these summaries are available in the
archive. Wiki will allow to keep this information online, browsable, and
*editable*.


You are not proposing to use CVS instead of mail-list, are you? ;)

Vadim


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