From: Florian Angeletti <florian.angeletti@inria.fr>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] OCaml language committee launched
Date: Fri, 14 Feb 2025 13:57:59 +0100 [thread overview]
Message-ID: <74afd1f2-8569-4a46-ac13-86a407635cfa@inria.fr> (raw)
Dear OCaml users,
It is my pleasure to announce the launch of the OCaml language
committee. This
committee is intended as collegial instance with the aim to facilitate
discussions and consensus making about the evolution of the OCaml
language and
its standard library.
Over the years, it has become a common shared grievance among both
maintainers
and contributors to the OCaml language that, sometimes, the review
process for
changes grinds to a halt, either because consensus is elusive or because
no one
feels empowered enough to take a decision single-handed.
In order to reduce the number of those instances of decision
paralysis, the
OCaml maintainers have decided to experiment with an OCaml language
committee:
a subgroup of the OCaml community organised to discuss evolution of the
OCaml
language in a timely fashion, see
-
https://github.com/ocaml/RFCs/blob/master/Committee.md#who-is-the-committee
for the list of members of the committee.
In practice, if someone feels that a contribution (a Pull Request, issue,
Request For Comment) might be stuck or might benefit from a wider
discussion,
they may ask the committee to take the contribution under consideration by
mentioning it to the committee chair (which is currently me, or
@Octachron on
GitHub).
Then the committee will deliberate on this contribution, both on the
archived public mailing list `ocaml-language-committee@inria.fr` for
internal committee
discussion (https://sympa.inria.fr/sympa/arc/ocaml-language-committee)
and possibly on the relevant community channels
(https://github.com/ocaml/ocaml or
https://discuss.ocaml.org).
At the end of this collegial discussion, the committee will publish
a consultative decision
on the matter. We expect that having such a collegial consultative
decision would be enough
to unblock most situations.
Note that the anyone is welcome to subscribe to the committee
mailing but please do not
flood it with messages so that we can keep it fully open.
For more details, the intended working of the committee is described at:
- https://github.com/ocaml/RFCs/blob/master/Committee.md
Happy hacking,
Florian Angeletti for the OCaml Language Committee
reply other threads:[~2025-02-14 12:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=74afd1f2-8569-4a46-ac13-86a407635cfa@inria.fr \
--to=florian.angeletti@inria.fr \
--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