caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Hendrik Boom <hendrik@topoi.pooq.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlbuild on Windows and bash vs. cmd
Date: Tue, 11 Oct 2016 09:27:28 -0400	[thread overview]
Message-ID: <20161011132728.GA29129@topoi.pooq.com> (raw)
In-Reply-To: <CACLX4jRNb-w7Gupfx5D_X69W2daa7UUmxZ2ofwS8vDpbCdEcKA@mail.gmail.com>

On Tue, Oct 11, 2016 at 09:13:01AM -0400, Yaron Minsky wrote:
> We have a CLA from all external contributors, so re-licensing under a
> more liberal license should be easy, except insofar as we need to do
> some due dilligence on whatever new license we pick. Presumably, the
> open source lawyer who advised us to pick Apache 2 had some reason for
> it, which we need to think about it.

Doesn't the current Apache license have a clause allowing you to 
relicence it with some variety of GPL? 

-- hendrik

> 
> (By the way: see? CLAs aren't all bad...)
> 
> We'll look into it.
> 
> y
> 
> On Tue, Oct 11, 2016 at 9:06 AM, Anil Madhavapeddy <anil@recoil.org> wrote:
> > The standard MirageOS license for our libraries is ISC, which is short and simple (and the standard license used for new code in OpenBSD):
> >
> > https://github.com/mirage/mirage/blob/master/LICENSE.md
> >
> > regards,
> > Anil
> >
> >> On 11 Oct 2016, at 14:00, Ivan Gotovchits <ivg@ieee.org> wrote:
> >>
> >> Hi Yaron,
> >>
> >> Given that most of the Janestreet codebase is developed in-house, it might be not that hard to relicense it. This is especially true for `shexp` that currently
> >> has only one contributor. I would suggest switching to ISC or MIT (aka X11, aka Expat) licenses. Probably the former should be preferred, as it is shorter and cleaner.
> >> The full list of licenses compatible with GPL is here [1].
> >>
> >> Regards,
> >> Ivan
> >>
> >> [1]: https://www.gnu.org/licenses/license-list.en.html
> >>
> >> On Tue, Oct 11, 2016 at 8:36 AM, Yaron Minsky <yminsky@janestreet.com> wrote:
> >> You have got to be kidding me.
> >>
> >> Maybe we can dual license? It would be lovely to avoid the rewrite.
> >> What license would be adequate? Maybe we can license everything under
> >> LGPLv2+exception and Apache?
> >>
> >> I hate licenses.
> >>
> >> y
> >>
> >> On Tue, Oct 11, 2016 at 7:49 AM, Soegtrop, Michael
> >> <michael.soegtrop@intel.com> wrote:
> >> > Dear Yaron,
> >> >
> >> >
> >> >
> >> >> I very much hope the licensing isn't an issue. We purposely picked a very
> >> >> liberal license to make this kind of thing as easy as possible. Do tell us
> >> >> if you find an issue there.
> >> >
> >> >
> >> >
> >> > it is hard to believe, but the licensing is an issue. According to this
> >> > reference from Apache:
> >> >
> >> >
> >> >
> >> > https://www.apache.org/licenses/GPL-compatibility.html
> >> >
> >> >
> >> >
> >> > citation:
> >> >
> >> >
> >> >
> >> > “Despite our best efforts, the FSF has never considered the Apache License
> >> > to be compatible with GPL version 2, citing the patent termination and
> >> > indemnification provisions as restrictions not present in the older GPL
> >> > license.”
> >> >
> >> >
> >> >
> >> > the apache license you use is not compatible with GPL2. Since the OCaml
> >> > library is LGPL 2.1, it cannot include Apache licensed code. The patent
> >> > issue mentioned above has nothing to do with the difference between GPL and
> >> > LGPL, so my guess would be that this also applies to LGPL 2.X.
> >> >
> >> >
> >> >
> >> > Please note that the above reference states that Apache is compatible with
> >> > GPL 3, but I guess you can write a PhD thesis in law and/or computer science
> >> > about the topic if it is better to have GPL 2.x+ or GPL 3+Apache.
> >> >
> >> >
> >> >
> >> > If you think it is worthwhile, I can ask one of our open source lawyers for
> >> > advice, but I think the above statement from Apache is fairly clear.
> >> >
> >> >
> >> >
> >> > So as it looks, I have to rewrite from scratch what I need - sigh
> >> >
> >> >
> >> >
> >> > Best regards,
> >> >
> >> >
> >> >
> >> > Michael
> >> >
> >> > Intel Deutschland GmbH
> >> > Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> >> > Tel: +49 89 99 8853-0, www.intel.de
> >> > Managing Directors: Christin Eisenschmid, Christian Lamprechter
> >> > Chairperson of the Supervisory Board: Nicole Lau
> >> > Registered Office: Munich
> >> > Commercial Register: Amtsgericht Muenchen HRB 186928
> >>
> >> --
> >> Caml-list mailing list.  Subscription management and archives:
> >> https://sympa.inria.fr/sympa/arc/caml-list
> >> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> >> Bug reports: http://caml.inria.fr/bin/caml-bugs
> >>
> >
> 
> -- 
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs

  reply	other threads:[~2016-10-11 13:27 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 [this message]
2016-10-11 13:53                     ` Soegtrop, Michael
2016-10-11 15:48                       ` Adrien Nader
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=20161011132728.GA29129@topoi.pooq.com \
    --to=hendrik@topoi.pooq.com \
    --cc=caml-list@inria.fr \
    /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).