Open Community (TDC) Meeting, Thursday 28 March 2024

[github-actions]

NOTE: 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.

Zoom: https://zoom.us/j/975841675, dial-in passcode: 763054

Participants must abide by our Code-of-Conduct.

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	TDC
New issues needing attention	@OAI/triage

/cc @OAI/tsc please suggest items for inclusion.

[handrews]

• Update GOVERNANCE.md #3669
• Replaced a longer draft features section with a proposed proposal process #3673
• Define and document branch strategy for the spec, both development and publishing #3677
• Typos: "Path Item Object" -> "Path Item Objects"
  • small typo fix #3674 (3.1.1) - approval from @handrews and @lornajane
  • small typo fix #3675 (3.2.0) - approval from @handrews and @lornajane

[mikekistler]

If there is time it might be worth discussing this one:

• Update Style Values and Style Examples for consistency #3682

[baywet]

As requested on the call, here is the source of the agenda initial post

[lornajane]

https://github.com/OAI/OpenAPI-Specification/projects?query=is%3Aopen <-- list of open projects

[lornajane]

Here are the points I jotted down in the meeting, please add any additional comments or observations that you want to capture from the meeting.

Our meeting agenda has a screenshot of the meeting guidelines, no alt text. @duncanbeevers offered to update our template to put the information into words and a picture.

A few updates from the SIGs this week:

• the travel SIG has a real live example going on in the wild, it's exciting
• the outreach group and the technical group need to overlap more. Happy to see Stu here this week, and we'd like to encourage every regular attendee of this meeting to get to the Monday one when they can.
• Workflows SIG is in the process of being renamed, please look out for and vote on polls on slack.
• Moonwalk has been discussing dynamic schemas
• Overlays has a lively discussion about using a replace operation in addition to add and remove

We approved #3669 to outline the recent changes to the governance processes.
Also approved: #3673 to update our guidelines for proposing new additions to the spec

We have a tangle of things going on with releases and versions and processes and branches and specs and registries and schemas, all outlined in #3677 . The points to note from the discussion:

• the markdown specification is the version of truth, and TSC has that as our focus. Since the schemas are widely used by the community and are expected to be dependable, we need to work more on those when we can.
• we agreed to move towards releases in the current branching setup, and then to create new branches and processes with a "clean slate". The releases will have the specs in scope, but no schema or registry changes.
• after releases of specs, we will proceed to work on publishing those in HTML
• the schema updates and publishing process (currently not working and not well understood) will follow
• registries after that as they are more independent.

The group also discussed #3682 relating to how we use style, @karenetheridge has given our feedback that some parts of the changes aren't a good fit, so we'll look for those pull requests to be updated.

We didn't look at it in the meeting but we commented that #2618 for the discriminator improvements has had updates and is ripe for being reviewed again.

Also if anyone has bandwidth, the projects (https://github.com/OAI/OpenAPI-Specification/projects?query=is%3Aopen) have a curated list of issues and we'd appreciate whatever help fits your skills and availability!

[duncanbeevers]

Thank @baywet and @lornajane.
The PR with these proposed changes to the Agenda Template is here: #3689