I'd be careful with this line of thinking. We've heard from perhaps 4 jakarta-commons folks on this thread, there are 70 some committers listed in the avail file for jaakrta-commons.
I for one am not sure that introducing "functional" or other sorts of groupings is necessarily solving a problem that jakarta-commons really has. There are mechanisms by which this could happen within jakarta-commons, including a component's committers deciding to split their mailing lists off from commons-dev/commons-user (as has happened with httpclient) or to move out of jakarta-commons entirely (as has happened with cactus), and yet incidents of this happening are extremely rare (these two cases cover it IIRC). It does not seem that the jakarta-commons community is clamoring for finer subdivisions. On a broader note, I'd strongly recommend that this group make an effort to engage the larger jakarta-commons community sooner rather than later. Coming to j-c with a pre-defined plan of "here's where your code and community is going to be placed within apache-commons" isn't going to be any more welcome (or effective) now than the announcement made a year or so ago stating "the board has created apache-commons to replace jakarta-commons". Jakarta-Commons is a mature, diverse and successful project. It would be a mistake to believe apache-commons has nothing to learn from it. On Fri, 7 Nov 2003, Justin Erenkrantz wrote: > The impression that I've gotten from the Jakarta Commons folks is that they > are not willing to even consider moving until we have the groupings in > place and to their liking. > > Ideally, yes, I'd prefer to wait, but I think that they won't consider > moving to the ASF Commons until we have groupings that they find acceptable. > > If I've misunderstood the messages, my apologies. -- justin - Rod <http://radio.weblogs.com/0122027/>
