Personal tools

Additional terms and revised gpl

From GPLv3 Wiki

(Difference between revisions)
Revision as of 07:59, 15 October 2006
jjvt (Talk | contribs)

← Previous diff
Revision as of 04:29, 4 November 2006
ashawley (Talk | contribs)
clarify and answer confusion.
Next diff →
Line 1: Line 1:
-Consider this scenario:+EvilCorp adds additional restrictions (per section 7) and writes a version of some GPLv3+ licenced program that is agaist the spirit of GPL (let's call it EvilApp). The FSF writes and releases GPLv4 that doen't allow such restrictions.
-EvilCorp finds out a way to exploit additional restrictions (section 7) and writes a version of some GPLv3+ licenced program that is agaist the spirit of gpl (let's call it EvilApp). Fsf writes gpl v3.1 that don't allow such restriction.+Even if EvilApp is licenced "gpl 3 or any later" it can be upgraded to GPLv4, but the restriction(s) can't be taken out even if they contradict the GPLv4. The copyright of EvilCorp would be violated if the restrictions were removed.
- +
-Which of the following happends according to current GPLv3 draft? Which of them should happend?+
- +
-# EvilApp cannot be upgraded to gpl v3.1 despite it is licenced "gpl 3 or any later".+
-# EvilApp can be upgraded to gpl v3.1, but the restrictions can't be taken out, even when they contradict gpl v3.1.+
-# EvilApp can be upgraded to gpl v3.1 and the restrictions can then be removed thus infridging EvilCorp's copyright.+

Revision as of 04:29, 4 November 2006

EvilCorp adds additional restrictions (per section 7) and writes a version of some GPLv3+ licenced program that is agaist the spirit of GPL (let's call it EvilApp). The FSF writes and releases GPLv4 that doen't allow such restrictions.

Even if EvilApp is licenced "gpl 3 or any later" it can be upgraded to GPLv4, but the restriction(s) can't be taken out even if they contradict the GPLv4. The copyright of EvilCorp would be violated if the restrictions were removed.