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

[miqui]

• Agenda item: Clarification on the purpose of the API license? #726

[handrews]

• Clarify interaction of format: byte and Content-Transfer-Encoding header definition #3929
• Should we update references to other specs? There are now three of these issues:
  • YAML JSON Schema is not enough for roundtrip-safe #2951 (comment) (change guidance to use YAML RFC)
  • RFC 7231 has been obsoleted by RFC 9110 #3800 (update for one RFC obsoleting another)
  • draft-bhutton-json-schema-00 is deprecated , Should the specification point to the 01 ? #3934 (update for one draft replacing another)
  • We did already replace some OIDC drafts with RFCs or other final specifications in the patch releases
• Other 3.0.4/3.1.1 issues requiring review
• @LasneF has asked about clarifications to request matching

[LasneF]

• 3.2 / 3.1 ? / 3.0 draft-bhutton-json-schema-00 is deprecated , Should the specification point to the 01 ? #3934

[miqui]

Updated is not warrant a patch change. will review RFCs in minor versions (no gaurantees)
Open to receive feedback from the community.