Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Relicensing is different. Note to that issue on the compliance guide.

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-18 18:25:01 -04:00
parent 6d116fa1f3
commit 2bafeda59e
2 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
compliance-guide.tex
View file

@ -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

5
gpl-lgpl.tex
View file

@ -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