Redis changes license from BSD-3 to dual RSALv2+SSPLv1
1–10 of 25 posts
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#2Previous discussion: https://news.ycombinator.com/item?id=39772562
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#3Let the forking ensue. What a stupid move. They have illegally removed the BSD headers from contributions by various cloud vendors like Redhat and Amazon. I hope they can all get together to.maintain a fork, and maybe sue Redis Inc. for this unlawful infringment of there copyrights.
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#4[deleted]
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#5[deleted]
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#6At least one community fork (redict) has already been announced:
https://news.ycombinator.com/item?id=39789986
I hope the community doesn't fracture too much and that at least one of possibly many forks gets enough momentum to be long-term sustainable.
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#7I haven't read this license but I wished they had at least gone with the BASL.
https://en.wikipedia.org/wiki/Business_Source_License
IANAL, but AFAICT the BASL is not open-source, but it is _eventually_-open-source is in the source will automatically transition to being open source (GPL v2 or compatible... not sure if either BSD or AGPL work).
But if you are going to go source available, license proliferation is still a problem, please try to maintain sanity.
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#8I am building a major open-source package around redis.
This kills it.
AGPL, I could go with. AGPL/proprietary dual licensing works well. There's an open ecosystem and a closed one.
Non-free is a non-starter. It's no longer GPL-compatible. EVERY project under the GPL using redis now has a potential legal liability from (what's looking like) a sleazeball company.
Now I need to figure out if I should move to a fork or switch to a different package. Fortunately, I have a nice key-value store abstraction, so it's easy to switch.
I expect distributions like Debian, and Ubuntu by proxy, will move away from having a redis .deb as well.
The damnable thing here is the dishonest copy: "In practice, nothing changes for the Redis developer community who will continue to enjoy permissive licensing under the dual license."
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#9I am building a major open-source package around redis. This kills it. AGPL, I could go with. AGPL/proprietary dual licensing works well. There's an open ecosystem and a closed one. Non-free is a non-starter. It's no longer GPL-compatible. EVERY project under the GPL using redis now has a potential legal liability from (what's looking like) a sleazeball company. Now I need to figure out if I should move to a fork or…
> I expect distributions like Debian, and Ubuntu by proxy, will move away from having a redis .deb as well.
What about this change indicates that? This sounds like fearmongering, the new licenses really shouldn't affect this use case?
Re: Redis changes license from BSD-3 to dual RSALv2+SSPLv1
#10I am building a major open-source package around redis. This kills it. AGPL, I could go with. AGPL/proprietary dual licensing works well. There's an open ecosystem and a closed one. Non-free is a non-starter. It's no longer GPL-compatible. EVERY project under the GPL using redis now has a potential legal liability from (what's looking like) a sleazeball company. Now I need to figure out if I should move to a fork or…
> I expect distributions like Debian, and Ubuntu by proxy, will move away from having a redis .deb as well. What about this change indicates that? This sounds like fearmongering, the new licenses really shouldn't affect this use case?
The new license is incompatible with Debian policy:
https://www.debian.org/doc/debian-policy/ch-archive.html#the...
The new licensing scheme effectively excludes redis from most of the open ecosystem, by cascading network effects from things like this. In this case, if you're building a package, if you pick redis, you've excluded yourself from distribution in many major distros.
Ditto for many other similar effects.
It's not fear-mongering. It's following laws and policies.