Meeting minutes - Office hours for CTI - 2026-09-18
Discussion on glibc mailing list consolidation continues with pointers to past discussions.
Carlos O’Donell references previous discussions about consolidating glibc mailing lists, including an RFC from May 2026 and another about closing specific lists. This continues the conversation sparked by questions about the necessity of multiple mailing lists.
- proposer
Recalls prior on-list discussions regarding the number and usage of glibc mailing lists, specifically referencing an RFC from May 2026 and another concerning list closures.
“We had an on-list discussion *specifically* about this topic in May 2026. "[RFC] How many mailing lists does glibc need or use? Closing 4 lists." https://inbox.sourceware.org/libc-alpha/932cc126-4a9a-4507-9c26-2c13524100d0@redhat.com/ I received feedback from Collin, and Arjun. Then again to discuss closing some lists: "[RFC] Closing libc-locales and glibc-bugs-regex mailing lists at the end…”
In Details
This is a follow-up to discussions about the number of mailing lists used by the glibc project. It references past RFCs and user feedback related to consolidating or closing lists like glibc-stable, libc-alpha, glibc-bugs-regex, and libc-locales, aiming to streamline communication.
- glibc-stable
- A mailing list for glibc, likely for stable branch updates and discussions.
- libc-alpha
- A mailing list for glibc, probably for development and pre-release discussions.
- RFC
- Request For Comments: a standard way to propose a change or new idea in open source projects, soliciting feedback.