I think John is right. Basically if you want to be an awesome programmer you need a good amount of reusable code. If you assign rights for your code to the client then you cant reuse it (depending on the verbiage). I would recommend making sure you have rights to reuse your own source code more often than not. You could even compromise and agree to deliver code and keep your rights to reuse it.
Thanks, Iman On Thu, May 29, 2008 at 12:18 AM, Martin Wood-Mitrovski < [EMAIL PROTECTED]> wrote: > > > John Grden wrote: > > I don't agree about keeping source - I think it's pretty well customary > > that the intellectual property invested in the code base is that of the > > client - IE: they paid for you to develop it, so therefore, it's > > theres. That's how's its been on ever gig I've done on the past 7 yrs +. > > I accept thats probably the most common, but I kind of treat it the other > way > around. I claim all IP rights over my work and then 'sell' the product and > support to the client. > > Of course with PHP stuff they have the code, but with the flash > applications > they're just buying the app and support. I've only given away source code > on one > project when I got tired of dealing with a constant flow of tiny changes > and > they had some flash skills themselves. > > but of course the golden rule is, whatever you do, make sure its written > down > and agreed. :) > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org >
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
