LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Isaac David <isacdaavid@isacdaavid.info>
To: Aaron Wolf <wolftune@riseup.net>
Cc: libreplanet-discuss@libreplanet.org
Subject: Re: Adding [A]GPLv3+ code to Quake-based code base
Date: Tue, 29 Aug 2017 19:51:04 -0500	[thread overview]
Message-ID: <1504054264.14912.1@plebeian.isacdaavid.info> (raw)
In-Reply-To: <9e05b304-53ad-2fb7-02ef-9947632215ee@riseup.net>

Aaron Wolf wrote :
> I can write a new copyleft license today that is explicitly 
> one-directionally compatible with the AGPLv3, and no change to AGPLv3 
> is needed for that to work.

the only scenarios i can conjure in which this would be possible are
trivial ones: one where your copyleft license is unequivocally (for
the courts) a one-to-one semantic copy of the AGPLv3, or what is more
likely, one where it's in effect a dual license (mutually exclusive
licenses, one of which is the AGPLv3). that's what CC-BY-SA-4.0 and
copyleft-next do.

this is because the AGPLv3, being a copyleft license itself, demands
that derived works carry exactly the same terms. no more, no less:

 > 5. Conveying Modified Source Versions.
 > [...] You must license the entire work, as a whole, under this
 > License [...]
 > [...] This License gives no permission to license the work in any
 > other way [...]

there's no other way a licensee combining one work under your
hypothetical copyleft license and another under the AGPLv3 can comply
with the AGPLv3. it would mean subjecting the AGPLv3 part to your
licence terms in addition to the AGPLv3. so until the second copyleft
license corresponds you, it wouldn't matter if your license were
explicitly accepting of it.

that said, it would be great to add an open-ended permission to
combine with future versions of the AGPL (or GPL), if you ever were to
write a new copyleft license. that way the authors of the AGPL could
decide whether to open the gates of compatibility, in which
directions, under what conditions, etc; allowing the existing body of
AGPLv3+ stuff to become retroactively compatible with all works under
your license in a single move.
-- 
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943



_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  reply	other threads:[~2017-08-30  0:52 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
2017-08-29 23:30       ` Isaac David
2017-08-29 23:43         ` Aaron Wolf
2017-08-30  0:51           ` Isaac David [this message]
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=1504054264.14912.1@plebeian.isacdaavid.info \
    --to=isacdaavid@isacdaavid.info \
    --cc=libreplanet-discuss@libreplanet.org \
    --cc=wolftune@riseup.net \
    /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).