From: Keir Fraser <keir.xen@gmail.com>
To: Bastian Blank <bastian@waldi.eu.org>, xen-devel@lists.xensource.com
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: License problems
Date: Sat, 30 Apr 2011 15:56:28 +0100 [thread overview]
Message-ID: <C9E1E1AC.17014%keir.xen@gmail.com> (raw)
In-Reply-To: <20110430135422.GA4412@wavehammer.waldi.eu.org>
On 30/04/2011 14:54, "Bastian Blank" <bastian@waldi.eu.org> wrote:
> Hi folks
>
> I did some license review of Xen. I found some problems. At least one
> part is undistributable as it stands.
>
> mini-os
> =======
> mini-os consists of parts with a MIT-style license, parts with GPL v2
> and parts with a 4-clause BSD:
> | extras/mini-os/include/lib.h: BSD (4 clause)
> | extras/mini-os/include/lib.h: BSD (4 clause)
> | extras/mini-os/lib/printf.c: BSD (4 clause)
> | extras/mini-os/lib/math.c: BSD (4 clause)
>
> The 4-clause BSD license is considered incompatible with the GPL[1].
Samuel already replied regarding these, and he is a maintainer of mini-os so
I'll leave it to him. My opinion is that the files should preferably be
updated if that allows us to license under modified BSD license. The
modified license is widely agreed to be GPL compatible, whereas the old
obnoxious advertising clause is definitely not.
> public headers
> ==============
> All the public headers in xen/include/public are supposed to be licensed
> under a MIT-style license, however some files lists other licenses.
>
> | xen/include/public/arch-ia64/debug_op.h: GPL (v2 or later) (with incorrect
> FSF address)
> | xen/include/public/arch-ia64/hvm/memmap.h: GPL (v2 or later) (with incorrect
> FSF address)
> | xen/include/public/arch-ia64/hvm/save.h: GPL (v2 or later) (with incorrect
> FSF address)
> | xen/include/public/arch-ia64/sioemu.h: GPL (v2 or later) (with incorrect FSF
> address)
> | xen/include/public/mem_event.h: GPL (v2 or later) (with incorrect FSF
> address)
> | xen/include/public/xsm/flask_op.h: *No copyright* GPL (v2,)
> | xen/include/public/xsm/flask_op.h: *No copyright* GPL (v2,)
The file include/public/COPYING *very clearly* states that all files in that
directory are licensed under a most permissive MIT-style license. The GPL
stanzas just confuse matters, are obviously unintentional, and I will delete
them. I'll add the MIT license text where it's missing, while I'm at it.
-- Keir
> Bastian
>
> [1]:
> http://en.wikipedia.org/wiki/BSD_licenses#4-clause_license_.28original_.22BSD_
> License.22.29
next prev parent reply other threads:[~2011-04-30 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 13:54 License problems Bastian Blank
2011-04-30 14:12 ` Samuel Thibault
2011-04-30 14:56 ` Keir Fraser [this message]
2011-04-30 15:33 ` [PATCH] mini-os: Fix printf.c licence Samuel Thibault
2011-04-30 16:10 ` [PATCH] mini-os: lib/math.c: import FreeBSD 8 functions Samuel Thibault
2011-04-30 19:31 ` Keir Fraser
2011-04-30 22:57 ` Samuel Thibault
2011-04-30 16:42 ` [PATCH] mini-os: fix lib.h licence Samuel Thibault
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=C9E1E1AC.17014%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=bastian@waldi.eu.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xensource.com \
/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).