All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] JSON license is non-free - how are we affected?
Date: Tue, 22 May 2012 17:58:13 +0200	[thread overview]
Message-ID: <4FBBB795.6080308@redhat.com> (raw)
In-Reply-To: <4FBBB5ED.1080408@redhat.com>

Il 22/05/2012 17:51, Eric Blake ha scritto:
> Is the JSON license only applicable to code downloaded from json.org,
> but not to the actual JSON language specification?

Yes, of course.  I think not even Oracle disagrees.

> If so, does that
> mean that a clean-room implementation of JSON (the language
> specification) can be written with different license than JSON (the
> license), and that such alternate code could then be linked into qemu?

That is what we did, in fact.

Paolo

  reply	other threads:[~2012-05-22 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 15:51 [Qemu-devel] JSON license is non-free - how are we affected? Eric Blake
2012-05-22 15:58 ` Paolo Bonzini [this message]
2012-05-22 16:56   ` Eric Blake
2012-05-22 17:05 ` 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=4FBBB795.6080308@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=eblake@redhat.com \
    --cc=libvir-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.