From: Adrien Nader <adrien@notk.org>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>
Cc: Hendrik Boom <hendrik@topoi.pooq.com>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild on Windows and bash vs. cmd
Date: Tue, 11 Oct 2016 17:48:49 +0200 [thread overview]
Message-ID: <20161011154849.GA19632@notk.org> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CF8EF70@IRSMSX102.ger.corp.intel.com>
The central aspect for these incompatibilities is patents afaik.
GPLv2 forbids additional restrictions being put in place. The GPLv3 has
additional restrictions compared to the GPLv2 (at least because of the
patent clauses) and is therefore obviously incompatible.
The Apache and GPLv3 licenses have patent retaliation clauses which help
deter actors that aren't patent trolls from suing (basically, they say
that if you sue someone over the patents which this software could
relate to, then you lose the right to use the software). Patent trolls
have nothing to lose so they don't really care but they're a different
matter.
Overall the patent retaliation clause is good and the Apache software
helps because it is about /both/ copyrights and patents. Only handling
the copyright aspects nowadays only works if you live in Care Bear's
world.
License compatibility is a fairly complex topic which brings an extra
set of constraints. Dual- or even triple- licensing is a good solution.
NB: this comes with the usual warnings but factored at the end rather
than being written in each and every sentence: IANAL, I'm not an expert,
add "as far as I know" in every sentence you want to.
--
Adrien Nader
next prev parent reply other threads:[~2016-10-11 15:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 13:38 Soegtrop, Michael
2016-10-06 13:45 ` Kakadu
2016-10-06 14:01 ` Soegtrop, Michael
2016-10-06 13:55 ` Daniel Bünzli
2016-10-06 14:15 ` Soegtrop, Michael
2016-10-06 14:45 ` Gabriel Scherer
2016-10-06 16:16 ` Soegtrop, Michael
2016-10-06 17:45 ` Jeremie Dimino
2016-10-06 18:56 ` Gerd Stolpmann
2016-10-07 6:58 ` Soegtrop, Michael
2016-10-07 16:19 ` Yaron Minsky
2016-10-11 11:49 ` Soegtrop, Michael
2016-10-11 12:36 ` Yaron Minsky
2016-10-11 13:00 ` Ivan Gotovchits
2016-10-11 13:06 ` Anil Madhavapeddy
2016-10-11 13:13 ` Yaron Minsky
2016-10-11 13:27 ` Hendrik Boom
2016-10-11 13:53 ` Soegtrop, Michael
2016-10-11 15:48 ` Adrien Nader [this message]
2016-10-11 13:46 ` Soegtrop, Michael
2016-10-14 12:19 ` Manfred Lotz
2016-10-17 8:08 ` Soegtrop, Michael
2016-10-17 9:22 ` Manfred Lotz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161011154849.GA19632@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=hendrik@topoi.pooq.com \
--cc=michael.soegtrop@intel.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.
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 NNTP newsgroup(s).