@@ -1410,24 +1410,29 @@ 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 \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.
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
should know the basic provisions of Free Software licenses and your source
disclosure requirements, and should explain those details to the software