Somehow my email from yesterday on this subject seems not to been have sent..
So i repeat it quickly: In most european countries (i know its different in the U.S.) writing code is a bit equal to writing a book if it comes to copyright. The natural copyright of a book lies with the author! The natural copyright of your code lies with you, the author, too. So if not stated clearly in the contract that you take distance from this natural right, the code is yours! Even if its php and run on the client's server (btw get your own server.. Less problems with difference php versions and environment settings plus the extra monthly income for the hosting). If the client wants you to step back from your right, of course that should be expressed in the equation of the agreed payment. In general I encourage everybody to use open copy rights (I use MIT-Licnese mainly). This way its free to inspire others and the client can have other developers on the project later as well as you can use it where ever you want. And yes.. Always contracts! Always copyright your code! And always partly payments up front! Niels On 5/29/08 9:34 AM, "Iman Khabazian" <[EMAIL PROTECTED]> wrote: > 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 _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
