From: Eric Blake <eblake@redhat.com>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [QUESTION] What is the best license option for new files introduced in QEMU?
Date: Mon, 25 Nov 2019 15:27:17 -0600 [thread overview]
Message-ID: <5edee836-b97b-57fb-70fb-9b6b6bc44a52@redhat.com> (raw)
In-Reply-To: <CAL1e-=i-u5eR7Fk_Muobbe0-Viim0iPceHoEGtJWCq7L1o9teA@mail.gmail.com>
On 11/25/19 1:25 PM, Aleksandar Markovic wrote:
> Thomas pointed to me that I mixed up GPL and LGPL - which is true.
>
> Still, the question remains with these options:
>
> * GPL 2.0
Not good. It artificially limits who can reuse this code.
> * GPL 2.0 + wording "or later (at your option)"
Matches what qemu itself uses, so fine; but makes it harder to reuse the
code in a standalone library.
> * LGPL 2.1
Same problems as GPL2-only
> * LGPL 2.1 + wording "or later (at your option)"
Looser than qemu as a whole, has all the benefits of GPL2+ plus the
additional benefit of being able to copy the code into other LGPL
standalone libraries.
It's also acceptable to use even looser licenses, like BSD 2-clause, but
preferably only if that other license is already used by part of qemu
(we don't need to make our mix even worse than it already is).
>
> The context of my question is that I am reviewing a series that came
> with files with different license preambles (or without it at all), and I
> want to advice the submitters on the best option.
You may also want advice from lawyers, based on how you see your code
being reused outside of qemu. This list can offer advice, but it is
non-binding and may not best fit your needs.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-11-25 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 17:49 [QUESTION] What is the best license option for new files introduced in QEMU? Aleksandar Markovic
2019-11-25 19:25 ` Aleksandar Markovic
2019-11-25 21:27 ` Eric Blake [this message]
2019-11-25 23:59 ` Aleksandar Markovic
2019-11-26 7:05 ` Thomas Huth
2019-11-26 9:29 ` Markus Armbruster
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=5edee836-b97b-57fb-70fb-9b6b6bc44a52@redhat.com \
--to=eblake@redhat.com \
--cc=aleksandar.m.mail@gmail.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).