How to "Open Source" Custom, Contract Software? 392
customWorks asks: "I've been approached to write a piece of custom software for a small business owner with the promise of autonomy in its design and implementation. I do not intend to stick around for incremental development after I've delivered it, and so I feel strongly that open sourcing the software would be prudent for the both myself and prospective client. That said, I still expect to be paid for the developing the software. The issue of course is over convincing the client of the benefit of giving away the source to something they've just paid to have developed. I'd like to know if any of you who've done similar contract work have had experience (success?) in presenting an argument for open sourcing the end product? What were the major concerns/misperceptions that you had to overcome in making the case for open source?"
Viral Nature (Score:2, Funny)
Don't reveal your client's identity (Score:5, Funny)
If I were paying someone to write code for my business I would want it as customized to my needs as possible while making it modular for further enhancement. What I would not want is for the entire open source community to know what network OS, database version, hardware, etc. I am using since that would reveal too much useful information to potential intruders.
Change the order :) (Score:2, Funny)
of open source INTO his app. So write the open-source on the side, increase the hourly rate
accordingly so that the labor of integrating it
pays the same, voila
Why tell him? (Score:2, Funny)