Implications of changing terms of a free license (LGPL, Apache, MIT, Eclipse, etc) after I started using software on old terms While creating my software (as a developer / startup owner) I rely on the fact that I can use some (software) library for free. I also rely on the fact that I can use it for commercial purpose and that I can keep my code private (not open-source). So, I created the product and launched it widely in the market. But what if after that the license suddenly changes (in the future)? Do I have (legally speaking) 100% firm guarantees that I can continue use it on the same terms (as I started), or it will be a possible "stub-in-the-back" at any time? And I will have to discontinue my business immediately?
In general, unless the license contains a clause which allows it to be modified at a later date through some defined means (publication, revocation of existing license etc) then you are free to continue to use the existing version of the software under the original license terms. So make sure you pin your versions! Look out for clauses such as exists in the GPL which allow the recipient of the distributed binary or code to choose what version of the GPL to apply if the original author does not state (GPLv2 Clause 9) as they then allow recipients to bind you, the distributor, to versions you might not agree with (eg the switch to GPLv3 with its patents clauses).
The first question is whose law you are concerned with, since in principle you might have violated copyright law in any country, and might be sued under the laws of multiple countries. The US has a concept of "fair use" which is notoriously difficult to apply. When you are sued in the US, you can defend against the allegation by arguing certain things: telegraphically, this includes purpose and character of use, nature of the work, substantiality in relation to the whole, and effect on market. Plus there is a 5th factor to be considered, transformativeness. The court then weighs these factors to decide if the use is "fair". By reading existing case law on the topic (conveniently available from the US Copyright office) you might develop a fact-based opinion of the risk: you would be vastly better off hiring an attorney who specializes in US copyright law to do an analysis for you. Do not hire a programmer to give you legal advice (do not hire an attorney to debug code). You would "fail" on the test of substantiality in that you are copying a highly substantial portion of the original work(s). You would "win" on nature of use (research especially non-profit and commentary are the underlying purposes that drive fair use law). It's not clear how you would fare w.r.t. nature of the work, which is intended to distinguish the extremes "news report" and "literature and artistic work" where copying news is at the fair use end of the spectrum. It is not clear how you would fare on "effect on market", but probably not so badly: are you avoiding some licensing fee? Coupled with the tranformativeness consideration, you are most likely having no effect on the market, since the product that you will distribute is not the original work, but a scientific conclusion about the work. Germany has different laws, and this article would be relevant if you cared about Germany. There was a change in the law that expanded the analog of fair use pertaining to research use. That law allows 15 percent of a work to be reproduced, distributed and made available to the public for the purpose of non-commercial scientific research. That, b.t.w., does not refer to what you are planning to do (unless you also publish quotes); for personal scientific research you may reproduce up to 75 percent. Since this is a new law only a year old, you could become part of the cutting edge in testing the limits of the law. So the standard disclaimer applies: ask your attorney. But note section 60d of the law which legalized data mining, and is squarely on point: (1) In order to enable the automatic analysis of large numbers of works (source material) for scientific research, it shall be permissible to reproduce the source material, including automatically and systematically, in order to create, particularly by means of normalisation, structuring and categorisation, a corpus which can be analysed and to make the corpus available to the public for a specifically limited circle of persons for their joint scientific research, as well as to individual third persons for the purpose of monitoring the quality of scientific research. In such cases, the user may only pursue non-commercial purposes. (2) If database works are used pursuant to subsection (1), this shall constitute customary use in accordance with section 55a, first sentence. If insubstantial parts of databases are used pursuant to subsection (1), this shall be deemed consistent with the normal utilisation of the database and with the legitimate interests of the producer of the database within the meaning of section 87b (1), second sentence, and section 87e. (3) Once the research work has been completed, the corpus and the reproductions of the source material shall be deleted; they may no longer be made available to the public. It shall, however, be permissible to transmit the corpus and the reproductions of the source material to the institutions referred to in sections 60e and 60f for the purpose of long-term storage.
The GPL does require you to keep any existing copyright notices: You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you [...] keep intact all the notices that refer to this License and to the absence of any warranty [...] The GPL also recommends adding a notice to each file: Copyright (C) yyyy name of author - This program is free software[...] From my reading of the GPL, if the software you modify contains such notices, which is likely, you must preserve them. This effectively attributes the original author. However, as far as I can see, there is no requirement to have a list of acknowledgements (as is customary in scientific papers), which lists all the software you used. How to attribute parts that are integrated in source form? (Where licence information is given in the file header) If you keep the original file header (and possibly add to it), that should be enough. How to attribute parts that are integrated in binary form? As far as I can see, there is no additional attribution required for distribution in binary form. The GPL requires you to supply the source code along with the binary form, so the attribution in the source code will be available.
Is this work for hire? There is an arguable case to be made that you are an employee for copyright law purposes and, if so, the copyright belongs to the company. The closer an employment relationship comes to regular, salaried employment, the more likely it is that a work created within the scope of that employment will be a work made for hire. But because no precise standard exists for determining whether a work is made for hire under part 1 of the definition in section 101 of the copyright law, consultation with a lawyer may be advisable. Second, if you do own the copyright, there is clearly an implied licence with the company to allow them to use it. It is arguable that the licence is exclusive since the software is bespoke and made specifically for the company. Can you sign an agreement now Yes, but … It is clear that the purpose of signing the agreement is to screw the company over (with the compliance of 2 of the directors). That’s a contract entered into in bad faith and possibly for an illegal purpose and would likely be found invalid. You need to understand that the company is a distinct legal entity from its owners and it has its own rights. People make the mistake of thinking the owners are the company: they aren’t. The two rebel founders are on dangerous legal ground. Assuming they are the directors of the company, they have a fiduciary duty to act in the best interests of the company. That is, they must put the company’s interests ahead of their own. It is clearly not in the company’s interest to have a rival business start so they cannot plan to do that while they are directors - they need to resign first. You are not so much at risk - as an employee/contractor your duty is to follow the directions of the company (the company - not a faction within the company). However, if you aid the other two in what might be a crime, you could be in trouble.
They certainly can make that a license term and revoke the license if you do not comply. However, revoking the license is all they can do to &quot;forbid&quot;. Or they could sue you for damages without revoking the license. That said, you are free to consult how to use their software so long as you do not hold a license so that you are not bound by the terms AND you do not break the law e.g. copyright. How to do it is up to you to figure. Maybe you could simply consult users that do have a license — on their premises and devices.
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).
It doesn't make a difference if the product is free or commercial use, if it's initiated by a company or an individual. What you are considering would be a &quot;derivative work&quot; and without explicit permission from the copyright holder, it is considered a violation.
The agreement linked in the question seems to be or to purport to be, for a non-final, non-production version of the board. I have seen such agreements used, both for hardware and software, used when beta-test versions of products are being distributed to those who agree to do such testing, often in exchange for a reduced price on the final product, or an early look. I have also seen similar language used when an evaluation version of a product is provided free, or at a much reduced price. In such a use, it would be a reasonable contract, it seem to me, and I see no reason why if it were agreed to by both parties in such a situation, it would not be binding. Often such agreements also include a non-disclosure aspect, but this one does not seem to do so. I cannot see how such an agreement could be made applicable automatically, without both parties having chosen to agree to it, and indicated this by signing, clicking, or in some other positive way. I doubt that it could be made automatically applicable, on an "by using this product you agree" basis. I don't know of any physical consumer product, or appliance, sold with such an agreement in ordinary commerce. I am not sure what would happen if a manufacturer wanted to require all purchasers to sign such an agreement. I don't know if it would be binding. I would think that the purchaser's rights under the First Sale doctrice, could be modified by a valid contract agreed to by the purchaser. I do not think that they could simply be revoked by a contract of adhesion, which the purchaser had no choice to decline before making the purchase. As the OP says this was not signed or agreed to in any way, I can't see how it binds the OP.