This year I decided to switch my “default license” to EUPL-1.2. This is an OSI-approved free software license created and published by the European Union. And it is quite a divergence from the licenses I’ve used in the past. EUPL is a strong copyleft license that closes the “SaaS loophole” by requiring reciprocal licensing regardless of how the software is distributed.

Over the years it has been clear that we in the “open source” camp (as opposed to the “free software” camp) were wrong all along.

We won the debate, and gained little for users or developers. All that our efforts did was to make it easier for big corporations build things more cheaply and for billionaires to become trillionaires.

And so it is time to stop messing about with permissive licenses. If corporations don’t want to use our software under our terms, they are free to spend the effort or tokens to build their own.

you are viewing a single comment's thread
view the rest of the comments

[–] vas@lemmy.ml 1 points 1 day ago* (last edited 1 day ago)

I was talking about mixing indeed. An example of a license that I think is less strong - but can be mixed with EUPL - is MPL (the Mozilla one). Your quote clarifies what happens in that case though: EUPL's requirements still hold. I still haven't looked at it sufficiently carefully. Also, sadly, the referenced page has multiple mistakes so I feel I need to read the actual license in detail before getting convinced. (My take on tivoization is also different than what the author of the page where he says "Note: This is still controversial: ....".) That page is also just a "news" article, and not a definitive source. So it's OK to be less polished, but then it means a push for me to trust the license itself only.