Slashdot Mirror
Why Paying For Code Doesn't Mean You Own It
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."
If I buy a bible, I don’t own the original Lindisfarne Gospels
Yes, actually you do. At least where I live they are public domain. You might not own the particular translation or interpretation of said gospels but you do own the core concepts. All of us own them. They are a part of humanity whether it be good or bad. This is the most confusing analogy one could produce.
if I pay a plumber to fix my tap, I don’t ask him to leave his toolbox so I can fix it myself next time;
No, but if you bought a book on plumbing you might just fix it yourself next time. The results may vary but it's different from compiled code in that the person has no option to 'decompile' the code and go through it. You're right but the analogy has flaws. The plumber isn't producing a copyrighted work for you, he's performing a service. No goods are exchanged between you and the plumber like a software release.
if I buy Harry Potter and the Half Blood Prince on Blu-ray, I don’t own the movie but only a copy (whose usage is restricted by the terms of the licence); if I buy Microsoft Word, I own one copy of the compiled code, not the source.
This is it, it comes down to licensing and copyright. Why do you waste so much breath on this rant when it's a legal agreement between you and your customer that is based on commonly known and accepted copyright and licensing terms?
I will say that with the advent of the Agile Methodology in where I work, the customer is much more involved. We meet with them every two weeks. We constantly incorporate their ideas into their site or program through our own code. And at the end it's a mixture of ideas but we're still the ones that coded it. Between you and I, I'd love to give them the code. But that's the decision of the guy who runs my company, not mine. If you have switched from the previous models of "wait a long time and big bang release" to "constant customer input" then you may now be experiencing something natural--the customer feels they own the code. Because they were with you every step of the way from infantile code to adult production code. Just keep that in mind.
My work here is dung.
Write a good contract and the issue is moot, for both parties.
---- Booth was a patriot ----
If someone pays you to perform work, they own all rights to that work. When I was married, we had a difficult time finding a photographer that agreed, and simply didn't do business with those that wanted to be paid for their work, and wanted to keep all rights to said photos for use in promotions and fees for reprints. I consider that a form of double jeopardy where I'm being forced to pay for something twice.
Software is no different. If you're being paid to perform a specific work, it's no different than if the person/organization paying you did the work themselves. You can't have both.
There's a practical presumption in law that if you pay for something and it is delivered, you own it. You have to have it in writing if you don't want to work that way. That, for instance, is why we have those obnoxious (and legally tenouous) "shrink-wrap" licenses. Because "licensing" is not the same as "owning." If licensing were the normal case in common law, you wouldn't need a "licensing" agreement.
I've had clients who think that they own the code simply because they paid for a website that uses one of our libraries. They buy the right to use the code.
When you buy software in a store or online you don't own the source code. Open source software may provide its source along with the executables but that doesn't mean you own it either.
When doing custom work we offer the client the option of full ownership at full price or 'shared' ownership for a reduced fee. With 'shared' ownership they can modify it at will but aren't allowed to ever resell it. We can't sell it to anyone who would be considered a competitor. I've yet to have someone opt for the full price/full ownership option.
This is a weird and slippery slope. I don't think that anybody feels that because they buy software they own rights to the source code, to edit code and distribute it, etc. But they do own the rights to use or utilize the software as they see fit within the confines of common copyright laws.
The author uses the example that you can buy a book or movie, but you don't own the rights to that book or movie. And that's fine, I think we'll all agree to that. However, if I buy a replication of a piece of art, a book, etc., I'm allowed to vandalize/defile it in any nature I wish as long as its for personal use and it is not distributed.
I'm not sure that I like the slippery slope that a lot of developers are trying to tread these days. Notice my use of the words "use" and "utilize." These are two very different words in the English language. Use means, well, to use something. Utilize means to use something for a purpose in which it wasn't originally intended. I can go to the hardware store and buy thousands of different tools and items for home repairs and various other projects. Many times I'll buy patented items because they almost meet my uses. I modify and "utilize" them for the specific task at hand. And this is fine, as you don't see me on the street corner trying to sell modified black and decker pecker wreckers at a markup. I think think that 1) that would infringe patents, 2) that would infringe registered trademarks and patents, and 3) I'd probably go to jail for trying to sell "pecker wreckers."
In the end, I have a product that meets my requirements and the vendor makes money off of my purchase. Everyone is happy, right? I think that this is the hurdle that software developers have to get over. As long as people buy your software, that's all you should care about. Let them modify it to their hearts content as long as they're not selling it for profit. In fact, possibly learn a lesson and integrate some of these features in your next version to appeal to a larger market. I think this is mutually beneficial in the long run. EULA are trash and need to go away.
Wise men say, "Forgiveness is divine, but never pay full price for late pizza."
IAAL, but the issues here are complex so this is NOT advice for any particular person in any particular situation:
If what you are interested in is owning a copyright to source code there are two ways for a "customer" to get the copyright:
1. If the software is a work made for hire. "Work for hire" is a legal definition (see 17 U.S.C. 101), with two different paths. The first path is for the software to be written by an employee within the scope of employment of the organization claiming copyright. Employee specifically does NOT mean an independent contractor, and code written by a contractor is NOT a work for hire! The definition of an employee goes into all sorts of common-law factors a court will look at, but the shorthand is the tax status of an employee with the IRS.... merely calling a contractor an employee is not enough. Also, the work has to be made within the normal scope of employment, so no, the employer cannot claim copyright as a work for hire for something the employee did outside of work. In fact, even if the employee works for the organization as a regular employee, if writing code is not within the normal scope of employment it still might not be a work for hire (up to the courts to decide if things go south). While some works for hire can be done by an independent contractors along with a specific written agreement, software code generally does not fall into any of the specifically enumerated categories where these written agreements work (see 17 U.S.C. 101 for more details).
Interesting: Technically, code written for a big company like MS or IBM by the armies of independent contractors are NOT works made for hire. See point 2 for how the companies can still get rights.
2. Assignment of Copyright: This is much more common for any work not directly made by an employee. There is a written agreement assigning ownership of the copyright to the contracting organization. The usual rules of contract law cover what is and is not within the scope of the assignment. Assignments can be non-exclusive (we can do what we want with the code, but the developer is also free to do what he wants), or more commonly, exclusive (the assignee getting rights to the code has full control, the original developer loses his rights to that specific work). So is there any difference from a work made for hire? YES! In a work made for hire, the organization OWNS the copyright for the entire length of the copyright term. However, in an assignment, Copyright law specifically splits the copyright term into two parts. An assignment made when the work is created transfers rights to the assignee (usually the company) for about 1/2 the term (the time varies depending upon whether the author dies and some other factors, but it is usually a long time > 30 years). The copyright automatically reverts back to the original author, and the assignment agreement cannot override this rule. The law is written this way to give the authors a "second bite at the apple" in case a work they assign away for peanuts becomes very valuable later. The author can extend the copyright to the second half of its term by paying a nominal fee, and can then go out and the assignee loses all previously held rights.
The upshot for the software industry: Any assigned copyrights will eventually revert to the authors. Now, by the time the reversion occurs most software will be long out of date, but as we all know there is plenty of software out there that lingers for a LONG time, and non-employees DO get there rights to the underlying code back.
One other point: Binary code gets a separate copyright from the underyling source code. But binary code is a derivative work of the underyling source code, so even if the developer never compiles code he writes, the binary distribution using that code would violate the copyright of the original code if ther
AntiFA: An abbreviation for Anti First Amendment.
It's pretty simple. If you are an employee, your employer owns your code. If you are a contractor you own your code unless your contract or agreement states that the work is a "work for hire" (or uses equivalent language). Requisite Wikipedia reference.
Other posters have already said that legally it all depends on the license you work out with the customer, and they are correct.
Having said that, I find that the customer's expectations will depend on what the financing model for the product was. Typically when you get paid for software, it will have been developed under one of two models:
If you're using one of the above approaches but want your licensing to work differently, the key is to make this clear to the customer up-front (managing expectations isn't something techies typically enjoy spending time doing, but it's a very important part of having a successful business relationship with your customer) and make sure all your legal wording is done correctly as well. I've worked at companies before where product development was funded by customers, but the need the customer wanted addressed was sufficiently general that the company wanted to retain the copyright and IP to resell to others. In this case, the customer was granted cheap or free perpetual licenses to use the software that was developed, but the contract was written so that the company retained the copyright and the right to sell licenses to others as well.
"if I pay a plumber to fix my tap, I don’t ask him to leave his toolbox so I can fix it myself next time"
"You might ask why I didn’t make a contract with this client in the first place. It’s because I’ve found, over the years, that insisting on a contract before development starts will result either in a delayed start or even a project being shelved."
So, this developer doesn't disclose this to customers who aren't aware that they are screwed when the developer walks away? His tortured analogy of the plumber and his tools is only correct if the plumber is installing pipes, valves, etc. that are 100% proprietary to the plumber and can't be purchased anywhere else. The word slimy leaps to mind for his business ethics (and plumbing in general).
"Powers. I have them."
Does the builder or architect own my house? No, but he might own the floor plan to my house. He might not too. it depends on what I paid for.
Some drink at the fountain of knowledge. Others just gargle.
Bottom line is that if you're buying COTS, then you get whatever the license says. If you're paying for development, then you get whatever you negotiate. Articulate your requirement for data rights in the RFP, carefully review the proposals for meeting your requirements, then follow-up to ensure the contract says what you need it to say.
I've done a significant amount of contract work over the years, "flying solo" so to speak. I've only once had a contention about copyrights, and since then, I've never done work where I don't own what I write!
My explanation goes something like this:
I have years of experience and have developed a standard set of tools that I use to solve different types of problems. I intend to use these tools to cut costs for you, and it's that time savings that makes me worth the money that I'm charging - I'll do a good job in a short time. But I'm writing the software for YOU, not for somebody else, and if I develop a new idea working on your code, I intend to use that same tool elsewhere. So I'll keep the copyrights, leaving me free to do my job elsewhere, and grant you a license letting you use the software as you see fit. You can do what you want to do, I can do what I want to do, and we can both be happy! I will grant you unlimited use license, including access to the sources, and I will make it transferrable - if you sell the business, it's no problem. The only right I won't grant is the right the resell the software, because I don't want to compete with myself!
This has never been a problem - when explained this way, nobody objects and everybody sees what I'm after.
I have no problem with your religion until you decide it's reason to deprive others of the truth.