The problem with moving Commons up is that when you look at where Jakarta needs to go, and when you look at where Commons generally is now; they are the same places - and it's hard to distinguish between the focuses.
Hm... interesting... funnily I have never seen it like that before. Always had the impression jakarta is for "products" while commons is for libraries. Sometimes it's just not that clear where to draw the line though.
Jakarta needs a way to blend community oversight with small numbers of active committers per component. That's pretty much Commons. For a start, I would merge BCEL, BSF, ECS, JCS, ORO and Regexp dev lists into either [EMAIL PROTECTED] or [EMAIL PROTECTED]
Why that combination? ...feels quite unnatural to me - I am sure so it will for the users. Combining mailinglist would definitely get a -1 from me. I don't want the few BCEL subscribers left to unsubscribe because they get annoyed because they are receiving mails they are not interested in. We might get away with that at commons - but in general I think it's quite a bad idea.
1) BCEL, BSF, ECS, JCS, ORO and Regexp dev lists merging 2) Alexandria dies 3) POI to TLP 4) Consider merging user lists from 1) 5) Flatten HttpComponents, Velocity, Taglibs. Some mad ideas :)
Sorry that I have to agree with the last sentence in some extend ;-) cheers -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
