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

Strictly speaking, for proprietary relicensing 'only' unconditional permissions are needed.

Browse source 
Signed-off-by: enyst <engel.nyst@gmail.com>
This commit is contained in:
enyst 2014-09-05 13:55:28 -04:00 committed by Bradley M. Kuhn
parent f31235afbc
commit 831c21febb
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
gpl-lgpl.tex
View file

@ -4322,10 +4322,11 @@ versions, and those forks that exist remain freely available.
A final common business model that is perhaps the most controversial is
proprietary relicensing of a GPL'd code base. This is only an option for
software in which a particular entity is the sole copyright holder. As
discussed earlier in this tutorial, a copyright holder is permitted under
copyright law to license a software system under her copyright as many
different ways as she likes to as many different parties as she wishes.
software in which a particular entity is the sole copyright holder or has
unconditional relicensing permissions. As discussed earlier in this tutorial,
a copyright holder is permitted under copyright law to license a software
system under her copyright as many different ways as she likes to as many
different parties as she wishes.
Some companies use this to their
financial advantage with regard to a GPL'd code base. The standard