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
...
 
@@ -1441,25 +1441,25 @@ are accountable to the IRS (and the public at large) in their annual Form 990
 
filings.   Everyone may examine their revenue models and scrutinize their
 
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 --- 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,
 
rather than any unexpected application of the GPL's source code disclosure
 
requirements.
 

	
 
Compliance is straightforward when the entirety of your enterprise is
 
well-informed and well-coordinated.  The receptionists should know how to
 
route a GPL source request or accusation of infringement.  The lawyers
0 comments (0 inline, 0 general)