Re: [Qemu-devel] Clearing slirp/ license

[Alexey Kardashevskiy]

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 <address@hidden> 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 <address@hidden>
>>>
>>> $ git shortlog -nes slirp/dhcpv6.{c,h}
>>>      6  Marc-André Lureau <address@hidden>
>>>      1  Philippe Mathieu-Daudé <address@hidden>
>>>      1  Thomas Huth <address@hidden>
>>>      1  Yuval Shaia <address@hidden>
>>>
>>> - ncsi.c, ncsi-pkt.h:
>>>   The code was contributed by Cédric Le Goater <address@hidden>
>>>
>>> $ git shortlog -nes slirp/ncsi.c slirp/ncsi-pkt.h
>>>      5  Marc-André Lureau <address@hidden>
>>>      4  Cédric Le Goater <address@hidden>
>>>
>>> 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