Changeset - 30e4942891c6
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 9 years ago 2014-11-19 17:56:28
bkuhn@ebb.org
Reword paragraph; Include ref: "standard requests"

Mostly these changes are wordsmith, but I added a note that violators
should ask for the "standard requests" for compliance to be adequate.
1 file changed with 8 insertions and 5 deletions:
0 comments (0 inline, 0 general)
compliance-guide.tex
Show inline comments
...
 
@@ -1152,6 +1152,7 @@ required to seek restoration of rights for distribution under GPLv2-only
 
after permanent termination.
 

	
 
\chapter{Standard Requests}
 
\label{enforcement-standard-requests}
 

	
 
As we noted above, different copyright holders have different requirements
 
for reinstating a violator's distribution rights.  Upon violation, you no
...
 
@@ -1443,12 +1444,14 @@ work.
 
However, entities and individuals who do GPL enforcement centered primarily
 
around a profit motive are likely the most dangerous enforcement entities for
 
one simple reason: an agreement to comply fully with the GPL for past and
 
future products, which is always the paramount goal to COGEOs, may not be an
 
future products --- always the paramount goal to COGEOs --- may not suffice as
 
adequate resolution for a proprietary relicensing company or grey hat GPL
 
enforcer.  Therefore, violators are advised to consider carefully who has
 
made the enforcement inquiry and ask when and where they have made public
 
commitments and reports regarding their enforcement work, perhaps asking them
 
to directly mimic the detailed public disclosures done by COGEOs.
 
enforcer.  Therefore, violators must consider carefully who has
 
made the enforcement inquiry and ask when and where the enforcer made public
 
commitments and reports regarding their enforcement work and perhaps even ask
 
the enforcer to directly mimic CEOGEO's detailed public disclosures and
 
follow the \hypperref[enforcement-standard-requests]{standard requests for
 
  resolution} found in this document.
 

	
 
\chapter{Conclusion}
 

	
0 comments (0 inline, 0 general)