in reply to Re: On Code Ownership
in thread On Code Ownership

Ownership != Right to Use != Right to Resell. In other words, it's quite possible to retain ownership (preserving my right to reuse the generic portions of code I develop) while at the same time granting non-exclusive rights for in-house use to the company. They get to do whatever they want with the code for their own purposes and so do I.

Replies are listed 'Best First'.
Re^3: On Code Ownership
by demerphq (Chancellor) on Jun 18, 2005 at 16:30 UTC

    Well presuming that i still had source code available to me then I suppose i wouldn't laugh you out of the room. But I suspect I would still insist that anything that encapsulated my business processes would remain my posession alone.

    Update: Just to make a point I dont have a problem with the use of open source and the process of contributing back modifications made to it. Nor would i have a problem with opensourcing much of the generic part of a product developed for me. I do mind having that code be closed source and not available to me as the customer who funded its initial development.

    ---
    $world=~s/war/peace/g

      I do mind having that code be closed source and not available to me as the customer who funded its initial development.
      I guess that depends on what level the funding was. If the employer wants to get something on the cheap by hiring a part time consultant and avoiding paying benefits, I'd have no problems with the consultant hanging on to their rights. There is also a difference between one-time use and permanent use e.g. the difference between a temporary sign and a logo. If the employer pays the rate for a temporary sign and then expects to get the logo, I have no problems with the designer keeping the logo rights. If the employer pays for the logo at a fair rate then the consultant doesn't have much argument for retaining those rights.