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

Wordsmith paragraph.

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-20 21:17:07 -04:00 committed by donaldr3
parent 6cbb2d530d
commit a5f9f756d4
1 changed files with 11 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
compliance-guide.tex
View file

@ -138,25 +138,29 @@ more complex obligations under the license.\footnote{While, there has been much
Licenses}'s Section on derivative works}{\S~\ref{derivative-works} of Licenses}'s Section on derivative works}{\S~\ref{derivative-works} of
this tutorial}.} this tutorial}.}
However, in our experience with GPL enforcement, few redistributors' However, experienced GPL enforcers find that few redistributors'
compliance challenges relate directly to the copyleft provisions; this is compliance challenges relate directly to the copyleft provisions; this is
doubly true for most embedders. Instead, the distributions of GPL'd particularly true for most embedders. Instead, the distributions of GPL'd
systems that we encounter typically consist of a full operating system systems most often encountered typically consist of a full operating system
including components under the GPL (e.g., Linux, BusyBox) and components including components under the GPL (e.g., Linux, BusyBox) and components
under the LGPL (e.g., the GNU C Library). Sometimes, these programs have under the LGPL (e.g., the GNU C Library). Sometimes, these programs have
been patched or slightly improved by direct modification of their sources, been patched or slightly improved by direct modification of their sources,
resulting unequivocally in a derivative work. Alongside these programs, resulting unequivocally in a derivative work. Alongside these programs,
companies often distribute fully independent, proprietary programs, companies often distribute fully independent, proprietary programs,
developed from scratch, which are designed to run on the Free Software operating developed from scratch, which are designed to run on the Free Software operating
system but do not combine with, link to, modify, or otherwise derive from system but do not combine with, link to, modify, derive from, or otherwise
create a combined work with
the GPL'd components.\footnote{However, these programs do often combine the GPL'd components.\footnote{However, these programs do often combine
with LGPL'd libraries. This is discussed in detail in \S~\ref{lgpl}.} with LGPL'd libraries. This is discussed in detail in \S~\ref{lgpl}.}
In the latter case, where the work is unquestionably a separate work of In the latter case, where the work is unquestionably a separate work of
creative expression, no derivative work has been created. The tiny creative expression, no copyleft provisions are invoked.
Admittedly, a tiny
minority of situations which lie outside these two categories, and thus minority of situations which lie outside these two categories, and thus
involve close questions about derivative works, require a highly do involve close questions about derivative and combined works. Those
situations admittedly do require a highly
fact-dependent analysis and cannot be addressed in a general-purpose fact-dependent analysis and cannot be addressed in a general-purpose
document. document, anyway.
Most companies accused of violations, however, lack a basic understanding Most companies accused of violations, however, lack a basic understanding
of how to comply even in the straightforward scenario. This document of how to comply even in the straightforward scenario. This document