From: "Jérôme Benoit" <jerome.benoit@grenouille.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml maintenance status / community fork
Date: Thu, 15 Dec 2011 19:49:09 +0100 [thread overview]
Message-ID: <20111215194909.37c9cc50@nemesis.grenouille.com> (raw)
In-Reply-To: <4adc9f6482cdbe0208c0baf4992392de.squirrel@gps.dynxs.de>
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
On Tue, 6 Dec 2011 12:31:07 +0100
"Gerd Stolpmann" <info@gerd-stolpmann.de> wrote:
>
> > I would like to comment on a tangential aspect of the rationale you
> > gave:
> >
> >> Given that OCaml is such a nice language with a lot of useful
> >> frameworks available,
> >> it is too sad to see it loosing ground just because of it's closed
> >> development process
> >> and lack of time of the official team.
>
> I'm quite reluctant to discuss topics about the said decline of
> something. However, there is certainly a point here. I have my own
> theory - basically the users with FP knowledge have now more options
> (e.g. F# or the JVM-based FP languages like Scala), and so the
> "share" for Ocaml is decreasing. This has nothing to do with the
> language.
It's not an issue for OCaml development, it's an issue for newcomers.
The main issue is : OCaml community do not have a fucking clue of what
a codeflow really *is*.
Never ever seen a commit only list on all of the OCaml projects seen so
far. Never ever seen a patches flow working (via BTS or mail). Never
read a well documented commit comment. Never read a comment on a patch
or a commit.
And you want hackers to be implicate in the OCaml development
process with not even a working and documented codeflow, the first
and essential brick any FOSS project just all share ?
Cheers.
--
Jérôme Benoit aka fraggle
La Météo du Net - http://grenouille.com
OpenPGP Key ID : 9FE9161D
Key fingerprint : 9CA4 0249 AF57 A35B 34B3 AC15 FAA0 CB50 9FE9 161D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-12-15 18:49 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 [this message]
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
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=20111215194909.37c9cc50@nemesis.grenouille.com \
--to=jerome.benoit@grenouille.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