Meeting Minutes - Office Hours for CTI - 2026-10-23

[Carlos O'Donell via Gdb <gdb@sourceware.org>]

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

RFCs:
[RFC] Using bugspray for updating glibc bugs in bugzilla?
https://inbox.sourceware.org/libc-alpha/a1c0fb87-de0f-40da-a917-25520839d209@redhat.com/

[RFC] Using git-mailbomb as post-commit VCS to email system for glibc-cvs emails?
https://inbox.sourceware.org/libc-alpha/5d2ef95d-94c4-40aa-83a7-84dc5f376e2b@redhat.com/

[RFC] Using project and service specific DNS end points to support flexible deployments.
https://inbox.sourceware.org/libc-alpha/8e167d49-86c5-45ba-841d-f9f74151d596@redhat.com/T/#u

Posting across the project mailing lists since some developers had questions and are only subscribed on some lists.

​Agenda:
  * Discussed the hyphenated name option in the recently posted RFC and why it was rejected: https://inbox.sourceware.org/libc-alpha/8e167d49-86c5-45ba-841d-f9f74151d596@redhat.com/T/#u
   * No further reasons except those already listed.
   * Developers can respond to the RFC with questions on the list.
  * Noted that https://sourceware.org/pipermail/libc-alpha/2026-October/181375.html post form Sachin is missing public-inbox.
   * Filed https://sourceware.org/bugzilla/show_bug.cgi?id=34879 for infrastructure discussion about missing post.
   * Noted: https://sourceware.org/bugzilla/show_bug.cgi?id=32977 is still outstanding for bypass of moderation into public-inbox archives.
  * Sachin posted v2: https://sourceware.org/pipermail/libc-alpha/2026-October/181417.html based on previous feedback.
   * Carlos: I'll review Sachin's work on list and the regular expressions we need.
  * Currently 3 RFCs in progress, with 1 more RFC coming.
  * Carlos: I will post the RFC on horizontal git scaling and the benefits it brings. Including git pulls from such a system. This RFC can be implemented right away with CTI and LF ITs help.
  * David: Developer convenience around 3level email? glibc-devel@lists.glibc.coretoolchain.dev, or simpler alias?
  * Siddhesh: You mean glibc-devel@glibc.coretoolchain.dev?
  * Carlos: Simplest being glibc-devel@coretoolchain.dev as an alias? Which maps from libc-alpha@coretoolchain.dev... so it could be libc-alpha@coretoolchain.dev?
  * Carlos: The first action item for LF IT is to setup the scaled mirror network?

-- 
Cheers,
Carlos.