From: Sven <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: John Field <jfield@us.ibm.com>, caml-list@inria.fr
Subject: Re: [Caml-list] License Conditions for OCaml
Date: Fri, 30 Nov 2001 09:09:28 +0100 [thread overview]
Message-ID: <20011130090928.B14742@dpt-info.u-strasbg.fr> (raw)
In-Reply-To: <20011128192239.B9601@pauillac.inria.fr>; from xavier.leroy@inria.fr on Wed, Nov 28, 2001 at 07:22:39PM +0100
On Wed, Nov 28, 2001 at 07:22:39PM +0100, Xavier Leroy wrote:
> John,
>
> Thank you for your feedback -- it's very interesting to hear from an
> industrial user who got the opinions of competent lawyers.
>
> Let me just state again what we'd like to achieve concerning the
> licensing of the OCaml runtime and libraries:
>
> 1- Users can link with it, statically or dynamically, without any
> restrictions on the final program.
> 2- Users can modify the runtime or the libraries themselves, but then
> must make their modifications public under the same conditions as
> the original source.
> 3- The license should be standard, OSI-approved, and well known to the
> public that cares about these things.
>
> All three items are easy to justify: for 1, we don't want to bother
> anyone who uses OCaml; for 2, we'd like OCaml to remain open
> source, meaning that everyone should be able to benefit from the
> modifications on OCaml itself that someone did; and for 3, we're not
> competent for inventing yet another license and get it recognized as
> open source compliant.
Well, a 4th way would be to take the technical steps which would allow the
current licence to fullfill the 2 first requirements. Also i think it will be
very welcome for other purposes also ...
Also please consider all the implications before going ahead with it ...
> Now the problem is that apparently there is no existing license that
> matches these three criteria. The LGPL was chosen before we realized
> all its implications w.r.t. static linking. But popular licenses such
> as BSD or X don't meet criterion 2. Our current hope is that the LGPL
Well, it is the silly requirement that guarantee's criterion 2, under other
things.
I have to go now, maybe we ca nfollow up on this discution at a later time ?
Friendly,
Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-11-30 8:11 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-30 1:18 Don Syme
2001-11-30 1:59 ` Julian Assange
2001-12-01 3:23 ` Richard Stallman
2001-12-04 18:53 ` Sven
2001-12-06 2:46 ` Richard Stallman
2001-11-27 19:10 ` John Field
2001-11-28 18:22 ` Xavier Leroy
2001-11-28 19:14 ` Ronald Kuehn
2001-11-29 0:38 ` Julian Assange
2001-11-29 8:32 ` Xavier Leroy
[not found] ` <20011129105008.DEBFD25A1B@suburbia.net>
2001-11-29 12:50 ` Xavier Leroy
2001-11-29 13:42 ` Jérôme Marant
2001-11-29 13:11 ` Greg Bacon
2001-11-29 23:01 ` Julian Assange
2001-11-29 23:13 ` Greg Bacon
2001-11-29 8:31 ` Florian Hars
2001-11-29 8:43 ` Daniel de Rauglaudre
2001-11-29 9:04 ` Jérôme Marant
2001-11-29 9:15 ` Xavier Leroy
2001-11-29 9:29 ` Jérôme Marant
2001-11-29 9:25 ` Daniel de Rauglaudre
2001-11-29 9:35 ` Jérôme Marant
2001-11-29 8:53 ` Xavier Leroy
2001-11-30 8:09 ` Sven [this message]
2001-12-07 0:09 ` YAMAGATA yoriyuki
2001-12-07 7:11 ` Richard Stallman
2001-12-06 12:26 ` Sven
2001-12-07 3:12 ` Richard Stallman
2001-12-10 15:28 ` Sven
2001-12-10 23:24 ` Jacques Garrigue
2001-12-11 4:22 ` hooh pxw
2001-12-11 10:19 ` Sven
2001-12-11 7:15 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2001-11-30 4:25 Gregory Morrisett
2001-11-29 19:49 David Gurr
2001-11-29 7:11 Ohad Rodeh
2001-11-28 20:29 John Field
2001-11-28 22:08 ` Al Christians
2001-11-29 1:25 ` james woodyatt
2001-11-29 8:47 ` Florian Hars
2001-11-30 7:12 ` james woodyatt
2001-11-09 15:55 Dave Berry
2001-11-09 4:30 Patrick M Doane
2001-11-09 4:48 ` Rafael 'Dido' Sevilla
2001-11-09 8:45 ` Xavier Leroy
2001-11-09 15:52 ` Dave Scott
2001-11-09 16:40 ` David Brown
2001-11-09 16:40 ` Brian Rogoff
2001-11-12 8:07 ` Tom
2001-11-12 15:58 ` David Brown
2001-11-09 4:49 ` Will Benton
2001-11-09 5:35 ` Patrick M Doane
2001-11-09 5:53 ` Michael Welsh Duggan
2001-11-09 5:58 ` Patrick M Doane
2001-11-09 9:27 ` Sven
2001-11-09 9:58 ` Julian Assange
2001-11-09 10:37 ` Sven
2001-11-09 15:39 ` Patrick M Doane
2001-11-09 15:36 ` Patrick M Doane
2001-11-09 9:25 ` Sven
2001-11-09 15:33 ` Patrick M Doane
2001-11-09 16:26 ` Tom
2001-11-11 12:25 ` Sven
2001-11-09 11:09 ` malc
2001-11-09 5:50 ` Michael Welsh Duggan
2001-11-09 8:59 ` Sven
2001-11-09 15:13 ` Patrick M Doane
2001-11-11 12:00 ` Sven
2001-11-11 14:56 ` Patrick M Doane
2001-11-26 16:21 ` Fergus Henderson
2001-11-26 16:47 ` Patrick M Doane
2001-11-27 10:28 ` Fergus Henderson
2001-11-27 10:58 ` Rafael 'Dido' Sevilla
2001-11-28 18:00 ` Xavier Leroy
2001-11-30 8:05 ` Sven
2001-11-09 20:54 ` Vitaly Lugovsky
2001-11-09 21:39 ` Patrick M Doane
2001-11-11 12:42 ` Sven
2001-11-11 22:05 ` Tom
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=20011130090928.B14742@dpt-info.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=jfield@us.ibm.com \
--cc=xavier.leroy@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