From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Brian Rogoff <bpr@best.com>
Cc: William Chesters <williamc@dai.ed.ac.uk>, OCAML <caml-list@inria.fr>
Subject: Re: licence issues
Date: Wed, 21 Apr 1999 22:08:09 +0200 [thread overview]
Message-ID: <19990421220809.31720@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.BSF.4.10.9904211200260.17048-100000@shell5.ba.best.com>; from Brian Rogoff on Wed, Apr 21, 1999 at 12:16:07PM -0700
> Since we are inventing hypothetical scenarios, try this one: INRIA stops
> funding the Caml project, for whatever reason. OCaml users are left
> "orphaned", as it is not clear who takes over, and begin the switch to
> SML and Haskell, or, much worse, C++, Perl, and Visual basic ;-). As a
> former Amiga and NextStep user, fear of being orphaned is a concern.
I was expecting this scenario to come up at some point in the
discussion. In the (presently unlikely) event that INRIA would pull
the plug out of the Caml project, we would of course do everything
possible so that the sources are released under a very liberal licence
so that others can continue the development if they wish.
You're right that this kind of code release hasn't been done often in
the past, especially by corporations, but it is becoming much more
commonplace now (see e.g. the MLJ project at Persimmon, or the
cancelled Java JIT project at Netscape). It is also very much in the
spirit of public research.
> I think the trick is to find a way to satisfy the valid concerns of the
> OCaml developers and the trepidations of some users.
Agreed. Some participants in this discussion have made interesting
contributions in this direction, and I thank them.
> Perhaps if there were
> another version of OCaml (like the Bigloo based Caml Light) under the GPL
> or a similar license these concerns would be lessened.
I'm not sure I follow you here. Are you suggesting some form of code
split? How would this solve the issue?
Best regards,
- Xavier Leroy
next prev parent reply other threads:[~1999-04-22 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-16 9:54 Markus Mottl
1999-04-16 16:40 ` Xavier Leroy
1999-04-19 11:56 ` William Chesters
1999-04-20 8:23 ` Xavier Leroy
1999-04-21 19:16 ` Brian Rogoff
1999-04-21 20:08 ` Xavier Leroy [this message]
1999-04-21 21:12 ` Brian Rogoff
1999-04-23 9:29 ` Sven LUTHER
1999-04-22 6:40 ` Sven LUTHER
1999-04-19 13:22 ` Sven LUTHER
1999-04-16 16:41 ` Brian Rogoff
1999-04-19 11:55 ` Michel Mauny
1999-04-19 17:53 ` Pierre Weis
1999-04-20 9:24 ` Dave Berry
1999-04-22 6:43 ` Sven LUTHER
1999-04-22 9:20 ` Dave Berry
1999-04-21 9:38 ` Sven LUTHER
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=19990421220809.31720@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=bpr@best.com \
--cc=caml-list@inria.fr \
--cc=williamc@dai.ed.ac.uk \
/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