CTI TAC Meeting Notes 2026-10-28

CTI TAC Meeting Notes 2026-10-28

[Carlos O'Donell]

Attendees:
  * Siddhesh Poyarekar (regrets)
  * Joseph Myers
  * Kris Borchers
  * David Edelsohn (regrets)
  
​Agenda:
  * Siddhesh: Going to work on the SBAR for MoinMoin migration to Sphinx and a gitolite repo.
   * Carlos: I asked Sid to use RFC/SBAR style so we can add it to the other 3 in the list.
  * Status of LF IT timeline for services including standing up the git pull mirrors.
   * Carlos: We asked LF IT to give an estimate on timeline for a horizontally scaled git pull mirror.
  * Kris: We need some help with a standard set of documents for:
   * Committee Rosters and chair(s) with term dates
    * This is going to live in the CTI git repo.
   * Election/voting records, election process definitions, etc
    * This is going to live in the CTI git repo.
   * Member Benefits and Onboarding docs (I assume these don't exist so I'll work on drafting them)
    * This is going to live in the CTI git repo?
   * Tool and infrastructure inventory
    * All tools and infra that supports the project(s), committee(s), communication, meetings, etc
     * gitolite.coretoolchain.dev:cti/keyring - CTI website keyring.
     * bbb.linuxfoundation.org - CTI uses for services.
    * Meeting recordings/transcripts if they exist
     * All by email: https://lore.kernel.org/cti-tac/, and recordings if they exist in httsp://bbb.linuxfoundation.org room for meetings and meeting recordings.
  * Carlos and Joseph agreed that keeping this in the git repo makes the most sense.
  * ACTION: Carlos to send Kris a writeup with more information for LF directed fund data.
  * Status of existing RFC requests.
   * [RFC] Using bugspray for updating glibc bugs in bugzilla? https://inbox.sourceware.org/libc-alpha/a1c0fb87-de0f-40da-a917-25520839d209@redhat.com/
    * Carlos: Do we need to finalize the update mechanism?
    * Joseph: Yes, a webhook is important to be able to update bugzilla right after the commit.
    * Carlos: OK, so webhook and timer are required.
   * [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/
    * Carlos: I expect we want the same outcome of webhook and timer.
    * Joseph: There was a question about providing information about who pushed the commit.
    * Carlos: LF IT noted that they have a transparency log for the kernel and can deploy for other projects too.
     * Sources: https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/post-receive-activity-feed
     * Reference: https://git.kernel.org/pub/scm/infra/transparency-logs/gitolite/git/1.git/commit/?id=4830331838dcc9b4eb65dbd511462264abcd5cf0
     * Two options: Simpler git-mailbomb improvement for post-receive hook information. Or deploy existing transparency log.
     * Joseph: Who pushed is the relevant thing to record.
     * With git-mailbomb we would loose this transparency unless we also deployed the transparency log.
     * ACTION: Carlos to respond on the thread about the transparency log question.
   * [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
    * Carlos: Still in progress in progress.
  * ACTION: Carlos to post RFC on horizontally scaled git pull mirror network.

-- 
Cheers,
Carlos.