Skip to content

Open Community (TDC) Meeting, Thursday 09 July 2026 #5416

Description

@github-actions

Weekly meetings happen on Thursdays at 9am - 10am Pacific

This agenda gives visibility into discussion topics for the weekly Technical Developer Community (TDC) meetings. Sharing agenda items in advance allows people to plan to attend meetings where they have an interest in specific topics.

Whether attending or not, anyone can comment on this issue prior to the meeting to suggest topics or to add comments on planned topics or proposals.

Meetings take place over Zoom: https://zoom-lfx.platform.linuxfoundation.org/meeting/92028872923?password=9ddcd542-4f5b-484a-a254-e00d8a8b15d8

Accessibility & Etiquette

  • Participants must abide by our Code-of-Conduct.

  • Meetings are recorded for future reference, and for those who are not able to attend in-person.

  • We invite you to feel comfortable to challenge any language or behaviour that is harmful or not inclusive during this meeting.

  • We look forward to your participation, but please consider these acts of etiquette:

    • Remain on mute when not speaking to prevent interruptions.
    • Blur your background to reduce visual distractions.
    • Use the Zoom meeting "Raise Hand" feature to notify the group when you wish to speak.
Blur My Background Raise Hand
Screenshot of Zoom UI showing the 'Stop Video' and 'Blur My Background' control Screenshot of Zoom UI showing the 'Reaction' and 'Raise Hand' control

Agenda Structure

Topic Owner Decision/NextStep
Intros and governance meta-topics (5 mins) TDC
Reports from Special Interest Groups (5 mins) SIG members
Any other business (add comments below to suggest topics) TDC
Approved spec PRs @OAI/tsc
Active Projects @OAI/openapi-maintainers
New issues needing attention @OAI/triage
Identify next week's meeting host (2 mins) All Comment on next week's agenda

/cc @OAI/tsc please suggest items for inclusion.

Activity

  1. pinned this issue on Jul 2, 2026
  2. handrews commented on Jul 6, 2026

    @handrews
    Member

    Build infrastructure for SAFs and to eliminate the endless flood of dependabot updates and syncs in this repository.

    We're suddenly getting a lot of security-related contributions, so we should decide ASAP if we are moving existing security content out to the sig-security repo and the new Security SAF specification. I am strongly in favor of doing so, as it will force us to work through the mechanics of modularizing the specification even before any new SAFs stabilize. It will also make it more clear to potential contributors what is going on so we won't have to re-explain it as much.

    For the security contributions themselves, what we should advise somewhat depends on where @SensibleWood is with his proposal:

  3. miqui commented on Jul 6, 2026

    @miqui
    Contributor

    If we have time, this post on agents and APIs, specially item 7 provides an interesting community feedback.

  4. unpinned this issue on Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions