From: Rob Landley <rob@landley.net>
To: Stefan Weil <sw@weilnetz.de>
Cc: Erik de Castro Lopo <mle+tools@mega-nerd.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Licensing question
Date: Fri, 02 Aug 2013 11:59:24 -0500 [thread overview]
Message-ID: <1375462764.8422.3@driftwood> (raw)
In-Reply-To: <51F89E47.4000500@weilnetz.de> (from sw@weilnetz.de on Wed Jul 31 00:19:03 2013)
On 07/31/2013 12:19:03 AM, Stefan Weil wrote:
> Am 31.07.2013 03:50, schrieb Erik de Castro Lopo:
> > Hi all,
> >
> > I have a patch I would like to submit and I am currently running it
> past
> > my employer's legal department. The legal department has identified
> 10
> > different licenses in the Qemu codebase and has asked about the two
> files
> > I am modifying:
> >
> > linux-user/syscall.c
> > linux-user/syscall_defs.h
> >
> > For the first its easy as it is clearly marked as GPLv2+. The
> second is
> > unmarked. Is there some blanket statement somewhere that all files
> that
> > are not explicitly marked are under say GPLv2+?
> >
> > Cheers,
> > Erik
>
> No, there is no such statement.
>
> There is an agreement that files with GPL should be GPLv2+
> (not only GPLv2), but files may also use other free licenses.
>
> In file LICENSE, it is said that QEMU as a whole is released
> under the GNU General Public License.
Which, if you don't specify, could mean GPLv1.
> Some files are copied from Linux and therefore must use
> the Linux license (usually GPLv2).
>
> syscall_defs.h might be a copy from Linux (=> GPLv2).
> If not, the default rule from LICENSE could be applied (=> GPL).
Some directories, such as TCG, have their own LICENSE files. These are
generally BSD-style license which are donor-compatible (but not
receiver-compatible) with GPLv2 or later.
(If "you are obligated to include this license text verbatim, but it
does not actually apply to the file" is an acceptable definition of
"compatible", but that's a legal argument nobody's made in court yet so
I'm sure you're fine. Nor has anybody recently brought up whether "the
Software" you're obligated to include it in is just source versions or
requires the license text to be in the binary; Android does it to be
safe, most others don't bother.)
Rob
(Personally I look back at the days when my Commodore 64 came bundled
with a "Disk Bonus Pack" of public domain software mostly written by
Jim Butterfield, and going "why did we stop doing that again? Because
awaiting hot coffee lawsuits was worse than awaiting patent troll
lawsuits?")
prev parent reply other threads:[~2013-08-02 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 1:50 [Qemu-devel] Licensing question Erik de Castro Lopo
2013-07-31 5:19 ` Stefan Weil
2013-07-31 5:45 ` Erik de Castro Lopo
2013-07-31 6:20 ` Paolo Bonzini
2013-08-02 16:59 ` Rob Landley [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=1375462764.8422.3@driftwood \
--to=rob@landley.net \
--cc=mle+tools@mega-nerd.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.