Back to the list...
[EMAIL PROTECTED] wrote:
>
> > The component will probally be includes in tomcat as a jar. Being
> > committer on tomcat doesn't automagically means I'm an expert on that
> > library too. A tomcat committer using the library is a user on the
> > library ml. Everybody will be encouraged to activaly partecipate to the
> > lib development but since it's a separate project you havo to gain your
> > cvs write access right.
>
> We are talking about _sharing_ a component between projects ( something
> like XMLConfig ), that was the problem we were trying to solve ( or at
> least that was my impression when we started this ). Not creating other
> separate projects and the associated mini-communities.
The huge difference is those mini-communities are composed by people
coming from the projects that use that piece of code so that even if the
component itself is separate it is deeply linked to those who use it.
It's not a sepatare tribe.
I just think such an extended commiters community is going to be a good
place for brinstorming but can't efficiantly achive the goal of pushing
project to actually share the same code (when it makes sense to do it).
It may help sharing of ideas, not code.
Fede
