Copyleft/guide Changeset - 6e61ea854503

Changeset - 6e61ea854503

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Bradley Kuhn (bkuhn) - 10 years ago 2014-03-21 16:54:24
bkuhn@ebb.org

Correct paragraph.

1 file changed with 4 insertions and 4 deletions:

compliance-guide.tex

0 comments (0 inline, 0 general)

compliance-guide.tex

➞

Show inline comments

@@ ... @@
 based on a violation of the GPL\@ in the USA. While  lawsuits are of course
 quite public, the vast majority of Conservancy's enforcement actions
 are resolved privately via
 cooperative communications with violators.  As both FSF and Conservancy has worked to bring
 individual companies into compliance, both organizations have encountered numerous
 violations resulting from preventable problems such as inadequate
 attention to licensing of upstream software, misconceptions about the
 GPL's terms, and poor communication between software developers and their
 management.  This document highlights these problems and describe
 best practices to encourage corporate Free Software users to reevaluate their
 approach to GPL'd software and avoid future violations.
 SFLC continues to conduct GPL enforcement and compliance efforts for many
 of its clients who release their software under the GPL, the GNU Lesser
 Public License (LGPL) and other copyleft licenses.  In doing so, we have
 Both FSF and Conservancy continue GPL enforcement and compliance efforts
 for software under the GPL, the GNU Lesser
 Public License (LGPL) and other copyleft licenses.  In doing so, both organizations have
 found that most violations stem from a few common mistakes that can be,
-for the most part, easily avoided.  We hope to educate the community of
+for the most part, easily avoided.  All copyleft advocates  hope to educate the community of
 commercial distributors, redistributors, and resellers on how to avoid
 violations in the first place, and to respond adequately and appropriately
 when a violation occurs.
 \chapter{Best Practices to Avoid Common Violations}
 \label{best-practices}
 Unlike highly permissive licenses (such as the ISC license), which
 typically only require preservation of copyright notices, the GPL places a
 number of important requirements upon licensees.  These requirements are
 carefully designed to uphold certain values and standards of the software
 freedom community.  While the GPL's requirements may appear initially

0 comments (0 inline, 0 general)