Changeset - 2bafeda59ed3
[Not reviewed]
0 2 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-03-18 22:25:01
bkuhn@ebb.org
Relicensing is different. Note to that issue on the compliance guide.
2 files changed with 8 insertions and 1 deletions:
0 comments (0 inline, 0 general)
compliance-guide.tex
Show inline comments
...
 
@@ -718,6 +718,10 @@ under the GPL\@.  This section outlines a typical enforcement case and
 
provides some guidelines for response.  These discussions are
 
generalizations and do not all apply to every alleged violation.
 

	
 
\section{Understanding Who's Enforcing}
 
\label{compliance-understanding-whos-enforcing}
 
% FIXME
 

	
 
\section{Communication Is Key}
 

	
 
GPL violations are typically only escalated when a company ignores the
gpl-lgpl.tex
Show inline comments
...
 
@@ -1951,7 +1951,10 @@ from all copying, modification and distribution of the GPL'd software.
 
At that point, violating licensees must gain the forgiveness of the copyright
 
holders to have their rights restored.  Alternatively, the violators could
 
negotiate another agreement, separate from GPL, with the copyright
 
holder.  Both are common practice.
 
holder.  Both are common practice, although
 
\tutorialpartsplit{as discussed in \textit{A Practical Guide to GPL
 
    Compliance}, there are }{Chapter~\ref{compliance-understanding-whos-enforcing}
 
  explains further } key differences between these two very different uses of GPL.
 

	
 
At FSF, it is part of the mission to spread software freedom. When FSF
 
enforces GPL, the goal is to bring the violator back into compliance as
0 comments (0 inline, 0 general)