upvote
> But those license changes were a response to how AWS was monetizing their work in ways unsustainable for the upstream projects

Or seen from the other side, these projects chose initial licenses that didn't fit with their wants for how others should use their project, in this mind.

If you use a license that gives people the freedom to host your project as a service and make money that way, without paying you, and your goal was to make money that specific way, it kind of feels like you chose the wrong license here.

What was unsustainable (considering this perspective) was less that outside actors did what they were allowed to do, and more that they chose a license that was incompatible with their actual goals.

reply
The situation changed. A license that's the right choice at one point may not be the right license a decade later.
reply
That's fair, but forking the FOSS version is also an adequate response.
reply
Yes. But so would financially contributing to the folks who did the work.
reply
AWS literally did that. They paid for full time developers to contribute back to the redis code base, including core redis developers. If you actually look at the redis code base the majority of it was written by people who never worked for redis.
reply
> If you actually look at the redis code base the majority of it was written by people who never worked for redis.

Thats a really big deal, how did they legally managed to do the license change? I was under the impression that only works if the original owner is the doing most work

reply
Permissive licenses don't protect against projects that decide to change the license when releasing a new version.

Copyleft protects against that as a general rule. However some projects that rely on copyleft require contributors to sign license agreements granting the project owners a more permissive license.

reply
> Thats a really big deal, how did they legally managed to do the license change? I was under the impression that only works if the original owner is the doing most work

Almost all of these license changes just change the terms under which _new_ work is contributed - which is why many of them have forks from the last OSI-licensed commit.

reply
Sure.

Since they're a for profit entity, they'll do whatever they think offers the best cost/benefit.

reply
If those folks wanted money for their work, they should be charging a price for it.
reply
That’s what they eventually did, yes.

But it’s ok to be voluntarily grateful for hard work.

reply
> But it’s ok to be voluntarily grateful for hard work.

You don't become a billionaire using that approach though.

reply
I hate Amazon and monopolies, but I hate companies that think opensourcing their code as a marketing stunt gives them more rights or whatever. If you don't want to opensource, then don't?!
reply
I can’t agree more, this “our software is open source but we have unwritten rules about how you can use it or we’ll attempt to shame you” attitude is absurd
reply
Agree, as long as existing contributors agree the license should be changed, projects should feel free to do so, no harm, no foul.
reply
I’m not sure any open source license is going to help when you can ask Claude to clone an application in the language of your choice.
reply
If Claude looks at the code when it does it, then you can still sue them. I don't think there's a "Claude Clean Room" product that trains on everything except the code you might be accused of copying.

I can't just translate Harry Potter to Spanish and sell it.

reply
Yes, this was my impression as well.
reply