From: Brian Rogoff <bpr@best.com>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: Brian Rogoff <bpr@best.com>,
William Chesters <williamc@dai.ed.ac.uk>,
OCAML <caml-list@inria.fr>
Subject: Re: licence issues
Date: Wed, 21 Apr 1999 14:12:57 -0700 (PDT) [thread overview]
Message-ID: <Pine.BSF.4.10.9904211357310.20911-100000@shell5.ba.best.com> (raw)
In-Reply-To: <19990421220809.31720@pauillac.inria.fr>
On Wed, 21 Apr 1999, Xavier Leroy wrote:
> > 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.
That's enough to satisfy me, though to be fair I was not bothered by the
current license.
> > 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?
Yes. This would solve the issue (and create many nastier new ones) by
letting those who have problems with the INRIA licensing use the
GPL/BSD/whatever version. Also, it would shoot down the criticism of OCaml
that it is a language defined by its current implementation. That said, I
think its a bad idea, as it takes too much time from the OCaml team and
community to have multiple variants at this stage of the language
development. Once the language design is "done", it may not be such a bad
idea, but from what I gather OCaml is still a research project and not a
frozen standard.
-- Brian
PS: I suggest that when the design is done, the new language be named
ML-2000, for the obvious humor value ;-)
next prev parent reply other threads:[~1999-04-22 16:55 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
1999-04-21 21:12 ` Brian Rogoff [this message]
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=Pine.BSF.4.10.9904211357310.20911-100000@shell5.ba.best.com \
--to=bpr@best.com \
--cc=Xavier.Leroy@inria.fr \
--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