It’s a done deal: MicroProfile is an Eclipse Foundation project
Colored confetti image via Shutterstock
Mike Milinkovich, the Executive Director of the Eclipse Foundation, announced that Eclipse MicroProfile project has joined the Eclipse Foundation under the Apache License v2.0 (ALv2). The only matter that needs to be resolved now is the dual-license of the project ALv2+EPL.
It’s official! The proposal for Eclipse MicroProfile has been approved and this project is now under the wing of the Eclipse Foundation.
— John Clingan (@jclingan) 14. Dezember 2016
Not so fast: Dual-license issue
Mike Milinkovich, the Executive Director of the Eclipse Foundation, broke the news about the creation of Eclipse MicroProfile in the MicroProfile discussion forum. Eclipse MicroProfile is joining the Eclipse Foundation under the Apache License v2.0 (ALv2). However, the only matter to be discussed now is the dual-license of the project.
The Eclipse Foundation Board also made a request that the Microprofile team re-consider dual-licensing the project ALv2+EPL. We would offer assistance in gathering up any required permissions from prior contributors. The reasons behind this request are:
- To support the conventions of the Eclipse community and its license.
- To support the copying of code between projects within the Eclipse community.
There is no down-side to adopters in having this dual license in place. So on behalf of the Eclipse community, I would respectfully ask that you consider this request.
David Blevins, the founder and CEO of Tomitribe, revealed that they are talking about it and that “dual license was discussed as a showstopper early on.” Milinkovich said that he does not recall “ever discussing EPL + ALv2” and emphasized that since MicroProfile has been fully approved to proceed with the ALv2 (only), “there is nothing preventing forward progress, nor is there a ‘show stopper’ happening here.”The Executive Director of the Eclipse Foundation added that in the Eclipse
The Executive Director of the Eclipse Foundation added that in the Eclipse Foundation Board discussion, “no one could articulate a downside to dual licensing EPL+ALv2.”
And to be honest, I cannot think of a downside either. Based on that, I was asked to make the request for the team to re-consider. However, if there is one just say so here, or point me to any prior conversations where that’s already been discussed. Regrettably, I cannot claim to have read every post in this thread.
Why Eclipse Foundation?
MicroProfile 1.0 was announced at JavaOne 2016. According to the project description, MicroProfile has “enough traction with the industry and community to be associated with a foundation.” They chose the Eclipse Foundation “due to its long history of providing great support for the Java Ecosystem and rigour with regards to dealing with IP. The MicroProfile community does not want to spend cycles on the infrastructure that is already available and acceptable via the Eclipse Foundation.”
Plus, Eclipse does not currently have any projects directly related to Microservices.