To what extent, if any, do I have ownership over, and rights to, works I create on my own time? I am a software engineer in California. If I create a piece of software, in my own time, using my own equipment, do I own the copyright on that creation, or does my employer? I see things such as "Google asserts copyright, even on work I do in my own time" (HN discussion). In the HN discussion, someone asserts, California law is pretty clear, if you do it on your own time, on your own equipment, it's yours. Sadly, he does not cite a source for this. The closest I'm able to find is in California's Labor Code §2870, (a) Any provision in an employment agreement which provides that an employee shall assign, or offer to assign, any of his or her rights in an invention to his or her employer shall not apply to an invention that the employee developed entirely on his or her own time without using the employer’s equipment, supplies, facilities, or trade secret information except for those inventions that either: Relate at the time of conception or reduction to practice of the invention to the employer’s business, or actual or demonstrably anticipated research or development of the employer; or Result from any work performed by the employee for the employer. (b) To the extent a provision in an employment agreement purports to require an employee to assign an invention otherwise excluded from being required to be assigned under subdivision (a), the provision is against the public policy of this state and is unenforceable. However, this uses the text "rights in an invention"; does that cover copyright? (Is this the correct law?) Does "Relate … to the employer's business" cover the entirety of software engineering, or just the particular software engineering my employer does? Otherwise, what law is there that backs up the above claim, if any? Or does my employer own copyright on everything down to the love letters I write?
However, this uses the text "rights in an invention"; does that cover copyright? Yes. (Is this the correct law?) It certainly seems to be. Does "Relate … to the employer's business" cover the entirety of software engineering, or just the particular software engineering my employer does? Imagine that you work for a company that writes trading software. In your spare time, you develop a photo editing tool. Do you think a court would find that your project "related to the employer's business"? I do not. Or does my employer own copyright on everything down to the love letters I write? Google does not own everything their employees create; they only claim to. If someone challenged them on it, a court would decide, and probably not in their favor.
Germany may be different, however in the United States this would be considered work-for-hire and the employer would be the rightful owner of the source code. Regardless of jurisdiction, and from a more practical point of view, you are better off not having a copy of the source code. Using it as reference or example in the future could easily turn into (unintentional) copyright infringement. If, in the future, you write code you would like to be able to freely keep and reuse in any project, make sure the owner/employer licenses it using something like the BSD, MIT, or ISC license.
Can anybody create their own license? That is to say, can I for example create my own license under which I can license software? Yep. It's just a contract granting rights to use a copyrighted work. You can write your own contracts, so you can write your own software license. It's just often recommended that you don't, because common licenses are more well-understood, and inexperienced drafters may make errors that could result in problems, such as unintended restrictions, failing to restrict things that were intended to be restricted, or creating provisions that aren't enforceable in some/all jurisdictions. Can you mandate how a software will be released? Yes. Many software licenses, including GPL, do. The restrictions you describe in your example sound similar to CC BY-NC-SA. Also, would the following clause even be legal? Using this software you agree that any work and intellectual property based on or created with this software will be under the [INSERT_NAME_LICENSE] license, even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up I'm not entirely certain, but &quot;even after any and all code from this software is removed in a future update, or even if the work is rebuilt from the ground up&quot; seems, in my opinion, unlikely to be enforceable—especially &quot;even if the work is rebuilt from the ground up.&quot; How would you differentiate a complete rebuild from a totally new piece of software? More broadly, once your copyrighted code is no longer in the product, there's nothing for them to license from you. It's hard to imagine how you'd be able to claim that you're harmed by someone releasing a new version of a product that used to contain your code under a different license. Without harm to you, there's nothing for a court to redress.
The comment is incorrect; creating a derivative work without permission is still disallowed, even for private use. In US copyright law 17USC 106 defines the exclusive rights that the copyright holder has, the right &quot;to do and to authorize&quot;. The second of these is: (2) to prepare derivative works based upon the copyrighted work; Note that the right is the right to &quot;prepare&quot; a derivative work, not the right to &quot;distribute&quot; or &quot;sell&quot; the work. US copyright law defines a derivative work in 17 USC 101 which reads: A “derivative work” is a work based upon one or more preexisting works, such as a translation, musical arrangement, dramatization, fictionalization, motion picture version, sound recording, art reproduction, abridgment, condensation, or any other form in which a work may be recast, transformed, or adapted. A work consisting of editorial revisions, annotations, elaborations, or other modifications, which, as a whole, represent an original work of authorship, is a “derivative work”. The laws of other countries are similar to US law on this point. Article 2, paragraph 3 of the Berne Copyright Convention provides that: (3) Translations, adaptations, arrangements of music and other alterations of a literary or artistic work shall be protected as original works without prejudice to the copyright in the original work. However, it should be noted that if a person creates a derivative work in private, and never shows it to anyone else, the copyright owner would never learn of it, and so could never sue for infringement. But if it were shown or described to anyone, and the owner did learn, then he owner could in theory sue. Whether the owner would choose to sue over a derivative work never circulated is a different matter. The real effect of this law is that when an infringing derivative work is distributed and the owner wants to sue, the owner need not prove distribution. Proving creation of the derivative work is enough. The quoted comment asks about whether such a rule is &quot;unconstitutional or something&quot; and says that &quot;You should be allowed to do whatever you want with your own stuff in your own home.&quot; The US constitution does not grant any such broad right. There are lots of things one might do in own's own home that are illegal: building a bomb for example. Article I, Section 8, Clause 8 of the US Constitution, sometimes called the Copyright Clause or the IP clause, grants Congress the power: To promote the progress of science and useful arts, by securing for limited times to authors and inventors the exclusive right to their respective writings and discoveries. See the LII page &quot;Intellectual Property Clause&quot; and the page Nature and Scope of the Right Secured for Copyright where it is written that: Congress was within its powers in giving to authors the exclusive right to dramatize any of their works. Even as applied to pantomime dramatization by means of silent motion pictures, the act was sustained against the objection that it extended the copyright to ideas rather than to the words in which they were clothed. {Kalem Co. v. Harper Bros., 222 U.S. 55 (1911). For other problems arising because of technological and electronic advancement, see, e.g., Fortnightly Corp. v. United Artists Television, Inc., 392 U.S. 390 (1968); Sony Corp. v. Universal City Studios, 464 U.S. 417 (1984).} See also the Wikipedia article &quot;Copyright Clause&quot;.
As you've presented them, I doubt the functions are protected by copyright in the first place. Originality is one of the threshold requirements for copyright protection, and it demands that the work in question be independently created by the author, and that it possess some minimal degree of creativity. If you're talking about programming at a level so basic that the function truly must be created in a particular way, there is no originality in simply following the instructions. And even if there's some wiggle room, but the language you used has likely been independently replicated by many programmers, that's still not original enough to be copyrightable. What you want to watch out for, though, is the possibility that they've been combined into an original arrangement that is protected. I don't know enough about how copyright law is applied to code to say where or how that line is drawn, but my instinct would be that it could be a fairly low threshold.
As the owner of your own computer, you can dispose of it however you see fit (as long as your choice is legal). The courts could, theoretically, force you do do something with your computer, but installing software is not one of the things that the courts are empowered to force you to do. (Mostly, they can force you to turn it over for a search). A company can't force you to do anything with your property: only the courts can order the use of force. But there is no legal basis for the courts to grant a company's request for an order to install software. A company can perhaps persuade you to install software on your personal computer, in exchange for keeping your employment. I assume you are familiar with the law regarding firing people. If you do not perform your job, you might be terminated for cause. You could hire an attorney and sue for wrongful dismissal, and it's not obvious that you have a valid reason for non-performance. So I would suggest consulting a Canadian employment attorney before sticking your neck too far out.
There are basically two kinds of things one could do. One could assign or transfer intellectual property rights and contracts related to the app to the entity, or one could license the intellectual property rights to the entity. Generally speaking, in a related party transaction, everything should be in a signed writing, and a notice of the transfer of an intellectual property right that has been registered or filed with a government agency should be provided to the government agency in question. Since there are potentially copyright, patent, trademark, publicity, and contractual rights that might be associated with the app, each aspect which exists should be transferred or licensed, as the case may be. While the forms to do this aren't particular long, the concepts involved and correct terminology are subtle, so this would not be a wise undertaking to attempt on a do it yourself basis.
If you develop a program yourself and it wasn't a work made for hire, then the program is yours to do with as you please. You hold the copyright to it. Many developers choose existing licencing arrangements or they can choose to create a license on their own, or using an attorney. And sometimes they choose to release their programs into the public domain. If you release it into the public domain, you are essentially giving up your copyright. The IDE (Integrated Development Environment) you used to develop your program does not dictate what licenses you can use. There are some existing licenses that others use (which you are free to use or NOT to use) give varying protections to you regarding what you are allowing others to do; right of others to copy, right of others to modify, right of others to distribute, rights to sub-licence, and so on. One of the licensing schemes is the GNU General Public License (GPL). But there are many others, too many to list here.