Re: update on only/or later etc.
If this is a potential problem once GPL-2.0 is changed to GPL-2.0-only, then it is currently a problem. And perhaps by altering the current identifier (GPL-2.0) to be more explicit (GPL-2.0-only) we will expose just how often GPL-2.0 has been used incorrectly. That may provide better examples to work off of to decide what ‘third option’ we need.
Just a reminder to all: when someone places a copy of the GPL, version 2 alongside source code files this does not make the licensing ambiguous; clearly there is a valid license. The question comes down to how you interpret clause 9:
- does the language, "If the Program specifies a version number of this License which applies to it and 'any later version,' you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation.” interpreted that placing a copy of the license is “specifying a version” and thu a user can redistribute the code under GPL version 2 (GPL-2.0-only) or, possibly some people read this as meaning GPL version 2 or any later version (GPL-2.0+)
- or does placing a copy of a version of the license NOT constitute specifying a version and thus the sentence, "If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.” in which case one can redistribute the code under GPL-1.0+
Some people have made this determination, e.g. Fedora, https://fedoraproject.org/wiki/Licensing:FAQ?rd=Licensing/FAQ#How_do_I_figure_out_what_version_of_the_GPL.2FLGPL_my_package_is_under.3F
Any scenario you could interpret, we have a way to express that currently and would still under the proposal.
While on this subject, an article that appeared on opensource.com came up on the last call. I just want to point out that that article, which explains the above interpretation issues (which we have been talking about for several months), does not reach a conclusion but simply encourages people to provide clarity of their intentions. We can certainly all agree on encouraging that! https://opensource.com/article/17/11/avoiding-gpl-confusion (Although, I think we should consistently encourage people to use the standard license notices provided by the license and/or SPDX short identifiers) :)