xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Wei Liu" <wei.liu2@citrix.com>, "Olaf Hering" <olaf@aepfle.de>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Keir Fraser" <keir@xen.org>,
	"Anil Madhavapeddy" <anil@recoil.org>,
	"George Dunlap" <George.Dunlap@eu.citrix.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Matthew Daley" <mattjd@gmail.com>, "Tim Deegan" <tim@xen.org>,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	"Roger Pau Monne" <roger.pau@entel.upc.edu>,
	"Jason Andryuk" <andryuk@aero.org>,
	"Jan Beulich" <JBeulich@suse.com>,
	xen-devel@lists.xenproject.org,
	"Daniel De Graaf" <dgdegra@tycho.nsa.gov>
Subject: Re: [PATCH for 4.7] libxenvchan: Change license of header from Lesser GPL v2.1 to BSD
Date: Fri, 10 Jun 2016 11:33:02 +0100	[thread overview]
Message-ID: <1465554782.20050.101.camel@hellion.org.uk> (raw)
In-Reply-To: <22361.36527.731461.736865@mariner.uk.xensource.com>

On Thu, 2016-06-09 at 16:43 +0100, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("[PATCH for 4.7] libxenvchan: Change
> license of header from Lesser GPL v2.1 to BSD"):
> > 
> > As the xen/COPYING file says:
> > "A few files are licensed under both GPL and a weaker BSD-style
> > license. This includes all files within the subdirectory
> > include/public, as described in include/public/COPYING. All such
> > files
> > include the non-GPL license text as a source-code comment. Although
> > the license text refers generically to "the software", the non-GPL
> > license applies *only* to those source files that explicitly
> > include
> > the non-GPL license text."
> I personally think this patch is a good idea.

To change xen/include/public/io/libxenvchan.h only or both that
and tools/libvchan/libxenvchan.h?

Historically the view of the Xen Project was the hypercall and PV ring
A[BP]Is should be BSD so that proprietary OSes could be ported to Xen
or PV drivers could be written for proprietary OSes etc.

But the view for toolstack libraries (libxenctrl, guest etc) was
traditionally that the project wanted them to remain copyleft. IIRC
originally one or both of libxenctrl and libxenguest were full-GPL but
we decided that was too far and went through a relicensing excercise to
make it LGPL, which allows for proprietary toolstack applications to be
built on top of the foundational libraries while still ensuring that
improvements to those libraries are contributed back.

So, I guess I don't really undertstand the case for / desire to
relicense tools/libvchan/libxenvchan.h, especially given that the other
tools/libvchan/*.[ch] files don't appear to be being relicensed in [0].

OTOH I only touched this file while at Citrix so I don't have any
actual say given Ian J's gotten sign off from Citrix.

Ian.

[0] http://lists.xen.org/archives/html/xen-devel/2016-06/msg01257.html

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-06-10 10:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 21:36 libxenvchan license (lGPLv2.1) and xen/include/public/COPYING license? Konrad Rzeszutek Wilk
2016-06-07 13:36 ` Konrad Rzeszutek Wilk
2016-06-07 15:54   ` Ian Jackson
2016-06-07 20:47     ` Marek Marczykowski-Górecki
2016-06-09 14:21       ` [PATCH for 4.7] libxenvchan: Change license of header from Lesser GPL v2.1 to BSD Konrad Rzeszutek Wilk
2016-06-09 14:30         ` Wei Liu
2016-06-09 15:10           ` Konrad Rzeszutek Wilk
2016-06-09 15:12           ` Ian Jackson
2016-06-09 15:16         ` Daniel De Graaf
2016-06-09 15:23           ` Marek Marczykowski-Górecki
2016-06-09 16:34             ` Jason P Andryuk
2016-06-09 16:37               ` Anil Madhavapeddy
2016-06-09 15:27         ` Olaf Hering
2016-06-09 16:36           ` Wei Liu
2016-06-09 15:35         ` George Dunlap
2016-06-09 15:37         ` Roger Pau Monné
2016-06-09 15:43         ` Ian Jackson
2016-06-10 10:33           ` Ian Campbell [this message]
2016-06-10 13:07             ` Ian Jackson
2016-06-10 13:31               ` Konrad Rzeszutek Wilk
2016-06-10 14:58                 ` Wei Liu
2016-06-13  9:28                   ` [PATCH v2 hopefully " Konrad Rzeszutek Wilk
2016-06-13 10:28                     ` Wei Liu
2016-06-10 15:00                 ` [PATCH " Ian Campbell
2016-06-09 15:44         ` Andrew Cooper
2016-06-09 16:19         ` Ian Jackson
2016-06-10 13:08           ` Ian Jackson
2016-06-09 16:45         ` Olaf Hering
2016-06-09 16:57           ` Wei Liu
2016-06-09 17:00             ` Olaf Hering
2016-06-10  7:04         ` Jan Beulich
2016-06-10 10:24         ` Matthew Daley

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=1465554782.20050.101.camel@hellion.org.uk \
    --to=ijc@hellion.org.uk \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=andryuk@aero.org \
    --cc=anil@recoil.org \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=mattjd@gmail.com \
    --cc=olaf@aepfle.de \
    --cc=roger.pau@entel.upc.edu \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).