From: Theodore Ts'o <tytso@mit.edu>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: demerphq <demerphq@gmail.com>, Git <git@vger.kernel.org>,
Jeff King <peff@peff.net>
Subject: Re: Will OpenSSL's license change impact us?
Date: Sat, 25 Mar 2017 17:11:35 -0400 [thread overview]
Message-ID: <20170325211135.62sa76hlvyiexvje@thunk.org> (raw)
In-Reply-To: <CACBZZX5bK=emjaQ80J7QuTHXHm=nT3G80zq4xogMqC7Eq9Bs+g@mail.gmail.com>
On Sat, Mar 25, 2017 at 06:51:21PM +0100, Ævar Arnfjörð Bjarmason wrote:
> In GPLv3 projects only, not GPLv2 projects. The paragraphs you're
> quoting all explicitly mention v3 only, so statements like
> "incompatible in one direction" only apply to Apache 2 && GPLv3, but
> don't at all apply to GPLv2, which is what we're using.
It's complicated.
It's fair enough to say that the FSF adopts a copyright maximalist
position, and by their interpretation, the two licenses are
incompatible, and it doesn't matter whether the two pieces of code are
linked staticaly, dynamically, or one calls the other over an RPC
call.
Not everyone agrees with their legal analysis. May I suggest that we
not play amateur lawyer on the mailing list, and try to settle this
here? Each distribution can make its own decision, which may be based
on its legal advice, the local laws and legal precedents in which they
operate, etc. And indeed, different distributions have already come
to different conclusions with respect to various license compatibility
issues. (Examples: dynamically linking GPL programs with OpenSSL
libraries under the old license, distributing ZFS modules for Linux,
etc.)
We don't expect lawyers to debug edge cases in a compiler's code
generation. Programmers shouldn't try to parse edge cases in the law,
or try to use a soldering iron, unless they have explicit training and
expertise to do so. :-)
- Ted
next prev parent reply other threads:[~2017-03-25 21:12 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
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 [this message]
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=20170325211135.62sa76hlvyiexvje@thunk.org \
--to=tytso@mit.edu \
--cc=avarab@gmail.com \
--cc=demerphq@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).