Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Wordsmith this paragraph

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-20 21:14:12 -04:00 • committed by donaldr3
parent de3e1df167
commit 929f60c316
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
compliance-guide.tex
View file

@ -111,11 +111,11 @@ licenses, by comparison, its terms are in fact clear and quite favorable to
licensees. Indeed, the GPL's terms actually simplify compliance when licensees. Indeed, the GPL's terms actually simplify compliance when
violations occur. violations occur.
GPL violations are often caused or compounded by a failure to adopt sound GPL violations occur (or, are compounded) most often when companies lack sound
practices for the incorporation of GPL'd components into a company's practices for the incorporation of GPL'd components into their
internal development environment. In this section, we introduce some best internal development environment. This section introduces some best
practices for software tool selection, integration and distribution, practices for software tool selection, integration and distribution,
inspired by and congruent with software freedom methodologies. We suggest companies inspired by and congruent with software freedom methodologies. Companies should
establish such practices before building a product based on GPL'd establish such practices before building a product based on GPL'd
software.\footnote{This document addresses compliance with GPLv2, software.\footnote{This document addresses compliance with GPLv2,
GPLv3, LGPLv2, and LGPLv3. Advice on avoiding the most common GPLv3, LGPLv2, and LGPLv3. Advice on avoiding the most common