Michael Sperber writes:
Same here. I'll do it, but I'm still trying to understand
the
implications: We need to track down every contributor, and have them
agree, right?
No. You're thinking about the "the doc license formerly known as
'Prince'" problem.
For the code, which is under GPL, we are simply selectively choosing
not to offer some of the licenses we received code under, specifically
GPLv2. Ie, unrolling the loop, we are allowed to redistribute all of
our code under "GPLv2" or "GPLv3 or later"; we're just choosing
to
drop the first alternative. Making this operation that easy is *why*
that wording was introduced into the permissions notice.
We do need to check that GPLv2 or later is the license published for
all the files in the distribution, and look up authors or remove code
for any that that is not true.
As a technical matter, I would like to tag or even branch the GPLv2 or
later code for historical interst if nothing else.
_______________________________________________
XEmacs-Patches mailing list
XEmacs-Patches(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-patches