Live data from Hacker News

A Reason Why Your Contractual Agreement Shouldn't Be a “Work for Hire”

blog.craftblue.com

31–36 of 36 posts

Re: A Reason Why Your Contractual Agreement Shouldn't Be a “Work for Hire”

#31
post #30

Has anyone seen any clauses within an independent contractor agreement, which would allow the retention of certain pieces of the finished work? For instance, I write a class/component/plugin/etc. that I want to use in several projects to increase productivity. Is there a standard way to carve out and retain those pieces of code?

[deleted]

Re: A Reason Why Your Contractual Agreement Shouldn't Be a “Work for Hire”

#32
post #30

Has anyone seen any clauses within an independent contractor agreement, which would allow the retention of certain pieces of the finished work? For instance, I write a class/component/plugin/etc. that I want to use in several projects to increase productivity. Is there a standard way to carve out and retain those pieces of code?

I don't know if there is a standard way to do it, bit that's the arrangement we have with almost all our clients. There are clauses about basically not taking IP, just reusable code for our own purposes. Clients with existing codebases are harder to sell but new projects almost never mind. You can tell the client this significantly benefits them because then they might also get "free" code from our other clients. It's like a microcosm of open source.

Re: A Reason Why Your Contractual Agreement Shouldn't Be a “Work for Hire”

#33
post #8

> A highly recommended practice is to institute a clause which covers a variety of scenarios of assignment of the copyright for all work produced. This is what I've done for years with my Service Agreement. IP transfer officially occurs on full payment, and rights are assigned to Client if Product would not be considered a work made for hire under applicable law. Though if I'm not paid, I send a written warning after…

How would you recommend drafting something similar? Did you work with a lawyer to produce your Services Agreement?

Consult a lawyer. Someone versed in it.

Obligatory: Fuck You, Pay Me https://www.youtube.com/watch?v=6h3RJhoqgK8

Re: A Reason Why Your Contractual Agreement Shouldn't Be a “Work for Hire”

#34
post #8

> A highly recommended practice is to institute a clause which covers a variety of scenarios of assignment of the copyright for all work produced. This is what I've done for years with my Service Agreement. IP transfer officially occurs on full payment, and rights are assigned to Client if Product would not be considered a work made for hire under applicable law. Though if I'm not paid, I send a written warning after…

Care to share your service agreement? Sounds like you've come up with a good formula.

Re: A Reason Why Your Contractual Agreement Shouldn't Be a “Work for Hire”

#35
Joel Spolsky recently wrote on this topic, with focus on full time employment

https://www.joelonsoftware.com/2016/12/09/developers-side-pr...

"... If you hire a photographer to take pictures for your wedding, you own the copies of the pictures that you get, but the photographer still owns the copyright and has the legal monopoly on making more copies of those pictures. Surprise! Same applies to code."

Re: A Reason Why Your Contractual Agreement Shouldn't Be a “Work for Hire”

#36
DRY (Don't Repeat Yourself) is one of the prime commandments of software development.

The problem I see with transferring IP/copyright on a 'work for hire' basis, is that certainly in my case a substantial portion of the codebase is often code that is being reused for good reason.

Losing control of that code now effectively prevents the same code from being reused this elsewhere without getting into further messy contractual details.

Personally I refuse to do work for hire - instead the client gets unrestricted right to use code as desired but does not own copyright.

Thoughts?

Post reply on HN