> >What makes you think that whatever DBPool you choose will be better ? And
> >what makes you think that a project will be happy to replace some code
> >they developed and serve their purpose with something they have no control
> >over ?
>
> I assumed there was some turbine developers on this list ;) If not is there
> some struts developers ? It may be good for people to say where they will
> be able to help migrate in code. I am involved with both Aalon and Ant and
> will be happy to do what is appropriate to facilitate sharing between these
> two and this library project.
My point was that the decision should come from a project that wants to
share a piece of code ( or use a shared component ) - and they shouldn't
have to be "aproved" by a library comitee.
I'm a tomcat commiter, but I can't decide on my own to take a piece of
tomcat, change it, put it in the library and then change
tomcat to use the library. It should be a decision on tomcat-dev, and the
people who vote +1 on it and are doing the work of refactoring the
component for inclusion should be able to maintain in the new repository.
If DBPool from turbine is to be included I hope it'll be a vote on
turbine-dev, some turbine developers ( who know the component the best
) will volunteer to help and do the needed refactoring ( I don't think
that someone from outside can do a better job than the original
maintainers of the code ).
It's very simple:
1. We either let each project decide on it's own to share / use, and make
it as easy as possible to do so.
or
2. Grab code from projects (selecting by vote which component) or create
new components, with the goal of creating server-side components for
projects.
I don't see any reason (2) can't be done in avalon - after all the goal of
avalon is exactly that.
I also think there is a need for (1), and if the project we are discussing
now (the library ) is not doing that, probably we need another project.
Costin
