3 ms·
The usual answer is that customers should pay for "support" that they will not use (effectively a form of insurance), leaving the maintainer free to continue ma
by wmf 5y ago
The usual answer is that customers should pay for "support" that they will not use (effectively a form of insurance), leaving the maintainer free to continue maintaining.
In practice I suspect we'll see a lot more license changes and hostage source in the future.
- jrochkind1 5y agoGetting people to pay for support they won't use sounds to me closer to a voluntary regular donation than it does the "long tradition of setting up a business, having invoices, and providing services for the pay." I guess it's a way of making a voluntary regular donation seem like a traditional invoice to satisfy the bookkeepers, but that's not what I thought @mfer was getting at. And if it magically worked to produce what are effectively donations, we probably wouldn't be having this conversation. " But yes, you are talking about something other than open source as the more likely future route, which is why i asked @mfer if they were! That's the straightforward way to get people to pay for software -- make it not open source, so they have to pay to use it.
- zozbot234 5y agoContinued maintenance of the software is also included under "support". As are custom feature requests, and sometimes marketing/sponsorship (i.e. the company that pays for "support" can request to be mentioned on the website and in the project documentation). All in all, it works quite well.