qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Eric Blake <eblake@redhat.com>,
	Luiz Capitulino <lcapitul@redhat.com>,
	Daniel Berrange <berrange@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Andrea Bolognani <abologna@redhat.com>
Subject: License advice for Async QMP
Date: Tue, 13 Jul 2021 14:26:28 -0400	[thread overview]
Message-ID: <CAFn=p-Y_j0fQJCGHrwryk9=7qjPPU6VHYiOSqiAuz==Mn2s4jw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]

Hi,

I'm deep into writing a new Async QMP library for QEMU, one that I intend
to ship outside of our castle walls and host on PyPI.

I need to choose a license for it. I slapped GPLv2 on it in keeping with
the license on the original library by Luiz Capitulino (And it is generally
my preference), but I was debating loosening the license to MIT so that it
plays nicer with Apache-licensed projects. ...Maybe.

I don't know if that's really necessary, though, and I do generally prefer
a "copyleft" to "permissive" these days.

My current understanding:

1. Apache-licensed projects probably cannot vendor GPL code of any kind
(v2, v3, LGPL)
2. Apache-licensed projects can *probably* import GPL'd Python code (v2,
v3, LGPL) at runtime without creating a "derivative work", but it isn't a
settled matter, legally.
3. LGPL has little or no effect on a Python library, because you do not
link against Python as such to produce a combined work -- The PIP installer
generally re-acquires the original distribution and uses that at runtime
instead, which avoids legal hassle from bundling GPL code.
4. I would *probably* need a permissive license only if I wanted to allow
the vendoring of this Python code by non-GPL projects.

Does that sound about right?

[-- Attachment #2: Type: text/html, Size: 1516 bytes --]

             reply	other threads:[~2021-07-13 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 18:26 John Snow [this message]
2021-07-13 18:39 ` License advice for Async QMP Daniel P. Berrangé
2021-07-14 14:35 ` Markus Armbruster
2021-07-14 14:40   ` Daniel P. Berrangé

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFn=p-Y_j0fQJCGHrwryk9=7qjPPU6VHYiOSqiAuz==Mn2s4jw@mail.gmail.com' \
    --to=jsnow@redhat.com \
    --cc=abologna@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=lcapitul@redhat.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).