mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
Cc: enh <enh@google.com>,  musl@lists.openwall.com
Subject: Re: [musl] C23 implications for C libraries
Date: Mon, 26 Sep 2022 12:49:26 +0200	[thread overview]
Message-ID: <87leq6if61.fsf@mid.deneb.enyo.de> (raw)
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")

* J. ₑₙₛ 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
  <https://www.open-std.org/jtc1/sc22/wg14/www/contributing.html>

Note that it never says where to submit your contribution.

Actually, towards the end, that document explains why: participation
from “all members of the broader C community” is pretty much 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
| <https://www.iso.org/members.html>.

Joining a “National Body” 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.

  parent reply	other threads:[~2022-09-26 10:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 14:25 Jₑₙₛ Gustedt
2022-09-23 14:58 ` Rich Felker
2022-09-23 15:11   ` Alexander Monakov
2022-09-23 15:35   ` Jₑₙₛ Gustedt
2022-09-23 15:28 ` enh
2022-09-23 15:40   ` Jₑₙₛ Gustedt
2022-09-23 23:52     ` enh
2022-09-24  7:31       ` Jₑₙₛ Gustedt
2022-09-26  3:18         ` Damian McGuckin
2022-09-26  3:33         ` Rich Felker
2022-09-26 10:49         ` Florian Weimer [this message]
2022-09-26 12:52           ` Jₑₙₛ Gustedt
2022-09-26 20:13         ` enh
2022-11-18 20:46 ` 罗勇刚(Yonggang Luo)
2022-11-19 14:33   ` Jₑₙₛ Gustedt
2022-11-19 17:19     ` 罗勇刚(Yonggang Luo)
2022-11-20  8:23       ` Jₑₙₛ Gustedt
2022-11-19 18:28     ` Rich Felker
2022-11-20  8:42       ` Jₑₙₛ Gustedt
2023-05-03 22:58     ` enh
2023-05-04  6:19       ` Jₑₙₛ Gustedt
2023-05-04 16:03         ` Rich Felker
2023-05-04 16:07           ` enh
2023-05-04 23:16             ` Gabriel Ravier
2023-05-05  0:37               ` JeanHeyd Meneide
2023-05-05  6:56                 ` Jₑₙₛ Gustedt
2023-05-05 12:40                   ` Rich Felker
2023-05-05  6:40             ` Jₑₙₛ Gustedt
2023-05-04 16:03         ` enh
2023-05-04 23:11           ` Gabriel Ravier
2022-11-19 18:31   ` Rich Felker
2022-11-20  4:25     ` 罗勇刚(Yonggang Luo)
2022-11-20  5:34       ` Markus Wichmann
2022-11-21 11:46 ` Reini Urban
2022-11-21 21:06   ` Jₑₙₛ Gustedt
2022-11-23  4:31     ` 罗勇刚(Yonggang Luo)
2022-11-23  8:11       ` Jₑₙₛ Gustedt
2022-11-23  8:20         ` 罗勇刚(Yonggang Luo)
2022-11-23  8:33           ` Jₑₙₛ Gustedt
2022-11-23  8:41             ` 罗勇刚(Yonggang Luo)

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=87leq6if61.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=enh@google.com \
    --cc=jens.gustedt@inria.fr \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).