From: Aaron Wolf <wolftune@riseup.net>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Adding [A]GPLv3+ code to Quake-based code base
Date: Tue, 29 Aug 2017 16:06:11 -0700 [thread overview]
Message-ID: <736b7bc7-c823-cc48-f9be-717cac9b9526@riseup.net> (raw)
In-Reply-To: <537d3ec3-b054-75e0-0d11-cfa1f1ac43b8@lyberta.net>
[-- Attachment #1.1: Type: text/plain, Size: 957 bytes --]
On 08/29/2017 02:58 PM, Lyberta wrote:
> Aaron Wolf:
>> You'll need the "or any later version" clause from the GPLv2 stuff. You
>> can ask all the copyright holders if they are willing to add it.
>
> I have talked to other developers and they clarified that the code has
> "or any later version" clause. So that means I can add GPLv3+ code to
> it. However, can I add AGPLv3+ code to it? GNU says AGPLv3+ and GPLv2
> are incompatible, but are GPLv2+ and AGPLv3+ compatible?
>
> [1]: https://www.gnu.org/licenses/license-list#AGPL
>
ALL code under GPLv3 or able to be compatible with GPLv3 is compatible
with AGPLv3 because the GPLv3 has an explicit clause that says the code
can be used in an AGPLv3 project. But that's a one-directional
compatibility, so it requires that the overall combination be under AGPLv3.
In short, GPLv2+ and AGPLv3 (with or without the +) *are* compatible,
but the resulting combo will be AGPL overall.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2017-08-29 23:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 9:53 Adding [A]GPLv3+ code to Quake-based code base Lyberta
2017-08-29 16:12 ` Aaron Wolf
2017-08-29 21:58 ` Lyberta
2017-08-29 22:18 ` Isaac David
2017-08-29 23:06 ` Aaron Wolf [this message]
2017-08-29 23:30 ` Isaac David
2017-08-29 23:43 ` Aaron Wolf
2017-08-30 0:51 ` Isaac David
2017-08-30 1:43 ` Aaron Wolf
2017-08-30 3:07 ` Isaac David
2017-08-30 3:19 ` Isaac David
2017-08-30 9:15 ` Lyberta
2017-08-30 16:19 ` Aaron Wolf
2017-08-31 1:54 ` Mike Gerwitz
2017-08-31 4:48 ` Aaron Wolf
2017-08-31 5:10 ` Mike Gerwitz
2017-08-31 5:23 ` Aaron Wolf
2017-08-31 19:43 ` John Sullivan
2017-08-31 19:49 ` Aaron Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=736b7bc7-c823-cc48-f9be-717cac9b9526@riseup.net \
--to=wolftune@riseup.net \
--cc=libreplanet-discuss@libreplanet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).