Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <601F6322AD71D5118D6C00034725152910FF249B@sjmemexc1.stjude.org>
From: "Hunsberger, Peter" <Peter.Hunsberger@stjude.org>
To: "'cocoon-dev@xml.apache.org'" <cocoon-dev@xml.apache.org>
Subject: RE: Regarding Excalibur XMLUtil and Store
Date: Tue, 13 May 2003 15:50:06 -0500
MIME-Version: 1.0
Content-Type: text/plain

Stefano Mazzocchi <stefano@apache.org> wrote:

> 
> on 5/13/03 8:52 AM Hunsberger, Peter wrote:
> > 
> > Does it really matter where the code is located as long as someone 
> > cares about it?  If access to Avalon code can be done in such a way 
> > that Cocoon developers can take care of it relatively easy 
> what else matters?
> 
> Community is not only about having access, but about asking 
> question, providing answers, challenging implementations, 
> throwing RTs, supervising CVS commits, having documentation.
> 
> That code has nothing of this and giving CVS access to all 
> cocoon committers won't change anything.

Sure, but changing the location of the code won't give a particular piece of
code "community".  It may be in the Cocoon CVS, but that doesn't necessarily
mean anyone will pay any more attention to it than they have in the past.
Sometimes people walk up and down the Cocoon code just for fun, but usually
it's to do something particular.  And at that point you change what needs
changing no matter where it resides (as long as you can do so)...

People can ask about code in Avalon here on Cocoon-dev just as easily as for
any other code and they seem to already do so...