Skip to content

Open Community (TDC) Meeting, Thursday 24 September 2026 #5554

Closed

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. miqui commented on Sep 21, 2026

    @miqui
    Contributor

    Agenda items

    • a new SAF requires its own sig repo. Also, how do we decide on a new SAF/SIG?
    • Lifecycle SAF draft
  2. miqui commented on Sep 21, 2026

    @miqui
    Contributor

    I (@miqui) can run the TDC call if no one else volunteers. Not a problem.

  3. baywet commented on Sep 22, 2026

    @baywet
    Member

    adding an agenda item upon @lornajane's request: build infra updates, we need to review how far we've propagated the last release (3.2.1)

    @lornajane edit: There's a stuck pull request here that I'm not sure does the right thing #5550

    @handrews edit: The fix for that stuck pull request is #5550

  4. lornajane commented on Sep 22, 2026

    @lornajane
    Contributor

    Spec rendering question for the Overlays specification: where is this new Abstract section coming from and does anyone know how to remove it? OAI/spec.openapis.org#138

  5. miqui commented on Sep 23, 2026

    @miqui
    Contributor

    Discuss decision related to OAI/spec.openapis.org#64. from last TDC. Lets close the loop on this.

    @lornajane edit: To add some wording context rather than just a pasted PR link, this point relates to the dates in the schemas and I think we should discuss this more if @karenetheridge is available (or in a future meeting), there are a few things here:

    • the idea was to avoid republishing the same assets multiple times where the only change was the version placeholder value
    • if we haven't published something yet, we should be able to publish a whole set of things with a version placeholder of our choosing, I think the autogenerated dates are part of the problem and agree they're not useful.

    (this is the second item I edited of someone else's, someone tell me if this is annoying)

  6. pinned and unpinned a comment on Sep 23, 2026
  7. handrews commented on Sep 24, 2026

    @handrews
    Member

    @miqui @karenetheridge the way SAFs will add even more schemas to the set might be an argument in favor of consistent dates across the board, where OpenAPI publishes schema sets with the most up-to-date SAFs at the time of publication, and users who want to mix newer and older SAFs in an unusual way would be the only ones who need to make their own custom schemas.

  8. SensibleWood commented on Sep 24, 2026

    @SensibleWood

    I won't be on the call today so just dropping this here:

    • Thanks @handrews and to people from OIDF & OBL for comments on the "sense check" API Security PR.
    • Still planning to open "official PR" by end of tomorrow BST.
    • Can you please discuss best place for this proposal to be added as PR:
      • As it does affect OpenAPI I would say that on the main repository is the best place for it.
      • @handrews mentioned on sig-security as an alternative, as this is proposal for API security.
      • Please discuss and report back, and I am happy to go with the majority.

    Thanks all.

  9. mikekistler commented on Sep 24, 2026

    @mikekistler
    Contributor

    @SensibleWood We discussed your topic and agreed that the sig-security repo is the right place.

  10. unpinned this issue on Oct 8, 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