Conservancy/website
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remove items that are time-focused; adapt for Conservancy's site

Browse source
This commit is contained in:
Bradley Kuhn 2021-03-25 12:24:28 -07:00
parent 68c8c42674
commit 4c852afa26
1 changed files with 16 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
www/conservancy/static/copyleft-compliance/principles.html
View file

@ -24,25 +24,19 @@ these situations, many companies comply properly, but some companies
also try to bend or even break the GPL's rules to their perceived
advantage.</p>
<p>The Free Software Foundation (FSF) and Software Freedom Conservancy
(Conservancy) today lead worldwide efforts to ensure compliance with
the GPL family of licenses. The FSF began copyleft enforcement
in the 1980s, and Conservancy has enforced the GPL for many of
its member projects since its founding nearly a decade ago. Last
year, the FSF and Conservancy jointly
published <a href="https://copyleft.org/guide/"><cite>Copyleft and
the GNU General Public License: A Comprehensive Tutorial and
Guide</cite></a>, which includes sections such as
<p>The Software Freedom Conservancy leads worldwide efforts to
ensure compliance with the GPL family of licenses. Conservancy has enforced
the GPL for many of its member projects since its founding in 2006. Conservancy also helped
published, and hosts, <a href="https://copyleft.org/guide/"><cite>Copyleft and the GNU
General Public License: A Comprehensive Tutorial and Guide</cite></a>
(often called the &ldquo;Copyleft Guide&rdquo;),
which includes sections such as
&ldquo;<a href="https://copyleft.org/guide/comprehensive-gpl-guidepa2.html#x17-116000II">A
Practical Guide to GPL Compliance&rdquo;</a> and
&ldquo;<a href="https://copyleft.org/guide/comprehensive-gpl-guidepa3.html#x26-152000III">Case
Studies in GPL Enforcement</a>&rdquo;, which explain the typical
process that both the FSF and Conservancy follow in their GPL
enforcement actions. (Shorter descriptions of these processes appear
in blog posts written
by <a href="https://www.fsf.org/blogs/licensing/compliance-situations">the
FSF</a>
and <a href="https://sfconservancy.org/blog/2012/feb/01/gpl-enforcement/">Conservancy</a>.)</p>
Studies in GPL Enforcement</a>&rdquo;. Those sections explain the typical process
that Conservancy follows in our GPL enforcement
actions. (A Shorter descriptions of these processes appeared in <a href="https://sfconservancy.org/blog/2012/feb/01/gpl-enforcement/">earlier blog post</a>.)</p>
<p>As stalwarts of the community's freedom, we act as a proxy for users when
companies impede the rights to copy, share, modify, and/or
@ -63,7 +57,8 @@ licenses. We must take care, in copyleft enforcement,
to focus on the ultimate freedom-spreading purpose of copyleft,
and not fall into an overzealous or punitive approach, or into
legitimizing inherently unjust aspects of the copyright regime.
Therefore Conservancy and the FSF do enforcement according to community-oriented principles originally formulated by the FSF in 2001.
Therefore Conservancy does enforcement according to community-oriented
principles originally formulated by other community leaders in 2001.
</p>
<h4>Guiding Principles in Community-Oriented GPL Enforcement</h4>
@ -72,7 +67,7 @@ Therefore Conservancy and the FSF do enforcement according to community-oriented
<li><strong>Our primary goal in GPL enforcement is to bring about GPL
compliance.</strong> Copyleft's overarching policy
goal is to make respect of users' freedoms the norm.
The FSF designed the GNU GPL's text towards this end.
The GNU GPL's text is designed towards this end.
Copyleft enforcement done in this spirit focuses on stopping
incorrect distribution, encouraging corrected distribution, and
addressing damage done to the community and users by the past
@ -191,11 +186,11 @@ communities.
</p>
<div class="doc-footer">
<p>This document is also published on <a href="https://fsf.org/licensing/enforcement-principles">FSF's site</a>.</p>
<p>We revise these principles from time to time based on community feedback. Please <a href="https://lists.sfconservancy.org/mailman/listinfo/principles-discuss">subscribe to our principles-discuss list</a> to follow the discussion and share your thoughts with us.</p>
Please <a href="https://lists.sfconservancy.org/mailman/listinfo/principles-discuss">subscribe to our principles-discuss list</a> to follow the discussion and share your thoughts with us.</p>
</div>
<p>Copyright &copy; 2015, Free Software Foundation, Inc., Software Freedom Conservancy, Inc., Bradley M. Kuhn, Allison Randal, Karen M. Sandler.
<p>Copyright &copy; 2021, Software Freedom Conservancy.<br/>
Copyright &copy; 2015, Free Software Foundation, Inc., Software Freedom Conservancy, Inc., Bradley M. Kuhn, Allison Randal, Karen M. Sandler.
<br/>Licensed under the <a rel="license" href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons Attribution-ShareAlike 4.0 International License</a>.
<br/>The copyright holders ask that per &sect;3(a)(1)(A)(i) and &sect;3(a)(1)(A)(v) of that license, you ensure these two links (<a href="https://sfconservancy.org/copyleft-compliance/principles.html">[1]</a>,
<a href="https://fsf.org/licensing/enforcement-principles">[2]</a>) are preserved in modified and/or redistributed versions.</p>