From fed5eac075c1428184dcda30a655734e8d13324d Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Tue, 11 Nov 2014 19:25:10 -0500 Subject: [PATCH] Correct and integrate this pasted paragraph. Upon closer inspection, this pasted paragraph contained a clear error: as written. Specifically, it stated that compliance was automatic if you merely "pass along" the CCS received from upstream. It's IOTTMCO that this is wrong. I've corrected it and integrated the text. --- compliance-guide.tex | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/compliance-guide.tex b/compliance-guide.tex index 0d7c9a0..1b76a3b 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -1302,12 +1302,12 @@ burden of the vendor's inattention to GPL compliance. Ask the right questions, demand an account of your vendors' compliance procedures, and seek indemnity from them. -% FIXME-URGENT: integrate - -In such instances it is advisable that you exercise your own rights as a user -to request C\&CS for all the GPL programs that your suppliers provided to you, -preferably in an automated process. Once you receive such C\&CS, passing it -along with your product will ensure your compliance with the license. +In particular, any time your vendor incorporates copylefted software, you +\textit{must} exercise your own rights as a user to request CCS for all the +copylefted programs that your suppliers provided to you. Furthermore, you +must ensure that CCS is correct and adequate yourself. Good vendors should +help you do this, and make it easy. If those vendors cannot, pick a +different vendor before proceeding with the product. % FIXME-URGENT: Needs a new section % \section{Mergers and Acquisitions}