Aaron Wolf wrote :
because the GPLv3 has an explicit clause that says the code can be
used in an AGPLv3 project.
in fact, both licenses have to contain such an explicit concession to
each other for the one-way compatibility to work.
the resulting combo will be AGPL overall
right.
it's also worth mentioning that this doesn't mean the non-AGPL parts
get re-licensed for the new project. it's only the whole combination
that is AGPL, and the GPL(v2+|v3) components' licenses stay as they
were.
i get the feeling that this has been poorly misunderstood,
historically. compatibility is often equivocated with relicense-ability.
--
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
