clacke, to 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…


linux_mclinuxface, to Redis
@linux_mclinuxface@fosstodon.org avatar

Welp. It's official. is no longer

While I wasn't a contributor to the core, I presented on it dozens of times, talked to thousands, and wrote a book about it.

I probably wouldn't have done any of that with that kind of license.

Very disappointed.

tallship,

@alex @linux_mclinuxface

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

#tallship #FOSS #SSPL #AGPL

.

neptune22222, to foss
@neptune22222@kolektiva.social avatar

MongoDB's SSPL (Server Side Public License) sounds like an extremely strong copyleft form of free software license. It sounds like MongoDB took the AGPL and made it much stronger.

Respected "open source" groups have rejected MongoDB's copyleft open source free software license, such as the OSI, RedHat, and Debian.

The criticism of the SSPL do not seem to recognize that it is a copyleft free software license. Is the OSI really a protector of copyleft free software? The politics of these organizations seem to leaning anarcho-capitalist "libertarian".

I don't believe the SSPL will harm any specific field of endeavor. Databases are used in all fields of endeavor. They are usually one of many provided cloud computing services. Cloud computing services are used in most every field of endeavor these days. Even my toothbrush has a cloud database.

By rejecting the SSPL, the OSI, RedHat, Debian have appeared to have ignored the copyleft freedoms that the SSPL guarantees.

retr0id, to random
@retr0id@retr0.id avatar
kkarhan,
@kkarhan@mstdn.social avatar

@joeo10 @anedroid @retr0id

IMHO @signalapp disqualifies itfels being a & "solution" that also demands data they have no "legitimate interest" to request or store so violating [ or at least ] and @element seems keen on forcing - changes to if not aka. The "You can't make money off it!" - !

benjaminedwardwebb, to opensource
@benjaminedwardwebb@mstdn.social avatar

Despite www.dnp.org claiming that "DNP3 is an open and public protocol," it seems that the specification is only available to members and membership costs US$400 for an individual. Not really the definition of "open" that I'm used to.

https://www.dnp.org/Join-Purchase/Member-Fee-Guide

kkarhan,
@kkarhan@mstdn.social avatar

@benjaminedwardwebb +9001%

access to standards isn't open - compared to that the anti-competitive is open despite being designed to make it impossible to do any commercial offering with it (it's worse than )...

I could at least understand if they said "Available for Licensing under terms" if everyone gets to pay the same flat fee...

JasonGoldman, to opensource

The upcoming release of the Open Source Definition (v1.11) will recognize as an software by @MongoDB. 🎉

rogue,

@anderseknert Looks like the replies to your post were deleted, since they certainly didn't look good for him!

To help other readers understand, is and not . @osi did not approve the as open source. The SSPL is also .

The only one who claims that MongoDB/SSPL is open source is a single person who is proprietary software using his website and his GitHub repo with 1 star. Just ignore it.

galdor, to random
@galdor@emacs.ch avatar

The old "we don't want competitors to undercut us" thing is such a bad justification for switching to non Open Source licenses (e.g. Elastic, Hashicorp…). You can absolutely keep some features in proprietary extensions and make them available to enterprise clients while keeping the main software OSS.

Cluster mode, SSO, SCIM, audit logs, account impersonation, integrations with proprietary software, the list goes on and on. And these features are usually hard to replicate, good for you.

voxpelli,
@voxpelli@mastodon.social avatar

@galdor Let’s not conflate the license that Elastic switched to with the .

The SSPL is an license modified to prohibit competition for eternity.

The BSL is a license that turns into a compatible license within at most 4 years and which the creators, @mariadb, created to ensure their proprietary extensions would be as close to OSS as possible and guaranteed to eventually become full OSS.

Likewise, @getsentry defaults to non-BSL: https://open.sentry.io/licensing/

tod, to random
@tod@hci.social avatar

The entire city of #Yellowknife is being evacuated. This is unprecedented and terrifying.

And thousands of citizens aren’t aware because Meta continues to block news in the country.

