Attached: 1 image
Welp. It's official. #Redis is no longer #OSS
While I wasn't a contributor to the core, I presented on it dozens of times, talked to thousands, and wrote a book about it.
I probably wouldn't have done any of that with that kind of license.
Very disappointed.
From what I’ve understood SSPL is a ridiculously ambiguous license, it’s extreme copyleft. It’s not just “open source the tooling you use to host the software”, it can also be interpreted to mean “open source all the hardware and firmware you use to host the software”. No one wants to risk going to court for that so corporate wants to use SSPL licensed software.
The ambiguity is a valid concern. Hopefully the next version addresses this a bit better. This being said mega corps will call anything they can’t abuse for profit “extreme”. So if they think it’s extreme that just means we are on the right track.
lmao imagine allowing to run your software only on RISC-V boxes basically, pretty based but also a shoot in the foot in terms of acquiring any major funding
Regardless of whether it is too strong or too ambiguous, it is absolutely an open source license regardless of whether the OSI and/or FSF approve of it.
From what I’ve understood SSPL is a ridiculously ambiguous license, it’s extreme copyleft. It’s not just “open source the tooling you use to host the software”, it can also be interpreted to mean “open source all the hardware and firmware you use to host the software”. No one wants to risk going to court for that so corporate wants to use SSPL licensed software.
AGPL is the best license you can go for IMO.
The ambiguity is a valid concern. Hopefully the next version addresses this a bit better. This being said mega corps will call anything they can’t abuse for profit “extreme”. So if they think it’s extreme that just means we are on the right track.
lmao imagine allowing to run your software only on RISC-V boxes basically, pretty based but also a shoot in the foot in terms of acquiring any major funding
To be fair the license is not meant to cause this and has never been enforced like this. The license was written for software tooling.
Huh I interpreted it as “everything involved with deployment” so connecting services, scripts, parts the OS that touch it, and an configurations.
I guess that is the ambiguity you mentioned
Regardless of whether it is too strong or too ambiguous, it is absolutely an open source license regardless of whether the OSI and/or FSF approve of it.
deleted by creator
In what way does SSPL not allow free redistribution for users but does for developers? It requires the source to be made available just like AGPL.
Damn, those copyleft extremists!