@@ -3149,25 +3149,25 @@ has always allowed relicensing under the ordinary GPL\@.
A challenge that faced the Free Software community heavily through out the
early 2000s was the proliferation of incompatible Free Software licenses. Of
course, the GPL cannot possibly be compatible with all such licenses.
However, GPLv3
contains provisions that are designed to reduce license incompatibility by
making it easier for developers to combine code carrying non-GPL terms with
GPL'd code.
This license compatibility issue arises for
three reasons. First, the GPL is a strong copyleft license, requiring
modified versions to be distributed under the GPL\@. Second, the GPL states
that no further restrictions may be placed on the rights of recipients.
Third, all other software freedom respecting licenses in common use contain certain
Third, all other software freedom respecting licenses in common contain certain
requirements, many of which are not conditions made by the GPL\@. Thus, when
GPL'd code is modified by combination with code covered by another formal
license that specifies other requirements, and that modified code is then
distributed to others, the freedom of recipients may be burdened by
additional requirements in violation of the GPL. It can be seen that
additional permissions in other licenses do not raise any problems of license
compatibility.
GPLv3 took a new approach to the issue of combining GPL'd code with
code governed by the terms of other software freedom licenses. Traditional
GPLv2 license compatibility theory (which was not explicitly stated in GPLv2
itself, but treated as a license interpretation matter by the FSF) held that GPLv2 allowed such