Looks like there will be a need for another fork 😒
Looks like this will be it: https://codeberg.org/redict/redict
You must log in or # to comment.
In practice, nothing changes for the Redis developer community who will continue to enjoy permissive licensing under the dual license. At the same time, all the Redis client libraries under the responsibility of Redis will remain open source licensed. Redis will continue to support its vast partner ecosystem – including managed service providers and system integrators – with exclusive access to all future releases, updates, and features developed and delivered by Redis through its Partner Program. There is no change for existing Redis Enterprise customers.
Seems this currently touches only cloud “resellers” of redis
That’s just marketing speak. Neither of the new licenses are OSI approved or FOSS.
FOSS projects must not discriminate the use of the project. Meaning no matter you host it for internal use, or resell the project as a service, they shall be treated the same with the same rights.
Ffffork it dead. Needs a better name anyway.
Blueis readthis OpenRedis (lol) wrotethat Redis95 Yakvs
OpenRedis, so they can never close it
OpenAI stares away
That’s likely a trademark violation.
wrotedat
hmm, or bluedat
As predicted: https://codeberg.org/redict/redict
Are all these wacky licenses because the OSI doesn’t have an AGPL (ostensibly anti-cloud) equivalent BSD style permissive license?
With SSPLv1, does that mean one can sell redis hosting as long as everything used to manage it is open source? It says it’s based on AGPL. So if say digitalocean open sourced all their api’s and UI they could still offer managed redis. It seems like the answer is yes but then the blog post also says
Under the new license, cloud service providers hosting Redis offerings will no longer be permitted to use the source code of Redis free of charge.
That sounds like no.
This just shows the true intention of the SSPLv1, i.e. to openwash what is in reality a shared-source license.
