From: Goswin von Brederlow <goswin-v-b@web.de>
To: oliver <oliver@first.in-berlin.de>
Cc: Benedikt Meurer <benedikt.meurer@googlemail.com>, caml-list@inria.fr
Subject: Re: [Caml-list] OCaml maintenance status / community fork
Date: Wed, 07 Dec 2011 10:39:30 +0100 [thread overview]
Message-ID: <87pqg0oh4d.fsf@frosties.localnet> (raw)
In-Reply-To: <20111206220739.GA2039@siouxsie> (oliver@first.in-berlin.de's message of "Tue, 6 Dec 2011 23:07:39 +0100")
oliver <oliver@first.in-berlin.de> writes:
> Hello,
>
>
> during the last years, more than one person mourned about
> this or that dark sides of OCaml.
>
> Even some of the mourning and the proposals had mentioned good ideas and had
> positive motivation, after a while it became clear, that the same people with
> the one or the other good idea, failed badly in other areas. Good, that they
> did not have had too much influence in the development of OCaml.
>
> Even in general I like the community/bazaar, I think in case of OCaml,
> there is a lot of high knowledge in the core team, which was criticized
> by others already, but in the long run, it turned out that the core team
> had their reasons for a lot of decisions, which were criticized.
> Ocaml of course will also have some history-related issues that might be
> changed, but maybe also a lot of decisions inside, which relies on theoretical
> reasoning.
That is no excuse for not reacting to bug or feature patches. If
there is a reason not to accept a patch then that can be communicated.
There is no excuse for silence.
MfG
Goswin
next prev parent reply other threads:[~2011-12-07 9:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 8:25 Benedikt Meurer
2011-12-06 9:17 ` Goswin von Brederlow
2011-12-06 10:08 ` Gaius Hammond
2011-12-06 9:31 ` rixed
2011-12-06 12:10 ` Benedikt Meurer
2011-12-06 9:42 ` Kakadu
2011-12-06 9:48 ` Joel Reymont
2011-12-06 10:51 ` Fabrice Le Fessant
2011-12-06 10:58 ` Stefano Zacchiroli
2011-12-06 16:12 ` Fabrice Le Fessant
2011-12-06 19:24 ` Mehdi Dogguy
2011-12-06 10:00 ` Gerd Stolpmann
2011-12-06 12:20 ` Benedikt Meurer
2011-12-06 10:35 ` Gabriel Scherer
2011-12-06 11:31 ` Gerd Stolpmann
2011-12-06 12:34 ` Benedikt Meurer
2011-12-15 18:49 ` Jérôme Benoit
2011-12-06 13:09 ` Goswin von Brederlow
2011-12-06 22:48 ` oliver
2011-12-07 7:23 ` Adrien
2011-12-06 11:40 ` Gabriel Scherer
2011-12-06 12:02 ` Stefano Zacchiroli
2011-12-06 12:16 ` Joel Reymont
2011-12-06 12:43 ` Stefano Zacchiroli
2011-12-06 12:27 ` François Bobot
2011-12-06 13:01 ` Benedikt Meurer
2011-12-06 13:52 ` ivan chollet
2011-12-06 14:42 ` Alexandre Pilkiewicz
2011-12-06 15:10 ` Gerd Stolpmann
2011-12-06 15:14 ` Yitzhak Mandelbaum
2011-12-06 15:24 ` Pierre-Alexandre Voye
2011-12-07 9:36 ` Goswin von Brederlow
2011-12-06 22:07 ` oliver
2011-12-07 9:39 ` Goswin von Brederlow [this message]
2011-12-07 20:42 ` oliver
[not found] <201112071100.pB7B0N8J020839@walapai.inria.fr>
2011-12-07 13:59 ` tools
2011-12-07 14:37 ` Jérémie Dimino
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=87pqg0oh4d.fsf@frosties.localnet \
--to=goswin-v-b@web.de \
--cc=benedikt.meurer@googlemail.com \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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