caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: ivan chollet <ivan.chollet@gmail.com>
To: Benedikt Meurer <benedikt.meurer@googlemail.com>
Cc: Alain Frisch <alain@frisch.fr>, caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml maintenance status / community fork (again)
Date: Thu, 8 Dec 2011 10:47:58 +0000	[thread overview]
Message-ID: <CACm_MF9L4S1EybE1jYuReqbJ+rok+z3eScSWEN-5STcKjr1k4Q@mail.gmail.com> (raw)
In-Reply-To: <DF4E0A16-38FC-4A33-A0C1-6AC618750164@googlemail.com>

[-- Attachment #1: Type: text/plain, Size: 2672 bytes --]

It's nice to see this thread coming back to the original issue after having
been hijacked. You can notice that contributers to this thread have
opinions but not many facts and arguments to support them.
Contacting the OCaml maintainers privately is definitely not the way to let
the development process happen in the open, but bad habits are hard to get
rid of.
I think we all understand that the core team is in an uncomfortable and
conflicting situation and that the questions asked in this thread won't get
an answer. In french this is called "avoir le cul entre deux chaises".
Benedikt did not suggest at any point to set OCaml free from the original
developers, he suggested to set it free from the INRIA.


On Thu, Dec 8, 2011 at 10:28 AM, Benedikt Meurer <
benedikt.meurer@googlemail.com> wrote:

>
> On Dec 8, 2011, at 10:54 , Alain Frisch wrote:
>
> > On 12/08/2011 10:10 AM, Benedikt Meurer wrote:
> >> There were already a few useful comments on the topic, but no statement
> from the current INRIA officials. Opening up the development of OCaml is a
> great suggestion, for example. Personally I'd even suggest to disconnect
> OCaml and INRIA, with an independent team of core maintainers (with
> appropriate spare time and knowledge). INRIA would still contribute to
> OCaml, but no longer control OCaml.
> >
> > Honestly, opening up the development of OCaml would be terrific; but
> trying to disconnect it from INRIA sounds like a very bad idea to me.
> >
> > Concerning the issues with the ARM port, there is no chance to get a
> good support for this architecture (which includes accepting patches)
> without someone in the core team who feels responsible for the port and
> commits to maintaining it.  You might want to create a new "core team"
> completely disconnected from INRIA, but the problem would remain the same
> (I don't believe in a completely decentralized development model for
> something like OCaml).
>
> The problem is IMHO that there is no one at INRIA caring about ARM. In an
> open model we would have maintainers for the ARM port(s).
>
> > Instead, I'd suggest contacting the existing core team (caml@inria.fr)
> in order to find a solution.
>
> I wasn't aware that there is a separate communication channel for the core
> team. I was under the impression that the caml-list was the best way to
> reach both the core team and the community.
>
> > Best regards,
> > Alain
>
> greets,
> Benedikt
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>

[-- Attachment #2: Type: text/html, Size: 3449 bytes --]

  parent reply	other threads:[~2011-12-08 10:48 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 [this message]
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
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=CACm_MF9L4S1EybE1jYuReqbJ+rok+z3eScSWEN-5STcKjr1k4Q@mail.gmail.com \
    --to=ivan.chollet@gmail.com \
    --cc=alain@frisch.fr \
    --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).