20 ms·
I have no experience in this so take my opinion with a grain of salt but what about charging for support contracts? While the project is open source and anybody
by jetti 10y ago
I have no experience in this so take my opinion with a grain of salt but what about charging for support contracts? While the project is open source and anybody could make changes/fixes it isn't always an option for a company to have somebody jump in the code to try and get a handle of the codebase to make certain changes. If they had a contract with you, somebody who is intimately familiar with the codebase, then bugs and changes could be implemented faster and better.
- tonyedgecombe 10y agoDoesn't that just make you a technical support person? I don't know about the OP but selling support sounds like hell to me.
- jetti 10y agoIt does. But a software company of 1 will always make you the technical support person, unless you just don't want to give support.
- chuhnk 10y agoEchoing tonyedgecombe, I'm not interested in the support model. I've spent a number of years as a sysadmin and developer on call, it's not the most enjoyable part of the job. Appreciate the comment though.
- jsegura 10y agoI know that pain very well, but for me it's difficult to think in a dual licensing model without providing support. How it will look like?
- tonyedgecombe 10y agoThere is a difference between providing support for something you sell and making it the whole of your business. I've been running an isv for years and support rarely takes more than 30 minutes in a day.
- mperham 10y agoCharging for support incentivizes you to provide poor documentation and frustrates the customer.