File diff 64fe9aae5b31 → c577c99202d3
Show inline comments
{% extends "base_compliance.html" %}
{% block subtitle %}Copyleft Compliance Projects - {% endblock %}
{% block submenuselection %}AboutCompliance{% endblock %}
{% block content %}
<h1>Conservancy's Copyleft Compliance Projects</h1>
<h1 id="ourwork">Conservancy's Copyleft Compliance Projects</h1>

<p>Free and open source software is
        everywhere and in everything; yet our software freedom is constantly
        eroded.  With the help of its volunteers, <a href="/members/current/">member projects</a>, and <a href="/about/staff/">staff</a>,
  Conservancy stands up for users' software freedom via its copyleft compliance work.</p>

@@ -27,13 +27,13 @@ compliance issues.  Thus, all Conservancy's compliance matter have full
  Conservancy's <a href="">principles-discuss</a>
  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>
<h2 id="projects">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,
@@ -80,13 +80,13 @@ 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="">&lt;;</a>.</p>

<h2>Conservancy's Commitment to Copyleft License Compliance</h2>
<h2 id="commitment">Conservancy's Commitment to Copyleft License Compliance</h2>

<p>Conservancy is dedicated to encouraging all users of software to comply
  with Free Software licenses. Toward this goal, in its compliance efforts,
  Conservancy helps distributors of Free Software in a friendly spirit of
  cooperation and participation.  In this spirit, Conservancy has co-published,
  with the Free Software Foundation (FSF), <a href="/copyleft-compliance/principles.html">the principles that both organizations
@@ -106,13 +106,13 @@ Conservancy should contact <a href="">&l
<p>However, the Guide is admittedly a large document, so for those who are
  interested in a short summary of describing how Conservancy handles GPL
  enforcement and compliance
  work, <a href="/blog/2012/feb/01/gpl-enforcement/">this
  blog post outlining the compliance process</a> is likely the best source.</p>

<h2>Reporting GPL Violations To Us</h2>
<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> (&mdash; in particular BusyBox, Evergreen, Inkscape, Mercurial,
  Samba, Sugar Labs, or Wine),
@@ -125,13 +125,13 @@ Conservancy should contact <a href="">&l
   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="">The Compliance Guide on</a>; submit it
   via <a href=""></a>.)</p>
<h2>Donate to Support This Work</h2>
<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="/supporter/">an official
  Supporter of Software Freedom Conservancy</a>. </p>