qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
	"Cédric Le Goater" <clg@kaod.org>,
	gwshan@linux.vnet.ibm.com
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>, QEMU <qemu-devel@nongnu.org>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	shan.gavin@gmail.com
Subject: Re: [Qemu-devel] Clearing slirp/ license
Date: Tue, 12 Mar 2019 17:03:36 +1100	[thread overview]
Message-ID: <cc62e1fd-c564-e1b7-d10c-30665b481352@ozlabs.ru> (raw)
In-Reply-To: <CAJ+F1C+hFfsa5gcSdttTP5J+uyDvNdYJWrm9OJM26+Zc1ZQkew@mail.gmail.com>

Gavig left the company sometime ago, cc:ing his gmail.


On 12/03/2019 05:01, Marc-André Lureau wrote:
> Hi Cédric, Gavin,
> 
> On Mon, Mar 11, 2019 at 4:23 PM Cédric Le Goater <clg@kaod.org> wrote:
>>
>> On 2/13/19 12:03 PM, Marc-André Lureau wrote:
>>> Hi,
>>>
>>> As we are trying to move slirp/ in a standalone project, which
>>> eventually could be installed as a shared library, we need to clear
>>> the license.
>>>
>>> slirp is supposed to be 3-Clause BSD license (according to
>>> https://git.qemu.org/?p=qemu.git;a=commit;h=2f5f89963186d42a7ded253bc6cf5b32abb45cec)
>>> but it seems to be effectively a 2-Clause BSD (the third clause is not
>>> in COPYRIGHT)
>>>
>>> However, there are two units that are GPL-2:
>>>
>>> - dhcpv6.c, dhcpv6.h:
>>>   The code was contributed by Thomas Huth <thuth@redhat.com>
>>>
>>> $ git shortlog -nes slirp/dhcpv6.{c,h}
>>>      6  Marc-André Lureau <marcandre.lureau@redhat.com>
>>>      1  Philippe Mathieu-Daudé <f4bug@amsat.org>
>>>      1  Thomas Huth <thuth@redhat.com>
>>>      1  Yuval Shaia <yuval.shaia@oracle.com>
>>>
>>> - ncsi.c, ncsi-pkt.h:
>>>   The code was contributed by Cédric Le Goater <clg@kaod.org>
>>>
>>> $ git shortlog -nes slirp/ncsi.c slirp/ncsi-pkt.h
>>>      5  Marc-André Lureau <marcandre.lureau@redhat.com>
>>>      4  Cédric Le Goater <clg@kaod.org>
>>>
>>> Could you reply that you have no objection in relicensing those files
>>> are 3-Clause BSD?
>>
>> Fine for me. You can change the license of slirp/ncsi.c and
>> slirp/ncsi-pkt.hto a 3-Clause BSD.
> 
> I noticed that ncsi-pkt.h has "Copyright Gavin Shan, IBM Corporation 2016"
> 
> I suppose Gavin should also give his agreement to relicense the file.
> 
> 
> Gavin, could you reply that you have no objection in relicensing
> ncsi-pkt.h as 3-Clause BSD?
> 
> 
> Thanks
> 
>>
>> Thanks,
>>
>> C.
>>
>>> After "[Qemu-devel] [PATCH 0/7] slirp: make it a standalone project",
>>> the vmstate subset that I adapted would also need to be relicensed.
>>> There are more contributors here, I am not sure how it should be
>>> handled. Any idea?
>>>
>>> thanks
>>>
>>
> 
> 

-- 
Alexey

  reply	other threads:[~2019-03-12  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 11:03 [Qemu-devel] Clearing slirp/ license Marc-André Lureau
2019-02-13 11:30 ` Thomas Huth
2019-03-11 15:23 ` Cédric Le Goater
2019-03-11 18:01   ` Marc-André Lureau
2019-03-12  6:03     ` Alexey Kardashevskiy [this message]
2019-03-11 17:45 ` Marc-André Lureau

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=cc62e1fd-c564-e1b7-d10c-30665b481352@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=clg@kaod.org \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=shan.gavin@gmail.com \
    --cc=thuth@redhat.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).