From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 18826 invoked from network); 26 Sep 2022 10:49:44 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 26 Sep 2022 10:49:44 -0000 Received: (qmail 24543 invoked by uid 550); 26 Sep 2022 10:49:41 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 24507 invoked from network); 26 Sep 2022 10:49:40 -0000 From: Florian Weimer To: =?utf-8?B?SuKCkeKCmeKCmw==?= Gustedt Cc: enh , musl@lists.openwall.com References: <20220923162518.56284329@inria.fr> <20220923174054.73258a83@inria.fr> <20220924093106.41e53819@inria.fr> Date: Mon, 26 Sep 2022 12:49:26 +0200 In-Reply-To: <20220924093106.41e53819@inria.fr> ("J. =?utf-8?B?4oKR4oKZ?= =?utf-8?B?4oKb?= Gustedt"'s message of "Sat, 24 Sep 2022 09:31:06 +0200") Message-ID: <87leq6if61.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [musl] C23 implications for C libraries * J. =E2=82=91=E2=82=99=E2=82=9B Gustedt: > Much as musl, the C standard is a volunteer project. Instead of > reclaiming things you should ask yourself how can you or your company > help. > > As all volunteer work, this is best effort. WG14 would have a much > better stand if more of the industry would inject real work force into > the committee. Currently there seem only be two of the bigger players > that have people there that substantially work on the C standard > during their office hours. The others are mostly academics like myself > and people working in their free time. The official contribution policies are here: C - Contributing Note that it never says where to submit your contribution. Actually, towards the end, that document explains why: participation from =E2=80=9Call members of the broader C community=E2=80=9D is pretty muc= h rejected: | While we wish we could encourage all members of the broader C | community to participate in the standardization process, we are an | ISO working group and subject to their requirements. Contributors | who are making sustained contributions should join their local | national body to officially become a WG14 expert. For more | information on joining a National Body, please see ISO | . Joining a =E2=80=9CNational Body=E2=80=9D requires a non-nominal yearly fee= , depending on where you live, and even then the relevant committee or group there needs to appoint you to WG14 (which may require participation in additonal, regular meetings). I'm sure there are ways around that if you know the right people, but I expect the issues around representation you observe are directly related to these admission policies. This situation is not going to change any time soon, and that's one reason why I started the libc-coord mailing list.