There has been a lot of talk about companies and individuals adopting licenses that aren’t OSI opensource to protect themselves from mega-corp leechers. Developers have also been condemned who put donation notices in the command-line or during package installation. Projects with opensource cores and paid extensions have also been targets of vitriol.
So, let’s say we wanted to make it possible for the majority of developers to work on software that strictly follows the definition of opensource, which models would be acceptable to make enough money to work on those projects full-time?
Personally I like the following two approaches:
Free and open source for selfhosting, paid when hosted by the company (e.g Nextcloud, gitea, cal.com)
Free and open source with basic features, paid for proprietary business addons (e.g Portmaster, Xpipe)
I think those approaches are fully compatible with the open source definition, but please correct me if I am wrong. (The examples I mentioned are just some of which I personally know and use, but of course they are many others)
I would add:
Also cost for commercial use, free for personal use.
I like this because it allows me a chance to test the full version at my job and then we purchase the full version when we’re sure we want it.