Open Community (TDC) Meeting, Thursday 20 June 2024

[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.

[handrews]

• Use document/description/definition consistently (3.0.4) #3908 (how to use "description document" vs "description" vs "document")
• Reorganize and streamline form media type guidance (3.0.4) #3923 (I think this makes the form media type stuff much more clear, but it's complex enough to warrant looking at in the call)
• Remove examples folder [main branch] #3913 (I'm arguing that we need to have the examples integrated into the learn site and link to their rendered versions instead of linking into the learn GitHub repo, which will cause problems next time we re-organize repos)

[lornajane]

I'd like to revisit #3785 (the style guide/release tasks one), possibly every week until we release. Related: @handrews do we have the script Mike used to tidy up those heading anchors? Otherwise I will figure something out alongside the other markdown tidying I promised.

[miqui]

TODO: PR for the style guide.