Open Community (TDC) Meeting, Thursday 15 May 2025

[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.us/j/975841675, dial-in passcode: 763054

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

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

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

[lornajane]

Planning to revisit the 3.2 and 3.3 plans: #4210

[ralfhandl]

Looking at the open issues planned for 3.2.0 I don't see anything urgent and think we are ready to publish after

• merging PR v3.2: $self field (Alternative Approach) #4556 and
• an editorial check of all changes since 3.1.1

We don't have a champion for the security topics, and I'd rather deprecate the half-hearted XML stuff and add full XML Schema support in Moonwalk.

[baywet]

If we have time #4585

[lornajane]

The general consensus is that we have some GREAT stuff in the 3.2 branch and we should release when we can.

Our community, especially people building tools against the specifications, need as much information as we can give them, as soon as we can give it. I'll start to outline the main points somewhere in the next week or so and we can take it from there.

[handrews]

Looking at the open issues planned for 3.2.0 I don't see anything urgent and think we are ready to publish after

I have three PRs nearing completion that are closely related to already-merged PRs. Please check with me before releasing.