Intellectual property at employee hackathon? The company I am working for this summer is going to be hosting an hackathon for its summer interns. Out of idle curiosity, I asked about the IP rights for any resulting projects, and got the (not entirely surprising) response that the company would own any resulting projects. That got me thinking, though- is this legal? It's a company event for employees, yes, but it's taking place outside work hours with no compensation (aside from food and a few prizes), and projects may be totally unrelated to any existing IP owned by the company. Of course, it's entirely possible that there was some clause in the new hire paperwork about this, but outside of that, would this hold up in court?
"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.
What you're talking about is called black-box reverse engineering. It can be done, and as long as you are meticulous in your record keeping the fact that it has been done should be an appropriate defence against copyright infringement. But that doesn't help against patent claims - while in copyright cases the fact that code has or has not been directly copied is critical, in patent cases it its irrelevant: if you use a patented method, it's a violation. You therefore will need to be careful about any patents that may have been issued to the original author, as well as avoiding copying.
Yes, a work with no license is All Rights Reserved, reserved meaning the creator of the work. Who is the creator of the work ? Everyone who contributed it, unanimously. Yes. If people contributed any copyrightable part of your work, in theory you cannot add any license or grant any right to use/reproduce/whatever the work without their unanimous agreement. That's very cumbersome, and almost nobody really does that, but it's what the law is. Big serious companies and repos require contributors to waive their rights on the code they contribute, by agreeing to a contributor's agreement. For example, python/cpython requires you to give your contribs a license allowing the python org to do essentially what they want with it, even though you retain copyright over them. If your project is not so serious, I suggest it should be enough to make the license clear, and that by contributing people are agreeing to place their contribution's code under the license. If it's a free license, that's all you need.
In the UK it is an offence to cause a computer to gain unauthorised access to any program or data held in any computer (s1 Computer Misuse Act 1990). It seems likely that other European jurisdictions have similar laws. Certainly Germany does: Penal Code 202a data espionage (German text - English translation). (I mention Germany because the linked thread does.) It might constitute theft in the jurisdiction if the finder did not take reasonable steps to find the owner - which may include informing the police of the find. Depending on the jurisdiction it might count as 'treasure' or abandoned property such that the finder is obliged to inform the authorities (the jurisdiction has the presumption of ownership of abandoned or lost property - e.g. Scotland), which then decide what to do with it. Legally speaking it seems to me that, to declare it legal, we have to get over such hurdles. [edit] There seems to be some dispute in the comments that cryptocurrency is subject to any regulation, counts as property, is something of value or is something that is owned and can be stolen, such that the person in the questioner's scenario could be held to account under the law for his behaviour. Aren't they merely numbers? No - plainly they do have value because people trade them with currency and goods and services. The UK's tax authority, HMRC, "does not consider cryptoassets to be currency or money" but sees them as having economic value because "they can be 'turned to account' - for example, exchanging them for goods, services, fiat currency (that is money declared by a government to be legal tender) or other tokens". They are "a new type of intangible asset". Individuals are liable "to pay UK tax if they are a UK resident and carry out a transaction with their tokens which is subject to UK tax". They are liable for "Income Tax and National Insurance contributions on cryptoassets which they receive from their employer as a form of non-cash payment [or from] mining, transaction confirmation or airdrops." (HMRC cryptoassets for individuals) Are they property? Something that can be owned, something that can be dishonestly appropriate (i.e. stolen)? That's the interesting dispute. Recently, the High Court of England and Wales ruled in a bitcoin ransomware-related case that "for the purpose of granting an interim injunction in the form of an interim proprietary injunction ... crypto currencies are a form of property capable of being the subject of a proprietary injunction". In that judgment there is some discussion of the authorities for considering or deciding they are property. ([2019] EWHC 3556 (Comm)) read from para 50 if not the whole judgment. In at least two other cryptocurrency-related cases the High Court treated the cryptocurrency as property. Vorotyntseva v Money-4 Limited, trading as Nebeus.com [2018] EWHC 2598 (Ch) and Liam David Robertson v Persons Unknown 2019. There was also a suggestion in the comments that the police would not understand and would not be interested. But there are several jurisdictions where people have been investigated, arrested, prosecuted and convicted of crimes relating to cryptocurrencies. A simple internet search for bitcoin theft, fraud or money laundering will result in some reports. In any case their interest or lack of it is irrelevant to what the law may say.
Attribution is not a legal requirement If company A owns IP (copyright and trademarks in this case), they can licence it to company N on whatever terms are mutually acceptable. They may require company N to attribute their IP or they may not.
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.
There is no fixed definition in the law of &quot;outside activities&quot; that is applied generally. This will depend entirely on how the employment agreement defines it, and/or how the management of your company defines it. There may be a useful definition in the agreement, ideally there will be. In the far too common case that the agreement leaves this key term undefined, you will have to ask them how they define it. While it is true legally that when they draft the contract and it is ambiguous, you may adopt any reasonable definition, as a practical matter, if you do not disclose something and they consider it an &quot;outside activity&quot; They may claim this is grounds for discharge. If the employment contract requires you to disclose outside activities, you must disclose them or be in breach of that contract, which is surely grounds for discharge, and possibly grounds for a breach of contract suit. Even if it is not part of the contract, saying that you have no such activities when you in fact do is arguably fraud. Saying that you decline to inform management of your outside activities is probably legal, but might well cause them to cancel the offer of employment. If you do inform management, and the activities are approved, there would be no automatic transfer of any existing IP rights. No transfer could occur without an agreement saying so. Some companies, in their employment agreements (or other related agreements) demand that an employee transfer the IP of any project created or worked on using company resources (such as a company computer or network). Some demand a transfer for any project worked on during the employee's working hours. Some demand a transfer for any project done during the period of employment, but they must clearly specify this for it to be effective. That last is unusual, because many employees dislike it enough to go elsewhere as soon as they can, which tends to be bad for the employer. But in no case can a transfer of IP for a project unrelated to the employer's business, not using company equipment or resources, and not done during work hours, be effective without a specific agreement to this effect.
Yes, there is legal precedent against this that would only apply to a government employee. First, let's discuss the private sector. In this case, you are a private employee that comes to your place of work and accuses you of "stealing the cookies from the cookie jar" which is a serious criminal offense. They wish to talk and your boss is in the room. You plead the 5th, but your boss says you're fired if you don't talk to the cops. This is legal because you still have the right to refuse to talk, you just lose your job. A private employer has the right to free association, and wants nothing to do with cookie thieves, alleged or actual. However, in the government employ, your boss is an agent of the government. This same situation is different because the government pays the boss and the agent... so in essence the government is saying talk or be fired. This is unconstitutional as the government cannot retalitate against you for your refusal to talk. Generally, in order to talk to you, the investigator would need either a signed Garrity Statement or a Signed Kalkines Statement. The former is a statement saying that they are investigating a wrong doing but you cannot lose your job if you refuse to speak to the investigators, where as Kalkines says you must talk but you are granted immunity for your part in the wrong doing, so long as you make truthful statements. For more on this, check this legal blog. There is also the matter that a false accusation (and let me be clear... this is academic, I'm not saying the accusation in the real life topic is false, nor am I saying that the defense is false... we're merely discussing a possibility) is made to your employer and they do not offer the job on the basis of the accusation alone, this is grounds for defamation actions... and in certain jurisdictions, it's criminal defamation, so there could be jail time. It's interesting you mentioned teachers, because this happens alot. Kids do know that there are certain things that get a teacher fired quickly, so teachers do get the occasional false accusation of sexual assault (I know one teacher who has had multiple accusations over the course of her career). One of the few good things I can say about the Teachers Union is they cover the legal defense of accused teachers. The accusations do get the teacher removed from the class for sometime, but they don't lose their jobs over this matter. It's followed up but the accusation doesn't immediately lead to the teacher getting fired..