9 ms·
For me, the license change upset me mainly for two reasons: 1. Many people had contributed their efforts to the Redis project for free - both in terms of code
by simonw 2y ago
For me, the license change upset me mainly for two reasons:
1. Many people had contributed their efforts to the Redis project for free - both in terms of code but also in advocacy, writing tutorials, publishing example code etc - and when they did that it was under the understanding that project would remain under the same open source license. It honestly felt like a betrayal of trust.
2. From a purely selfish point of view, my favourite thing about open source licenses is that they let me know exactly what I'm allowed to do and build on that software without having to consult a license. Licenses like the new Redis one leave me potentially needing to get my own legal advice depending on what I'm building on the software. I don't want to spend my time, energy or money on that stuff!
I do also see these kinds of license trends as harmful to open source generally. It used to be that you could pick an open source project and build a business on it and expect that the project would stay available to you under those well understood terms. That's not the case any more - not just because of Redis, there are a number of other high-profile license rug-pulling projects. I'm sad about that.
(And yes, I do understand and dislike the trend of businesses building on open source without contributing back. There are no clearly correct answers here.)
- jcgrillo 2y agoThe question of what constitutes a "service" seems very murky, and although it's obviously not the intention of all these source-available, BSL style things, in a dark timeline it seems like there's a lot of room for litigious actors to behave very badly. The uncertainty is what makes it scary, I'd also like a lot more clarity.
- antirez 2y agoThe good thing about this is that since the companies are copyright holder of the code, if this creates issues, the licenses can be rewritten and modified in order to be as sharp as possible in the use cases they want to avoid (which is... two/three users in the world :D).
- jcgrillo 2y agoThis is a great point, it'll probably take the better part of the next decade for all this to shake out. It'll be interesting to see where it goes.
- zokier 2y agothe issues of sspl have been frequently and loudly been brought up previously, and nothing has happened. just to reiterate, this section is ridiculously expansive: > “Service Source Code” means the Corresponding Source for the Program or the modified version, and the Corresponding Source for all programs that you use to make the Program or modified version available as a service, including, without limitation, management software, user interfaces, application program interfaces, automation software, monitoring software, backup software, storage software and hosting software, all such that a user could run an instance of the service using the Service Source Code you make available. it is practically impossible for anyone to comply with that, to provide source code for every single program (without limitation) that they happen to use anywhere. of course none of the major sspl-using vendors are even pretending to themselves to follow these rules. sspl would be much better license if it just simply forbids providing services, instead of hiding behind this thin veneer of fake copyleft. > You can even still sell Redis as a service if you want, as long as you release all the orchestration systems under the same license (something that nobody would likely do, but this shows the copyleft approach of the license). note that this is not right, the "copyleft" is not limited to orchestration systems, it covers all programs that you use
- ndiddy 2y agoI believe that the original reason why they didn't just say "you're not allowed to provide this program as a service" is that MongoDB were trying to get SSPL approved by the OSI. The OSI didn't approve it because as you mention, it's basically impossible for a cloud provider to actually attempt to comply with the SSPL. Not only would they have to release the code to all software used to make the program available, they would have to do so under the SSPL. I'm not sure why MongoDB didn't change the wording when they gave up on getting the license classified as "open source".
- 2y ago
- fweimer 2y agoNo one is expected to use any of the code licensed in this way commercially. You enter a contract with the vendor, tell them what you need, and negotiate a price. At that point, it doesn't really matter what the copyright license says.
- jcgrillo 2y agoSo the entire license is just a bad faith trap? I could see it being used that way, potentially, but I don't believe that's actually Confluent's, MongoDB's, Elastic's, Hashicorp's, or Redis Labs' intent. In fact they've all explicitly stated the opposite. Are they all lying?
- fweimer 2y agoI don't think it's in bad faith. A lot of people still believe that they have to pay one of AdaCore/Baylibre/Embecosm/Red Hat/SUSE/Wind River if you want to use GCC commercially, to cover GPL-related risk.
- antirez 2y ago"Many people had contributed their efforts to the Redis project for free - both in terms of code but also in advocacy, writing tutorials, publishing example code etc" I can understand that, but the thing about the BSD license is that such value never gets lost. People are able to fork, and after a fork for the original project to still lead will be require to put something more on the table. Inside Redis it was tried very hard to don't change license. For years it was some kind of "dogma", something one could not even speak about. Then after all the kind of attempts, and following the experiences of MongoDB and others, finally this choice was made. (Disclaimer: I saw the switch as an outsider, so my information is not complete about the final decisions -- I for sure know how this was always considered to avoid if other setups were possible). However now I see that there is the case for giving the community something in exchange to the license change: a lot of good things in the core, a very good attitude towards the community, and so forth.
- benatkin 2y agoIn a sense valkey is the main line and redis is now the fork. Valkey is about the same except losing the trademark. It’s similar to Hudson and Jenkins. It’s not so clear cut with OpenSearch.
- sroussey 2y agoWhat’s valkey?
- benatkin 2y agoPersistent key-value database with network interface https://packages.debian.org/testing/database/valkey-server https://packages.debian.org/testing/database/valkey-server
- alanwreath 2y agofork of redis https://github.com/valkey-io/valkey https://github.com/valkey-io/valkey just before the transition to their new source available licenses
- bsnnkv 2y ago> I do also see these kinds of license trends as harmful to open source generally I've re-read this a few times and I'm still not sure what "harmful to open source" means in this sentence, could you expand on this a bit when you have time? (readings I considered: this will dissuade people from using OSI licenses, this will dissuade people from trying to monetize open source components, this will dissuade people from using open source components in their products all together, this will dissuade people from contributing to open source) > Many people had contributed their efforts to the Redis project for free This one is not directly addressed at OP but I would be interested to see what the contribution numbers are like for Redis and other projects post-license change. In my own limited experience (project with >10k, <100k end users), I received no meaningful code contributions when the project was MIT licensed, but contributions of significant features and large bug fixes skyrocketed after switching away from it (not saying that the license change is the reason for that, just that it didn't dissuade some people who are willing to contribute significant effort from contributing to the project). Editing this post to say thanks for the response and clarity, I don't have anything else to add!
- simonw 2y agoI see the open source movement as being about developers sharing their work in order to raise all ships and dramatically accelerate the rate at which participants in that community can build cool software. A lot of that benefit comes from not having to worry about licenses: pick platform components with known open source licenses, build cool things with them. I think the rise in not-quite-open-source licenses (especially projects switching to those licenses) undermines the things that I value about open source, and further encourages more projects to make those decisions in the future.
- deleted 2y ago[deleted]
- enugu 2y agoOne of the motivations of copyleft licenses like GPL which are a part of open source, was the freedom for users to see and modify code. The fact that the user works with the software in a browser rather than inside a native app is a technicality which shouldn't mean that the principle becomes invalid. Of course, this makes it harder for developers to monetize their work. But, instead of framing the discussion in terms of these conflicting interests and finding a balance, the term 'open source' becomes a debate target (even though the OSI definition includes AGPL which is also radioactive if one wants to monetize the work.) So we have three parties 1) Users 2) App Developers who write commercial closed source code for the user facing app 3) Dependency Developers who write code used by App Developers. (There is a simplification here as 2 can be a startup writing selling a closed source dependency used by other developers) Just as App developers would like to monetize via user payments, some licenses allow the same option for Dependency developers while simultaneously allowing source code to be available and modified. The basic idea behind such a license is 'free of cost and inspectable/modifiable code for almost all users, but commercial for large companies making a significant revenue from the software'. There needs to be some work done, to make the license predictable - which users it requires to pay, and the price involved.
- deleted 2y ago[deleted]
- _acco 2y agoAFAIK, the reason for these changes is basically "prevent AWS from eating our business". Is that right? If so, are these trends harmful to open source? Are we not choosing between: 1. A world where all revenue in OSS infrastructure ultimately flows to a few big platform companies. 2. A world where these carve-outs are commonplace. Meta's carve-out with Llama is so interesting because it practically calls the big companies out by name. Should there be a similar standard license for open source infrastructure?
- gpderetta 2y agoAffero 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.
- eudoxus 2y ago> although they are treated as radioactive by most companies Isn't this reason enough to not consider it an option?
- hnfong 2y agoAFAIK, the main issue of the GPL family of licenses is that they are rather poorly drafted. The GNU project has great evangelists but ideological-minded people make bad lawyers. Their licenses are long winded and hard to interpret, and often make assumptions about unsettled bits of copyright law. Their legal theories (eg. "GPL is not a contract") have been rejected by courts. In short, if you're a company wanting to use some AGPL-like license, you'd probably want to use a license that's better drafted over the original AGPL.
- gavindean90 2y agoCan you link some info on the portion about contracts having been rejected by the courts? I’m having trouble finding specifics on that myself.
- Suppafly 2y ago>there are a number of other high-profile license rug-pulling projects. I'm sad about that. It also severely sets the industry back every time one of these rug pulls happens and we have to scramble to find a replacement. Sure it might drive some minor innovation, but it also wastes a ton of resources by splitting communities and leading to tons of rewrote just to get back to a place of stability.
- hgs3 2y ago> Many people had contributed their efforts to the Redis project for free It's worth noting that the bulk of the code was written by antirez with only ~12 others exceeding 100+ commits [1]. And if you continue scrolling the number of commits-per-user drops off fast. It's striking given how famous the project is. [1] https://github.com/redis/redis/graphs/contributors https://github.com/redis/redis/graphs/contributors
- softwaredoug 2y agoIt goes far beyond the actual codebase to the long tail of supporting projects, conference talks, blog posts, etc
- dig1 2y agoAgree. Writing code is (TBH, only a tiny) part of the project - creating packages for different OSes and distros, testing, filling bug reports, promoting project, writing tips and ticks, articles... Many projects remain unpopular not because the authors aren’t actively maintaining them but because these essential components are missing.
- reconditerose 2y agoAs one of those 12 other people, number of commits is not a good metric in this context. When you have a single maintainer, like antirez was for a long time, he could commit 10+ commits for a single small feature but I needed to get someone else to approve my commit before merging.
- mise_en_place 2y agoThe license change is a necessary evil, otherwise BigCo will continue EEE and extract value from the project without giving anything back. It's time to hit them where it hurts. The world will be a better place if Google collapsed tomorrow. FOSS must adapt to SaaS and the modern rent-seeking behaviors of BigCos.
- kqr 2y ago> It used to be that you could pick an open source project and build a business on it and expect that the project would stay available to you under those well understood terms. By "used to be" you mean for a brief period in the 2000s, right? Because this extremely generous open source landscape we have seen in the past 20 years were not the normal state of software for most of software's existence. A generous open source landscape is something we -- you, I, the readers of HN -- have to actively maintain by shouldering the burden of maintaining the correctly licenced software. We cannot trust this important job to profit-making corporations.
- osigurdson 2y agoMIT + popularity = commercial license
- space_oddity 2y agoYep, when people contribute to a project, they invest more than just code; they invest trust in its principles
- berkes 2y ago> It used to be that you could pick an open source project and build a business on it and expect that the project would stay available to you under those well understood terms. I'm not familiar with what's happening in this Redis licence change. But if it was Open Source at version N, and you built your business (or stack, etc) on top of that, N will remain forever available to you as FLOSS, not? Is the problem maybe that ppl expect future updates, maintenance to remain Open Source? Something that, AFAIK, no Open Source licence guarantees? So, misaligned expectations? > That's not the case any more - not just because of Redis, there are a number of other high-profile license rug-pulling projects. It's not new. MySQL, Redhat and many others have done this for ages in the floss community.
- alecco 2y agoNote his "build a business on it" angle. It's not an open source problem. Greedy techbros want free support forever from the community while contributing almost nothing back. Same for large corporations. They see this as "rug pulling". I think developers need to do a lot more of that for things to change.
- thanksgiving 2y agoOP wrote > The license language is almost the same as the AGPL, with changes regarding the SAAS stuff. So, not OSI approved? Yes, but I have issues calling the SSPL a closed license. What is it that changed from AGPL in SSPL that was absolutely needed? Why can't we have an AGPL 1.1 or 2.0 if it is a breaking change? I am not saying anyirez is wrong. I would like to learn why this was necessary, if at all.
- alecco 2y ago> What is it that changed from AGPL in SSPL that was absolutely needed? https://opensource.stackexchange.com/a/8028 https://opensource.stackexchange.com/a/8028 Big cloud players would put a thin layer on top and ignore the AGPL.
- bojanz 2y agoWhat I dislike about the license change is that by trying to extract an extra dollar from Amazon&Google, the entire community gets hurt in the process. Can I "dnf/apt install redis" on my Fedora or Debian install? I cannot, it's no longer packaged because it's no longer open source. Can I go buy a shared hosting plan and get Redis? Or a small PaaS that sits on top of AWS? I cannot, because we have decided that every hoster is now as exploitative as Amazon, regardless of their margin. For decades we lived in a world where someone could sell you an Apache server and a MySQL instance without having to pay money to Apache or MySQL. We can change that social contract, but like all tariffs, this one will be paid by the end users, not by the companies providing the service. Disclaimer: I work for a PaaS.
- mschuster91 2y ago> For decades we lived in a world where someone could sell you an Apache server and a MySQL instance without having to pay money to Apache or MySQL. We can change that social contract, but like all tariffs, this one will be paid by the end users, not by the companies providing the service. Yeah, but the Internet community at large took care about funding. MySQL always had the commercial support leg to stand on, and Apache httpd... looking at the contributor list [1], it's a healthy mix of universities, large companies (IBM, HP), ISPs (Vodafone, Cable & Wireless), hosters (Rackspace), small consultancies and individual private contributors. In contrast, the megacorporations are largely absent from FOSS contributions (the exceptions being Netflix and partially, where it suits them, Google, Microsoft and Apple). [1] https://httpd.apache.org/contributors/ https://httpd.apache.org/contributors/
- bojanz 2y agoValkey, the Redis fork, is currently sponsored by Ampere, AlmaLinux OS Foundation, Broadcom, DigitalOcean, Memurai, NetApp, Aiven, Alibaba Cloud, AWS, Canonical, Chainguard, Ericsson, Heroku, Huawei, Google Cloud, Oracle, Percona, Snap Inc and Verizon[0]. There is enough interest in sponsoring the development of infrastructure software. But if you want to build a "commercial arm", get VC funding[1][2] and earn millions, then it will never be enough. And I can't say it's unreasonable to want to do that, it just ultimately ends up being against the long-term interests of the project as a whole. [0] https://www.linuxfoundation.org/press/valkey-welcomes-new-partners-amid-growing-momentum https://www.linuxfoundation.org/press/valkey-welcomes-new-pa... [1] https://redis.io/press/redis-labs-raises-100-million-series-f-financing/ https://redis.io/press/redis-labs-raises-100-million-series-... [2] https://redis.io/press/redis-labs-110-million-series-g-led-by-tiger-global/ https://redis.io/press/redis-labs-110-million-series-g-led-b...
- SergeAx 2y ago> you could pick an open source project and build a business on it and expect that the project would stay available to you Why not just stay on the last version with the license of your original choice?
- prmoustache 2y ago> 1. Many people had contributed their efforts to the Redis project for free - both in terms of code [...] it was under the understanding that project would remain under the same open source license. The whole point of the MIT/BSD licenses versus licenses like the GPL is to not be limited by that. > It honestly felt like a betrayal of trust. It feels like total ignorance from. If such license change bother you, you should only contribute to projects that are licensed under GPL or similar licenses and that don't force contributors to sign a CLA. I don't like current Redis license, but nobody lost any code and any contributor can still contribute to any fork that started using the last open source version.
- no_wizard 2y ago>Many people had contributed their efforts to the Redis project for free - both in terms of code but also in advocacy, writing tutorials, publishing example code etc - and when they did that it was under the understanding that project would remain under the same open source license. It honestly felt like a betrayal of trust I'm not seeing this being a factor in the broader community of users. Redis is still 'go-to' solution in its space. Haven't yet had anyone bring this up. >I do also see these kinds of license trends as harmful to open source generally. It used to be that you could pick an open source project and build a business on it and expect that the project would stay available to you under those well understood terms. That's not the case any more - not just because of Redis, there are a number of other high-profile license rug-pulling projects. I'm sad about that. I think the biggest thing is - that you acknowledge- that companies (particularly big businesses, like the cloud and service providers) build entire lines of business on this tech without contributing back, monetarily or otherwise, or even worse, try to shorehorn a project into prioritizing what they want over what may be better for the long term health of the community. These license changes I've seen so far are all attempts to address that. How else are they able to do it with any long term success? They already aren't getting the funding they're looking for, clearly, while businesses build multi million and in some cases billion+ dollar businesses on top of the technology. I'd argue that old permissive licenses aren't sustainable in the long run for any project like Redis