@@ -3092,50 +3092,49 @@ The GPL is a statement of permissions, some of which have conditions.
Additional terms --- terms that supplement those of the GPL --- may come to be
placed on, or removed from, GPL-covered code in certain common ways.
Copyleft licensing theorists have generally called
those added terms ``additional permissions'' if they grant
exceptions from the conditions of the GPL, and ``additional requirements'' if
they add conditions to the basic permissions of the GPL\@. The treatment of
additional permissions and additional requirements under GPLv3 is necessarily
asymmetrical, because they do not raise the same interpretive
issues; in particular, additional requirements, if allowed without careful
limitation, could transform a GPL'd program into a non-free one.
With these principles in the background, GPLv3~\S7 answers the following
questions:
\begin{enumerate}
\item How do the presence of additional terms on all or part of a GPL'd program
affect users' rights?
\item When and how may a licensee add terms to code being
distributed under the GPL?
\item When may a licensee remove additional terms?
\end{enumerate}
Additional permissions present the easier case. Since the mid-1990s,
permissive exceptions often appeared alongside GPLv2 with permissive
exceptions to allow combination
permissive exceptions often appeared alongside GPLv2 to allow combination
with certain non-free code. Typically, downstream
stream recipients could remove those exceptions and operate under pure GPLv2.
Similarly, LGPLv2.1 is in essence a permissive variant of GPLv2,
and it permits relicensing under the GPL\@.
These practices are now generalized via GPLv3~\S7.
A licensee may remove any additional permission from
a covered work, whether it was placed by the original author or by an
upstream distributor. A licensee may also add any kind of additional
permission to any part of a work for which the licensee has, or can give,
appropriate copyright permission. For example, if the licensee has written
that part, the licensee is the copyright holder for that part and can
therefore give additional permissions that are applicable to it.
Alternatively, the part may have been written by someone else and licensed,
with the additional permissions, to that licensee. Any additional
permissions on that part are, in turn, removable by downstream recipients.
As GPLv3~\S7\P1 explains, the effect of an additional permission depends on
whether the permission applies to the whole work or a part.
% FIXME-LATER: LGPLv3 will have its own section
Indeed, LGPLv3 is itself simply a list of additional permissions supplementing the
terms of GPLv3. GPLv3\S7 has thus provided the basis for recasting a
formally complex license as an elegant set of added terms, without changing