8 ms·
The "Work For Hire" Doctrine Almost Never Works in Software Contracts
- k__ 12y agoSo, if I just go anywhere, write code, write a bill for it and get paid, the whole copyright of the code belongs to me?
- wpietri 12y agoI'm no lawyer, but my understanding is that unless you are an employee, copyright remains with the author unless explicitly transferred. Which is why it's important to get stuff like this in writing. Having a good lawyer look over my contracts has always been worth the price. Partly because my lawyer makes sure that stuff gets done even when the client and I are inclined to focus on the actual work.
- analog31 12y agoThis would be the case if you were a musician performing a concert for pay, so I wouldn't be surprised if it applied to writing code as well.
- gonzo 12y agoif you submit patches to an open source project, you retain copyright on them as well. This is why many OS projects now have contributor license agreements.
- dsymonds 12y agoI don't think a CLA typically assigns copyright. It only provides the project with a license to use the contribution; the contributor still retains the copyright.
- ihnorton 12y ago> I don't think a CLA typically assigns copyright. Be sure to read the fine print. The main point of the CLA for most corporate-backed projects is to allow re-licensing under different terms (read: proprietary). This does not require explicit copyright assignment. On the other hand, the Free Software Foundation requires copyright assignment to give the FSF standing to defend the copyright - to enforce the GPL. > It only provides the project with a license to use the contribution Most projects simply specify that any contributions must be made under the same license as the existing code. The act of voluntary contribution is considered (by most) as sufficient to establish assent to this, although many projects take it a step further and require copyright statements in each file header. For projects that never plan to re-license, this works fine.
- rmc 12y ago> On the other hand, the Free Software Foundation requires copyright assignment to give the FSF standing to defend the copyright - to enforce the GPL. One reason for this is in case someone uses GNU code without following the GPL. With the FSF as copyright assignment, then the FSF can sue the organisation breaking the GPL. Otherwise the individual programmers would have to do it.
- ww520 12y agoYes if you are hired as a contractor. You are the author of the written code and you own the copyright. You lose the copyright to the hiring party only if the "work-for-hire" clause is in the signed contract.
- platz 12y agoAnd the article is arguing that the "work-for-hire" clause isn't sufficient to cause the contractor to loose the copyright.
- Dystopian 12y agoAnd in turn the company should look to copyright assignment. As a contractor, you shouldn't be signing umbrella work-for-hire clauses either. They're usually part of the shotgun approach of "we own everything you do, always, ever". Copyright assignment is where the give-and-take should take place (which I'm surprised the author didn't speak about) - "company gets copyright assignment based on XYZ (which could include payment, equity agreement, etc.)" IANAL - I just hire one with one who protects me from signing stupid stuff and is occasionally the nasty stick when clients act up.
- ars 12y agoYes. However the company that hired you gets an implied license to the code. Which is usually sufficient for them. I don't know if this implied license is exclusive or not though.
- logicallee 12y agoYou should assign the code to the employer of your own initiative simply because it's the right thing to do, and should be the status quo already. Propose language to this effect even if they don't know about it.
- mike_herrera 12y agoCan anyone explain why written code couldn't be considered "a compilation (an original manner of selecting or arranging preexisting works)?" I would think common sense would define most software as an arrangement of preexisting works. e.g. If I'm contracted to develop a web app it's an original arrangement of an existing programming language.
- gohrt 12y agoThe language is tricky, but writing (a book, a program) (or drawing a picture) isn't considered "arranging" words (or paint drops). The entirety of existence is just a series of rearranging molecules, atoms, and quarks! The attempted distinction is intuitive to me, but I for one can't think of the words for it.
- mike_herrera 12y agoLet's try a concrete example: Jane was hired as a contractor to deliver a business process application in C#. The contract to hire Jane was a work-for-hire contract without the explicit copyright transferring language... /end of example. I would presume that Jane's final work product is an arrangement of previous work by Anders Hejlsberg (who lead the original C# development team) and other employees of Microsoft. Is this not a sound line of reasoning?
- Locke1689 12y agoNah. If I build a bridge using Caterpillar equipment I haven't re-arranged Caterpillar equipment into a bridge, I've just used tools. Similarly, just because you write code in C# and then send it to code I wrote, which translates it to CIL, that doesn't mean that any of your code is actually an arrangement of my code. Your code just conformed to the required input of my tool (the C# compiler).
- mike_herrera 12y agoAaaand it's a Roslyn member who replies-- just my luck. :) I'll cede this one.
- zanny 12y agoSounds like a good opportunity to develop FOSS code rather than limit it to one company. I don't get it, though. The business wants the software - they pay to have it made. And then they also want rights to it. I really like how you have to make copyright assignment explicit in the contract, because in general it is ridiculous to write code and then lock it behind a vault door and treat it like liquid gold when other people could benefit from it.
- csense 12y ago> it is ridiculous to write code and then lock it behind a vault door and treat it like liquid gold when other people could benefit from it This isn't "ridiculous". If other people could benefit from the code in question, it seems like at least some of them might be willing to pay for it. Why throw open your vault doors to the public for free when you can charge admission and there are people who want what's inside badly enough to pay?
- coderzach 12y agoBecause the people who need contract development probably aren't the same people who would sell software libraries. Twitter, Facebook, et al, could probably make money off of all the stuff they open source. But they don't, because it's not their business.
- HeyLaughingBoy 12y agoI don't often do this, but I feel I should take the opportunity to point out that I disagree completely with the sentiment in this post, but yet I was "forced" to upvote it because it had been unfairly downvoted. It's may be an unpopular opinion but it's not off topic nor offensive. Please don't downvote for popularity reasons.
- mantrax5 12y agoOther people. Like said company's competition? Like said company's clients? If I go to a restaurant and order a meal, and the waiter decides that's a good opportunity to invite his friends to eat from my plate, I'd find this a good opportunity to walk out without paying a dime.
- patio11 12y agoThis is one of the reason consulting clients are paranoid about IP assignment clauses. I've signed MSAs where the language about the IP assignment was as long as all other contractual terms and the NDA combined. That was historically one of the points of highest friction at my consultancy during contract negotiation, because every lawyer had a different idea of how to totally derisk the IP assignment for the client, many of which were not compatible with me signing them and then continuing to run a consultancy or software company. (Hypothetical example: If I'm doing A/B testing for you, I am of course amenable to giving you copyright to code/copy/reports delivered to you, but I'm not going to give you exclusive rights over "all procedures and knowhow used in the production of the deliverables.") Word to the wise: when you have your lawyer draft your standard contract, ask them "Hey can we have IP assignment happen only after SoW's associated invoices have been paid in full?" That's a valuable lever to have to encourage clients operating in good faith to prioritize getting your invoices paid expeditiously.
- cperciva 12y agoI once had a client present me with an NDA which stated that their Intellectual Property included "all knowhow related to the project", and then a few paragraphs later that they had "the right to seize all Intellectual Property" upon termination of the contract. When I asked if they intended this to include brain surgery, they agreed to amend it to only seizing documents.
- mgkimsal 12y agoI really really really don't think most clients want all my intellectual property. Even I don't want it all...
- GrinningFool 12y agoIt seems like the needed change there was not to alter the scope of what they would seize, but the scope of their definition of Intellectual Property. It's a little unclear from your post - is that what you got modified?
- 12y ago
- roberthahn 12y agoAs with anything legal, whether this applies to you depends on where you are. The article appears to be quoting from laws based on the State of California. If you're not under their jurisdiction, it probably doesn't apply to you. At the least, you should look up the work-for-hire laws in your jurisdiction. Or, you know, work with a lawyer to learn your rights. (edit: copy tweaks)
- tzs 12y agoThe copyright law aspects of the article apply everywhere in the United States. The gist of the article is that you should use an assignment clause instead of a work for hire clause. The work for hire clause is unnecessary. The California law example was to illustrate that trying to be clever and including both an assignment clause and a work for hire clause could actually hurt you in some jurisdictions.
- roberthahn 12y agoah, thanks, that clarifies things a bit more for me. That said, I'm writing from a Canadian perspective. And it's likely that our laws are different in this regard. I'll be looking it up within the next day or so. EDIT: And I got curious enough to look it up quickly: http://www.gowlings.com/KnowledgeCentre/article.asp?pubID=2231 http://www.gowlings.com/KnowledgeCentre/article.asp?pubID=22... states that unlike the US, Canada doesn't have a work-for-hire provision, so copyright remains with the employee or contractor. Which is similar in effect to what's written in the OP. I'd want to corroborate that more before staking my business on it, but at the very least my point about checking the laws in your jurisdiction is important.
- josephlord 12y agoBut isn't it always worth being clear and explicit about who will own what copyrights and and have what licenses to use/modify/distribute the material? And it might not be uniform for everything in the project. There could be build tools that are developed that the client doesn't own but has a very liberal license to use while the actual product and source code copyright could be transferred to the client.
- tzs 12y agoI wonder how Linux distributions fit in? They are typically compilations or collective works, and so a work for hire agreement to write something for a specific distribution does not seem to run into the problems the article discusses.
- M2Ys4U 12y agoThis is because the terms of the license are sufficient for the kernel/distro use. It's kinda the point about free software.
- ChuckMcM 12y agoOne of the things that always amazes me is how intensely people pursue this stuff. Which presumably means they are taking the position that you are going to screw them the first chance you get. And the thing that amazes me is that many employees don't take an equivalent stance regarding the company. Wouldn't you think that if a company was that worried perhaps should worry you too? Love patio11's advice about having the payout be dependent on the transfer of IP, very nice and very appropriate.
- mantrax5 12y agoMalice is not the only way problems occur between contractor and company. Ignorance, misunderstanding, confusion, stress, poor planning, unforeseen circumstances are other very common reasons. Contracts aren't written and signed just so you can sue each other. Contracts are written and signed as an evidence for both sides about what both sides agreed at the time, because no one's memory is that good. Contracts are written so when the proverbial s--t hits the fan, both sides are aware of what happens and are fine with the consequences. And in all of those cases it pays to use the correct, specific, unambiguous language to express the intent of both sides. Expressing intent isn't easy. You can't go back and fix a contract easily the way you can say "Oh no, I mean X, not Y" in a casual conversation. Lots of people, resources and time are about to be spent fulfilling a contract. A lot of problems will occur on the way to it being fulfilled. If you think it's an option to take contracts lightly and you think it's an option to just trust fate & the goodwill of people you didn't know yesterday to sacrifice themselves in order to save your money, time, property and business, it's a sign you've not been burned enough times to learn to think otherwise. Remember, that when stress gets high, and both sides paint themselves in a corner, even the most moral, loyal and honest of people may find themselves bending their morality, loyalty and honesty in order to survive in an impossible situation.
- wikwocket 12y agoIf you see code that checks for every possible type of exception or input error, do you think that code is secretly hoping that an exception occurs? Or do you just think the programmer is trying to cover all the bases so he/she can decide what happens when an error occurs? Contracts are just the 'source code' that define agreements. There's nothing wrong with very specific and precise language. Granted, since contracts are tied to negotiation, some people can be over-aggressive, but mostly long contracts just come from people who have gotten burned before, and have no desire to be burned again.
- M2Ys4U 12y agoI'd love to see an analysis of these issues from an international perspective. Copyright is enough of a quagmire in a single jurisdiction, but there are a LOT of contracts that span multiple jurisdictions.