alt Hacker NewsOn the face of it, no it doesn't say that. It just says the combined work can be MPL. Then someone can take that MPL work, and distribute it without source code because the MPL allows that. It explicitly says any conflict between the EUPL and the MPL shall be resolved in favor of the MPL.
Replies
> But as none of the compatible licenses come into conflict with the EUPL *by prohibiting the essential points* of publication of the source code and coverage of remote distribution (closing the SaaS loophole), these obligations, that are the core of the "reciprocal" condition, persist for the derivatives concerned.
aka: the compatible licenses do not put additional restrictions, so no, it is not MPL.
also, from the license:
> this Distribution or Communication can be done under the terms of this Compatible Licence..
So you are allowed distribution, not relicensing.
To simplify It seems to me that:
* GPL will automatically make something GPL.
* EUPL will automatically make something selectively dual-licensing. parts EUPL, parts whatever.
Also do note that EUPL is the first license to explicitly state that any issues fall under EU(Belgium) law, so EU has the last say on its license.
This isn’t the intent, and will hopefully be fixed/clarified in version 1.3: https://interoperable-europe.ec.europa.eu/collection/eupl/di...
A “conflict” is intended to mean the case that following some EUPL obligation (such as publishing the derived source code) wouldn’t be allowed under the alternative license.