Please don't missunderstand me - I will probably participate in the
sandbox and contribute code.
But I have too much work to do and this debate is eating too much time -
and I don't think it's worth it.
I don't want to be part of the "commons" commiters if this is another
tribe who decide what's right and wrong for the components. I think the
projects need to have ( and feel they have ) a lot of control over the
components in order to participate.
The concern is that the "commons" will be involved in decisions without
having the right knowledge about it - the subprojects that are sharing
some code or developing it in the common place are the best to judge the
quality and the only that can provide the right support.
The concern is that this will turn into another round of debeate each time
someone will decide that a component is too "J2EE-ish" or duplicates
another component or they don't like something else. And the projects will
prefer to avoid this and keep the component private.
( don't tell me this will not happen - look at the current thread where
most people that are interested in developing components
jakarta-style argue pasionately about what should happen in the agora
side, and give all kind of arguments about why this shouldn't be allowed )
It's already difficult to go along with another project and share
something - even if you have a clear common goal in a component - add a
group of even more diverse people and put them in charge of deciding
what's good for the shared component.
So that's my concern - that we'll keep fighting about what's right and
wrong instead of letting the jakarta projects that are supposed to share
decide what's good or bad for themself.
> "20. A CVS repository will be available to all Jakarta committers as a
> workplace for new packages or other projects. Before release to the
> public, code or documentation developed here must be accepted into the
> Commons or sponsored by another Jakarta subproject. The sponsoring
> subproject(s) will distribute the code or documentation along with the
> rest of their codebase."
What about:
"The sponsoring project will maintain, support the distributed component
along with their codebase"
If 2 projects share a component it may be better to have a single point of
distribution for the component.
( they may decide not to place it in commons, but keep it an
agora component )
Costin
