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

Correct CEGEO to COGEO.

Browse source 
Honestly, I just made up this acronym so I'm still not even used to it
yet myself.

OTOH, this is another example of why it's not so good. :)
This commit is contained in:
Bradley M. Kuhn 2014-11-11 22:04:05 -05:00
parent 29e2d38e9d
commit 077feb2da0
1 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
compliance-guide.tex
View file

@ -976,7 +976,7 @@ stay in compliance is a company's regular evaluation of their own compliance.
First, exercise a request CCS for all copylefted works from all your upstream
providers of software and of components embedding software. Then, perform
your own CCS check on this material first, and verify that it meets the
requirements. This tutorial presents later a case study of a CEGEO's CCS
requirements. This tutorial presents later a case study of a COGEO's CCS
check in \S~\ref{pristine-example}, which you can emulate when examining
their own CCS\@.
@ -1000,7 +1000,7 @@ of 10 lines of GPL'd Java code an engineer accidentally pasted into the
source of your ERP system.
Thus, reject the ``compliance industry'' suggestions that code scanners find
and help solve fundamental compliance problems. Consider how CEGEO's tend to
and help solve fundamental compliance problems. Consider how COGEO's tend to
use code scanners. FOSSology is indeed an important part of a violation
investigation, but such is the last step and catches only some (usually
minor) licensing notice problems. Thus, code scanners can help solve minor
@ -1016,7 +1016,7 @@ alleging that you have infringed copyrights that were licensed to you
under the GPL\@. This section outlines a typical enforcement case and
provides some guidelines for response. These discussions are
generalizations and do not all apply to every alleged violation. However,
CEGEO's in particular universally follow the processes described herein.
COGEO's in particular universally follow the processes described herein.
\section{Communication Is Key}
@ -1050,13 +1050,13 @@ generally find that software freedom developers and their lawyers are willing to
have a reasonable dialogue and will work with you to resolve a violation
once you open the channels of communication in a friendly way.
Furthermore, if the complaint comes from a CEGEO, assume they are
well-prepared. CEGEO's fully investigate compliance issues before raising
Furthermore, if the complaint comes from a COGEO, assume they are
well-prepared. COGEO's fully investigate compliance issues before raising
the issue. The claims and concerns will be substantiated, and immediate
denials will likely lead the CEGEO to suspect malice rather than honest
denials will likely lead the COGEO to suspect malice rather than honest
mistake.
However, the biggest and most perennial mistake that all CEGEOs see during
However, the biggest and most perennial mistake that all COGEOs see during
enforcement is this: failure to include the violators' software development
teams in the enforcement discussions and negotiations. As described above,
CCS verification and approval is the most time-consuming and difficult part