Re: [jakarta.ee-spec.committee] Jakarta EE Scope Statements Guidelines

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

The ECA/ICA/MCCA provide an additional grant that allows us to release specification documents under the Eclipse Foundation Specification License (EFSL). With this, I believe that the legal issues are addressed.

There are some exceptions, but the standard is that EE4J projects are licensed under  EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0. Specification documents developed in projects under those exceptional licenses are still subject to the EFSL grant in the committer/contributor agreements.

Wayne

On Thu, Apr 18, 2019 at 11:35 AM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

Wayne Beaton wrote on 4/18/19 7:18 AM:

Unless there is a compelling reason to keep them separate, the TCKs are in-scope for specification projects. That's not to say that they must be moved to the specification projects by any particular date.

Just to be clear...

The legal issues that previously caused us to decide that TCK projects must be separate from Specification projects no longer apply, correct?

Will all EE4J projects be under the same licensing scheme, including implementation and TCK projects?

I vaguely remember that IP contributions to specification projects would come with additional grants that we didn't want or need to apply to non-specification projects.  Is that no longer the case?

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.