@@ -123,32 +123,4 @@ Conservancy should contact <a href="mailto:debian-services@sfconservancy.org">&l
work, <a href="/blog/2012/feb/01/gpl-enforcement/">this blog post outlining
the compliance process</a> is likely the best source.</p>
<h2 id="reporting">Reporting GPL Violations To Us</h2>
<p>If you are aware of a license violation or compliance issue regarding
Debian, Linux, or any <a href="/members/current/">Conservancy member
project</a> (— in particular BusyBox, Git, Inkscape, Mercurial,
Samba, Sugar Labs, or Wine),
please <a href="mailto:compliance@sfconservancy.org">contact us by email at
<compliance@sfconservancy.org></a>.</p>
<!--- FIXME: bkuhn is rewriting this blog post fresh the weekend of --
2020-07-18 so we need not link to ebb.org anymore when we roll out
these changes -->
<p>If you think you've found a GPL violation, we encourage you to
read <a href="http://ebb.org/bkuhn/blog/2009/11/08/gpl-enforcement.html">this
personal blog post by our Policy Fellow, Bradley M. Kuhn</a>, about good
practices in discovering and reporting GPL violations. (We'd also like
someone to convert the text of that blog post into a patch for
<a href="http://compliance.guide">The Compliance Guide on
copyleft.org</a>; submit it
via <a href="https://k.copyleft.org/guide/">k.copyleft.org</a>.)</p>
<h2 id="support">Donate to Support This Work</h2>
<p>Finally, Conservancy welcomes <a href="#donate-box"
class="donate-now">donations</a> in support of our GPL Compliance Projects,
and we encourage you to become a <a href="/sustainer/">an official
Supporter of Software Freedom Conservancy</a>. </p>
{% endblock %}