qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] LICENSE: clarify
Date: Thu, 1 Aug 2013 04:21:44 -0400 (EDT)	[thread overview]
Message-ID: <1456316945.8007085.1375345304796.JavaMail.root@redhat.com> (raw)
In-Reply-To: <CA+aC4ku=S=i81p_fc8iGNwiBgwNa-M3Z2gz5y6f=-RCxobOJ8w@mail.gmail.com>


> On Wed, Jul 31, 2013 at 1:19 AM, Paolo Bonzini <pbonzini@redhat.com> 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).
> 
> I am okay *discouraging* GPLv2 only contributions but if there's
> compelling code that cannot be relicensed, I would object strongly to
> rejecting it purely because it wasn't GPLv2+.

Yes, that's why I included "as of".  We can certainly broaden the
set of GPLv2-only features, but it would require discussions and another
patch to LICENSE.  If you believe "as of July 2013" is not enough, I can
send v2.

> > 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.
> 
> I think it's better at this point to just put QEMU team.  Fabrice is
> no longer associated with the project.

It still mentions the trademark, and one of the last times he was
contacted was exactly to enforce the BSDness of TCG, so I left it in.
As the most active committer, you can certainly submit a follow-up
patch to remove it; I didn't really feel qualified to do that.

Paolo

  reply	other threads:[~2013-08-01  8:35 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 [this message]
2014-11-20 19:06   ` Christopher Covington
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=1456316945.8007085.1375345304796.JavaMail.root@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --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).