I'm really interested in this bit: "the fracture with the community is not about licensing, or at least it’s not mainly about licensing" I wish he'd elaborated a bit more on what he thought it was about. My understanding is that it's 100% about the license. That's certainly why I'll reach for valkey instead of redis next time I need it. That's also what I've heard from everyone else in a similar position. What else w…
For somebody, like you and many others, it was very important to retain an OSI license. But I feel that in general given that the new license is IMHO good for almost every user, from the POV of what they can do with the code, and that the cloud situation was quite self evident, I believe that with better communication, and immediate developments/merges in the core, to counter balance the license switch, many people w…
From where I left
271–280 of 472 posts
Re: From where I left
#272Earlier quoted context omitted.
Affero GPL-style copyleft licenses are an option, although they are treated as radioactive by most companies. A clause that triggers the extensions over GPL only for companies beyond a certain size might make them more platable.
> although they are treated as radioactive by most companies Isn't this reason enough to not consider it an option?
Re: From where I left
#273Earlier quoted context omitted.
Is this snarky or real? If real, how would this work? If snarky, then :(
Absolutely real: focus on the community, merge things that were now in payed versions of Redis into the core, so that everybody can benefit, contribute positively to the clients space, improve the documentation, and so forth.
Re: From where I left
#274Earlier quoted context omitted.
If a company's survival is threatened by people using its open-source software, then maybe it shouldn't be open source. Open source software (to me) says I should be able use the software for any purpose, including commercial ones.
I agree. It seems that "open core"[1] is a failed experiment. I'm hopeful the idea will be replaced either by governments being smarter about the computers, or companies agreeing to sponsor foundations, or... something. But clearly taking venture investment to build OSS and turn it into a profitable enterprise is an idea that has been thoroughly shown to be flawed. [1] aptly named if you think about the nuclear power…
Re: From where I left
#275Earlier quoted context omitted.
> in such a way that could be construed as reneging on your promise Nothing could be construed in such a way, because such a reneging is not possible.
Well in this case, antirez literally promised[1] they wouldn't change the license of the core away from BSD, and then Redis Labs did just that, and now antirez is speaking favorably of that decision. [1]: https://antirez.com/news/120
Re: From where I left
#276Earlier quoted context omitted.
and remains truly open-source, unlike Redis.
Redis from Redis Labs, available under a choice of its own license or the SSPL, is pretty close to truly open-source , IMO closer to it than the BUSL, which is another source-available license. It is pretty similar to the AGPLv3, and they even credibly applied to get it OSI-approved. https://blog.tidelift.com/what-i-learned-from-the-server-sid... https://opensource.stackexchange.com/questions/11291/how-to-... What it…
Re: From where I left
#277Earlier quoted context omitted.
Cloud providers offer productized versions of Redis, so their interest in Valkey should be obvious :)
Yep. It is still a bit ironic that the community rallied behind Big Tech instead of a small startup though. Just saying.
Re: From where I left
#278Re: From where I left
#279All the conversations about SSPL seem to go the same way: - Someone complains about the extra restrictions imposed on AWS (lets be real, it's basically just about AWS) - People point out that SSPL is basically AGPL+, and that for the vast vast majority of people it doesn't make any difference - People counter that the SSPL is written ambiguously/untested in court, and so while it might seem like it's AGPL+ and doesn'…