Does a non-commercial software project constitute an outside activity and does declaring it to my employer risk any transfer of IP? Background I am based in the UK, and about to enter into a new full-time job as a software engineer at a UK-based software company. I have been asked to declare my outside activities. I have several non-commercial, personal software programs that I write for myself, and hope to continue to develop, outside of working hours and with my own materials. These software programs are not related to the company I am about to work for, or its areas of interest. These programs will never use IP produced by the company, and me working on these programs is unlikely to threaten my job performance because I have no contractual obligations to maintain them. Question Do outside activities have a legal definition and does software like this constitute an outside activity? If software like these do constitute outside activities, is there any risk that their approval by the company could constitute any kind of transfer of IP?
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.
It should contain one of the following two clauses: A clause that explicitly lists all of the side projects you are working on at the point of employment, that will not be transferred to the employer's ownership under Section 11 of the Copyright, Designs and Patent Act 1998 (&quot;the Act&quot;) which states (1) The author of a work is the first owner of any copyright in it, subject to the following provisions. (2) Where a literary, dramatic, musical or artistic work, or a film, is made by an employee in the course of his employment, his employer is the first owner of any copyright in the work subject to any agreement to the contrary. (3) This section does not apply to Crown copyright or Parliamentary copyright (see sections 163 and 165) or to copyright which subsists by virtue of section 168 (copyright of certain international organisations). This would mean that your existing side projects are protected, but any future side projects would transfer to your employer under S11(2). This might be fine if you don't intend on doing any more side projects during your employment and simply want to protect your existing work. A clause that explicitly rejects S11(2) of the Act in relation to work undertaken outside of your employment and not on company resources, that is specifically defined as &quot;side projects&quot; (including a non-exhaustive list of examples) and the rebuttable presumption that any such work is outside S11(2) unless proven to the civil standard in a court of law. This provides balance to both sides: the employee is free to pursue their side projects outside of work, but in the event that they work on them in company time and on company resources (e.g. a laptop) the employer is free to rebut that presumption in court and have the work transferred to them. Generally, the second clause seems to be what most employees would want in a contract to protect their side projects. Whether it can successfully be inserted depends on the negotiation between both sides. Most reasonable employers would not refuse it. The leading case on the matter of S11(2) is Penhallurick v MD5 Ltd [2021] EWCA Civ 1770 (02 December 2021) which future courts of first instance are presently bound to follow, unless the Supreme Court issues a different decision. What does &quot;in the course of employment&quot; mean? Per Penhallurick mentioned above, &quot;in the course of employment&quot; is generally held to mean doing things that you are paid for as part of your employment. For example, if you are a baker and you write a novel in your free time, it is clear that has nothing to do with your employment: you are not being paid by the bakery to write novels. However, if you were to write a baking cookbook that incorporated recipes that you developed at the bakery, that could be held to be done &quot;in the course of employment&quot; because the bakery could argue that you are paid to develop new recipes for them. The development of side projects in relation to software development is fraught with peril. A lot of employers will try and advance the argument that, although you did not develop the work using company resources and time, your work is still &quot;connected&quot; to the area they operate in. Well known examples of this include Google asserting ownership of software development side projects that, on the surface of it, aren't done on company time and resources and don't appear to have been done &quot;in the course of employment&quot; as you are not being paid specifically to work on, e.g. game development when you are employed as a website backend engineer. If the employer can present enough evidence that what you are/were working on is &quot;connected&quot; to their business in some fashion, that is (at present, in England and Wales) sufficient for ownership to transfer to them under S11(2) even if the work wasn't done in company time and/or using company resources. An example of a clause that seeks to protect side projects Both Parties agree that Section 11(2) of the Copyright, Designs and Patent Act 1988 (&quot;the Act&quot;) does not apply to any and all Side Projects started prior to the commencement of employment. Both Parties also agree that S11(2) of the Act does not apply to any and all Side Projects started after the commencement of employment, specifically where said Side Projects are unrelated to the Employer's business of area of business. For the avoidance of doubt, &quot;unrelated&quot; has the ordinary meaning that a reasonable person would assign to it. For example, since the Employer operates in area of business, a Side Project regarding the development of an online video game is clearly unrelated to the Employer's business. This ex post presumption is rebuttable on the provision of clear and compelling evidence presented in a competent and validly constituted court of law in England and Wales that the Side Project was developed on company time and/or using company resources (e.g. a laptop) or that it validly infringes upon a business domain the Employer operates in. Both Parties agree that it will not be sufficient to adduce that the Employer &quot;could&quot; seek to operate in the Side Project's domain. For ownership to transfer under S11(2) of the Act, the Employer must demonstrate that they operated in that domain prior to the creation of the Side Project or that the Side Project has taken advantage of company resources that were not legitimately available outside of the company. For example, confidential company know-how that is specific to the Employer and not an industry standard or widely known thing. For the avoidance of doubt, use of open-source software (used in compliance with the licence and regardless of whether that software was created, released, or maintained by the Employer or someone else) does not constitute taking advantage of company resources. The Employer agrees to pay the Employee a sum of special damages assessed and awarded appropriately by a court of law in England and Wales for any attempt to subvert this clause or sue the Employee for a Side Project contrary to this clause. In the alternative, at the Employee's absolute discretion, a permanent injunction enforcing this clause may be awarded against the Employer.
It depends on what you are selling to the enterprises. You could be selling just a licence to use the program, and retain all the rights on the source code. You could be selling the rights to the source code. For #1, the source code is yours and you can do what it pleases with it1. In fact many programs offer both an open-source licence (which usually forces the user to make its changes to the code publicly available) and a commercial one (which allows the user to keep the modifications of the source code for themselves). For #2, the source code is no longer yours so it is not up to you to decide what to do with it. 1I am assuming no other agreements imposing limits on those; for example that none of your contracts to your customers have a clause forbidding you from making the code available to the public.
Links are in French. As the author of a work, you would generally hold copyright unless there's a contract otherwise. L113 of the Code de la propriété intellectuelle determines who is the rights holder of a given work and I don't see anything there that changes things for you as a contractor. Even if you assigned some rights to your employer through a contract, France has moral rights which can never be ceded. In fact, even if you were a salaried employee, you still hold the rights by default, unlike the US. There are a few exceptions to that though: software, inseparable joint works, and works where the creative process was purely directed by your superiors.
Yep, you are. You still need to keep the LICENSE and NOTICE files in the repository, if there were any in your copy of the project. These files contain the terms and conditions for the project, and provide attribution to the original developers. If you're trying to attribute in the UI of your application, you probably should. It's considered courteous and in the spirit of open source as well. This is also related: Do I need to include the full text of the MIT license in the UI of my app?
The UK Government released an article last year that explains some of the issues relating to ownership of copyright This article is informative. The headline point: Ownership of literary, dramatic, musical, artistic and film works created by an employee during the course of their employment, automatically vests in their employer by virtue of section 11(2) of the Copyright, Designs and Patents Act 1988. The meaning of during the course of their employment has been interpreted by the courts to mean during the course of normal or specifically assigned duties, and that these duties include the creation of intellectual property for the employer. Patents are similarly affected - if the role does not specify or would not imply the creation of patents and other IP, it may not vest in the company automatically. This is a standard clause and is designed to protect the interests of the company, in the event that you create intellectual property as part of your role. Bear in mind here that there's no real need for this property to be created during work hours. That is, if part of your role is to design new software, ownership of that software vests in the company, whether you spent substantial amounts of work hours making it or not. Conversely, if your role does not include, or would be expected to include, the creation of intellectual property, then if you do so - even if it is during work hours - ownership may not necessarily vest in the company. IP you create in the course of your employment will vest in the company in the course of your employment will probably mean: if you are employed to create IP generally, all any IP resulting from your work, or; if you are employed to create a specific work, that work and possibly related works. This is a fairly standard clause, for most companies - I have had several jobs (though none of them technology-related) and they all include some clause to this effect
Can you locate your license (generally not a trivial task)? It may appear under Help-About and a click to view EULA. The EULA specifically addresses redistribution of parts of the software and number of installations you can make with a single license. They do not say what uses you make make of the software, except that &quot;You may not rent, lease, lend or provide commercial hosting services with the Software&quot;. There is no express prohibition against commercial or non-commercial political use of the product: anything not prohibited is allowed. The fact that they say nothing about the content that you create with Word means, they have declined to have a say in the matter. (I am not sure about the wording of the &quot;Educational&quot; versions of Office: those are somewhat negotiated between the institution and MS).
You should probably get a lawyer, but my reading is this: The company whose SDK you use owns their SDK, owns their code, and is free to take any of your ideas how to improve their code without paying you. But they say that ideas are ten a penny, so this is mostly there to prevent pointless lawsuits. On the other hand, it says that everything you do with your product is yours. I might be completely wrong, that's why you should get a lawyer.