Thanks for the info from a code point of view.
But I was thinking from a design point of view and whether giving a client the copyright to the design gives them a right to have the source Photoshop and Fireworks design files. If they did, there is the risk of them selling the design concept on to it's customers!! Something I don't want after the hard work I put into creating it.
I guess I could write a agreement claus (I use a agreement that they have to agree to by replying to the email), that gives them the copyright, but they can't rebrand it and use the design to sell it to it's customers.
Lee.
Main Topics
Browse All Topics





by: lunadlPosted on 2007-05-31 at 16:49:23ID: 19192246
Well I ran into this problem once before myself. It's really up to you whether or not it is worth giving up your code, but when I did do it because the client insisted on it I charged a processing fee for providing the code and wrote a contract that disallowed him or any entities under his control to use it for profit or even non-profit use with out my consent. The source of page from a design perspective is always available to them so you really aren't losing out on too much. What you do lose out on is the server-side code. It is important to some businesses to know what they will be running on their servers. For example my client wanted to make certain there was no code that would 'break' my app once in a while so i could collect more support money. Either way, it is common for code to be made available at an extra cost to the client, but only if the contract is worth the time and the price is right. Others may say that all code should be open-source, but ya know.. it can't always be that way.