Re: Meeting Minutes - Office Hours for CTI - 2026-09-18

[Andrea Pinski via Gdb <gdb@sourceware.org>]

On Mon, Sep 21, 2026 at 9:34 AM Carlos O'Donell via Gcc <gcc@gcc.gnu.org> wrote:
>
> CTI: https://cti.coretoolchain.dev/
>
> The CTI project holds Office Hours every Friday, these are the minutes for this Friday's meeting.
>
> The CTI project in collaboration with glibc is working on: https://cti.coretoolchain.dev/projects/glibc.html
>
> Posting across the project mailing lists since some developers had questions and are only subscribed on some lists.

This assumes that there is consensus on moving forward with any
proposal.  And second, there is not enough information in these
meeting notes.
They don't contain the attendance which is important to understand why
there is not much discussion around the issues already raised.
The notes don't contain the rationale for the choices on hand; for an example:

>
> Agenda:
>   * Community items that need review.
>   * 1. What does the ouput of vcs to email look like? Post to libc-alpha for review.
>    * What does the output of git-mailbomb-cron look like.
>     * Asked LF IT on #cti-help for examples of output.
>    * 2. What does the output of bug text to bugzilla look like? Post to libc-alpha for review.
>     * Asked LF IT on #cti-help for examples of output.
>   * Come up with exact DNS names for services that can be split and moved.
>    * Support using DNS to route services in the future and for isolation.
>    * Even though isolation can be achieved at the proxy side after DNS, the splitting is easier with DNS.
>   * Discuss on libc-alpha finalizing git URLs
>    * git.glibc.coretoolchain.dev/glibc (RO mirror)
>    * gitolite.glibc.coretoolchain.dev/glibc (RW for developers)
>    * gitolite.glibc.coretoolchain.dev/glibc-keyring (RW for admins)

What is the rationale for having 3 different URLs? What is the
rationale for using `coretoolchain.dev` rather than something more
specific named with gnu?
Why have a glibc subdomain?  Etc.

>   * Discuss on libc-alpha finalize mailing list names:
>    * Place mailing list services under lists.glibc.coretoolchain.dev
>    * glibc-announce@lists.glibc.coretoolchain.dev
>    * glibc-devel@lists.glibc.coretoolchain.dev
>    * glibc-stable@lists.glibc.coretoolchain.dev
>    * glibc-testresults@lists.glibc.coretoolchain.dev
>    * glibc-help@glibc.lists.glibc.coretoolchain.dev
>    * glibc-vcs@lists.glibc.coretoolchain.dev

Especially here about why not just have lists.coretoolchain.dev rather
than have a glibc subdomain.  Plus isn't glibc on the mailing list
name and the domain redundant?
There is no rationale there at all; even the previous meetings notes
don't mention why.  Rather just the final choices.

This is a communication failure and a trust issue here.

>   * ACTION: Carlos to email the mailing list with proposals for discussion.
>
> --
> Cheers,
> Carlos.
>