4 ms·
Isn't it an obvious problem that lots of OSS people have? If your project is non-trivial and effective, millions of people want to use it but it takes a lot to
by lbriner 5y ago
Isn't it an obvious problem that lots of OSS people have? If your project is non-trivial and effective, millions of people want to use it but it takes a lot to maintain it. In most cases, without vetting, it is hard to accept PRs from random people because you pretty much have to review the entire code and in most cases, it would probably take ages to understand enough about something like Babel to be a useful contributor.
The obvious solution is to charge a small amount ($10?) for a licence to use on a single site/application. You can't entirely enforce it but with some basic registration process, you could tie a licence to the code so that an internet scanner could potentially find people violating the rules. Minor updates included, major updates cost another $10. If only 500K projects are using it, that is still $5M, which would go some way to helping.
I understand that licences can be a problem if the code is/was open source since people might just fork it and use their own version but that is not a 100% easy workaround and requires time and maintenance to keep it up to date.
- imtringued 5y agoThe problem is the contradictory nature of commercial open source. You want everyone to have access to the code but you also want to charge businesses. You can't have both. So OSS companies split the code base in to a community and a business edition. The business edition builds on top of the community edition which requires the community edition to either be GPL licensed with a CLA or a permissive license with the risk of competitors building their own business edition.
- danuker 5y agoAnother option is to offer the code for free, but charge for support and a managed instance. I can provide an example: NextCloud. https://nextcloud.com/ https://nextcloud.com/