caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Max Skaller <skaller@ozemail.com.au>
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: Mon, 12 Feb 2001 02:26:36 +1100	[thread overview]
Message-ID: <3A86AF2C.9CE172C8@ozemail.com.au> (raw)
In-Reply-To: <20010210205617.G16265@verdot.inria.fr>

Daniel de Rauglaudre wrote:

> 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. But if you are the boss of a big
> company and decide to use it, it can be terrible if it no more supported.

	As an individual I _do_ care if Ocaml stops,
since I have invested considerable amounts of _my_ time and effort
into it, whereas companies have the resources to amortise risk,
and the 'big boss' didn't invest his money, and will still get
paid his salary.

	I only have one short life, and I have a vested interest
in Ocaml succeeding commercially that is far more important
to me than a small change in profits of some company.
This interest is not merely to obtain money from work,
but also to contribute to better practice, so I can feel
my life is worthwhile.

	Therefore, it would be useful if I could register that
interest, even if my financial contribution is small compared
to a large company: ultimately, Ocaml programs have to be written
by people.

	A Consortium may benefit from having both corporate members
and individuals, for example companies may be able to get more code
more cheaply from a pool of individuals who would be grateful for
_some_ funding for work they might well have done anyhow.

-- 
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net



  parent reply	other threads:[~2001-02-12 12:42 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 [this message]
2001-02-12  1:44         ` Brian Rogoff
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=3A86AF2C.9CE172C8@ozemail.com.au \
    --to=skaller@ozemail.com.au \
    --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).