If AWS and other cloud providers gave if only 0.1% of the profit they generate out of these open source projects back to the developers we probably wouldn't have this problem. Unfortunately they don't and it's only fair that eventually those developers take it in their own hands. It's not a great situation but it's certainly understandable.
> Unfortunately they don't and it's only fair that eventually those developers take it in their own hands.
"Fair" is somewhat loaded. The developers certainly have a right to change their product and charge for it, but it's not nearly as cut and dry in my opinion. How many contributions were made because of the completely open nature of the product? Is it "fair" to those people that the controllers of the project want to change how it's offered at a later date? Some people are happy to feel like something they have contributed is in use by a lot of people regardless of whether someone else is making money from it.
There are often lots of entangled assumptions in open projects like these. Ultimately, people have a right to offer their work as they want, so I see no problem with projects trying to request additional restrictions on how their work is used, but I also don't see a problem with companies using open projects as offerings. It was offered for free, and it's not like the cost of the offering isn't usually just the cost of the underlying resources plus some additional amount for ease of management.
Disregarding the question of if the CSP compete fairly with providers of open source SaaS, your math is broken:
AWS revenue is about $90.76B, though most of it isn't from Redis, I'd assume. But let's be generous, and assume 10% of that is. So about $10mm. For the recent version, Redis-the-company contributions to Redis-the-software were less than third of the code base, so let's say they get $4mm. That's very little revenue for a company that has a valuation of over $2B.
Revenue is irrelevant, profit is what matters. The vast majority of the cost of any redis service offered is going to be the cost of the underlying compute and disk resources used. In some cases the margins could be close to nonexistent after paying for the resources utilized and the people to manage it, and it's used as a table stakes service that needs to exist for people to want to use your platform.
The vast majority of these projects didn't seem to have a problem with large companies like Netflix using their software, even if it was put on a cloud server, as long as it was managed by Netflix. Now that the management portion is moved to the cloud provider, along with some amount of possible profit, it's a large problem? Was it not a large problem when the companies were using these projects directly? Was there not some assumption and hope these companies would use these projects by the people contributing to them?
You must mean something other than 10%, that would be $9 billion by your numbers. 0.1% would be about $9 million so would be closer to your envelope math.
OP suggested the CSP should give 0.1% of their revenue to open source software they make their revenue from. As Redis isn't the only SaaS AWS offers, I was gracious and allocated 10% of those 0.1% to it.
Got it. It would actually be less than that since the number you selected was for revenue, not profit which is what OP asked for. Looking at some prior years it looks like AWS profit is close to 1/4 their revenue, so $90 billion would leave them with (generously) $25 billion profit. 0.1% of that would be $25 million and 10% of that (your estimate of Redis's share) would be $2.5 million.
