From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
Luiz Capitulino <lcapitul@redhat.com>,
John Snow <jsnow@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
Andrea Bolognani <abologna@redhat.com>
Subject: Re: License advice for Async QMP
Date: Wed, 14 Jul 2021 15:40:53 +0100 [thread overview]
Message-ID: <YO73deXajBVajJw9@redhat.com> (raw)
In-Reply-To: <87eec1ezfe.fsf@dusky.pond.sub.org>
On Wed, Jul 14, 2021 at 04:35:17PM +0200, Markus Armbruster wrote:
> John Snow <jsnow@redhat.com> writes:
>
> > 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.
>
> In addition to what Daniel wrote: I'd recommend GPLv2+ over GPLv2.
Yep, that'd be my pref too generally.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2021-07-14 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 18:26 License advice for Async QMP John Snow
2021-07-13 18:39 ` Daniel P. Berrangé
2021-07-14 14:35 ` Markus Armbruster
2021-07-14 14:40 ` Daniel P. Berrangé [this message]
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=YO73deXajBVajJw9@redhat.com \
--to=berrange@redhat.com \
--cc=abologna@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@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).