Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Markus Mottl" <markus.mottl@gmail.com>
To: "Gerd Stolpmann" <info@gerd-stolpmann.de>
Cc: ocaml <caml-list@inria.fr>, ocaml-users@janestcapital.com
Subject: Re: [Caml-list] Re: The OCaml Community (aka back from the Developer Days)
Date: Tue, 29 Jan 2008 15:07:34 -0500	[thread overview]
Message-ID: <f8560b80801291207g18183e1eleefd1480fced762a@mail.gmail.com> (raw)
In-Reply-To: <1201614300.24248.23.camel@flake.lan.gerd-stolpmann.de>

Dear Gerd,

On Jan 29, 2008 8:45 AM, Gerd Stolpmann <info@gerd-stolpmann.de> wrote:
> 1. GODI is meant as an effort to bundle the activities of the community.
> It is not a commercial offer, and there is no customer support
> complaints can be directed at. If you want to improve it, the only way
> is to spend time and energy, and to enter a constructive discussion on
> godi-list. It is a pity that nobody at Jane Street wants to do this.

It seems to me that the OCaml mailing list is an appropriate place to
discuss the future of package management systems for OCaml.  We would
certainly gladly contribute to the development of Godi, since we, too,
think that a good package management system is essential for the
success of OCaml.  It's just that we feel that the basic design of
Godi, especially it's reliance on NetBSD-like package management,
would not play out well in the long haul, because we came to the
conclusion that it is not sufficiently developer-friendly.

We don't see that as a failure on your side, because finding the right
solution to notoriously complex problems of this sort is, to a large
degree, a matter of trial and error.  It seems that the major problems
that people faced back then as package users were addressed well.
Experience taught us that better support for other roles, especially
developers, is needed, and this may require a substantially different
approach.

> 2. As I'm the guy who mainly developed the core of GODI I can tell you
> that every hour I work on GODI is an hour I cannot work for one of my
> customers. So GODI produces opportunity costs for me. From that point of
> view I cannot understand a (probably) rich company that profited from
> this project for free, and is unwilling to share some of the costs.
> There is an economy behind free software, and Jane Street seems not to
> have understood it.

I think you have to admit that you are not being fair here.  Our
company has spent a fairly significant amount of time and money on
contributing to OCaml.  Organizing the OCaml Summer Project alone has
easily cost us many tens of thousands of dollars. And that's not
counting lost developer time.

> 3. Jane Street announced several times that they wanted to release
> software into the OSS world. Nothing happened.

This, too, is not true.  We certainly haven't released as much as we
would like to, since, as you might guess, we are extremely busy making
a living of our work, too. But I think you are doing us a big disfavor
with such false remarks by disregarding contributions we have made,
newly developed libraries like Sexplib, substantially rewritten ones
(Sqlite3-bindings), feature extensions (e.g. to Lacaml), compiler
patches (e.g. function call backtraces; tons of bug reports and
fixes), etc., and there is much more, very well-tested code in the
final stage of our release process.  Note that not all our
contributions are published on our website.  We are not into
marketing.

> From that experience I think your "new approach" is also nothing but vaporware.

I haven't said anywhere that we already have a "new approach".  In
fact, I said the exact opposite, namely that we are not sure yet what
exactly a better alternative would look like.  This is the reason why
we want to contribute to the discussion, and pointing out the
downsides of existing software, too, is important to make progress.

Lets face it: the vast majority of people just want to install a few
libraries they need for their work on their research or pet projects.
Godi is perfectly fine for maintaining such environments.  But if
sharing code and collaborative work is high on your list of priorities
(as it is for large teams like ours and surely also open source
development teams), Godi seems more like an obstacle.  A more
integrated and sufficiently standardized approach that combines
version control, build systems, automated compilation and test suites,
and packaging seems necessary to really give a boost to our
productivity.

> Sorry for the direct language, but you provoked it. It is a pity to lose
> Jane Street as supporter of GODI. If you still want to enter into a
> constructive dialog, I'm open to it.

Constructive dialogs cannot only consist of positive remarks, and I'm
sure you understand that.  You have pioneered an area that nobody else
in the OCaml community had tried before, because it's hard and a lot
of work.  As much as pioneers discover fruitful areas, they also
discover parts that are not worthwhile going.  I appreciate this
effort, and I can understand your defensive and natural reaction to
our criticism.  But note that this is not a criticism of you but of
the potential of Godi as the foundation for a standardized package
management system for OCaml.

Best regards,
Markus

-- 
Markus Mottl        http://www.ocaml.info        markus.mottl@gmail.com


  reply	other threads:[~2008-01-29 22:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27 13:09 David Teller
2008-01-28  0:38 ` [Caml-list] " Oliver Bandel
2008-01-28 11:27   ` David Teller
2008-01-28 13:42     ` Sylvain Le Gall
2008-01-28 16:38       ` [Caml-list] " Andrej Bauer
2008-01-29  0:26         ` Markus Mottl
2008-01-29 13:45           ` Gerd Stolpmann
2008-01-29 20:07             ` Markus Mottl [this message]
2008-01-30 13:04             ` Kuba Ober
2008-01-30 13:26               ` Jon Harrop
2008-01-30 14:17                 ` Kuba Ober
2008-01-30 15:14                   ` Jon Harrop
2008-01-30 16:26                     ` Kuba Ober
2008-01-30 17:41                   ` [Caml-list] Re: The OCaml Community (aka back fromthe " David Allsopp
2008-01-30 21:32                     ` Kuba Ober
2008-01-30 13:10             ` [Caml-list] Re: The OCaml Community (aka back from the " Vincent Hanquez
2008-01-30  9:22           ` Sylvain Le Gall
2008-01-28 17:25     ` [Caml-list] " Peng Zang
2008-01-28 13:35   ` Sylvain Le Gall
2008-01-28 15:25     ` [Caml-list] " Jon Harrop
2008-01-28 15:43       ` Sylvain Le Gall
2008-01-28 19:49         ` [Caml-list] " Jon Harrop
2008-01-28 20:16           ` Hezekiah M. Carty
2008-01-28 20:35             ` Jon Harrop
2008-01-28 20:48               ` Hezekiah M. Carty
     [not found]             ` <6f9f8f4a0801281235s136f53b4qae8ec2c928f931c@mail.gmail.com>
2008-01-28 20:46               ` Hezekiah M. Carty
2008-01-28 21:29             ` Alterlib? (was "Re: The OCaml Community") Dario Teixeira
2008-01-28 21:48               ` [Caml-list] " blue storm
2008-01-28 13:52 ` [Caml-list] The OCaml Community (aka back from the Developer Days) Romain Beauxis
2008-01-28 14:42   ` Sylvain Le Gall
2008-01-28 15:39     ` [Caml-list] " Romain Beauxis
2008-01-28 15:49       ` Sylvain Le Gall
2008-01-28 15:56         ` [Caml-list] " Romain Beauxis
2008-01-29 15:23     ` Stefano Zacchiroli

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=f8560b80801291207g18183e1eleefd1480fced762a@mail.gmail.com \
    --to=markus.mottl@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    --cc=ocaml-users@janestcapital.com \
    /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