File diff 85bbbf1ec649 → 7286fe56bb36
compliance-guide.tex
Show inline comments
...
 
@@ -1416,12 +1416,17 @@ 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 \hyperref[enforcement-standard-requests]{standard requests for
 
  resolution} found in this document.
 

	
 
\section{Using the GPL with OpenSSL/BSD-4-clause}
 
\label{bsd4clause-openssl}
 
\input{bsd4clause-openssl}
 

	
 

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