From 46d8650becf8cd1a4222914d7f0422d9a5f61f2f 2014-11-11 02:07:18 From: Bradley M. Kuhn Date: 2014-11-11 02:07:18 Subject: [PATCH] Remove problematic text. 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. --- diff --git a/compliance-guide.tex b/compliance-guide.tex index 53fae066bdea0b4af39e9c8be82f09936dc7e8ac..f7c2727575f3ee6ccdaa35dd28502751f2859b81 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -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}