Search Results

The GPL FAQ indicates this is legally valid but not advised for practical reasons: A clear statement [about GPL licensing] in the program's README file is legally sufficient as long as that accompani …

Putting "now" is a bad practice since it will necessarily become inaccurate over time. Even if you continue to update your work and remember to change "now" to a specific year whenever you make your f …

First, modern copyright law imposes no requirement to include a copyright notice whatsoever. You could include no copyright notice, and your work would be just as covered by copyright law as a work wi …

If downstream users of your project distribute it without including attribution for the CC-BY-licensed work, they are in violation of the terms of that CC-BY-licensed work. This is an obligation that …

This is a little tricky because the LGPL and AGPL are not strictly compatible. For LGPL code that is linked to AGPL code, compatibility is not required, because LGPL-licensed can be linked to anything …

Section 4(c) lists the only obligations you have with regards to copyright notices: You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, …

Files and authors can have many-to-many relationships: a file may have many different authors. I suppose you could enumerate the list of copyrights of each and every file in a master list somewhere, b …

You should certainly remove the statement from your distribution going forward, but here are several points to consider to put your mind at ease about your past mistake: "Free software" is not a leg …

Only a legal entity can hold a copyright. However, it is worth noting that your copyright notice is not legally significant, since it has virtually no legal effect. Generally speaking, in an overwhelm …

As far as I am aware, all FLOSS licenses that deal with copyright notices only require the preservation of notices that exist. Each author had the opportunity to add their own name to header when they …

From a legal perspective: You should attach licensing information to a file in such a way that you cannot successfully deny that you intended to license the file under those terms. Suppose, at some po …

Since you don't distribute the software, you have no distribution-related obligations. (However, double-check if this really true. Notably, if you're running a Web service, check if any licensed code …

In any nation that is signatory to the Berne Convention, copyright (i.e., a monopoly on redistribution, derivatives, public display, etc.) is automatically in force for the author of a creative work. …