caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] Re: How can I lend developers to the Caml team?
Date: Sat, 17 Apr 2004 22:31:02 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDAECMHBAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <4f29de96459e39dd9736d64199d7ea28@mail.futureworlds.it>

futureworlds wrote:
>
> > Some parts of the core OCaml distribution could
> > use outside help ....  But the compilers and core
> > runtime system don't need additional manpower,
> > in my opinion.
>
> > - Xavier Leroy
>
> Xavier as a commercial guy I could not disagree more
> strongly.  OCaml desperately needs more "core" developers.
> [...]
> If someone offers you a free car, don't turn them down
> because you wanted a free motorbike.

Aren't you forgetting that INRIA's goals aren't your goals?  I think it
would be best if we can figure out how to make "more commercial, more
pragmatic" contributions without invading INRIA's turf.  If we are more
considerate of what INRIA wants, if we can work with their concerns, we
might find them willing to declare "ok, let this be your area" on things
they aren't thinking too hard about right now.

> In fact it's very surprising that no third-party core
> developers have joined to date, after all these years.
> It's about time.  Look at how many folks work on Python
> core for example.  All overseen by benevolent Guido.
> And the Linux kernel has dozens, all overseen by Linus.
> It works.

Whereas my personal experience with Guido is he's damn inflexible when
he's made up his mind about something.  I don't have any experience with
him on the technology front, but for marketing, it was a debacle.  INRIA
is not Guido or Linus, it is not orchestration around a single
individual.  So consider yourself potentially thankful to be working
with an institution rather than a strong-willed individual.


Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA

20% of the world is real.
80% is gobbledygook we make up inside our own heads.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.643 / Virus Database: 411 - Release Date: 3/25/2004

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-04-18  5:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-18  4:47 futureworlds
2004-04-18  5:31 ` Brandon J. Van Every [this message]
2004-04-18 17:03   ` skaller
2004-04-20 11:46 George Orwell
2004-04-20 17:41 ` Benjamin Geer
2004-04-20 17:47   ` Shawn Wagner
2004-04-20 20:16 ` skaller
2004-04-21  4:14   ` Jeffrey J. Cook

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=OOEALCJCKEBJBIJHCNJDAECMHBAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).