Copyleft/guide Changeset - fcec57fe6dce

Changeset - fcec57fe6dce

Parent rev.

Child rev.

[Not reviewed]

0 2 0

Bradley Kuhn (bkuhn) - 10 years ago 2014-03-18 22:26:14
bkuhn@ebb.org

Move this text to the compliance guide, which is really where it belongs.

2 files changed with 16 insertions and 15 deletions:

compliance-guide.tex

gpl-lgpl.tex

0 comments (0 inline, 0 general)

compliance-guide.tex

➞

Show inline comments

@@ ... @@
 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
 % 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}
 GPL violations are typically only escalated when a company ignores the
 copyright holder's initial communication or fails to work toward timely
 compliance.  We urge accused violators to respond very promptly to the

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
 negotiate another agreement, separate from GPL, with the copyright
 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
 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}
 GPLv2~\S5 brings us to perhaps the most fundamental misconception and common
 confusion about GPLv2\@. Because of the prevalence of proprietary software,
 most users, programmers, and lawyers alike tend to be more familiar with

0 comments (0 inline, 0 general)