WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] License problems

To: Bastian Blank <bastian@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] License problems
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Sat, 30 Apr 2011 15:56:28 +0100
Cc: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Delivery-date: Sat, 30 Apr 2011 07:57:17 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:cc:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=GaNsrk6Jd/bcr+7FhrkCoM1ydzBKDPb2779DZ6Fnmww=; b=Tgw721+/tSsbG9qkc3eMIWYTEjPUIbb0vVlwAYvGjrceCvW4mOG4Iu1XPN2Uu/FreK pmktclCT3usDKCmhX9laTRr8p8CRgsZE8xdsjSxF8eHKwUAK95WME6NCJqLKnwvLgj5L 7tJ03yEDUNA4U6qx5bJ7XzFvt2VbMjWADLqtQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=E37aTFuDpF/NB13ItBRPJl3OyZE+zgH+9DRgxRTtwt6Mdi3GsOBSLUoxt8DGHpF5ga dF72QS6I94h/uEwH9r0LdPdeBIHmnUIwED1mjG8Xo6eMnUHTEZUIK+1xJw76fSnnDWz4 zR0FxjWVhMKvIc5B7ySmG4p18Kr74hSyTZZao=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110430135422.GA4412@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcwHRsiCj+0mT5C5mE6m/FVnHr1hHA==
Thread-topic: [Xen-devel] License problems
User-agent: Microsoft-Entourage/12.29.0.110113
On 30/04/2011 14:54, "Bastian Blank" <bastian@xxxxxxxxxxxx> 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



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel