4 ms·
Lots of cynical takes in this thread - and I get it, there isn't a guarantee they won't relicense again in the future (they have a CLA that would let them) and
by simonw 2y ago
Lots of cynical takes in this thread - and I get it, there isn't a guarantee they won't relicense again in the future (they have a CLA that would let them) and people feel betrayed by the last license change.
I think we should celebrate this anyway. It's a smart decision, it's what the community wanted to happen and it would be great if other companies with janky licenses could see "Redis relicensed to open source and had a great boost out of it", not 'Redis relicensed to open source and it didn't help them at all".
I'm delighted. Thank you, team Redis.
- antirez 2y agoThank you, Simon. I believe that cases like Elastic and Redis returning back to an open source license is like writing on the rock: "open source won", at least in the system software space. Companies get created, prosper and fail over time, but this message is here to stay with us for a long time, and shapes the society of tomorrow. It's a win of the software community itself.
- lolinder 2y agoIt's a win for the community over and against the corporations that are Redis and Elastic. They're not the good guys for giving in to the pressure. They tried to ride FOSS to prominence and then extract wealth on the backs of the community and found that the community mattered more than they did. So sure, let's celebrate, but celebrate the community, not those who tried to pull the rug out from under them.
- deleted 2y ago[deleted]
- antirez 2y agoI said exactly that's a win of the community. But money are needed to pay the folks that work at open source software, and the companies that went for the SSPL were trying to protect their business (and, as a side effect, wanted or not, the ability to pay for such work). I believe the software world failed to protect open source software in the cloud era, but in general the environment that we collectively created made the open source software won.
- lolinder 2y agoI don't buy that justification. These two companies (and the others like them) set up a model for funding their business knowing full well that they would have to compete with others who were able to provide the same service they were. That's always been baked into FOSS—you can't plan around a monopoly when you're releasing your code for free, that's part of the trade-off you make. When AWS and Co did provide hosting and provided it better than these guys could, now it's suddenly AWS who are the bad guys for using the FOSS software the way the license always said they could. Now we're suddenly supposed to ignore the terms on which FOSS has always been released and pick up our pitchforks against the big mean cloud provider. Instead of sticking to the fundamental principles of FOSS (principles which they won business by openly espousing) and adapting their business to the fact that Elastic and Redis lost in the competition they knowingly set up, they fixated on hosting (on top of AWS and Co, no less!) as the business model and changed the licenses to give themselves a monopoly on it.
- jimbokun 2y agoThere is no possible way to compete against someone else who doesn't need to fund the development of the software but can still take in all the revenues and profits from deploying it as a service.
- lolinder 2y agoBut that has always been true, from the beginning. It's baked in to the FOSS model and always has been. If the companies had made a bad call in structuring their business and owned up to it I think we'd be having a very different conversation than we are. We're here because they failed to own up to it and instead tried to get people to raise pitchforks against AWS. Never mind that their intended model was the obviously doomed model of reselling AWS's hosting with a commission on top, and never mind that it was the trade-off they chose when they chose to release their software as FOSS and get the boost in adoption that comes with. I do fully agree with antirez above that we need a new plan for funding FOSS. But I think that's a poor justification for the rug pulling and vilifying that the existing companies did.
- thayne 2y agoI strongly suspect there was pressure from within these companies, among developers as well.
- znpy 2y agoI’d say that open source definitely lost, and lost real bad. Free Software won, as you ended up adopting the AGPL. It’s an important distinction.
- fastball 2y agoNo its not.
- znpy 2y agoOne more major piece of software is not open source (BSD) anymore, it's now Free Software (AGPL). And every time someone talks about Open Source licensing, we'll remember how Redis was BSD and that became a shitshow so bad (everybody was fleeing to Valkey) they had to relicense it to AGPL (Free Software). If this isn't losing...
- primitivesuave 2y agoI also appreciate this perspective because you never know what's going on in the board room. I have seen some morally upstanding leaders make questionable decisions that were totally out of character for them, all for the sake of appeasing a narrow-minded investor.
- overfeed 2y ago> it would be great if other companies with janky licenses could see "Redis relicensed to open source and had a great boost out of it", not 'Redis relicensed to open source and it didn't help them at all". If the other companies can't figure out that adopting a janky license and alienating the community is the self-inflicted problem, then they are beyond help. Relicensing to open source not helping the company may serve as a cautionary tale for other companies and may prevent them from repeating the same mistake. As an open source enthusiast, the worst case scenario is companies switching licenses tactically and frequently to test the waters and walking back with no consequences; I'd prefer the cost of such actions to be swift and severe.
- ksec 2y ago>Lots of cynical takes in this thread - and I get it, there isn't a guarantee they won't relicense again in the future (they have a CLA that would let them) and people feel betrayed by the last license change. Oh good. There is still hope of it returning to the original BSD license. ( I am still using good old Memcached )
- mort96 2y agoI don't want companies to see, "re-licensing to janky licenses is risk-free, because we can always go back to the old license if people react too negatively". I would like them to see, "re-licensing to janky licenses is a death sentence which immediately makes your product almost completely irrelevant and causes the community to switch to a fork and never switch back".
- gloomyday 2y agoIt could be cynical, but I think it is important to show severe consequences for breaking trust between a company and its community. Anyone that saw their history and contributes to it must be aware they are doing unpaid work for a company.