I am currently working for a company on a contract-to-hire (eventually) plan. Apart from tax forms, I never signed an official contract. Do I maintain all rights to my work? I am by no means planning on walking away and calling it mine - just interested in reusing portions of it on other projects. Would that be acceptable?
This has bitten many people involved in work-for-hire situations.
I feel like this is kind-of a cop-out on an answer, but honestly, it depends a very great deal on what kind of work you're doing, and I think Harvard Law School's Professor Terry Fisher has already answered your question with incredibly elaborate detail in Lecture 6 (entitled, The Mechanics of Copyright; in 3 parts) of his universally available CopyrightX MOOC, so I'm just going to refer you there for now. There are several other examples of situations like the one you describe throughout the other lectures too, but I know he talks about work-for-hire situations in that lecture.
5Hi CopyrightX, would you be able to summarize the most important points from the lecture here in the body of your post? Listing that information here would ensure that this post is still helpful a year from now, once that professor has removed those lectures, breaking the link, and therefore leaving future visitors with no recourse. I also made an edit to help your post appear more concise and focused on the problem. Hope this helps! :) May 22, 2013 at 2:21
Your edit of my answer removes the specific answer to your question in your comment (which is why I haven't approved the edit for now): "...time is precious for me at the moment so alas, that's all I can do for now to answer your question." May 22, 2013 at 2:25
2I removed the last paragraph because I was hoping to take the focus off the fact that you haven't really answered the question, and I was hoping maybe you could summarize the slide with more details. Consider that, if we all posted a promise of more details later, this new site may not be all that useful. I don't think you need to write a thesis, but a summary of the main ideas and takeaways would make this a really great answer. Hope this helps. May 22, 2013 at 2:28
1The reason it's impossible to summarize details like these are the same reasons that the US Register of Copyrights Maria Pallante testified before Congress two months ago that, "...my point is, if one needs an army of lawyers to understand the basic precepts of the law, then it is time for a new law." I think your edit made my answer worse, and I think your edit and comments reflect a "throw out the baby with the bathwater" cliché. It's not a slide. It's about 90 minutes of lecture to watch and listen to. No, I can't summarize that. May 22, 2013 at 2:34
That is usually settled in a contract. For example, I do mostly open source development on LedgerSMB. My contracts state that my work is my own, but that I am willing to license them to the customer under any of the GPL v2, BSD, or MIT licenses, with the GPL v2 being the default.
I have also done work for Microsoft where the contract stipulated that they owned my work but licensed it back to me under the Microsoft Permissive License (very little difference except that the copyright statements say Microsoft). The first thing you need to do is figure out what is acceptable to you, as a business decision, and then decide what to do. However, I would recommend trying to retain copyright (and give them a non-exclusive license under terms they can live with) because it gives you better protection if you do something similar for another client and they then allege copyright infringement.
Again, I am not a lawyer, this is not legal advice, etc. It is probably something worth discussing with a qualified intellectual property lawyer, however, to help you come to a decision about what contract elements you are comfortable with in your specific business.
This is highly dependent on local jurisdiction, unless there is a contract governing the rights. The best practice is to have a lawyer draft up a boilerplate contract for you that specifies the rights in a way you are comfortable with and make sure they explain it to you so you understand the implications. Then if a client has questions about it or wants to make alterations, you understand what you are giving up if you remove a particular part of the contract.
Also, be aware that if you want to maintain rights to code you've written, it is also often necessary to have a solid NDA (non-disclosure agreement) that can help protect your clients' proprietary information and business processes that may be incorporated in the code. In those cases, you may have the rights to the code, but may not be able to reuse it without stripping out the portions that fall under NDA restrictions.