caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brian Rogoff <bpr@best.com>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Cc: Markus Mottl <mottl@miss.wu-wien.ac.at>, caml-list@inria.fr
Subject: Re: R: Consortium Caml
Date: Sun, 11 Feb 2001 17:44:01 -0800 (PST)	[thread overview]
Message-ID: <Pine.BSF.4.21.0102111726090.23155-100000@shell5.ba.best.com> (raw)
In-Reply-To: <20010210205617.G16265@verdot.inria.fr>

On Sat, 10 Feb 2001, Daniel de Rauglaudre wrote:
> Hi,
> 
> On Fri, Feb 09, 2001 at 05:22:25PM +0100, Markus Mottl wrote:
> 
> > This is a legal question rather than an economic one. Still, I fear that
> > it will be difficult to gain many (= enough) members unless they see a
> > certain benefit from it without having too much risk.
> 
> I don't agree with that. The idea of the Consortium is not for companies
> to get their money back: they pay for the warranty that OCaml continues.
> If you decide that OCaml has to be used in your company, you may take
> some advantages on paying. It is sponsoring, nothing else.

I agree, if the OCaml developers at INRIA disband and no one else picks
up development, commercial software developers who took a chance on this 
research language will be screwed. So we commercial users have a lot of 
incentive to pay. 

> The Consortium is for companies: for people who make strategic decisions
> like using the language. It is not for individuals: as an individual, of
> course, you don't care that OCaml stops. 

As an individual OCaml programmer, I have a lot of incentive to see OCaml 
succeed. Companies are made up of individuals, some of whom have been a 
continuous nuisance to their managers to join the Consortium ;-).

> But if you are the boss of a big
> company and decide to use it, it can be terrible if it no more supported.

Being "orphaned" is my biggest fear wrt Ocaml. So far the open source
moves and the formation of the Consortium have gone a good way towards 
allaying that fear.

-- Brian




  parent reply	other threads:[~2001-02-12 12:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05 22:55 Alex Baretta
2001-02-07 19:30 ` Michel Mauny
2001-02-08  7:27   ` Sven
2001-02-08 15:59     ` Michel Mauny
2001-02-08 10:01       ` Sven
2001-02-08 17:18         ` Michel Mauny
2001-02-08  0:45 ` R: " Markus Mottl
2001-02-09 14:45   ` Fabien Fleutot
2001-02-09 16:22     ` Markus Mottl
2001-02-10 15:33       ` Jan Skibinski
2001-02-10 19:56       ` Daniel de Rauglaudre
2001-02-11 12:05         ` Markus Mottl
2001-02-11 14:49           ` Daniel de Rauglaudre
2001-02-11 18:36             ` Markus Mottl
2001-02-11 19:23               ` Daniel de Rauglaudre
2001-02-12  0:32                 ` Markus Mottl
2001-02-11 15:26         ` John Max Skaller
2001-02-12  1:44         ` Brian Rogoff [this message]
2001-02-12  8:36         ` Xavier Leroy
2001-02-13 11:02           ` Frank Atanassow
2001-02-12  9:37       ` Jean-Marc Alliot

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.21.0102111726090.23155-100000@shell5.ba.best.com \
    --to=bpr@best.com \
    --cc=caml-list@inria.fr \
    --cc=daniel.de_rauglaudre@inria.fr \
    --cc=mottl@miss.wu-wien.ac.at \
    /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).