Changeset - 06178c3fb273
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-03-21 16:53:21
bkuhn@ebb.org
Move this section on License Compatibility here.
1 file changed with 11 insertions and 15 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -3082,20 +3082,6 @@ on the User Product''.
 
Finally, GPLv3\S6 makes it clear that there is also no requirement to
 
provide warranty or support for the User Product itself.
 

	
 
\section{Understanding License Compatibility}
 
\label{license-compatibility}
 

	
 
% FIXME: more about license compatibility here.
 

	
 
A challenge that faced the Free Software community heavily through out the
 
early 2000s was the proliferation of incompatible Free Software licenses.  Of
 
course, we cannot make the GPL compatible with all such licenses. 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.
 

	
 
% FIXME: connecting text
 

	
 
\subsection{GPLv3~\S7: Additional Permissions}
 

	
 
The GPL is a statement of permissions, some of which have conditions.
...
 
@@ -3155,7 +3141,17 @@ GPL with permissive exceptions.  The removability of additional permissions
 
under GPLv3\S7 does not alter any existing behavior of the LGPL since the LGPL
 
has always allowed relicensing under the ordinary GPL\@.
 

	
 
\subsection{Additional Requirements and License Compatibility}
 
\section{Understanding License Compatibility}
 
\label{license-compatibility}
 

	
 
A challenge that faced the Free Software community heavily through out the
 
early 2000s was the proliferation of incompatible Free Software licenses.  Of
 
course, we cannot make the GPL compatible with all such licenses. 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.
 

	
 
\subsection{GPLv3~\S7: Additional Requirements and License Compatibility}
 

	
 
We broadened the title of section 7 because license compatibility, as it is
 
conventionally understood, is only one of several facets of the placement of
0 comments (0 inline, 0 general)