From: Paul Eggert <eggert@cs.ucla.edu>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Sam James <sam@gentoo.org>, Mark Wielaard <mark@klomp.org>
Cc: Jakub Jelinek <jakub@redhat.com>,
libc-alpha@sourceware.org, Andreas Schwab <schwab@suse.de>,
Joseph Myers <joseph@codesourcery.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Carlos O'Donell <carlos@redhat.com>
Subject: Re: [Action Required] glibc decision to use CTI services.
Date: Fri, 1 Sep 2023 07:54:58 -0700 [thread overview]
Message-ID: <89eeebda-4f12-e819-4a8d-c0aaac50a3c9@cs.ucla.edu> (raw)
In-Reply-To: <43743bb5-e79e-f915-9528-4b3556de1c5c@gotplt.org>
On 2023-09-01 05:30, Siddhesh Poyarekar wrote:
> It is the Technical Advisory Committee that decides on the
> infrastructure tech and that is comprised completely of members from the
> GNU toolchain community. We will make sure that glibc services are
> implemented using Free software.
This sounds good, but I don't see the Linux Foundation agreeing to it in
the URLs Carlos mentioned at the start of this thread (see below). What
I see are statements[1][2] from the GNU Toolchain Infrastructure project
that GTI has "requested" that only free software be used. This is not
the same thing.
It'd be helpful to have a statement from the Linux Foundation that they
agree to use only free software to support glibc, and that GTI's
Technical Advisory Committee is empowered to inspect the Core Toolchain
Infrastructure used for glibc, so that the GTI TAC can verify that only
free software is used.
This shouldn't be that much to ask for. And I would think that the Linux
Foundation would welcome such an agreement, not only because the Linux
Foundation wants to support free software, but because it wants its
infrastructure to be open and checkable and usable by others.
> it's not about the overseers, who have indeed been prompt in handling requests and providing support for existing infrastructure. It's about doing things like service isolation, future enhancements/scaling and dedicated devops
It would indeed be nice to have things like that.
Here are the URLs from Carlos's earlier email.
> [1] https://sourceware.org/pipermail/overseers/2022q3/018896.html
> [2] https://sourceware.org/pipermail/overseers/2022q4/018981.html
> [3] https://lore.kernel.org/gti-tac/804cee43-a120-3acf-a302-b1640f2285a9@redhat.com/
> [4] https://lore.kernel.org/cti-tac/47d5d7a0-60ab-b400-2f75-880fdaae0738@redhat.com/T/#u
> [5] https://sourceware.org/pipermail/libc-alpha/2023-August/150610.html
> [6] https://sourceware.org/pipermail/libc-alpha/2023-July/150071.html
next prev parent reply other threads:[~2023-09-01 14:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b84ea4a5-651a-1a4c-06c8-e9ade4b7d702@redhat.com>
2023-08-30 17:19 ` Alexandre Oliva
2023-08-30 17:31 ` Joseph Myers
2023-08-31 19:59 ` Paul Eggert
2023-09-01 6:03 ` Sam James
2023-09-01 8:55 ` Florian Weimer
2023-09-01 9:02 ` Sam James
2023-09-01 9:21 ` dmarc, dkim and From rewriting Mark Wielaard
2023-09-01 11:52 ` Florian Weimer
2023-09-01 9:03 ` [Action Required] glibc decision to use CTI services Andrew Pinski
2023-09-01 11:49 ` Florian Weimer
2023-09-01 13:32 ` Frank Ch. Eigler
2023-09-01 12:30 ` Siddhesh Poyarekar
2023-09-01 14:54 ` Paul Eggert [this message]
2023-09-01 16:08 ` Siddhesh Poyarekar
2023-09-01 15:01 ` Sam James
2023-09-01 16:19 ` Frank Ch. Eigler
2023-09-01 16:30 ` Siddhesh Poyarekar
2023-09-02 18:25 ` Mark Wielaard
2023-09-01 9:08 ` Mark Wielaard
2023-09-03 6:31 ` Alexandre Oliva
2023-09-27 13:49 ` Carlos O'Donell
2023-10-04 0:09 ` Paul Eggert
2023-09-01 15:09 ` Alexandre Oliva
2023-09-27 13:50 ` Carlos O'Donell
2024-02-13 0:43 ` Carlos O'Donell
2024-02-19 21:22 ` Alexandre Oliva
2024-02-19 22:03 ` DJ Delorie
2024-02-20 1:49 ` Mark Wielaard
2024-02-20 3:01 ` Alexandre Oliva
2023-08-31 8:37 ` Mark Wielaard
2023-09-01 15:08 ` Alexandre Oliva
2023-08-31 10:34 ` Florian Weimer
2023-09-04 6:09 ` Alexandre Oliva
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=89eeebda-4f12-e819-4a8d-c0aaac50a3c9@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=carlos@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=mark@klomp.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=sam@gentoo.org \
--cc=schwab@suse.de \
--cc=siddhesh@gotplt.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).