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

Rewrite paragraph to fix better with section.

Browse source 
This paragraph was from text brought through from another document, and
as such, while this section was built "around it", the text itself was
stylistically different and otherwise problematic.  This change brings
it into form with the rest of the document.
This commit is contained in:
Bradley M. Kuhn 2014-11-19 12:48:45 -05:00
parent 3e88116a43
commit 39ead95e9b
1 changed files with 6 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
compliance-guide.tex
View file

@ -1421,13 +1421,12 @@ to ``fix them'' for companies. Other such operators hold copyrights in some
key piece of copylefted software and enforce as a mechanism to find out who
is most likely to fund improvements on the software.
A few stories abound in the GPL enforcement community that companies have
often formed beneficial consulting or employment relationships with
developers they first encountered through enforcement. In some cases,
working together to alter the mode of use of the project's code in the
company's products was an explicit element in dispute resolution. More
often, the communication channels opened in the course of the inquiry served
other and more fruitful purposes later.
A few companies report that they have formed beneficial consulting or
employment relationships with developers they first encountered through
enforcement. In some such cases, companies have worked with such consultants
to alter the mode of use of the project's code in the company's products.
More often in these cases, the communication channels opened in the course of
the inquiry served other consulting purposes later.
Feelings and opinions about this behavior are mixed within the larger
copyleft community. Some see it as a reasonable business model and others