From: demerphq <demerphq@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Will OpenSSL's license change impact us?
Date: Sat, 25 Mar 2017 09:40:12 +0100 [thread overview]
Message-ID: <CANgJU+UCJ9qR-pi9w3+oYjEwDdhbtNX9Nv6brj31VXvt-k-3Lw@mail.gmail.com> (raw)
In-Reply-To: <CACBZZX6F47uC9jLxppgkUnwVpGV2jpzzP4kwTuqKgayCevomeA@mail.gmail.com>
On 25 March 2017 at 00:51, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
> They're changing their license[1] to Apache 2 which unlike the current
> fuzzy compatibility with the current license[2] is explicitly
> incompatible with GPLv2[3].
Are you sure there is an issue? From the Apache page on this:
Apache 2 software can therefore be included in GPLv3 projects, because
the GPLv3 license accepts our software into GPLv3 works. However,
GPLv3 software cannot be included in Apache projects. The licenses are
incompatible in one direction only, and it is a result of ASF's
licensing philosophy and the GPLv3 authors' interpretation of
copyright law.
Which seems to be the opposite of the concern you are expressing.
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
next prev parent reply other threads:[~2017-03-25 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 23:51 Will OpenSSL's license change impact us? Ævar Arnfjörð Bjarmason
2017-03-25 8:40 ` demerphq [this message]
2017-03-25 9:18 ` Ævar Arnfjörð Bjarmason
[not found] ` <CANgJU+UG1JGYomyQa1FgyN8Q6SkPeEtGKEJfNETrkbtGwrMn9g@mail.gmail.com>
2017-03-25 16:35 ` Ævar Arnfjörð Bjarmason
2017-03-25 16:57 ` demerphq
2017-03-25 17:51 ` Ævar Arnfjörð Bjarmason
2017-03-25 21:11 ` Theodore Ts'o
2017-03-25 21:50 ` Ævar Arnfjörð Bjarmason
2017-03-25 21:44 ` brian m. carlson
2017-03-25 21:52 ` Ævar Arnfjörð Bjarmason
2017-03-26 4:43 ` Jeff King
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=CANgJU+UCJ9qR-pi9w3+oYjEwDdhbtNX9Nv6brj31VXvt-k-3Lw@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.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.
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).