From: Pratyush Yadav <me@yadavpratyush.com>
To: Han-Wen Nienhuys <hanwen@google.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git <git@vger.kernel.org>,
Christian Couder <christian.couder@gmail.com>
Subject: Re: Reftable format implementation in C and Go
Date: Wed, 20 Nov 2019 20:04:28 +0530 [thread overview]
Message-ID: <20191120143428.u3rmuufhphbntgm5@yadavpratyush.com> (raw)
In-Reply-To: <CAFQ2z_PBPPQuJYA-mvKz532GikBXureOi1ePr7YdBRJbxOJCeA@mail.gmail.com>
On 20/11/19 06:22AM, Han-Wen Nienhuys wrote:
> On Wed, Nov 20, 2019 at 6:19 AM Han-Wen Nienhuys <hanwen@google.com> wrote:
> >> Would you mind, however, to relicense the code under a license compatible
> >> with GPLv2? Currently your code is under the Apache License (which I heard
> >> somewhere is probably incompatible with the GPLv2 used by the Git
> >> project):
> >> https://github.com/google/reftable/blob/6cd8dbb4106d18627f442d3148de71d7db43d4b6/c/api.h#L1-L13
> >>
>
> according to our open source lawyers, Apache is actually compatible
> with GPLv2, but I think we could dual-license the code.
The GNU website [0] says:
Apache License, Version 2.0
This is a free software license, compatible with version 3 of the GNU GPL.
Please note that this license is not compatible with GPL version 2,
because it has some requirements that are not in that GPL version.
These include certain patent termination and indemnification
provisions. The patent termination provision is a good thing, which
is why we recommend the Apache 2.0 license for substantial programs
over other lax permissive licenses.
[0] https://www.gnu.org/licenses/license-list.html#apache2
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2019-11-20 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFQ2z_Pe1Pdjy22VmCMzf4Gvx3wte1eQRn_PjSisJbr9_y7bbg@mail.gmail.com>
2019-11-20 11:48 ` Reftable format implementation in C and Go Johannes Schindelin
[not found] ` <CAFQ2z_PiuFe=ZKNaZG3=2AqjcNRb-k5-CYSXeN6MQ0r5sv4S=g@mail.gmail.com>
2019-11-20 14:22 ` Han-Wen Nienhuys
2019-11-20 14:34 ` Pratyush Yadav [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191120143428.u3rmuufhphbntgm5@yadavpratyush.com \
--to=me@yadavpratyush.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).