Rewrite page; fully discuss all compliance effort

This about page now talks about all of Conservancy's compliance efforts.
This commit is contained in:
Bradley M. Kuhn 2015-10-01 19:15:41 +00:00
parent 17c9edbc60
commit abe226a6f4

View file

@ -4,35 +4,77 @@
{% block content %} {% block content %}
<h1>Conservancy's Copyleft Compliance Projects</h1> <h1>Conservancy's Copyleft Compliance Projects</h1>
<p>The GPL Compliance Project for Linux Developers is comprised of copyright <p>Free and open source software is
holders in the kernel, Linux, who have contributed to Linux under its everywhere and in everything; yet our software freedom is constantly
license, <a href="http://www.gnu.org/licenses/gpl-2.0.html">the eroded. With the help of its volunteers, <a href="/members/current/">member projects</a>, and <a href="/about/staff/">staff</a>,
GPLv2</a>. These copyright holders have formally asked Conservancy to engage Conservancy stands up for users' software freedom via its copyleft compliance work.</p>
in compliance efforts for their copyrights in the Linux kernel.</p>
<p>Historically, Conservancy was well-known for its ongoing license <p>Conservancy engages in copyleft compliance work in two different ways: by acting directly
compliance efforts on behalf of its BusyBox member project. In May on behalf of <a href="/memebers">Conservancy's Member Projects</a> who request
2012, <a href="https://sfconservancy.org/news/2012/may/29/compliance/">Conservancy Free and Open Source License compliance efforts, and for
announced a coordinated compliance effort</a> on behalf of its BusyBox and specific, targeted member projects for communities of developers.</p>
Samba projects, and also launched this unique project, called 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>Conservancy's GPL Compliance Project is run in a collaborative manner with <p>Conservancy's Copyleft Compliance Projects are run in a collaborative manner with
the project developers. All copyright holders involved have the opportunity the project developers. All copyright holders involved have the opportunity
to give input and guidance on Conservancy's strategy in dealing with to give input and guidance on Conservancy's strategy in dealing with
compliance issues. Thus, all Conservancy's compliance matter have full compliance issues. Thus, all Conservancy's compliance matter have full
support of relevant copyright holders.</p> support of relevant copyright holders.</p>
<h2>Member Project Compliance Project</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 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>
<h2>GPL Compliance Project For Linux Developers</h2>
<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>
<p>Linux copyright holders who wish to assign copyright to or sign an enforcement agreement with
Conservancy should contact <a href="mailto:linux-services@sfconservancy.org">&lt;linux-services@sfconservancy.org&gt;</a>.</p>
<h2>The Debian Copyright Aggregation Project</h2>
<p>In August 2015, <a href="/news/2015/aug/17/debian/">Conservancy announced the Debian Copyright Aggregation
Project</a>. This project allows Debian contributors to assign copyrights to
Conservancy, or sign enforcement agreements allowing Conservancy to enforce
Free and Open Source (FOSS) licenses on their behalf. Many Debian contributors
have chosen each of these options already, and more continue to join.</p>
<p>Debian contributors who wish to assign copyright to or sign an enforcement agreement with
Conservancy should contact <a href="mailto:debian-services@sfconservancy.org">&lt;debian-services@sfconservancy.org&gt;</a>.</p>
<h2>Conservancy's Commitment to Copyleft License Compliance</h2>
<p>Conservancy is dedicated to encouraging all users of software to comply <p>Conservancy is dedicated to encouraging all users of software to comply
with Free Software licenses. Toward this goal, in its compliance efforts, with Free Software licenses. Toward this goal, in its compliance efforts,
Conservancy helps distributors of Free Software in a friendly spirit of Conservancy helps distributors of Free Software in a friendly spirit of
cooperation and participation. In this spirit, Conservancy also sponsors cooperation and participation. In this spirit, Conservancy has co-published,
with the Free Software Foundation (FSF), <a href="/linux-compliance/principles.html">the principles that both organizations
follow in their compliance efforts</a>.
Also in collaboration with the FSF, Conservancy also sponsors
the <a href="https://copyleft.org/guide/"><cite>Copyleft and the GNU the <a href="https://copyleft.org/guide/"><cite>Copyleft and the GNU
General Public License:A Comprehensive Tutorial and Guide</cite></a>, in General Public License:A Comprehensive Tutorial and Guide</cite></a>,
collaboration with the Free Software Foundation (FSF), which <a href="/news/2014/nov/07/copyleft-org/">formally
which <a href="/news/2014/nov/07/copyleft-org/">Conservancy formally
launched in fall 2014</a>. The Guide includes tutorial materials about launched in fall 2014</a>. The Guide includes tutorial materials about
copyleft and compliance with copyleft licenses, copyleft and compliance with copyleft licenses,
including <a href="https://copyleft.org/guide/comprehensive-gpl-guidepa2.html"><cite>A including <a href="https://copyleft.org/guide/comprehensive-gpl-guidepa2.html"><cite>A
@ -48,7 +90,7 @@ support of relevant copyright holders.</p>
blog post outlining the compliance process</a> is likely the best source.</p> blog post outlining the compliance process</a> is likely the best source.</p>
<p>If you are aware of a license violation or compliance issue regarding <p>If you are aware of a license violation or compliance issue regarding
Linux, or Debian, Linux, or
any <a href="https://sfconservancy.org/members/current/">Conservancy member any <a href="https://sfconservancy.org/members/current/">Conservancy member
project</a> (and in particular BusyBox, Evergreen, Inkscape, Mercurial, project</a> (and in particular BusyBox, Evergreen, Inkscape, Mercurial,
Samba, Sugar Labs, or Wine), Samba, Sugar Labs, or Wine),
@ -56,11 +98,9 @@ support of relevant copyright holders.</p>
&lt;compliance@sfconservancy.org&gt;</a>.</p> &lt;compliance@sfconservancy.org&gt;</a>.</p>
<p>Finally, Conservancy welcomes <a href="#donate-box" <p>Finally, Conservancy welcomes <a href="#donate-box"
class="donate-now">donations</a> in support of the GPL Compliance Project class="donate-now">donations</a> in support of our GPL Compliance Projects.
for Linux Developers. Just use the <a href="#donate-box" Just use the <a href="#donate-box"
class="donate-now">PayPal link on this page or any of our other donation class="donate-now">PayPal link on this page or any of our other donation
methods listed</a>. Be sure to mention &ldquo;GPL Compliance Project for methods listed</a>. </p>
Linux Developers&rdquo; in the memo line or description field of the
donation.</p>
</div> </div>
{% endblock %} {% endblock %}