-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sam Liddicott wrote:
> I want them to use it, I just want modifications to the GPL3 part to be
> GPL3 licensed. Thats why I propose the AGPL link-exception alternative
> to GPL3/13
Well,
this is section 13 of GPLv3:
"Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such."
Note: It says that *the terms of this License will continue to apply to
the part which is the covered work*, which is: If you combine a work
under the GPLv3 with a work under the Affero GPL, e.g. I create a
realtime online GCC compiler using a CMS under the Affero GPL (not that
weird an idea: The compiler might create binaries for portable devices
on which it's not easy to install a compiler yourself), then the Affero
GPL will apply to the CMS as well to the work as a whole - HOWEVER, the
GCC compiler will still be pure GPLv3.
As far as I can see, that's exactly what you want?
To put it in other words: If somebody includes a GPLv3 project in a
program released under the Affero GPL, I will be able to extract this
project' part and work with it under the GPLv3 ("the terms of this
License will continue to apply to the part which is the covered work"),
however, if I want to use the *combined* work (like the online GCC
compiler), I must stick to the Affero GPL.
If that's the case, it works as you say you wish?
br
carsten
- --
http/::www.modspil.dk/itpolitik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHRyJtletyW1YzdSERAu6lAJ4nVfSKkqwTnoKZobzvE7w1JxDN5wCfYUXN
Phud0GAzdGQKhKIctoCUrS0=
=+GBf
-----END PGP SIGNATURE-----