diff --git a/conservancy/content/copyleft-compliance/principles.html b/conservancy/content/copyleft-compliance/principles.html index 0c15cf3ccf85609302d9006626d3370382d8ebc5..583ff83ebcee033c46fedbe6c1411b56699eb014 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.)