mailing list, which is named

  for <a href="/copyleft-compliance/principles.html">Principles of

  Community-Oriented GPL Enforcement</a> which Conservancy follows in all our

  copyleft compliance.</p>

<h2>Compliance Project For Our Fiscally Sponsored Projects</h2>

<p>Historically, Conservancy was well-known for its ongoing license

compliance efforts on behalf of its BusyBox member project.  Today, Conservancy

does semi-regular compliance work for its BusyBox, Evergreen, Git, Inkscape, Mercurial,

Samba, Sugar Labs, QEMU and Wine member projects.  If you are a copyright holder

in any member project of Conservancy, please contact the project's leadership committtee,

via <a href="mailto:PROJECTNAME@sfconservancy.org">&lt;PROJECTNAME@sfconservancy.org&gt;</a>

for more information on getting involved in compliance efforts in that project.

</p>

<p>In May

2012, <a href="/news/2012/may/29/compliance/">Conservancy

launched</a> the <cite>GPL

Compliance Project for Linux Developers</cite>, which handles compliance and

enforcement activities on behalf of more than a dozen Linux copyright

holders.</p>

<p>The GPL Compliance Project for Linux Developers is comprised of copyright

holders in the kernel, Linux, who have contributed to Linux under its

license, <a href="http://www.gnu.org/licenses/gpl-2.0.html">the

GPLv2</a>. These copyright holders have formally asked Conservancy to engage

in compliance efforts for their copyrights in the Linux kernel.  In addition,

some developers have directly assigned their copyrights on Linux to Conservancy,

so Conservancy also enforces the GPL on Linux via its own copyrights in Linux.</p>