[EMAIL PROTECTED] wrote:
>
> Well, after a bit more thinking - I do agree that something is wrong in
> the proposal.
>
> But that's the fact that the commons commiters can vote and release to the
> public a component that is developed by a small group, and the vote
> involves people who can't provide any guarantee for the quality of the
> product or the future maintainance.
But I think you are inverting the picture here a little, because I can't
imagine that the commons committers can *proactively* do that, go grab
something and release it. I would imagine that vote by the commons
committers would be *reactive* : only after a group of component
developers decided *they* want to release (and are willing to continue
to be responsible), only then would the commons committers vote on the
appropriateness of that component to the Commons / Jakarta charter.
By asking the Commons committers to vote on the 'separation' of their
component into a distinct entity in Commons, the component committers
are declaring their intent to continue to support the component.
>
> So if you are worried about the Apache brand - probably we should remove
> the possibility for commons to release components - the only people that
> can vote for a components are those involved in the development and
> maintainance of the component.
Again, the distinction should be :
1) Only the people that are involved in the development and maintenance
of the component can decide to ask that it become a separate component
under Commons.
2) Then the Commons must decide if it is an appropriate thing to as a
separate entity, and if the vote is positive, then it is up to the set
of people in 1) to continue to work and support the component.
> On the other side jakarata projects who use a component and support it as
> part of their product do have the knowledge and can insure the quality of
> the product.
>
> If you work on a DBCP I don't see how can you vote and promise support for
> a ThreadPool - since commons will be composed of many subprojects you
> can't expect everyone to be involved with all components.
It's my interpretation that you wouldn't - the same people would
continue.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/