mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

341K
active users

#sspl

0 posts0 participants0 posts today
Replied in thread

@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...

Replied in thread
@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
Open Source InitiativeFair LicenseFair License (Fair) <Copyright Information> Usage of the works is permitted provided that thisinstrument is retained with the works, so that any entitythat uses the works is notified of this…
Continued thread

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).

Replied in thread

@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)...

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...
youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

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

Финансирование разработки Kubernetes крупнейшими спонсорами на GitHub за последние десять лет, источник Эти компании сначала при помощи сообщества разрабатывают опенсорсный софт или берут готовый, строят на нём прибыльный бизнес, зарабатывают миллионы. А потом меняют лицензию, оставляя контрибуторов, пользователей и партнёров в недоумении, что им делать. Такова бизнес-модель некоторых современных компаний вроде Redis Labs . Но ещё хуже поступают крупные облачные провайдеры. Они просто используют готовые решения, вообще не занимаясь разработкой и убивая бизнес «паразитов», описанных выше. Здесь вообще паразиты в квадрате. И весь этот террариум кормится опенсорсом.

habr.com/ru/companies/ruvds/ar

#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 за последние десять лет, источник Эти компании сначала при помощи сообщества разрабатывают опенсорсный софт или берут готовый,...

Having had a front-row seat for 's travails in adopting the , I have some thoughts on ' recent relicensing. Bottom line, I don't think the 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 world, even if that respects the letter of the definition. findthethread.blog/redis/mongo

Find The Thread · Defensive MovesThe news of the day is that Redis has changed its licensing, moving from the nice simple 3-clause BSD license to a combination of the Server Side Public License (SSPL) first introduced by MongoDB, and a rev of its own Redis Source Available License (RSAL).

[Перевод] В погоне за заменой Redis

21 марта Redis Ltd. объявила, что, начиная с Redis 7.4, ее «in-memory data store» будет выпускаться под несвободными лицензиями с доступным (source-available) исходным кодом. Новость малоприятная, но вполне ожидаемая. Необычно в этой ситуации обилие альтернатив для тех, кто хочет остаться со свободным ПО: есть как минимум четыре варианта замены, включая уже существующий форк под названием KeyDB и недавно анонсированный проект Valkey от Linux Foundation. Вопрос теперь в том, что предпочтут пользователи, провайдеры и создатели дистрибутивов Linux.

habr.com/ru/companies/flant/ar

ХабрВ погоне за заменой Redis21 марта Redis Ltd. объявила, что, начиная с Redis 7.4, её in-memory data store будет выпускаться под несвободными лицензиями с доступным (source-available) исходным кодом. Новость малоприятная, но...