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

[Andrea Pinski]

On Tue, Sep 22, 2026 at 11:34 AM Joseph Myers <josmyers@redhat.com> wrote:
>
> On Mon, 21 Sep 2026, Andrea Pinski wrote:
>
> > >   * 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?
>
> The subdomain facilitates different projects making different hosting
> choices in future (via DNS changes) if they wish without needing to make
> further changes to email addresses.
>
> The use of glibc in the list names is formally redundant, but we felt it
> was convenient for informal references to the lists in text, email client
> aliases, etc. to be able to talk about e.g. glibc-devel and have it
> unambiguous rather than just talking about devel@ which could refer to
> multiple projects.

So there was no consensus on the community members except for the ones
who were at the meeting?
Ok. I think that it is wrong to have separate domains.  The moving
part is a bad reason for having a seperate domain. If we have a
separate domain the redundant part is just broken and maybe better
names could come up with.

Also why NOT use a forge for patches instead of pushing for mailing lists?
Also why NOT just one email list?  Why 6 mailing lists?
What is the need for glibc-stable?
Maybe glibc-testresults should not be a mailing list but rather a
better way of collecting test results and displaying them?

>
> --
> Joseph S. Myers
> josmyers@redhat.com
>