#sspl — Public Fediverse posts

"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

https://redis.io/blog/agplv3/

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.

#Redis #SSPL #SourceAvailable #AGPL

"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

https://redis.io/blog/agplv3/

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.

#Redis #SSPL #SourceAvailable #AGPL

"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

https://redis.io/blog/agplv3/

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.

#Redis #SSPL #SourceAvailable #AGPL

"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

https://redis.io/blog/agplv3/

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.

#Redis #SSPL #SourceAvailable #AGPL

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)

#SourceAvailable #Redis #Valkey

"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

https://fossforce.com/2024/03/redis-goes-from-open-source-to-fauxpen-and-the-forks-have-already-started/

#Redis #Redict #SourceAvailable #SSPL #Redis

Как компании зарабатывают на опенсорсе, а потом выкидывают его

Финансирование разработки 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

@hexaheximal Lets be honest:

The average #EndUser is most likely so #TechIlliterate they'd not even know how to file an issue on #GitHub, much less provide any patches to it.

#GPLv3 harmed #FLOSS as a net negative for being more of an ideological manifesto than a useable license, demanding stuff that goes completely against existing laws and reality (espechally in terms of patents) and basically opened up the floodgates to what I consider "asshole licensing" that solely exists to stifle any competition and enshure said FLOSS can't be freely used. (see #SSPL, which is worse than a CC-BY-NC-SA as it literally has provisions that may not be strictly legal in many juristictions)...

"Freedoms" also don't work if they ain't real choices:
We can't claim people ain't forced to do wagework when not having a job will cause them to get homeless, die from starvation and sickness.

#TechLiteracy is seriously underdeveloped and in fact we see massive amounts of #regression.

The Idea of OS/1337 is to build something that is actually auditable and reproduceable even at the cost of functionality...

Because only the freedoms one can actually exercise against the will of the state are effective!