From ed205b4f61fe77ec9148bae8e5a7f9a2cc803add Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Fri, 7 Nov 2014 07:38:12 -0500 Subject: [PATCH] Write out "CCS" when first mentioned in chapter. Also, add FIXME for when more material is available to link to. --- enforcement-case-studies.tex | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/enforcement-case-studies.tex b/enforcement-case-studies.tex index cec9431..3274bf4 100644 --- a/enforcement-case-studies.tex +++ b/enforcement-case-studies.tex @@ -250,12 +250,15 @@ begin, we offer a study in how copyleft compliance done correctly. This example is, in fact, more than ten years in the making. Since almost the inception of for-profit corporate adoption of Free Software, companies have requested a clear example of a model citizen to emulate. Sadly, while -community-oriented enforcers have vetted uncounted thousands of CCS -candidates from hundreds of companies, the CCS release describes the first -one CCS experts have declared a ``pristine example''. +community-oriented enforcers have vetted uncounted thousands of ``Complete, +Corresponding Source'' CCS candidates from hundreds of companies, the CCS +release describes the first one CCS experts have declared a ``pristine +example''. -% FIXME: link to a ``CCS iteration'' discussion in compliance-guide.tex when -% one exists. (the ``iteration process'' is discussed in~\ref{} of this guide) +% FIXME (above): link to a further discussion of CCS in the compliance guide +% when a good spot exists, then (below) link to a ``CCS iteration'' +% discussion in compliance-guide.tex when one exists. (the ``iteration +% process'' is discussed in~\ref{} of this guide) Of course, most CCS examined for the last decade has (eventually) complied with the GPL, perhaps after many iterations of review by the enforcer.