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

[Siddhesh Poyarekar]

On 2026-09-21 13:58, DJ Delorie wrote:
>> Why have a glibc subdomain?
> 
> To make room for gcc.*, binutils*, gdb.*, 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?
> 
> This assumes that all projects want to have their project name in
> their mailing list names.  For example, gcc might want
> "patches@lists.gcc.*" or "patches@gcc.*"
> 
> I would not be opposed to renaming our mailing lists to be
> "foo@glibc.*" instead of "glibc-foo@.*" if we're moving them *at all*.
> 
> I don't think we need the "lists." part in the mailing list name - MX
> records can redirect glibc.* to lists.glibc.* unless there are
> technical reasons to not send local non-list mail (there shouldn't be
> any IMHO) through the list server host.

The base reasoning here is that we'd like the infrastructure for 
projects to be independent and easy to move independently.

Sid