3 ms·
First, I would like to suggest that you take a step back and think about how many non-FOSS projects are complete failures even though a ton of money was thrown
by palata 3y ago
First, I would like to suggest that you take a step back and think about how many non-FOSS projects are complete failures even though a ton of money was thrown into them. So yeah... there are good, average and bad FOSS projects just like there are good, average and bad proprietary projects.
Then, you have identified some characteristics of FOSS projects: some do tons of things somewhat passably (that's typically the case when the maintainers try to accommodate the contributors), some don't do much and don't get many contributions, some don't do much and just refuse contributions that the maintainers don't care about, etc.
But you have to understand that maintainers don't all have the same goals. I don't know if you have ever been a maintainer, but users can be real jerks. Almost blackmailing the maintainers ("if you don't implement this feature I won't use your software for free"), sometimes even being aggressive ("this project sucks, I spent 2 days trying to understand how to do that, if I had a choice I would use something else but I don't want to pay"). Almost nobody says "I will pay you to implement this feature properly and I don't expect you to maintain it for free forever".
It's hard to be a maintainer, and if you manage to do a good job and went for a permissive license, chances are that people (companies) will just use it without contributing anything back (not even honoring the attribution clause, because 99.999% of people don't understand that permissive licenses require attribution).
IMO companies would have to contribute much more if everything was copyleft (at least MPLv2).