Looking back in history, there have been various occaisions when this should have happened. The trouble is that now it is a recognised product other factors come into play:
1) ASF policy on everything going via the Incubator - this stuffs me basically. JodaTime is the work primarily of two people, Brian S ONeill and I. To get into ASF we would have to pass lots of tests of community viability, mentoring, documentation, license assignment, ................... Frankly the beaurocracy of even considering it seems pointless. * 2) Existing users - I'm about to do a 1.0 of JodaTime in its current package, because its way overdue 3) Package name change/Brand name change - actually I'm not too worried about this 4) Commons-Time - Does a 450k jar file, time-'framework' belong in commons. But its too small to be an ASF top level project. 5) Would any other ASF people contribute to it just because I brought it to ASF? Would the code be better? Stephen * Note that this worries me about ASF in general, although I'm not convinced everyone actually plays by the rules ----- Original Message ----- From: "Gary Gregory" <[EMAIL PROTECTED]> > Would it be interesting to bring Joda-Time as commons-time? Gary > -----Original Message----- > From: Stephen Colebourne [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 02, 2004 14:12 > To: Jakarta Commons Developers List > Subject: Re: [lang] Commons Lang DateRange/Duration classes > > See http://joda-time.sourceforge.net > > This project makes me biased as to whether a DateRange/Duration class > should > be in [lang]. So I'll wait for other views. > > Stephen > > ----- Original Message ----- > From: "Eric Crampton" <[EMAIL PROTECTED]> > > I've noticed on the Commons Lang task list that there is a need for > > DateRange/Duration classes. I've written such a thing when needing to > > scratch an itch and, after some cleanup to better look like existing > > Jakarta Commons code, would like to submit it. > > > > Before submitting, however, I'd like to make sure no one else has > > tackled or is tackling this. Also, does anyone have any special ideas > > or requirements for such classes? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
