From: Anil Madhavapeddy <anil@recoil.org>
To: oliver <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Licenses - Confusion
Date: Wed, 22 May 2013 13:39:29 +0100 [thread overview]
Message-ID: <D8052089-B330-412F-932B-5E1772E7782E@recoil.org> (raw)
In-Reply-To: <20130522123427.GA1894@siouxsie>
On 22 May 2013, at 13:34, oliver <oliver@first.in-berlin.de> wrote:
>
> Regarding the third point: it would be a good idea to provide
> "ready to use" licenses, which include the exceptions, instead
> of lawyer-compatible (but not necessarily programmer-compatible)
> explanations with many if-then-else's.
>
The GPL, with all of its static linking verbiage, and OCaml are
not a good fit. All of the Mirage libraries now prefer the ISC
license where possible, and the LGPL+linking exception is considered
deprecated for new code. The last time I spoke to a lawyer about
the LGPL+exception (back in 2008 in Xensource), there were alarm
bells raised about the shoddy legal wording involved. A BSD-style
license is significantly simpler, as long as it doesn't include the
advertising clause.
Copyright (c) Year(s), Company or Person's Name <E-mail address>
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
best,
Anil
next prev parent reply other threads:[~2013-05-22 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 12:34 oliver
2013-05-22 12:39 ` Anil Madhavapeddy [this message]
2013-05-22 16:40 ` Marek Kubica
2013-05-22 13:02 ` Török Edwin
2013-05-22 17:19 ` Adrien Nader
2013-05-23 6:36 ` Stéphane Glondu
2013-05-23 8:41 ` Daniel Bünzli
2013-05-23 21:07 ` Marek Kubica
2013-05-23 21:36 ` Stéphane Glondu
2013-05-23 22:28 ` Daniel Bünzli
2013-05-23 21:39 ` Ernesto Posse
2013-05-23 21:45 ` Chet Murthy
2013-05-23 22:11 ` Stefano Zacchiroli
2013-05-23 22:52 ` oliver
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=D8052089-B330-412F-932B-5E1772E7782E@recoil.org \
--to=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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