From fcec57fe6dce1c058bd7290aa9c4b717289f590f Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Tue, 18 Mar 2014 18:26:14 -0400 Subject: [PATCH] Move this text to the compliance guide, which is really where it belongs. --- compliance-guide.tex | 17 ++++++++++++++++- gpl-lgpl.tex | 14 -------------- 2 files changed, 16 insertions(+), 15 deletions(-) diff --git a/compliance-guide.tex b/compliance-guide.tex index d764104..c1a1ebd 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -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} diff --git a/gpl-lgpl.tex b/gpl-lgpl.tex index 44c9015..f661a2a 100644 --- a/gpl-lgpl.tex +++ b/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}