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#sspl
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.
@kotaro gramted, all of tuhe #Forks that are #BSD-licensed had way more #effort put into them.
- I just think that #AssholeLicensing is as bad as #Tivolization in terms of #OpenSource and #useability.
#SSPL is still worse than #AGPLv3, but #AGPL & #GPLv3 are just completely disregarding the legal reality of #IP and #Licensing.
- If they don't want to accept #competition, they could've chosen @creativecommons #CCBYNCSA instead, but they did not!
Needless to say if I were a #developer of it and had contributed under #BSD license I'd expect to either get my code removed entirely or the license to be kept the same.
- And now you know why I'll refuse to sign any "#ContributorLicenseAgreement" (#CLA) UNLESS I get a paid, non - term-limited position as an enployee in return…
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
@landley @burnoutqueen Yeah...
#GPLv3 is a desaster as it's 99% ideology and 1% license text and alongside #AGPLv3 completely ignores the reality of how #licensing and #patents and #IP works.
- Not that I like the status-quo, but we'd rather see businesses steer clear of anything GPLv2+ or GPLv3 or worse.
And on the flipside we basically get "source available" stuff like #SSPL which only serves as a means to commit #AssetDenial and monopolize commercial offerings...
- I think #Linux being #GPLv2only is a good compromise and my personal gripes with #FSF & #GNUtils as well as #GlibC are something different...
@larsmb@mastodon.online
You see, when #OSI people talk about "license proliferation" they means "#copyleft proliferation" that is, in fact, the proliferation of licenses that protect the work from appropriation.
In fact, OSI approved over 100 mostly equivalent permissive licenses, among which some masterpiece like the #FairLicense https://opensource.org/license/fair just because they were backed by the right corporation.
They cry about license proliferation only when a #copyleft license conflict with the interests of their largest sponsors.
Indeed the #MongoDB #SSPL was not approved while #Amazon was one of the biggest OSI donor, while #CAL (that was even more "dangerous" as a copyleft according to the same arguments that got SSPL refused) was approved, because no #BigTech ever gave a shit about blockchain stuff (for obvious reasons).
The OSI behaviour over the years shows that they cry about license proliferation only to justify their refusals. So if they don't care, you shouldn't either.
Sure, conflicts among licenses exists (for example, you cannot mix code under the #HackingLicense and code under #GPL), but right now we need first and foremost to widen the overton windows that OSI gatekeepers try desperately to keep closed.
We have urgent need of new licenses that can protect the commons that we create without restricting their spread and evolution.
Code is Speech.
@lproven@vivaldi.net @tante@tldr.nettime.org
You see, when #OSI people talk about "license proliferation" they means "#copyleft proliferation" that is, in fact, the proliferation of licenses that protect the work from appropriation.
In fact, OSI approved over 100 mostly equivalent permissive licenses, among which some masterpiece like the #FairLicense https://opensource.org/license/fair just because they were backed by the right corporation.
They cry about license proliferation only when a #copyleft license conflict with the interests of their largest sponsors.
Indeed the #MongoDB #SSPL was not approved while #Amazon was one of the biggest OSI donor, while #CAL (that was even more "dangerous" as a copyleft according to the same arguments that got SSPL refused) was approved, because no #BigTech ever gave a shit about blockchain stuff (for obvious reasons).
The OSI behaviour over the years shows that they cry about license proliferation only to justify their refusals. So if they don't care, you shouldn't either.
Sure, conflicts among licenses exists (for example, you cannot mix code under the #HackingLicense and code under #GPL), but right now we need first and foremost to widen the overton windows that OSI gatekeepers try desperately to keep closed.
We have urgent need of new licenses that can protect the commons that we create without restricting their spread and evolution.
Code is Speech.
@lproven@vivaldi.net @tante@tldr.nettime.org
@Nicholasr_ITSulu @nixCraft nodds in agreement and since there are so many stakeholders with opposing interests and a #copyleft license, #GAFAMs can't #enshittify or #tivolize it!
- And due to #GPLv2only eben a move to #AssholeLicensing like #AGPLv3 or #SSPL is not possible!
@GossiTheDog consider putting all your content under #AGPLv3, #SSPL or even better #CCBYNCND?
I'm disappointed that despite #elasticsearch being #opensource again it seems there is no release under the open licence - only the #SSPL 😢
What a bunch of capitalists confronting eachother.
Apparently #SSPL is just, nothing more than a capitalistic response to a capitalist phenomenon, of course concerning the use of code with software by some companies solely to enrich themselves.
https://community.coops.tech/t/the-rise-of-the-server-side-public-license-sspl/2516
@xerxespersrex nodds in agreement...
- Shit like #SSPL & #RSAL is IMHO even worse than #SourceAvailable as it's literally "#AssholeLicensing"...
At least most source available products like #Tarsnap are honest that they are not #OpenSource!
@anderseknert Everyone who uses #AssholeLicensing like #SSPL or tries to infringe upon users' #FLOSS #Rights like #grsecurity & #RedHad do should be banned from any professional developments and supply chains as part of the #RiskAssessment and #RiskAvoidance in #DueDiligence.
- Anything else in criminal neglect at this point...
One can really see this is an older video, as it misses not only #0BSD between #PublicDomain and #MIT but also #SSPL right of #AGPLv3 in a tab that's right of it called "#AssetDenial" or "#Monopolistic" or just "#AssholeLicensing" and a tab right of that for "#SourceAvailable" licensing, but I get ahead of myself...
#Sarcasm #OpenSource #Licensing #Copyleft #Cipyright #Copywrong #rant #vent #venting
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
@marcan @fuchsiii Either way, like @landley I did the #copyleft experiment and those projects didn't see even remotely as much resonance or contribution as when I embraced #0BSD as a #PermissiveLicense (cuz #PublicDomain legally doesn't exist in #Germany: One cannot renounce #Authorship for legal reasons, otherwise #HateSpeech would be unprosecute-able, so only #Copyright lapses 70 years post-mortem of the Authors)...
- I think "#AssholeLicensing" like #SSPL is inherently unfree and #AGPLv3 is just an act of committing #AssetDenial which doesn't work.
TBH, the only way to preven #GAFAMs like Amazon from leeching #FLOSS is to either make #CCSS or offer the superior [#SaaS] solution by ticking boxes #aws can't ( i.e. due to #CloudAct, like #GDPR compliance) or inherently won't hecause it's antithetical to their business ( i.e. [airgapped] #SelfHosting & Support/Management Options for self-hosted systems)...
- #healthcare-IT based startups in the #EU pay Companies like #Telekom to host their medical data because unlike #Amazon they can and will evidently enshure their U.S. division can't leak that data to U.S. govt. agencies and if one butters them with enough money, they'll likely sign the hardest NDAs one can throw at them...
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst