> and Source Available, a set of licenses that allow users to see and modify your source code provided they meet some kind of criteria you set up, such as not using the code for commercial purposes or not doing things you don't like with it.
Last time I checked GPL explicitly allows using the code for any purpose ("Freedom 0"). FSF is also clear that it's fine with people making money off free software. The requirement to distribute code together with binaries makes many kinds of business impossible with GPL-d software, but that's a side effect, not the goal as in "Source Available" licenses.
Some people have argued that, yes. I've even argued it occasionally in the past.
The short justification given is that even though the GPL doesn't let you do everything, it still doesn't interfere with the 4 essential freedoms that Open Source guarantees. You may or may not agree with that justification.
But the people arguing in favor of SSPL as an Open Source license are moving in the wrong direction. If TechCrunch wanted to make the argument that the GPL wasn't free enough for inclusion into Open Source, they could do so. Instead, they're arguing that because the GPL might stretch the definition, we should just go whole hog and introduce straight-up end-user usage restrictions as well.
Techcrunch is taking the, "your thing isn't perfect, so we should all make it worse" position.
> The short justification given is that even though the GPL doesn't let you do everything, it still doesn't interfere with the 4 essential freedoms that Open Source guarantees. You may or may not agree with that justification.
Wait, what? "Four essential freedoms" are part of FSF philosophy, not Open Source, and GPL is literally the canonical example of a license that guarantees and safeguards them. Many Open Source (not Free Software) licenses do not, in fact, guarantee these freedoms.
Yes, the open source definition has its own rules. The one that seems most relevant here is:
"No Discrimination Against Fields of Endeavor
"The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research."
I am conflating Open Source and FSF, and I think people are very right to call me out on that. Especially in this context :)
The point I was trying to get at is that regardless of existing debates over the merits of permissive vs. copyleft licenses, neither side of that debate would say that SSPL belongs here.
Permissive license advocates would say that while they dislike GPL's restrictions, adding more restrictions is a bad idea. GPL advocates would say that the point of the GPL is to safeguard the 4 essential freedoms, and SSPL doesn't safeguard them.
Techcrunch is arguing that because there isn't perfect consensus within FOSS, FLOSS, and Open Source communities, that we might as well just turn this whole thing into a free-for-all.
No. If you wanna get technical about it GPL is structured around ensuring every user can see and modify the code, and do whatever they want with it, except prevent people from doing the first thing (seeing and modifying the code). It's sort of a vacuously false thing where "provided they meet some kind of criteria you set up" has the criteria of ensuring the original clause of "a set of licenses that allow users to see and modify your source code".
GPL is source available, then?