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

[ralfhandl]

v3.2

• adds ABNF for path templating #4244

dev

• dev: build HTML from src/oas.md #4254

spec rendering

• Update ReSpec-rendered specification versions #4255

learn

• Fix example-tests workflow learn.openapis.org#119
  • Now with green examples-test workflow
• examples/v3.1/tictactoe fix security property name learn.openapis.org#116

[handrews]

@char0n posted PR #4257 to 3.0.4 fix a misleading error in one of the sections I added. It definitely can't be merged under our current policy, but there are two things I think we should consider:

• We should post errata for things that are truly misleading / wrong. This is just an error and someone could be quite confused. We should update the build script to put a link to errata in the appropriate existing version(s), just like RFCs are updated with a link to errata when errata exist.
• Another thing we could consider adding to the build script, again following IETF RFC precedent (and W3C precent as well, I think) is to add "obsoleted by" links pointing to the latest patch release. This way when someone ends up looking at 3.0.0, they see something that tells them they should be looking at 3.0.4 as it obsoletes (rather than enhances with new content) 3.0.0.
• I'd like to maybe wait a bit to see if other errors are found, and then I'd be in favor of doing a 3.0.5 that only fixes errors (nothing else, no clarifications, no explanations, just error fixes).

[baywet]

adding

• adds server url template abnf #4264

[lornajane]

We agreed it might be nice to add some errata. And also a paragraph in the markdown source for everything except the latest version to link people to the latest version.