Changeset - 251bcc69475e
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 9 years ago 2014-12-03 01:48:42
bkuhn@ebb.org
Typo fix.
1 file changed with 1 insertions and 1 deletions:
0 comments (0 inline, 0 general)
compliance-guide.tex
Show inline comments
...
 
@@ -1447,13 +1447,13 @@ one simple reason: an agreement to comply fully with the GPL for past and
 
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 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
 
follow the \hyperref[enforcement-standard-requests]{standard requests for
 
  resolution} found in this document.
 

	
 
\chapter{Conclusion}
 

	
 
GPL compliance need not be an onerous process.  Historically, struggles
 
have been the result of poor development methodologies and communications,
0 comments (0 inline, 0 general)