On 10 Nov 2003, at 19:30, Justin Erenkrantz wrote:
--On Monday, November 10, 2003 14:09:20 -0500 Tim O'Brien <[EMAIL PROTECTED]> wrote:
I think that J-C has some (easily remedied) problems - (I see J-C turning
into an umbrella project inside of an umbrella project [Jakarta]).
The problem with that is there may be no oversight from the Board/Jakarta PMC if you add yet another layer. That's a serious problem. I think the only layer of bureaucracy should be the PMC. Anything else, IMHO, should be only about code.
IMHO the real mistake that jakarta made was to allow umbrella sub-projects. once a sub-projects becomes either too big or too diverse for one mailing list and one cvs repository, it should either take steps to reduce it's size (by spinning offer components, for example) or by applying for top level project status.
jakarta-commons has been a tremendous success but now the limits of a single list and repository are starting to be brought into focus. we need to take steps now to ensure that the success of jakarta-commons can continue but without the formation of any more sub-sub-projects.
- robert
