Write out "CCS" when first mentioned in chapter.

Also, add FIXME for when more material is available to link to.
This commit is contained in:
Bradley M. Kuhn 2014-11-07 07:38:12 -05:00
parent fbbc18c7f6
commit ed205b4f61

View file

@ -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.