From 2244b0d442d451630174421de210fa9568358cf8 Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Thu, 20 Mar 2014 21:23:29 -0400 Subject: [PATCH] Wordsmith paragraph. --- compliance-guide.tex | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/compliance-guide.tex b/compliance-guide.tex index 419459c..d03682b 100644 --- a/compliance-guide.tex +++ b/compliance-guide.tex @@ -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