caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Stéphane Glondu" <steph@glondu.net>
To: Benedikt Meurer <benedikt.meurer@googlemail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml maintenance status / community fork (again)
Date: Thu, 08 Dec 2011 12:07:18 +0100	[thread overview]
Message-ID: <4EE09A66.9020306@glondu.net> (raw)
In-Reply-To: <55531934-37A5-4CC5-AB67-20CE4CCE8269@googlemail.com>

On 12/08/2011 10:10 AM, Benedikt Meurer wrote:
> [...] I'm already pissed off by the fact that it will probably take ages for someone to even respond to the patch, not to mention that it will take forever to get it out to the users (well maybe Debian will include the patch for armhf, but that means the Debian developers have to do upstream work...).

As a maintainer of OCaml (among other things) in Debian, I must agree
with you that slow reaction, opacity in its development process, etc.
make OCaml a very frustrating upstream (one of the worst I have to deal
with). See for example:

  http://caml.inria.fr/mantis/view.php?id=4963
  http://caml.inria.fr/mantis/view.php?id=5131
  http://caml.inria.fr/mantis/view.php?id=5254
  http://caml.inria.fr/mantis/view.php?id=5279
  http://caml.inria.fr/mantis/view.php?id=5393

All very precise bugreports with rather trivial patches or suggestions.
Yet, no satisfactory reaction.

I once proposed a patch to "fix" the "-custom" behaviour that made
resulting executables not strippable, to avoid all sort of
special-casing that had to be done in Debian (and Fedora) because of
this behaviour. It has been rejected (but I applied it nonetheless to
the Debian package). See the discussion at:

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=256900

