Copyleft/guide Changeset - ce71c2fc8cf8

Changeset - ce71c2fc8cf8

Parent rev.

Child rev.

[Not reviewed]

0 1 0

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

Wordsmith paragraph and correct for accuracy.

1 file changed with 8 insertions and 7 deletions:

compliance-guide.tex

0 comments (0 inline, 0 general)

compliance-guide.tex

➞

Show inline comments

@@ ... @@
 ridicule of violators in the press and on Internet fora supplemented
 ongoing private enforcement and increased pressure on businesses to
 comply.  In 2003, the FSF formalized its efforts into the GPL Compliance
 Lab, increased the volume of enforcement, and built community coalitions
 to encourage copyright holders to together settle amicably with violators.
 Beginning in 2004, Harald Welte took a more organized public enforcement
 approach and launched \verb0gpl-violations.org0, a website and mailing
 list for collecting reports of GPL violations.  On the basis of these
 reports, Welte successfully pursued many enforcements in Europe, including
 formal legal action.  Harald earns the permanent fame as the first copyright
 holder to bring legal action in a Court regarding GPL compliance.
 In 2007, the SFLC filed the first U.S.~copyright infringement lawsuit
 based on a violation of the GPL\@. While the lawsuits filed by SFLC on
 behalf of its clients have been quite public, SFLC resolves the vast
 majority of enforcement actions privately via
 cooperative communications with violators.  As we have worked to bring
 individual companies into compliance, we have encountered numerous
 In 2007, two copyright holders in BusyBox, in conjunction with the
 Software Freedom Conservancy (``Conservancy''), filed the first copyright infringement lawsuit
 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.  In this document, we highlight these problems and describe
+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
 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
 commercial distributors, redistributors, and resellers on how to avoid
 violations in the first place, and to respond adequately and appropriately
 when a violation occurs.

0 comments (0 inline, 0 general)