On Mon, 27 Jul 2009 12:07:47 Craig Boxall wrote: > If it is explained and agreed to at the outset that there is going to > be use of an open source product and they agree to X, Y and Z about > maintaining that code then all is well in my opinion. If they dont > agree to it, then that is also fine and a resolution can be found > before any work is done.
When the 'offer' side of the equation is complex and/or ambiguous, the onus just about always falls on the supplier to remedy any controversy. A wise web developer at this point won't be debating the point on here - they will be working out a way to capitalise on the situation, in other words take commercial advantage of the common market place perception. This should ideally take the form of a portfolio of product offerings that is so simple any numbnuts could understand it. This could be sold over and over again, taking a few hundred to a few thousand dollars each time. While I am not a web developer my professional background is in the Internet industry. I am relating things I have been hearing from customers for almost as long as I can recall. For myself the day I got out of selling technically complex systems, and opted for a product range that could be trivially described and sold over and over again, was the business business decision I ever made. --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
