Copyleft/guide Changeset - 5e195ab80a22

Changeset - 5e195ab80a22

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Bradley Kuhn (bkuhn) - 9 years ago 2014-11-12 12:50:28
bkuhn@ebb.org

Integrate this short sentence from pasted text.

This was easily integrated, but I am now not sure what I was thinking
with the FIXME note about linking back to the copyleft definition. The
right link is a forward-link to the derivative works chapter, and thus
I've added that.

1 file changed with 6 insertions and 8 deletions:

gpl-lgpl.tex

0 comments (0 inline, 0 general)

gpl-lgpl.tex

➞

Show inline comments

@@ ... @@
 the domain of copyright law and the courts --- not the licenses that utilize
 those systems.
-Copyright law as a whole doesn't propose clear and straightforward guidelines
+Copyright law as a whole does not propose clear and straightforward guidelines
 for identifying the derivative and/or combined works of software.  However,
 no copyright license --- not even the GNU GPL --- can be blamed for this.
 Legislators and court opinions must give us guidance in borderline cases.
 % FIXME-URGENT: integrate (and back ref to copyleft section)
+A
 lawyer’s conclusion on that subject will be based on the application of rules
 Meanwhile, lawyers will likely based their conclusions on the application of rules
 made in the context of literary or artistic copyright to the different
 context of computer programming.
 %FIXME-URGENT: end
 context of computer programming and by analyzing the (somewhat limited) case
 law and guidance available from various sources.
 (Chapter~\ref{derivative-works} discusses this issue in depth.)
 \section{GPLv2~\S1: Verbatim Copying}
 \label{GPLv2s1}

0 comments (0 inline, 0 general)