Kean Johnston writes:
Actually my preference would be to have it read "GPL V2 or
later" to
give people the opportunity to use GPL v2 which I understand, versus
GPL v3 which I don't fully yet. If that is acceptable please consider
this my formal permission to license it under GPL v2 or later. If you
insist on it being "GPL v3 or later" I will need to read the new GPL
more carefully to ensure it protects freedoms I want protected.
While GPLv3 is similar enough to GPLv2 that I would be unwilling to
maintain a separate GPLv2 distribution, I definitely plan to tag the
tree at the point where we switchover so that your code (and mine! I
feel the same was except that I already know that I like v2 better
than v3) will be easily accessible to people under GPLv2. Would that
satisfy you, too?
Note that once the wording is "GPLv2 or later", legally anybody can
unilaterally choose to revise that to "GPLv3 or later". That is
precisely the point of the "or later" wording. Were you aware of
that?
If we do not make this change, it is practically infeasible to import
changes from GNU Emacs or any GPLv3 packages. AIUI, we can legally
distribute individual files under "GPLv2 or later", and (as part of
XEmacs) they automatically become v3 or later in some weird legal
sense. However, once XEmacs goes to "v3 or later" as a whole, that
means that the "default" for contribution is "v3 or later", and we
would need to check every contribution for (a) the actual license of
the file and (b) whether the new contributor finds that acceptable.
There are ways we can improve this situation, but they all require
changing our traditional workflow.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta