Move this text to the compliance guide, which is really where it belongs.
This commit is contained in:
parent
2bafeda59e
commit
fcec57fe6d
2 changed files with 16 additions and 15 deletions
|
@ -720,7 +720,22 @@ generalizations and do not all apply to every alleged violation.
|
|||
|
||||
\section{Understanding Who's Enforcing}
|
||||
\label{compliance-understanding-whos-enforcing}
|
||||
% FIXME
|
||||
% FIXME: this text needs work.
|
||||
|
||||
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
|
||||
quickly as possible, and redress the damage caused by the violation.
|
||||
That is FSF's steadfast position in a violation negotiation --- comply
|
||||
with the license and respect freedom.
|
||||
|
||||
However, other entities who do not share the full ethos of software
|
||||
freedom as institutionalized by FSF pursue GPL violations differently.
|
||||
MySQL AB, a company that produces the GPL'd MySQL database, upon
|
||||
discovering GPL violations typically negotiates a proprietary software
|
||||
license separately for a fee. While this practice is not one that FSF
|
||||
would ever consider undertaking or even endorsing, it is a legal way for
|
||||
copyright holders to proceed.
|
||||
|
||||
|
||||
\section{Communication Is Key}
|
||||
|
||||
|
|
14
gpl-lgpl.tex
14
gpl-lgpl.tex
|
@ -1956,20 +1956,6 @@ holder. Both are common practice, although
|
|||
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
|
||||
quickly as possible, and redress the damage caused by the violation.
|
||||
That is FSF's steadfast position in a violation negotiation --- comply
|
||||
with the license and respect freedom.
|
||||
|
||||
However, other entities who do not share the full ethos of software
|
||||
freedom as institutionalized by FSF pursue GPL violations differently.
|
||||
MySQL AB, a company that produces the GPL'd MySQL database, upon
|
||||
discovering GPL violations typically negotiates a proprietary software
|
||||
license separately for a fee. While this practice is not one that FSF
|
||||
would ever consider undertaking or even endorsing, it is a legal way for
|
||||
copyright holders to proceed.
|
||||
|
||||
\section{GPLv2~\S5: Acceptance, Copyright Style}
|
||||
\label{GPLv2s5}
|
||||
|
||||
|
|
Loading…
Reference in a new issue