From 52d72eb5541db75a1a71a7abdcb1b921d10f0a33 Mon Sep 17 00:00:00 2001 From: Denver Gingerich Date: Tue, 28 May 2024 16:09:10 -0700 Subject: [PATCH] Remove links to historical-purposes-only documents --- .../content/copyleft-compliance/about.html | 18 +----------------- .../copyleft-compliance/principles.html | 16 +--------------- 2 files changed, 2 insertions(+), 32 deletions(-) diff --git a/conservancy/content/copyleft-compliance/about.html b/conservancy/content/copyleft-compliance/about.html index 424767d8..76f764d8 100644 --- a/conservancy/content/copyleft-compliance/about.html +++ b/conservancy/content/copyleft-compliance/about.html @@ -105,22 +105,6 @@ Conservancy should contact &l cooperation and participation. In this spirit, Conservancy has co-published, with the Free Software Foundation (FSF), the principles that both organizations follow in their compliance efforts. - Also in collaboration with the FSF, Conservancy also sponsors - the Copyleft and the GNU - General Public License:A Comprehensive Tutorial and Guide, - which formally - launched in fall 2014. The Guide includes tutorial materials about - copyleft and compliance with copyleft licenses, - including A - Practical Guide to GPL Compliance. The materials - on copyleft.org have been developed and - improved since 2002, and are themselves copylefted, and developed - collaboratively in public.

- -

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, this blog post outlining - the compliance process is likely the best source.

+

{% endblock %} diff --git a/conservancy/content/copyleft-compliance/principles.html b/conservancy/content/copyleft-compliance/principles.html index 0c15cf3c..583ff83e 100644 --- a/conservancy/content/copyleft-compliance/principles.html +++ b/conservancy/content/copyleft-compliance/principles.html @@ -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.

-

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, Copyleft and the GNU - General Public License: A Comprehensive Tutorial and Guide - (often called the “Copyleft Guide”), - which includes sections such as - “A - Practical Guide to GPL Compliance” and - “Case - Studies in GPL Enforcement”. Those sections explain the typical process - that Conservancy follows in our GPL enforcement - actions. (A Shorter descriptions of these processes appeared in earlier blog post.)

-

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. -(Good examples of +(Good examples of compliance already exist to help distributors understand their obligations.)