Stand-alone Nashorn licensing

[Attila Szegedi]

I am not considering moving Nashorn to Apache.

As to the why: I believe OpenJDK is a very robust open source organization with a good governance model. Nashorn already exists as a project in OpenJDK, and it was a natural choice to continue its development within its existing organization. Setting it up within ASF, or Eclipse, or some other software organization would’ve incurred significantly more work (and by implication time.)

I don’t see any clear benefits from transferring the project to a different org. If the OpenJDK organization would not have been open to continuing hosting Nashorn, it would’ve made sense to try to find a different host organization. 

Attila.

> On 2020. Oct 14., at 15:49, Colby Russell <nashorn-dev at x.colbyrussell.com> wrote:
> 
> My last probe about moving to Apache got derailed.  Is that going to be given any serious consideration, and if not, why?
> 
> -- 
> Colby Russell
> 
> On 10/14/20 7:27 AM, Attila Szegedi wrote:
>> I’m talking with folks within Oracle about this topic. My assumption is that the code being lifted out of the jdk project doesn’t change its licensing, so it should continue to be GPL Version 2 with Classpath exception. A past example of a project similarly spun off from jdk was JavaFX and that appears to also be under GPLv2 + Classpath.
>> 
>> As soon as I have a definitive word from Oracle, I’ll let the mailing list know.
>> 
>> Attila.
>> 
>>> On 2020. Oct 13., at 14:43, BURRIS Thomas <Thomas.BURRIS at 3ds.com> wrote:
>>> 
>>> Hi Attila (et. al.) - This is, indeed, good news. What specific license do you intend to release the stand-alone Nashorn under?
>>> 
>>> After having been burnt by Oracle with the removal, it'd be very useful to know the targeted license.
>>> 
>>> Best Regards,
>>> 
>>> Thomas BURRIS
>>> 
>>> RDF Modeling R&D Software Architecture Director
>>> 
>>> 
>>> 
>>> 
>>> This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged.
>>> 
>>> If you are not one of the named recipients or have received this email in error,
>>> 
>>> (i) you should not read, disclose, or copy it,
>>> 
>>> (ii) please notify sender of your receipt by reply email and delete this email and all attachments,
>>> 
>>> (iii) Dassault Syst?mes does not accept or assume any liability or responsibility for any use of or reliance on this email.
>>> 
>>> 
>>> Please be informed that your personal data are processed according to our data privacy policy as described on our website. Should you have any questions related to personal data protection, please contact 3DS Data Protection Officer at 3DS.compliance-privacy at 3ds.com<mailto:3DS.compliance-privacy at 3ds.com>
>>> 
>>> 
>>> For other languages, go to https://www.3ds.com/terms/email-disclaimer
> 
>