#sspl — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #sspl, aggregated by home.social.
-
"After I joined the company, and a year of evaluating alternatives, in March 2024, we decided to move Redis to the SSPL license. This achieved our goal—AWS and Google now maintain their own fork ..."
#RowanTrollope, 2025
Huh. No wonder warning them that a relicense to SPPL would only result in a fork had no impact. It never occurred to me that getting corporate re-users to fork was the *goal*! But that kind of makes sense.
-
"After I joined the company, and a year of evaluating alternatives, in March 2024, we decided to move Redis to the SSPL license. This achieved our goal—AWS and Google now maintain their own fork ..."
#RowanTrollope, 2025
Huh. No wonder warning them that a relicense to SPPL would only result in a fork had no impact. It never occurred to me that getting corporate re-users to fork was the *goal*! But that kind of makes sense.
-
"After I joined the company, and a year of evaluating alternatives, in March 2024, we decided to move Redis to the SSPL license. This achieved our goal—AWS and Google now maintain their own fork ..."
#RowanTrollope, 2025
Huh. No wonder warning them that a relicense to SPPL would only result in a fork had no impact. It never occurred to me that getting corporate re-users to fork was the *goal*! But that kind of makes sense.
-
"After I joined the company, and a year of evaluating alternatives, in March 2024, we decided to move Redis to the SSPL license. This achieved our goal—AWS and Google now maintain their own fork ..."
#RowanTrollope, 2025
Huh. No wonder warning them that a relicense to SPPL would only result in a fork had no impact. It never occurred to me that getting corporate re-users to fork was the *goal*! But that kind of makes sense.
-
A couple of years back, a bunch of projects started switching to proprietary Source Available licenses like #SSPL. I predicted that they would soon regret it, as they started to be replaced with forks of their own software. Feeling pretty smug reading this ...
"Redis bets big on an open source return
The company is hopeful that changing its license will allow it to better compete with the Valkey fork."
#MattAsay, May 2025
https://www.infoworld.com/article/3975620/redis-bets-big-on-an-open-source-return.html
(1/2)
-
I missed this news a couple of days ago: #Redis is officially FOSS again, as it has backtracked from #SSPL and moved to AGPL (which IMHO is what they should have adopted all along).
This closes the cycle of my prediction:
- That Redis had made a terrible mistake by switching to SSPL
- That the switch to SSPL would have just resulted in a fork fever that would have critically eroded their user base and reputation
- That those forks would have been eventually included in standard Linux distros instead of Redis itself because of their OSI-compatible licenses, and adopted as alternatives to Redis by the cloud providers (hence invalidating the whole point of SSPL)
- That Redis would have eventually backtracked and switched back to AGPL
There’s a 5th point in my prediction that hasn’t materialized yet though: that the damage is already done and it will be hard to revert.
Fedora, Arch and Alpine have all replaced Redis with Valkey in their repos already, and Debian has opted to temporarily provide both.
Many Docker configurations, cloud and on-prem deployments, Terraform templates, home servers etc. have already all migrated to Valkey.
Not only, but the seismic fork allowed Valkey to implement features that have been requested in Redis for a while but not implemented because of the most complex governance of the project (like RDMA). Plus, while Valkey guarantees parity of features as of Redis 7.2.4, the mismatch of features is only supposed to increase as the hard fork diverges. This makes it even more unlikely that an enterprise software that has already migrated to Valkey takes the risk of migrating back to Redis later.
Redis’ decision leaves MongoDB as the only major SSPL-licensed project out there. And that is also coming with its costs. For example, the Linux Foundation has just opened its arms to Microsoft’s DocumentDB rather than MongoDB because the former is released under an OSI-compatible MIT license rather than Mongo’s SSPL.
The other project that still partly uses SSPL is Elastic. And even in that case the decision has backfired. It opened the way to AWS to release OpenSearch under an Apache license, and grab a lot of FOSS developers to power its proprietary cloud efforts for free instead.
-
The Story of #Valkey 🚀 🧑🏫
Back in early 2024, a popular #opensource project, #Redis, made a bold change: it shifted its licensing from #BSD to a more restrictive #SSPL license...
-
@sogrady I don't entirely agree with the take that Redis relicensing to #AGPL means the #SSPL has lost; to me, it's more of a question of timing of Redis' move, as opposed to MongoDB's original move to the SSPL. More here: https://findthethread.blog/Licentious-Licensing/
-
What I learned during the license switch —Creator of Redis
What I learned during the license switch —Creator of Redis #redis #opensource #sspl #fauxpen #valkey -
Hot Take: The misinformation about the SSPL needs to stop.
If you disagree with the SSPL, that's fine.
But if you argue against what you think what the SSPL is, rather than what it actually is, you are actively harming the FOSS community.
The SSPL is based on the AGPL (Edit: It's actually based on the GPLv3). MongoDB (the company) has a nice little difference PDF that you can read. https://webassets.mongodb.com/_com_assets/legal/SSPL-compared-to-AGPL.pdf
The OSI says the SSPL is not Open Source. I understand their reasoning, and that's their prerogative. But I think this call was more harmful than it was beneficial.
The FSF said they'd look into the SSPL and make a comment, it's been a long while and they've been silent on the matter. Claims that the SSPL is not a Free Software license are false. Note that I'm also not making a claim that the SSPL is a Free Software license, because that equally lacks evidence.
I appreciate that people *really* do not like the requirements for Section 13. That's fine, if that's your beef with the SSPL, then say that instead of spreading falsities. I *really* don't like it when software fails to provide Freedom 3. I prefer copyleft licenses over permissive licenses. Some people prefer licenses that allow people to close the source later, I disagree with that.
Can we please just argue against realities, instead of fantasies? Thank you.
-
Last year, #Redis changed its license to the #SSPL, which is neither an #OpenSource nor a #FreeSoftware license. This led to #Valkey, a fork and drop-in replacement.
Now Redis has decided to go back to a real Free Software license, the #GNU #AGPL. This is a great decision, although it remains to be seen if they reverted their decision in time, or if it is too late and the community will continue with Valkey and not look back.
-
@brouhaha #OpenSearch has continued to grow and do well even after #Elasticsearch relicensed. In some steep heavy irony, #Graylog had moved to #OpenSearch from #Elastic, which should have been an obvious example to everyone else that SSPL is absolutely terrible for your dev community and business. (Ditto for BuSL).
Shot:
https://graylog.org/post/graylog-v4-0-licensing-sspl/Chaser:
https://go2docs.graylog.org/1380099/planning_your_deployment/planning_your_upgrade_to_opensearch.htm -
I'll start: #Graylog is #SSPL licensed (which is NOT a #FOSS license) and does not accept any contributions without giving up your copyright completely. They also removed a really essential feature (user groups) from the free version, but continue to offer the exact same feature with a different name behind their ridiculously expensive "Enterprise License" paywall.
Graylog was #GPL licensed up until 4.0 (2021).
-
Elastic announces open source license option for #Elasticsearch https://www.admin-magazine.com/News/Open-Source-AGPL-Added-as-License-Option-for-Elasticsearch
#AGPL #OpenSource #ELv2 #SSPL #OSI #license #Elastic -
Elasticsearch 打算要回來提供 AGPL 授權
在「Elasticsearch is open source, again (elastic.co)」這邊看到的，Elasticsearch 目前是自家的 ELv2 以及 SSPL 授權，現在打算要提供 AGPL 授權了：「Elasticsearch is Open Source, Again」。
不過應該也
#Computer #Murmuring #SearchEngine #Software #amazon #aws #elastic #elasticseach #elv2 #license #open #opensearch #source #sspl
-
Elasticsearch 打算要回來提供 AGPL 授權
在「Elasticsearch is open source, again (elastic.co)」這邊看到的，Elasticsearch 目前是自家的 ELv2 以及 SSPL 授權，現在打算要提供 AGPL 授權了：「Elasticsearch is Open Source, Again」。
不過應該也
#Computer #Murmuring #SearchEngine #Software #amazon #aws #elastic #elasticseach #elv2 #license #open #opensearch #source #sspl
-
Elasticsearch 打算要回來提供 AGPL 授權
在「Elasticsearch is open source, again (elastic.co)」這邊看到的，Elasticsearch 目前是自家的 ELv2 以及 SSPL 授權，現在打算要提供 AGPL 授權了：「Elasticsearch is Open Source, Again」。
不過應該也
#Computer #Murmuring #SearchEngine #Software #amazon #aws #elastic #elasticseach #elv2 #license #open #opensearch #source #sspl
-
Elasticsearch 打算要回來提供 AGPL 授權
在「Elasticsearch is open source, again (elastic.co)」這邊看到的，Elasticsearch 目前是自家的 ELv2 以及 SSPL 授權，現在打算要提供 AGPL 授權了：「Elasticsearch is Open Source, Again」。
不過應該也
#Computer #Murmuring #SearchEngine #Software #amazon #aws #elastic #elasticseach #elv2 #license #open #opensearch #source #sspl
-
Elasticsearch 打算要回來提供 AGPL 授權
在「Elasticsearch is open source, again (elastic.co)」這邊看到的，Elasticsearch 目前是自家的 ELv2 以及 SSPL 授權，現在打算要提供 AGPL 授權了：「Elasticsearch is Open Source, Again」。
不過應該也
#Computer #Murmuring #SearchEngine #Software #amazon #aws #elastic #elasticseach #elv2 #license #open #opensearch #source #sspl
-
"Last Thursday... Redis announced that it had changed the license covering its software from the open-source 3-Clause BSD License to the Redis Source Available License and the Server Side Public License, both source-available proprietary licenses..."
#ChristineHall, 2024
-
Как компании зарабатывают на опенсорсе, а потом выкидывают его
Финансирование разработки Kubernetes крупнейшими спонсорами на GitHub за последние десять лет, источник Эти компании сначала при помощи сообщества разрабатывают опенсорсный софт или берут готовый, строят на нём прибыльный бизнес, зарабатывают миллионы. А потом меняют лицензию, оставляя контрибуторов, пользователей и партнёров в недоумении, что им делать. Такова бизнес-модель некоторых современных компаний вроде Redis Labs . Но ещё хуже поступают крупные облачные провайдеры. Они просто используют готовые решения, вообще не занимаясь разработкой и убивая бизнес «паразитов», описанных выше. Здесь вообще паразиты в квадрате. И весь этот террариум кормится опенсорсом.
https://habr.com/ru/companies/ruvds/articles/811679/
#ruvds_статьи #Amazon #Redis #ElasticSearch #OpenSearch #Redis_Enterprise_Cloud #Apache 20 #Server_Side_Public_License #SSPL #Berkeley_Software_Distribution #BSD #HashiCorp #Terraform #Mozilla_Public_License #MPL #Business_Source_License #BSL #Redict #KeyDB #Valkey #OpenTofu #OpenTF
-
Как компании зарабатывают на опенсорсе, а потом выкидывают его
Финансирование разработки Kubernetes крупнейшими спонсорами на GitHub за последние десять лет, источник Эти компании сначала при помощи сообщества разрабатывают опенсорсный софт или берут готовый, строят на нём прибыльный бизнес, зарабатывают миллионы. А потом меняют лицензию, оставляя контрибуторов, пользователей и партнёров в недоумении, что им делать. Такова бизнес-модель некоторых современных компаний вроде Redis Labs . Но ещё хуже поступают крупные облачные провайдеры. Они просто используют готовые решения, вообще не занимаясь разработкой и убивая бизнес «паразитов», описанных выше. Здесь вообще паразиты в квадрате. И весь этот террариум кормится опенсорсом.
https://habr.com/ru/companies/ruvds/articles/811679/
#ruvds_статьи #Amazon #Redis #ElasticSearch #OpenSearch #Redis_Enterprise_Cloud #Apache 20 #Server_Side_Public_License #SSPL #Berkeley_Software_Distribution #BSD #HashiCorp #Terraform #Mozilla_Public_License #MPL #Business_Source_License #BSL #Redict #KeyDB #Valkey #OpenTofu #OpenTF
-
Как компании зарабатывают на опенсорсе, а потом выкидывают его
Финансирование разработки Kubernetes крупнейшими спонсорами на GitHub за последние десять лет, источник Эти компании сначала при помощи сообщества разрабатывают опенсорсный софт или берут готовый, строят на нём прибыльный бизнес, зарабатывают миллионы. А потом меняют лицензию, оставляя контрибуторов, пользователей и партнёров в недоумении, что им делать. Такова бизнес-модель некоторых современных компаний вроде Redis Labs . Но ещё хуже поступают крупные облачные провайдеры. Они просто используют готовые решения, вообще не занимаясь разработкой и убивая бизнес «паразитов», описанных выше. Здесь вообще паразиты в квадрате. И весь этот террариум кормится опенсорсом.
https://habr.com/ru/companies/ruvds/articles/811679/
#ruvds_статьи #Amazon #Redis #ElasticSearch #OpenSearch #Redis_Enterprise_Cloud #Apache 20 #Server_Side_Public_License #SSPL #Berkeley_Software_Distribution #BSD #HashiCorp #Terraform #Mozilla_Public_License #MPL #Business_Source_License #BSL #Redict #KeyDB #Valkey #OpenTofu #OpenTF
-
Как компании зарабатывают на опенсорсе, а потом выкидывают его
Финансирование разработки Kubernetes крупнейшими спонсорами на GitHub за последние десять лет, источник Эти компании сначала при помощи сообщества разрабатывают опенсорсный софт или берут готовый, строят на нём прибыльный бизнес, зарабатывают миллионы. А потом меняют лицензию, оставляя контрибуторов, пользователей и партнёров в недоумении, что им делать. Такова бизнес-модель некоторых современных компаний вроде Redis Labs . Но ещё хуже поступают крупные облачные провайдеры. Они просто используют готовые решения, вообще не занимаясь разработкой и убивая бизнес «паразитов», описанных выше. Здесь вообще паразиты в квадрате. И весь этот террариум кормится опенсорсом.
https://habr.com/ru/companies/ruvds/articles/811679/
#ruvds_статьи #Amazon #Redis #ElasticSearch #OpenSearch #Redis_Enterprise_Cloud #Apache 20 #Server_Side_Public_License #SSPL #Berkeley_Software_Distribution #BSD #HashiCorp #Terraform #Mozilla_Public_License #MPL #Business_Source_License #BSL #Redict #KeyDB #Valkey #OpenTofu #OpenTF
-
Honestly, this is not bad. Wonder if someone can put together an open source license album with an SSPL bonus track just to upset the purists. https://arstechnica.com/?p=2015379
-
Having had a front-row seat for #MongoDB's travails in adopting the #SSPL, I have some thoughts on #Redis' recent relicensing. Bottom line, I don't think the #OSI is doing itself or the open-source community any favors by opposing these reasonable defensive moves by vendors. The SSPL is much closer to the spirit of open-source than some of what goes on in the #cloud world, even if that respects the letter of the definition. https://findthethread.blog/redis/mongodb/database/open-source/enterprise/2024/04/04/Defensive-Moves.html #foss #opensource
-
[Перевод] В погоне за заменой Redis
21 марта Redis Ltd. объявила, что, начиная с Redis 7.4, ее «in-memory data store» будет выпускаться под несвободными лицензиями с доступным (source-available) исходным кодом. Новость малоприятная, но вполне ожидаемая. Необычно в этой ситуации обилие альтернатив для тех, кто хочет остаться со свободным ПО: есть как минимум четыре варианта замены, включая уже существующий форк под названием KeyDB и недавно анонсированный проект Valkey от Linux Foundation. Вопрос теперь в том, что предпочтут пользователи, провайдеры и создатели дистрибутивов Linux.
https://habr.com/ru/companies/flant/articles/804969/
#субд #redis #keydb #valkey #open_source #лицензии #bsl #sspl #bsd #garnet
-
Btw I’m wondering how this license may impact use-cases where the component A released under #SSPL is not used directly by software B, but software B uses C (or it forks C), which in turn uses A (i.e. if the license is transitive).
An example: in #Platypush I use #Redis quite heavily - as an in-memory cache, as a pub/sub framework for inter-process communication, and as a memory queue.
Platypush is already FOSS, but it’s released under a relatively permissive MIT license. (I’ve pondered a lot over the pros/cons of MIT vs. *GPL when licensing a product like Platypush, in the future I may also considering switching to AGPL, but for now MIT is a good trade-off).
This means that people are free to copy the code of a Platypush plugin into their projects. Or use its plugins as libraries for their own integrations. Or extend it with their own plugins. Or make a fork and expose it as a service on their cloud. And the MIT license doesn’t require anybody to redistribute the full source.
But Platypush also uses Redis, which is now under SSPL.
What should company X, which has made their closed fork of Platypush with a bunch of proprietary integrations, and maybe distribute it as a service, do now? They are basically exposing a closed service that uses Redis under the hood, which violates SSPL. But the service itself is a fork of an open service released under MIT, so there’s no violation from that point of view.
In other words, does SSPL override other more permissive licenses every time a product is exposed as a service?
-
From my PoV, it's certainly a license that's preferable to that of BSD or MIT. There's a solid reasoning behind this HERE.
After all, even Tanenbaum himself was surprised to discover that MINIX is the most ubiquitous of all operating systems:
> "I guess that makes MINIX the most widely used computer operating system in the world, even more than Windows, Linux, or MacOS."
The SSPL being akin to that of the AGPL avoids that sort of dreadful situation, ensuring protections for the end users that not even the GPL affords them where #SaaS is concerned ;)
⛵
.
-
#Redis abandons Open Core and moves to Open Nothing.
Redis Labs 2019:
"This change has zero effect on the Redis core license, which is and will always be licensed under the 3-Clause-BSD."
redis.com/blog/redis-labs-modu…
Redis (just Redis[0]) 2024:
"Beginning today, all future versions of Redis will be released with source-available licenses. Starting with Redis 7.4, Redis will be dual-licensed under the Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). Consequently, Redis will no longer be distributed under the three-clause Berkeley Software Distribution (BSD)."
redis.com/blog/redis-adopts-du…
[0] redis.com/press/redis-labs-bec…
#RedisSharedSource #RedisSourceAvailable #RedisProprietary #RedisCore
#RedisSSPL #RedisRSAL #SSPL #RSAL -
#Redis abandons Open Core and moves to Open Nothing.
Redis Labs 2019:
"This change has zero effect on the Redis core license, which is and will always be licensed under the 3-Clause-BSD."
redis.com/blog/redis-labs-modu…
Redis (just Redis[0]) 2024:
"Beginning today, all future versions of Redis will be released with source-available licenses. Starting with Redis 7.4, Redis will be dual-licensed under the Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). Consequently, Redis will no longer be distributed under the three-clause Berkeley Software Distribution (BSD)."
redis.com/blog/redis-adopts-du…
[0] redis.com/press/redis-labs-bec…
#RedisSharedSource #RedisSourceAvailable #RedisProprietary #RedisCore
#RedisSSPL #RedisRSAL #SSPL #RSAL -
#Redis abandons Open Core and moves to Open Nothing.
Redis Labs 2019:
"This change has zero effect on the Redis core license, which is and will always be licensed under the 3-Clause-BSD."
redis.com/blog/redis-labs-modu…
Redis (just Redis[0]) 2024:
"Beginning today, all future versions of Redis will be released with source-available licenses. Starting with Redis 7.4, Redis will be dual-licensed under the Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). Consequently, Redis will no longer be distributed under the three-clause Berkeley Software Distribution (BSD)."
redis.com/blog/redis-adopts-du…
[0] redis.com/press/redis-labs-bec…
#RedisSharedSource #RedisSourceAvailable #RedisProprietary #RedisCore
#RedisSSPL #RedisRSAL #SSPL #RSAL -
#Redis abandons Open Core and moves to Open Nothing.
Redis Labs 2019:
"This change has zero effect on the Redis core license, which is and will always be licensed under the 3-Clause-BSD."
redis.com/blog/redis-labs-modu…
Redis (just Redis[0]) 2024:
"Beginning today, all future versions of Redis will be released with source-available licenses. Starting with Redis 7.4, Redis will be dual-licensed under the Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). Consequently, Redis will no longer be distributed under the three-clause Berkeley Software Distribution (BSD)."
redis.com/blog/redis-adopts-du…
[0] redis.com/press/redis-labs-bec…
#RedisSharedSource #RedisSourceAvailable #RedisProprietary #RedisCore
#RedisSSPL #RedisRSAL #SSPL #RSAL -
#Redis abandons Open Core and moves to Open Nothing.
Redis Labs 2019:
"This change has zero effect on the Redis core license, which is and will always be licensed under the 3-Clause-BSD."
redis.com/blog/redis-labs-modu…
Redis (just Redis[0]) 2024:
"Beginning today, all future versions of Redis will be released with source-available licenses. Starting with Redis 7.4, Redis will be dual-licensed under the Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1). Consequently, Redis will no longer be distributed under the three-clause Berkeley Software Distribution (BSD)."
redis.com/blog/redis-adopts-du…
[0] redis.com/press/redis-labs-bec…
#RedisSharedSource #RedisSourceAvailable #RedisProprietary #RedisCore
#RedisSSPL #RedisRSAL #SSPL #RSAL -
My Apologies and thanks are due to the OP of the rabbit hole that led me here, their username got lost in a fog of FUD and Corporate apologia.
but this was the escape hatch I was looking for, thanks.
Toward Copyleft Equality for All
by Bradley M. Kuhn#FOSS #AGPL #SSPL #AfferoGPL #CopyLeft
https://sfconservancy.org/blog/2020/jan/06/copyleft-equality/
-
Is there an FSF antifa agenda?
If not, why?
Is fascism really not a concern?
#freesoftware #foss #floss #flosh #fosh #libresoftware #sspl #agpl #copyleft
-
Is there an FSF antifa agenda?
If not, why?
Is fascism really not a concern?
#freesoftware #foss #floss #flosh #fosh #libresoftware #sspl #agpl #copyleft
-
Is there an FSF antifa agenda?
If not, why?
Is fascism really not a concern?
#freesoftware #foss #floss #flosh #fosh #libresoftware #sspl #agpl #copyleft
-
Is there an FSF antifa agenda?
If not, why?
Is fascism really not a concern?
#freesoftware #foss #floss #flosh #fosh #libresoftware #sspl #agpl #copyleft
-
Is there an FSF antifa agenda?
If not, why?
Is fascism really not a concern?
#freesoftware #foss #floss #flosh #fosh #libresoftware #sspl #agpl #copyleft
-
I don't see a clear answer in the history of the email thread that you've linked regarding the question of how the SSPL does not satisfy the OSD.
I find that there are various people's individual opinions represented in the meeting minutes, but these don't represent the decisions of the OSI (or the FSF).
I am interested in strong copyleft licenses and the SSPL sounds like a strong copyleft license to me, on first reading, as an amateur.
It is not clear to me why it is not a strong (and healthy) open source free software license.
If this information is already clearly summarized somewhere, please point me to that location.
Otherwise, it would be great to hear a brief summary of how the SSPL violates the rules of the OSD.
#freesoftware #foss #floss #flosh #fosh #libresoftware #agpl #sspl #fsf #osi #copyleft
-
I don't see a clear answer in the history of the email thread that you've linked regarding the question of how the SSPL does not satisfy the OSD.
I find that there are various people's individual opinions represented in the meeting minutes, but these don't represent the decisions of the OSI (or the FSF).
I am interested in strong copyleft licenses and the SSPL sounds like a strong copyleft license to me, on first reading, as an amateur.
It is not clear to me why it is not a strong (and healthy) open source free software license.
If this information is already clearly summarized somewhere, please point me to that location.
Otherwise, it would be great to hear a brief summary of how the SSPL violates the rules of the OSD.
#freesoftware #foss #floss #flosh #fosh #libresoftware #agpl #sspl #fsf #osi #copyleft
-
I don't see a clear answer in the history of the email thread that you've linked regarding the question of how the SSPL does not satisfy the OSD.
I find that there are various people's individual opinions represented in the meeting minutes, but these don't represent the decisions of the OSI (or the FSF).
I am interested in strong copyleft licenses and the SSPL sounds like a strong copyleft license to me, on first reading, as an amateur.
It is not clear to me why it is not a strong (and healthy) open source free software license.
If this information is already clearly summarized somewhere, please point me to that location.
Otherwise, it would be great to hear a brief summary of how the SSPL violates the rules of the OSD.
#freesoftware #foss #floss #flosh #fosh #libresoftware #agpl #sspl #fsf #osi #copyleft
