From: Christopher Covington <cov@codeaurora.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] LICENSE: clarify
Date: Thu, 20 Nov 2014 14:06:09 -0500 [thread overview]
Message-ID: <546E3BA1.6000801@codeaurora.org> (raw)
In-Reply-To: <1375251592-2537-3-git-send-email-pbonzini@redhat.com>
Hi Paolo,
On 07/31/2013 02:19 AM, Paolo Bonzini wrote:
> 1) The GPL says that "if the Program does not specify a version number
> of this License, you may choose any version ever published by the Free
> Software Foundation". This is not true, QEMU includes parts that are
> v2-only.
>
> 2) Provide a default for files with no licensing information.
>
> 3) It is not just hardware emulation that is under BSD license.
>
> 4) Restrict GPLv2-only contributions to user mode emulation (due to
> code from Linux) and PCI passthrough (due to code from Neocleus).
>
> 5) The rules were initially set by Fabrice but are being amended by
> other people (already in commit ee12e1f, LICENSE: There is no libqemu.a
> anymore, 2011-11-15). Do not put words in his mouth.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> LICENSE | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/LICENSE b/LICENSE
> index acae9a3..2bd2e95 100644
> --- a/LICENSE
> +++ b/LICENSE
> @@ -1,16 +1,21 @@
> The following points clarify the QEMU license:
>
> -1) QEMU as a whole is released under the GNU General Public License
> +1) QEMU as a whole is released under the GNU General Public License,
> +version 2.
>
> 2) Parts of QEMU have specific licenses which are compatible with the
> -GNU General Public License. Hence each source file contains its own
> -licensing information.
> +GNU General Public License, version 2. Hence each source file contains
> +its own licensing information. Source files with no licensing information
> +are released under the GNU General Public License, version 2 or (at your
> +option) any later version.
>
> -Many hardware device emulation sources are released under the BSD license.
> +As of July 2013, contributions under version 2 of the GNU General Public
> +License (and no later version) are only accepted for the following files
> +or directories: bsd-user/, linux-user/, hw/misc/vfio.c, hw/xen/xen_pt*.
>
> 3) The Tiny Code Generator (TCG) is released under the BSD license
> (see license headers in files).
>
> 4) QEMU is a trademark of Fabrice Bellard.
>
> -Fabrice Bellard.
> +Fabrice Bellard and the QEMU team
http://wiki.qemu.org/License appears to be out of sync with these changes.
Thanks,
Chris
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-11-20 19:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 6:19 [Qemu-devel] [PATCH 0/2] Clarify licensing terms Paolo Bonzini
2013-07-31 6:19 ` [Qemu-devel] [PATCH 1/2] raw: add license header Paolo Bonzini
2013-07-31 7:52 ` Kevin Wolf
2013-07-31 8:01 ` Markus Armbruster
2013-08-02 7:01 ` Peter Lieven
2013-07-31 10:49 ` Stefan Hajnoczi
2013-07-31 12:24 ` Jeff Cody
2013-07-31 13:04 ` Luiz Capitulino
2013-08-01 8:13 ` Christoph Hellwig
2013-08-01 8:38 ` Paolo Bonzini
2013-08-15 13:16 ` Anthony Liguori
2013-07-31 6:19 ` [Qemu-devel] [PATCH 2/2] LICENSE: clarify Paolo Bonzini
2013-07-31 7:27 ` Erik de Castro Lopo
2013-07-31 7:40 ` Andreas Färber
2013-07-31 16:48 ` Stefan Weil
2013-07-31 16:58 ` Eric Blake
2013-08-01 8:29 ` Paolo Bonzini
2013-07-31 17:40 ` Anthony Liguori
2013-08-01 8:21 ` Paolo Bonzini
2014-11-20 19:06 ` Christopher Covington [this message]
2013-07-31 15:01 ` [Qemu-devel] [PATCH 0/2] Clarify licensing terms Artyom Tarasenko
2013-08-14 16:29 ` Anthony Liguori
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=546E3BA1.6000801@codeaurora.org \
--to=cov@codeaurora.org \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@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).