I feel there's a few cases cited here to make a case that an entired business model is dying, but it doesn't look to me that this is an overall trend. You can't extrapolate from "5 projects didn't fare well with this, so it's not working". But there's more. I followed the MongoDB case a bit and it's not exactly how many make it sound like. MongoDB was doing fine as a company. It wasn't like they were unable to pay th…
I wish there was a FOSS license with a clause along the lines of: - if your company makes >X revenue a year, give us some of it. Ofc, they (FSF/OSI/DFSG) would have to relax their FOSS definition(s), but with more projects dying in this way hopefully more FOSS organisations will take heed and think about this. Ofc, the wording of the license has to be precise enough to avoid something like fobbing off the servers to…
(1) Ignore the problem -- your license has no teeth.
(2) Hold the larger corp responsible for payment anyway -- pretty sure this can't be accomplished purely within copyright law, and if it can then it's still not great because implementation details of the hosting company now matter in terms of the larger company's liabilities.
(3) Hold the hosting company responsible -- fine enough, that can probably be a valid term in your license. Suppose another company inserts themselves in the middle though; does your license exclude them because they're transitively connected to megacorp, or do we again find that your license has no teeth? The first case is an issue because now you're exposed to risk from your customers' customers, over whom you have no control.
Not every piece of software can be meaningfully hosted and resold by a chain of corporate entities, but it's not exactly an uncommon behavior in the wild either.