What rights do I have to the software I created partially on company time? I work for a large, international company. As a hobby, and in my free time, I began learning software development. To learn, I began creating a small tool that I could use at work to assist with my duties there. However, its usefulness soon caught the eye of coworkers who also wanted to use it. Long story short, my application is now being used in multiple departments, with myself still as the sole developer. It has continued to grow and I now have leadership making specific requests for additional changes to be made to the software. The majority of the early work on the software was done at home, on my own time. However, within the past 6 months, I have spent some company time working on it as well. I am now working on it nearly full time at the request of my managers. My question is this: What are my legal rights to this software? Would I be able to sell it? Or deny its use to my company? There have been no contracts signed at all, no change in my salary, and no offers to pay for the work I've done on it (and no, I do not make a developer's salary; I actually make a relatively low salary-grade). Did I lose all of my legal rights or bargaining power the moment I brought it to work and used company time to work on it? Thank you for your help!
I'll assume you are salaried full time exempt in the U.S. in an at-will, right-to-work state and are covered by a standard "employee handbook". This has been developed by you, employee, to assist in doing your job, employment, for your company, employer, using time, materials and information belonging at least partially to your employer. Since creating it, you gave it to other employees and have accepted management directives to continue work on the software as part of your full-time job. This is the company's software now. Your best bet is to support it like crazy, make it a big deal and ride it as high as it will take you in the company. Ask for a raise, ask for a promotion, get references and put it as an accomplishment on your resume. But you can't sell it or take it away from your employer. That ship has sailed. You can still greatly benefit from your work (at your employer's discretion) and learn from it for next time.
The German law mandates minimum notice periods for work contracts. But there is no restriction on maximum notice periods, as long as the employee does not have a longer notice period than the employer (§622 BGB de|en). So yes, in theory you could negotiate that the company is not allowed to fire you in the first 4 years. But I would find it unlikely that they would agree to that. When the stock options are really your only reason why you want to avoid getting terminated in the first 4 years, then they are more likely to be open to negotiations about the stock option clause than about the termination clause.
"The company you are working for ..." Stop. We're done. An employer owns the IP created by an employee in the course of their employment: the hackathon is in the course of your employment.
You Own The Code To answer your question on whether or not it is copyright infringement: Yes, you do own the rights to the written code but posting it on Github gives Github the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it. To simply put it, no matter what license you use, you give GitHub the right to host your code and to use your code to improve their products and features. This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive your Content. So with respect to code that’s already on GitHub, I think the answer to the question of copyright infringement is fairly straightforward. Things aren’t quite as clear-cut in a scenario where Copilot is trained on code that is hosted outside of GitHub. In that situation, the copyright infringement question would hinge largely on the concept of fair use. If Copilot is being trained on code outside of GitHub, we accept that at least some of what they’re looking at is copyrightable work. So, the question then becomes if it’s fair use. Now, you ultimately can’t conclude definitively that something is fair use until you go to court and a judge agrees with your assessment. But I think there’s a strong case to be made that Copilot’s use of code is very transformative, a point which would favor the fair use argument. There is precedent for this sort of situation. Take the case of Google Books, for example. Google scanned millions of books, provided people who were doing research with the ability to search the book, and provided the user a small snippet of the text that the user was searching for in the book itself. The court did in fact find that was fair use. The use was very transformative. It allowed people to search millions of books. It didn’t substitute for the book itself. It didn’t really take away anything from the copyright holders; in fact, it made it easier for readers to access the work and actually opened a broader market for book authors. And, it was a huge value add on top of the copyrighted corpus. In the latter scenario, a lot depends on the thoroughness and the length of Copilot’s suggestions. The more complex and lengthy the suggestion, the more likely it has some sort of copyrightable expression. If a suggestion is short enough, the fact that it repeats something in someone else’s code may not make it copyrightable expression. There’s also the question of whether what’s being produced is actually a copy of what’s in the corpus. That’s a little unclear right now. GitHub reports that Copilot is mostly producing brand-new material, only regurgitating copies of learned code 0.1% of the time. But, we have seen certain examples online of the suggestions and those suggestions include fairly large amounts of code and code that clearly is being copied because it even includes comments from the original source code.
You probably own the copyright, since this wasn't an explicit part of your job. However, there may be other legal reasons which preclude you from using them anyway; copyright isn't all there is. Since you are in the middle of an active dispute, you should consult an actual lawyer (which I am certainly not) for legal advice.
In Germany, there is no concept that corresponds directly to public domain. You automatically hold the Urheberrecht (~ copyright) for all creative works that you make, and it can't be given up or transferred (§29 UrhG). The work only enters the Gemeinfreiheit (~public domain) 70 years after your death. You can however license Verwertungsrechte (economic usage rights). When you make creative works in the course of employment (see §43 UrhG), your employer automatically gets the Verwertungsrechte necessary in the context for the work, which is typically an exclusive right (no one else, not even you, can use the work). Your are not in an employment relationship with your school, so it has no rights to your works and cannot prevent you from publishing them on copyright grounds. When you see advice on the internet to check with your school first, that is U.S.-specific advice. Since you're still a minor (7–17), you only have limited capacity to enter contracts or legal transactions (bedingte Geschäftsfähigkeit). While you are able to make transactions involving your own means (e.g. buying something with your pocket money) or make transactions that are only to your benefit (such as accepting a gift), other transactions are schwebend unwirksam (~ pending ratification), until your parents agree. The relevant law is in §107 and §108 BGB. This is a problem with open source licenses. If you publish software under a license, this license is schwebend unwirksam. Someone might start using the software under the license. But then if your parents refuse ratification, the license would be invalid, and everyone would have to stop using your software and destroy any derivative works they made. This is a bit of a problem, especially since open source licenses are otherwise assumed to be irrevocable. So if you want to offer a license (including open source licenses), please give legal certainty to the recipients of the license and ask your parents for their consent first, possibly even in writing. Per §107 BGB, the license you offer with their consent will be valid.
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.
Yes, you do. But you should not base your claim primarily on copyright, but just on the license contract you agreed to. It's typically much easier to prove that a party did not fulfill its part of a sales contract (here: Pay the agreed amount) than to prove violation of a copyright you own. Also, you then only need to sue one guy, and not care about every platform your game might be hosted on. This is particularly difficult here, since they have not done anything wrong. It's not their fault that the publisher didn't properly pay the programmer. They (very likely) got their copy of the game legally. For details, you should consult a lawyer. We can't give you detailed legal advice.