Open Community (TDC) Meeting, Thursday 27 February 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.

[mikekistler]

• Allow discriminator to be optional #4339

Note: I have updated this PR to make defaultMapping apply to cases where the discriminating value is not explicitly or implicitly mapped, in addition to the original case of no discriminating property.

[ralfhandl]

Schema development & publishing

• dev: sync with main #4383 - can we document the everyday/expected merge workflows? These are hard to review as pull requests and once a change is accepted on a "left hand branch" (according to the diagram in the contributing file), they don't need more signoff.
• 3.2: update from dev branch #4375 - merge after dev: sync with main #4383
• v3.1-dev: update from dev and resolve conflicts #4374

spec.openapis.org

• gh-pages: show OAS 2.0 schema #4366

Style guide

• style guide: no requirements in "Examples" sections #4382

[baywet]

I'd like to talk about max/min and data types

[lornajane]

We talked a bit about moving changes from main to dev, and from dev to specific dev versions, and how to effectively review a pull request in this situation where it is difficult to verify that all incoming changes are appropriate and already approved. There's some suggestion that changes that go to main and then need to go to dev should be immediately applied to both branches. We have some tooling options.

[lornajane]

• sync up changes to v3.2.0 schema definition to v3.2-dev branch #3400 to sync 3.2 schema with the changes in the spec is looking for someone to work on it and check that the schema has the changes in place as expected. I'll add this to next week's agenda as a followup

[lornajane]

After we talked about how we could identify the security use cases, @mikekistler created an issue on the learn site, go there and comment with what you use in your own API descriptions: OAI/learn.openapis.org#126