From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: plum.tunbury.org; dkim=pass (1024-bit key; unprotected) header.d=inria.fr header.i=@inria.fr header.a=rsa-sha256 header.s=dc header.b=Sr01YvQM; dkim=fail reason="signature verification failed" (1024-bit key) header.d=inria.fr header.i=@inria.fr header.a=rsa-sha256 header.s=dc header.b=YtGdqj/D; dkim-atps=neutral Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=192.134.164.83; helo=mail2-relais-roc.national.inria.fr; envelope-from=caml-list-owner@inria.fr; receiver=tunbury.org Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by plum.tunbury.org (Postfix) with ESMTPS id DBCB1401B9 for ; Fri, 14 Feb 2025 12:58:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=message-id:date:mime-version:to:from: content-transfer-encoding:subject:reply-to:sender:list-id: list-help:list-subscribe:list-unsubscribe:list-post: list-owner:list-archive; bh=olaVlKP1bgzz9ZXdt3iDoMjEfJc3l1vzJ+NlZNAppIU=; b=Sr01YvQM7tjwzQQdXEcoe4KR0PTbxY67bqDCf1Ev3ISANluJAGR+x++/ U2K6CCBQr30Q+nAwpWpzDzrwVYu/VRkWKol85f6FUs3FlPd02G4tFLg8v PgUX0c07wAI51haE2CR9NBmnxQqkQT1xbupy2FvzsaKYnfkj4YwQBPLCC U=; Received-SPF: Pass (mail2-relais-roc.national.inria.fr: domain of caml-list-owner@inria.fr designates 128.93.162.160 as permitted sender) identity=mailfrom; client-ip=128.93.162.160; receiver=mail2-relais-roc.national.inria.fr; envelope-from="caml-list-owner@inria.fr"; x-sender="caml-list-owner@inria.fr"; x-conformance=spf_only; x-record-type="v=spf1"; x-record-text="v=spf1 include:mailout.safebrands.com a:basic-mail.safebrands.com a:basic-mail01.safebrands.com a:basic-mail02.safebrands.com ip4:128.93.142.0/24 ip4:192.134.164.0/24 ip4:128.93.162.160 ip4:128.93.162.3 ip4:128.93.162.88 ip4:89.107.174.7 mx ~all" Received-SPF: None (mail2-relais-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@sympa.inria.fr) identity=helo; client-ip=128.93.162.160; receiver=mail2-relais-roc.national.inria.fr; envelope-from="caml-list-owner@inria.fr"; x-sender="postmaster@sympa.inria.fr"; x-conformance=spf_only Authentication-Results: mail2-relais-roc.national.inria.fr; spf=Pass smtp.mailfrom=caml-list-owner@inria.fr; spf=None smtp.helo=postmaster@sympa.inria.fr; dkim=hardfail (signature did not verify [final]) header.i=@inria.fr X-IronPort-AV: E=Sophos;i="6.13,286,1732575600"; d="scan'208";a="208309324" Received: from prod-listesu18.inria.fr (HELO sympa.inria.fr) ([128.93.162.160]) by mail2-relais-roc.national.inria.fr with ESMTP; 14 Feb 2025 13:58:03 +0100 Received: by sympa.inria.fr (Postfix, from userid 20132) id 0F7C8E0264; Fri, 14 Feb 2025 13:58:03 +0100 (CET) Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 84D8DE0260 for ; Fri, 14 Feb 2025 13:57:59 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=message-id:date:mime-version:to:from:subject: content-transfer-encoding; bh=olaVlKP1bgzz9ZXdt3iDoMjEfJc3l1vzJ+NlZNAppIU=; b=YtGdqj/DBnGiiRxAYXsAcPoe6laKEIRcf021Ue8NMP5DDuQioTrH+nYt tl4MmkTWtE5wTy8/Oscwb7pfL0pIrJzzxhJXGHci+YV/1g35/mJ/xgtM7 TBzalkKk91TjbbATQ0/lbshicKna+n6wFTNJCk0w10F08r2KPAdET9Ggv A=; X-IronPort-AV: E=Sophos;i="6.13,286,1732575600"; d="scan'208";a="208309294" Received: from cadillac.paris.inria.fr (HELO [128.93.64.106]) ([128.93.64.106]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Feb 2025 13:57:59 +0100 Message-ID: <74afd1f2-8569-4a46-ac13-86a407635cfa@inria.fr> Date: Fri, 14 Feb 2025 13:57:59 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB To: caml-list From: Florian Angeletti Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: [Caml-list] OCaml language committee launched Reply-To: Florian Angeletti X-Loop: caml-list@inria.fr X-Sequence: 19267 Errors-To: caml-list-owner@inria.fr Precedence: list Precedence: bulk Sender: caml-list-request@inria.fr X-no-archive: yes List-Id: List-Help: List-Subscribe: List-Unsubscribe: List-Post: List-Owner: List-Archive: Archived-At: 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