Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Licensing considerations for EE4J implementation projects
Not to sound like a smart-ass here, but the PMC minutes explicitly state that sub-projects are not required to follow the same licencing as their parent project.

They also state that EPL-2.0 is being considered for APIs and Specs, but that implementations might be allowed to use their preferred licencing scheme.

Can we all please calm down and read everything before we start arguing about non-issues?

Mariano Amar

Senior Consultant

email/hangouts: mariano.amar@xxxxxxxxxx
skype: marianoamar

AVISO DE CONFIDENCIALIDAD DE CORREO ELECTRÓNICO

Esta comunicación contiene información que es confidencial y también puede contener información privilegiada. Es para uso exclusivo del destinatario. Si usted no es el destinatario tenga en cuenta que cualquier distribución, copia o uso de esta comunicación o la información que contiene está estrictamente prohibida. Si usted ha recibido esta comunicación por error por favor notifíquelo por correo electrónico(info@xxxxxxxxxx) o por teléfono (+54 11 3249 7503)

This communication contains information that is confidential and may also be privileged. It is for the exclusive use of the recipient. If you are not the intended note that any distribution, copying or use of this communication or the information it contains is strictly prohibited. If you have received this communication in error please notify us by email(info@xxxxxxxxxx) or phone (+54 11 3249 7503)


On Tue, Jan 23, 2018 at 1:29 PM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> wrote:
On 2018-01-23 11:21 AM, Werner Keil wrote:
So with Vert.x or JNoSQL, should they ever apply EPL2, does one license have to be "primary" and the other "secondary" or can they also remain side-by side as they are now with those projects?

 Yes, those projects can move from EPL-1.0+APACHE-2.0 to EPL-2.0+APACHE-2.0 any time that they want.

Except JNoSQL which already uses an EPL 1 based licensing (so does Yasson and no change is proposed there) if either MicroProfile components were to migrate under the EE4J TLP or projects like CDI, Bean Validation, Portlet, etc. all of which are strictly Apache 2, they will face that question.

If Eclipse MicroProfile ever moved to the EE4J top-level project, they could retain their existing APACHE-2.0 licensing. There is no fixed requirement to change licenses, although they can do so if desired. Eclipse Ozark (MVC) is a current example of that. AFAIK, Ozark is intending to retain its APACHE-2.0 licensing, which it can do with agreement of the PMC and the Eclipse Foundation Board. This is all quite ordinary licensing "stuff" for us.

--
Mike Milinkovich
mike.milinkovich@eclipse-foundation.org
(m) +1.613.220.3223


_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community


Back to the top