This is what happens when citizens are convinced to use an American multinational corporation as their community’s primary communications channel — a corporation that couldn’t give two shits about anything except its “fiduciary duty” to shareholders.

https://www.cbc.ca/news/canada/north/nwt-wildfire-emergency-update-august-16-1.6938756

kkarhan,
@kkarhan@mstdn.social avatar

@JustinLachance @tod It's called "Formulating a #NuancedOpinion" and I can highly recommend it.

It's way more complex but it allows for some consistent yet realistic approaches.

I.e. one can acknowledge that #grsecurity and #RedHat showed the need for stronger #Copyleft whilst also noting that neither #GPLv3 nor #AGPLv3 nor #SSPL doesn't adress that problem and instead demand illegal actions to comply [i.e. surrendering all patents] which ignore the reality of #tech.

https://postchat.io/@JustinLachance/110907574633552171

ian, to random
@ian@mckellar.social avatar

I love when a company who built their whole business on top of open source developed by others (Linux, Ruby, Go, etc) decry "vendors who take advantage of pure OSS models, and the community work on OSS projects, for their own commercial goals" switch to a proprietary license rather than a copyleft that actually codifies the culture of reciprocal sharing.

https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license

kkarhan,
@kkarhan@mstdn.social avatar

@ian The problem with all existing licenses is that they don't force those that take something to publish back their modifications.

and didn't really fix that either...

kkarhan,
@kkarhan@mstdn.social avatar

@natsume_shokogami @ian

And whilst the has it's own problems that disqualify it, a "" provision requiring public code to remain could be added to any , not just @creativecommons licenses.

I.e. "Any used versions - released as part of a product or on their own - must have their released in public for everyone to access and reproducably build with no form of barriers!"

https://en.wikipedia.org/wiki/Creative_Commons_license#Types_of_licenses
https://en.wikipedia.org/wiki/Server_Side_Public_License
https://en.wikipedia.org/wiki/BSD_licenses

geerlingguy, to opensource
@geerlingguy@mastodon.social avatar

As belts tighten, corporate evolves—further and further from the ideals of Free Software.

Partly due to bad actions by "freeloaders," but also companies putting too much value in building code, and not enough on community and support. https://www.hashicorp.com/blog/hashicorp-adopts-business-source-license

kkarhan,
@kkarhan@mstdn.social avatar

@geerlingguy Not that I doubt that companies want to make and that they want to enshure that no - espechally - just yoinks their code and make a better out of it whilst contributing 0 $ or code back into the project.

Stuff like the & won't fix the issues - in fact they'd rather worsen the situation, only empowering the rich that can pay lawyers.
https://en.wikipedia.org/wiki/Server_Side_Public_License

rain, to random
@rain@hachyderm.io avatar

A lot of things online, like open source projects, are gifts given to a community, and people just don't know how to handle gifts given to them

kkarhan,
@kkarhan@mstdn.social avatar

@rain not necessarily...

Some and/or don't allow you to do that.

I'm not just talking about "published source" like 's client, but also and which are basically designed to prevent competiton - or not - from making any commercial product.

Basically aiming at monopolizing any commercial product.
https://en.wikipedia.org/wiki/GNU_Affero_General_Public_License
https://en.wikipedia.org/wiki/Server_Side_Public_License

voxpelli, to opensource
@voxpelli@mastodon.social avatar

Another day and another push for having startups adopt the BSL-license rather than a bespoke hybrid proprietary setup or an orphaning-prone AGPL / SSPL licensed setup: https://github.com/SigNoz/signoz/discussions/3021

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • thenastyranch
  • rosin
  • GTA5RPClips
  • osvaldo12
  • love
  • Youngstown
  • slotface
  • khanakhh
  • everett
  • kavyap
  • mdbf
  • DreamBathrooms
  • ngwrru68w68
  • provamag3
  • magazineikmin
  • InstantRegret
  • normalnudes
  • tacticalgear
  • cubers
  • ethstaker
  • modclub
  • cisconetworking
  • Durango
  • anitta
  • Leos
  • tester
  • JUstTest
  • All magazines