[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUnet-developers] a solution for integrated package definitions; g
Re: [GNUnet-developers] a solution for integrated package definitions; gnurl and the copyrights
Sat, 31 Dec 2016 23:46:56 +0100
Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
I do not see the copyright assignment apply to gnurl in any way, it
would not help anyway as (1) it is questionable that our changes to curl
are even copyrightable, and (2) the copyrights clearly are with the curl
devs, so we would not succeed at centralizing anyway. Finally, the
issues pEp/Taler has are primarily with strong copyleft code (*), and
curl/gnurl are weak copyleft. Hence, we also have no _need_ for this
for curl/gnurl anyway, as far as I can see.
(*) For example, Apple appstore forbids GPL, but AFAIK not LGPL. Hence
GNUnet being GPL is an issue for a pEp/GNUnet-to-iOS port. Also, Taler
Systems may want to make some code for merchants available under LGPL,
and libgnunetutil is currently GPL. curl's license has no impact here.
On 12/31/2016 11:40 PM, ng0 wrote:
> I have a question I forgot to ask during the meeting...
> Following the copyright assignment (I still have to get my
> printer working again), how will gnurl be treated? Are there any
> changes for gnurl I have to make? Can changes be made, or will it
> just be left as is?
Description: OpenPGP digital signature