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

Remove links to historical-purposes-only documents

Browse source
This commit is contained in:
Denver Gingerich 2024-05-28 16:09:10 -07:00
parent 8091c44c26
commit 52d72eb554
2 changed files with 2 additions and 32 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
conservancy/content/copyleft-compliance/about.html
View file

@ -105,22 +105,6 @@ Conservancy should contact <a href="mailto:debian-services@sfconservancy.org">&l
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
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
General Public License:A Comprehensive Tutorial and Guide</cite></a>,
which <a href="/news/2014/nov/07/copyleft-org/">formally
launched in fall 2014</a>. The Guide includes tutorial materials about
copyleft and compliance with copyleft licenses,
including <a href="https://copyleft.org/guide/comprehensive-gpl-guidepa2.html"><cite>A
Practical Guide to GPL Compliance</cite></a>. The materials
on <a href="https://copyleft.org/">copyleft.org</a> have been developed and
improved since 2002, and are themselves copylefted, and developed
collaboratively in public.</p>
<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>
</p>
{% endblock %}

16
conservancy/content/copyleft-compliance/principles.html
View file

@ -24,20 +24,6 @@ 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 Software Freedom Conservancy regularly engages in 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;. 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
redistribute copylefted software. We require all redistributors to
@ -146,7 +132,7 @@ those identified in initial reports and those relating to any clauses of the
relevant licenses, are raised and fixed. This is important so that
the dialogue ends with reasonable assurance for both sides that additional
violations are not waiting to be discovered.
(<a href="http://gpl.guide/pristine-example">Good examples of
(<a href="/usethesource/candidate/thinkpenguin-tpe-r1300-round-1-of-1/">Good examples of
compliance</a> already exist to help distributors understand their
obligations.)</li>