Meeting Minutes - Office Hours for CTI - 2026-05-29

[Carlos O'Donell]

​Agenda:
  * Raised for awareness the discussion "[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/
  * Carlos: Also spoke with DJ Delorie about keeping libc-stable. Particularly when trying to distinguish between stable release branch patch review and master development review.
  * Joseph: Keeping libc-stable seems to make sense.
  * Carlos: Noted that we have libc-locales and glibc-bugs-regex that we could close.
  * Sachin: Have used libc-stable once or twice.
  * Carlos: Yes, libc-stable is used for backporting.
  * Carlos: Looks like we could close libc-locales and glibc-bugs-regex.
  * Carlos: Need to review...
   * gnu.org pages for libc for references to the mailing lists.
   * sourceware.org pages for libc for references to the mailing lists.
   * glibc manual for references to the mailing lists.
   * bugzilla auto-assignment to the mailing list.
   * Adjust those references to the new location.
   * Then close and mark the lists as archived.
  * Carlos: Recommended timeline? Couple of weeks.
  * Carlos: I'll say end of June to close the lists.
  * Sachin: Do we have any dates for the transition plan?
  * Carlos: We just finalized an updated SOW with LF IT that is the same as the previous 2024 SOW, and next steps are to start public discussions about service transitions and dates.
  * Carlos: I'll email the list to notify of the closure of the mailing lists.
  * We discussed a regular mailing list names.
  * Joseph: Pick names that make logical sense.
  * Joseph: glibc-commits, glibc-devel, glibc-bugs, etc.
  * David: GCC has a mailing list for a couple of the languages, but primarily the gcc mailing list is gcc@gcc.gnu.org, and gcc-patches@gcc.gnu.org.
  * Would we want to split the lists to be per-project?
  * Separable DNS for lists? glibc.lists.coretoolchain.dev
  * It would end up being glibc-devel@glibc.lists.coretoolchain.dev or devel@glibc.lists.coretoolchain.dev? "devel@lists.glibc.coretoolchain.dev"
    e.g. lists.glibc.coretoolchain.dev
         glibc.coretoolchain.dev
         git.glibc.coretoolchain.dev
         git.gdb.coretoolchain.dev
         git.binutils.coretoolchain.dev
         lists.binutils.coretoolchain.dev
         ...
-- 
Cheers,
Carlos.