db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy Jefferson <a...@datanucleus.org>
Subject Re: Apache (Oracle?) JDO 3.1 release, revisited
Date Fri, 18 Apr 2014 17:15:20 GMT
Hi Craig,

> Long answer:
> JDO falls outside the boundaries of "normal" Oracle-led JSRs. It has taken
> more time than I expected to get Oracle legal to understand that JDO is a
> different project with different licensing requirements. Mostly, Oracle is
> used to being in control of JSRs in which it has an interest.

One would argue (well I would) that Oracle DOESN'T HAVE an interest. It never 
did :-P

> I have discussed with Oracle attorneys several scenarios: transferring
> Maintenance Lead responsibilities to another organization. Apparently
> transferring to Apache sounds so far-fetched as to be a non-starter. If
> there is another organization or individual willing to be Maintenance Lead,
> that might be possible. Volunteers?
> Another alternative is for JDO to leave JCP completely. This would mean
> renaming the API name space from javax.jdo to org.apache.jdo just like the
> TCK has already done. The specification license would still be problematic.
> Also, the name Java TM Data Objects would probably need to be changed.

Politics to the end :-)

> Short answer: no, there is no expected release date.

Thanks for your reply, and time taken to extract this info from the people 
concerned. I appreciate how difficult that can be.

One possibility from my side is to fork it and be done with it. Yes I'd choose 
a different name. Well not too different, but not one of their registered names 
(do we have a complete list of what "names" are registered?). 
Obviously if doing that then anyone who has contributed to it so far would be 
welcome to continue participating and could have access to its GitHub repo, 
and it would continue as an Apache 2 license.

DataNucleus (Web: http://www.datanucleus.org   Twitter: @datanucleus)

View raw message