Home > slashdot > Why Paying For Code Doesn’t Mean You Own It

Why Paying For Code Doesn’t Mean You Own It

March 6th, 2010 03:20 admin Leave a comment Go to comments

Barence writes “Why do people think they own code just because they’ve paid for it? PC Pro’s Kevin Partner says many of his clients believe that by paying for the work to be done, they take ownership of it. But, put simply, code is owned by its developer even once the client has paid, unless that developer is legally employed by the client or a contract exists that transfers full ownership (and even then it’s far from clear-cut). He discusses the thorny issue of making clients understand that distinction and gives advice on how developers can assert their rights.”

Source: Why Paying For Code Doesn’t Mean You Own It

Related Articles:

  1. Paying With the Wave of a Cellphone
  2. Paying Hacker Extortion
  3. Paying Hacker Extortion
  4. Microsoft Says No To Paying Bug Bounties
  5. 75% of Linux Code Now Written By Paid Developers
blog comments powered by Disqus
YOYOYOOYOYOYO