I can see some good use of an apache-commons : 1) Projects that are implementing eg RFC's that is not language related can commonly discuss implementations, have their API's (where usefull) about the same. 2) Joining expertise 3) Clear for the outside : want an http common implementation go to http://blah and you find all the possible implementations there
And some bad : 1) Decisions will be a great pain, unless the specific languages can acutally make decisions on their own. 2) It can get messy in ML's with language specific issues, not even speaking about not very interesting commits from the c part of the project So I come to my conculsion : apache-commons should be there for the outside and for joining expertise, so mainly containing a website + mailinglists. This way nothing changes, just some things get added. The problem with this can be however who will bring parties together in such an effort ;)) Just a mind spin here.. Mvgr, Martin On Mon, 2002-10-21 at 21:46, Stephen Colebourne wrote: > But Nicola Ken, the basic problem is that I don't support the merging of a > Java commons with a non-Java commons. There are way too many issues > generated and few if any benefits. So, I should spend even more of my time > subscribing to yet another list, to get another 50 emails a day, just to say > no. > > And whats more, no-ones given me any opportunity to vote on it. Its being > presented as a fait accompli. (And yes I've read your email about it not > being imposed, but it sure as hell feels that way). > > This 'reorg' is going to be very community destroying before long. > > Stephen > > ----- Original Message ----- > From: "Nicola Ken Barozzi" <[EMAIL PROTECTED]> > To: "Jakarta General List" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Monday, October 21, 2002 8:15 PM > Subject: Re: Naming issues > > > > > > Michael A. Smith wrote: > > > On Mon, 21 Oct 2002, Nicola Ken Barozzi wrote: > > > > > >>Why not just decide to move the Jakarta Commons projects to Commons and > > >>the Sandbox ones to Incubator? > > >> > > >>This is not a proposal for a diktat, but a *suggestion* for Jakarta > > >>Commons projects to take part of the Commons and Incubator Project > creation. > > >> > > >> [EMAIL PROTECTED] > > > > > > > > > As far as jakarta-commons goes (ignoring the sandbox/incubator), I sent > > > a message to [EMAIL PROTECTED] asking whether this is > > > something we, as committers on jakarta-commons, wanted to consider, and > > > so far the only real reaction was major uncertainty due to the lack of > > > defined structure/procedures in @commons.apache. > > > > Yeah, that's why I posted it here! > > > > Come on guys, come over to [EMAIL PROTECTED], let's make > > ourselves heard, help create the rules there, so finally Commons can > > have it's top-level project! > > > > It's not something that has to be imposed, we can help over there! > > > > [EMAIL PROTECTED] > > > > > hrrmmm... when'd this thread move from reorg@apache to general@jakarta? > > > strange. > > > > hehehe, when I cross-posted ;-) > > > > Oh, and now I'm at it, here it goes, welcome to the discussion > > commons-dev! :-D > > > > -- > > Nicola Ken Barozzi [EMAIL PROTECTED] > > - verba volant, scripta manent - > > (discussions get forgotten, just code remains) > > --------------------------------------------------------------------- > > > > > > -- > > To unsubscribe, e-mail: > <mailto:commons-dev-unsubscribe@;jakarta.apache.org> > > For additional commands, e-mail: > <mailto:commons-dev-help@;jakarta.apache.org> > > > > > -- > To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org> > > -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