(in particular, starting from message #42).

All this often leads me to just not trying to solve bugs in OCaml
myself, even for things that do affect Debian. See for example:

  http://caml.inria.fr/mantis/view.php?id=1710
  http://caml.inria.fr/mantis/view.php?id=1711
  http://caml.inria.fr/mantis/view.php?id=1836
  http://caml.inria.fr/mantis/view.php?id=4812
  http://caml.inria.fr/mantis/view.php?id=5371

Concerning your work on ARM, PR#5049 completely deterred me from working
on it myself, or submitting it to more competent people (and I do know
some thanks to Debian and Ubuntu).

I really think that OCaml could benefit from a more open development
model, and should leverage external contributors (that are not members
of the consortium) instead of plainly ignoring them. There is for
example no need for someone in the "core team" to feel responsible for
the ARM port. Have a look at:

  https://bugs.launchpad.net/ubuntu/+source/ocaml/+bug/810402

People who care about ARM solved the bug themselves. Having ocamlopt
working on all Debian architectures wouldn't look so unreasonable if the
"core team" were willing to integrate necessary changes as part of
official releases (which is clearly not the case).

I'm not advocating for faster development, endless addition of new
features, or a better standard library, I just wish better reactivity to
the community concerning the compiler or the language itself. The
general lack of "official" (whatever that means) participation in this
mailing-list is another example of this problem.


Cheers,

-- 
Stéphane

  parent reply	other threads:[~2011-12-08 11:07 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08  9:10 Benedikt Meurer
2011-12-08  9:54 ` Alain Frisch
2011-12-08 10:28   ` Benedikt Meurer
2011-12-08 10:46     ` Alain Frisch
2011-12-08 11:08       ` Benedikt Meurer
2011-12-08 16:42       ` Fabrice Le Fessant
2011-12-08 10:47     ` ivan chollet
2011-12-08 14:07       ` oliver
2011-12-08 11:11     ` Pierre-Alexandre Voye
2011-12-08 18:18       ` Török Edwin
2011-12-09 21:42         ` oliver
2011-12-08 10:16 ` Gabriel Scherer
2011-12-08 11:07 ` Stéphane Glondu [this message]
2011-12-09  2:11 ` Jacques Garrigue
2011-12-09 10:37   ` Jérémie Dimino
2011-12-09 11:03     ` Gabriel Scherer
2011-12-09 11:17       ` Stefano Zacchiroli
2011-12-09 11:50         ` Jonathan Protzenko
2011-12-09 12:36           ` Alain Frisch
2011-12-09 23:22         ` Goswin von Brederlow
2011-12-09 22:33       ` oliver
2011-12-09 14:24     ` Benedikt Meurer
2011-12-09 17:00       ` Mehdi Dogguy
2011-12-09 17:36         ` Benedikt Meurer
2011-12-09 17:45           ` Mehdi Dogguy
2011-12-09 23:24             ` Goswin von Brederlow
2011-12-10  9:31               ` Benedikt Meurer
2011-12-10 14:45 ` Xavier Leroy
2011-12-10 15:58   ` Benedikt Meurer
2011-12-12 10:21     ` Xavier Leroy
2011-12-12 10:59       ` Benedikt Meurer
2011-12-12 12:20         ` Mehdi Dogguy
2011-12-12 15:17           ` Goswin von Brederlow
2011-12-19  4:09           ` Romain Beauxis
2011-12-19 17:35             ` Alain Frisch
2011-12-12 12:57         ` Gerd Stolpmann
2011-12-10 17:06   ` Török Edwin
2011-12-10 18:28   ` Jérémie Dimino
2011-12-10 18:34     ` Wojciech Meyer
2011-12-10 19:10       ` Wojciech Meyer
2011-12-10 20:55         ` Jérémie Dimino
2011-12-10 21:40           ` [Caml-list] Camlp4/p5 type reflection [was: OCaml maintenance status / community fork (again)] Wojciech Meyer
2011-12-10 23:34             ` Gabriel Scherer
2011-12-11  0:47               ` [Caml-list] Camlp4/p5 type reflection [ Wojciech Meyer
2011-12-11 11:19                 ` Gabriel Scherer
2011-12-11 18:14                   ` Jérémie Dimino
2011-12-11  9:04               ` [Caml-list] Camlp4/p5 type reflection [was: OCaml maintenance status / community fork (again)] Stéphane Glondu
2011-12-11  9:36                 ` Török Edwin
2011-12-11 10:29                 ` Gabriel Scherer
2011-12-11 11:23                   ` Gerd Stolpmann
2011-12-11 11:38                     ` Gabriel Scherer
2011-12-11 10:20               ` Fabrice Le Fessant
2011-12-11 10:47                 ` Gabriel Scherer
2011-12-11 13:27               ` Alain Frisch
2011-12-11 13:35                 ` Gabriel Scherer
2011-12-11 13:42                   ` Alain Frisch
2011-12-11 13:36                 ` Arnaud Spiwack
2011-12-11 13:46                 ` Stéphane Glondu
2011-12-10 23:28   ` [Caml-list] OCaml maintenance status / community fork (again) Jesper Louis Andersen
2011-12-11 11:02     ` Gerd Stolpmann
2011-12-13 19:36       ` oliver
2011-12-14 12:13         ` Gerd Stolpmann
2011-12-16 10:03           ` Stéphane Glondu
2011-12-11 13:33   ` Goswin von Brederlow
2011-12-11 13:59     ` [Caml-list] Community distribution [was: OCaml maintenance status / community fork (again)] Benedikt Meurer
2011-12-12 17:48   ` [Caml-list] OCaml maintenance status / community fork (again) Stéphane Glondu
2011-12-13 20:39     ` [Caml-list] New experimental ARM backend [was: OCaml maintenance status / community fork (again)] Benedikt Meurer
2011-12-14  9:18       ` Mark Shinwell
2011-12-14 21:51         ` Benedikt Meurer
2011-12-18 11:57       ` [Caml-list] " Benedikt Meurer
2011-12-18 13:08         ` Benedikt Meurer
2011-12-18 14:50           ` Alexandre Pilkiewicz
2011-12-18 16:42             ` Benedikt Meurer
2011-12-18 17:23           ` Stéphane Glondu
2011-12-21 10:11             ` [Caml-list] " Benedikt Meurer
2011-12-18 13:16         ` [Caml-list] " Benedikt Meurer
2011-12-17 18:36   ` [Caml-list] OCaml maintenance status / community fork (again) Stéphane Glondu
2011-12-18  4:25     ` Till Varoquaux

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=4EE09A66.9020306@glondu.net \
    --to=steph@glondu.net \
    --cc=benedikt.meurer@googlemail.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).