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

Wordsmith paragraph.

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-20 21:23:29 -04:00
parent 79f9ba4668
commit 6bc993ffd1
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
compliance-guide.tex
View file

@ -198,16 +198,16 @@ software components to improve products. However, along with that
freedom should come rules and reporting procedures to make sure that you
are aware of what software that you include with your product.
The companies we contact about GPL violations often respond with: ``We
didn't know there was GPL'd stuff in there''. This answer indicates a
The most typical response to an initial enforcement action is: ``We
didn't know there was GPL'd stuff in there''. This answer indicates
failure in the software acquisition and procurement process. Integration
of third-party proprietary software typically requires a formal
arrangement and management/legal oversight before the developers
incorporate the software. By contrast, your developers often obtain and
integrate Free Software without intervention. The ease of acquisition, however,
incorporate the software. By contrast, developers often obtain and
integrate Free Software without intervention nor oversight. That ease of acquisition, however,
does not mean the oversight is any less necessary. Just as your legal
and/or management team negotiates terms for inclusion of any proprietary
software, they should be involved in all decisions to bring Free Software into your
software, they should gently facilitate all decisions to bring Free Software into your
product.
Simple, engineering-oriented rules help provide a stable foundation for