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

Remove problematic text.

Browse source 
After rereading this text a few times, I realized that it doesn't
actually say anything of value.  It looks pretty but is devoid of
meaning (or, less glibly, it doesn't express any concept not already
covered by other text in the tutorial), so I'm cutting it entirely.
This commit is contained in:
Bradley M. Kuhn 2014-11-10 21:07:18 -05:00
parent 4daa86b30f
commit 46d8650bec
1 changed files with 0 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
compliance-guide.tex
View file

@ -382,23 +382,6 @@ for the GPL'd components and your modifications thereto, but not
for independent proprietary applications. The procedures described in
this document address this typical scenario.
% FIXME-URGENT: integrate
Use of these terms allows GPLv3 to be interpreted authoritatively based
solely on local legal knowledge and the technical facts. Parties who may have
questions about compliance with GPLv3 under domestic copyright provisions
need only to ask two questions, one legal and the other factual:
Do I need a license under local copyright law to carry out this activity?
Does my activity enable any other party to make or receive a copy of the program?
If question 1 is answered by a local copyright lawyer in the negative, then
the activity involved is not propagation and is permitted by GPLv3 without
more. If the answers to both questions are positive, then the activity
involved is ``conveying'', and copyleft obligations apply.
%FIXME-URGENT: END
\section{Monitor Software Acquisition}