Earlier quoted context omitted.
This keeps happening: 1. People put a lot of work into building databases. The license choice is OSS / FOSS. 2. Some people in the community (original authors, community leads) make a company around the database and continue developing it for years on end. They sometimes raise venture capital to expand the business. 3. Amazon / Google / Microsoft offer managed versions of the database and make bank on it. Easily mill…
> The solution is clear: start your new database with an "equitable source / source available" license from day one. Nobody will complain about a relicense since your license will handle the hyperscalers right off the bat. Yes, this would be the honest thing to do, but people don't do it because using a non-FOSS license loses you adoption. The step you're missing in your little timeline is that the only reason the pr…
Redis is open source again
421–430 of 815 posts
Re: Redis is open source again
#422From the CEO blog post - https://redis.io/blog/agplv3/ >This achieved our goal—AWS and Google now maintain their own fork Was this really the goal though? Forcing your biggest users to fork your software and maintain their own divergent version is not really good for anyone. Sure, Amazon and Google (or AWS and GCP - type confusion in the source material) now have to contribute some more engineering hours to the open…
Re: Redis is open source again
#423Earlier quoted context omitted.
Yes, it does! The "problem" with AGPL3 is that it has no carve-out for companies smaller than Amazon, Microsoft, or Google. If you use AGPL, you have to open source your entire stack. Not everyone thinks infectious copyleft / free software is a problem. But it will mean that if you use AGPL3, every part of your stack has to be open. That doesn't work for everyone. This is why "equitable source" / "fair source" is gai…
AGPL doesn’t require you to open source the entire stack. Only the changes you made to the AGPL software if you interact with over a network AGPL does not and has not prevented hyperscalers from creating managed services for software licensed with it That’s why mongo created the server side public license, which does require open sourcing the entire stack. MongoDB was AGPL before that
Re: Redis is open source again
#424Earlier quoted context omitted.
Many people switched to Valkey and didn't even know it. A lot like how many users are using MariaDB but think they are using MySQL. Several major linux distros transparently switched to Valkey and the users are none-the-wiser. On Fedora, for example, doing `sudo dnf install redis` just installs Valkey.
Well that's a reason not to use a distro right? If I type `sudo dnf install redis`, I want to install redis not valkey.
Re: Redis is open source again
#425Earlier quoted context omitted.
Dunno about Redis, but for Elastic I still feel sorry for them being thrown around like a rag doll by Amazon. On principal I will not use the Amazon fork, because I don’t want to support a company that would prefer to fork a project rather than fork over some cash. Amazon is more than willing to sell you their Elasticsearch fork at a loss as long as they can eventually recoup the losses when Elastic inevitably dies.…
I sure wish I lived in a world where anti-competitive regulators weren't a joke.
Re: Redis is open source again
#426Earlier quoted context omitted.
SSPL isn't recognized as either open source or free software. I don't think it earns being discussed in the same context.
only because OSI says so. I don't agree with the idea of OSI defining my philosophical positions and technical terms for me, just like I don't agree with the BSD people excluding GPL from the definition of open source.
Re: Redis is open source again
#427Earlier quoted context omitted.
Interestingly their CEO states that AWS an Google forking redis and maintaining it separately was their "goal" all along. Because fragmentation is apparently good?
> Because fragmentation is apparently good? I think it's more "they are no longer piggybacking off our work for free". I also think what they actually wanted was that plus "...and they paid us".
Re: Redis is open source again
#428Again? Didn’t it go from BSD to some infectious copyleft thing? Doesn’t seem “open source again” to me if we can’t use it in private work projects without being forced to open source our project. Isn’t AGPL even WORSE than what they switched from? Wouldn’t “open source again” imply going back to BSD?
They went to SSPL, which isn't open source. (Whether it's copyleft is an interesting exercise left to the reader. I genuinely don't know, I'd have to stare at definitions for a bit to form an opinion.)
> Doesn’t seem “open source again” to me if we can’t use it in private work projects without being forced to open source our project.
Er, I'm not a lawyer, but why wouldn't you be able to use it in a private work? AFAIK the viral parts of AGPL/GPL only say you have to share source with users of the software; if your only user is you then it's immaterial.
> Isn’t AGPL even WORSE than what they switched from? Wouldn’t “open source again” imply going back to BSD?
Worse/better is somewhat subjective, but AGPL is a (Free and) Open Source license. It was open source (BSD), then it wasn't (SSPL), then it was open source (AGPL).
Re: Redis is open source again
#4291. To monetize a project, it must first gain wide adoption.
2. To gain wide adoption, it must have a permissive license.
3. To successfully monetize (after gaining wide adoption), it must have a restrictive license.
4. Changing a project's license to be more restrictive will alienate the community and hurt adoption.
I see no solution to this dilemma.