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

• Patch Releases: referencing and identification DONE! 🎉
• Patch Releases: parameters and encoding
  • Appendix for percent-encoding concerns (3.0.4) #3859
• Patch Releases: other
  • Clarification on the purpose of the API license? #726 (is this something that goes in the patch release?)
  • does the XML "namespace" field allow URI fragments? #3263 (this was probably an error of "absolute URI" when "non-relative URI" was intended – OK to fix or defer to 3.2 as it would allow values not allowed by the current wording?)
  • RFC 7231 has been obsoleted by RFC 9110 #3800 (should we update obsoleted RFCs in patch releases?)
• GitHub pages site (spec.openapis.org):
  • Should we-organize our GitHub pages to a separate repo (by way of a directory on main)? #3717 (@frankkilcommins has requested that we make it a separate repo instead of a directory here; I am in favor so that the spec-specific part is clearly in each spec repo, and the common part is not in any one spec's repo)
  • Move gh-pages into main branch #3868 (migrating to a directory, so if we decide "no" to the above question, we should see if we can approve this)