Open Community (TDC) Meeting, Thursday 16 November 2023

[github-actions]

NOTE: This meeting is on Thursday at 9am - 10am PT

Zoom Meeting link: https://zoom.us/j/975841675. Dial-in passcode: 763054 - Code-of-Conduct

In order to give some more visibility into the topics we cover in the TDC meetings here is the planned agenda for the next meeting. Hopefully this will allow people to plan to attend meetings for topics that they have an interest in. And for folks who cannot attend they can comment on this issue prior to the meeting. Feel free to suggest other potential agenda topics.

Please submit comments below for topics or proposals that you wish to present in the TDC meeting

The agenda backlog is currently maintained in issue #2482

Topic	Owner	Decision/NextStep
Reports from Special Interest Groups	TDC
AOB (see below)	TDC
Approved spec PRs	TDC
New issues / PRs labelled review	@OAI/triage
New issues without response yet	@OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

[baywet]

proposing:

• final review and merge of - updates agenda workflow so it closes older agenda issues automatically #3435
• final review and merge of - adds a workflow to handle stale issues #3437

[frankkilcommins]

Discuss next steps on Workflows Specification and target TSC review and launch.

• Specification
• Working towards implementor draft

[mikekistler]

I'd like to add this to the agenda:

• Last call on "double-int" entry to format registry Add double-int to formats registry #3381

Also, can we push forward on #3390 ?

[lornajane]

Merged both #3435 and #3437 with thanks to @baywet . There's a follow on issue for us to adopt these, in #3452 .

[lornajane]

@frankkilcommins explained that the Workflows SIG is ready to release a version 1.0.0 implementer draft.

The spec needs more eyes on it and feedback, please. They are tracking feedback on the implementer draft issue OAI/Arazzo-Specification#49

We discussed whether it would be better to have a registry of supported types, and also reviewed some of the wording and design choices. Everyone agrees to go and read the specification and examples, and respond with questions and comments on what's there to support the SIG - deadline for comment is December 1st (so be quick!!).

There is no established process for releasing the specifications done by the SIG, and we need one. Proposal is for the SIG to own the sources of truth in markdown, following a similar process to the way OpenAPI works. We agreed that we should update our website spec.openapis.org to instead of saying "The Spec", update it to be "OpenAPI Specification" and "Workflows Specification" (other SIG outputs could appear here over time too). The rendering of the Workflows spec for this website is already in progress in OAI/Arazzo-Specification#42 and more help is needed.

[lornajane]

Good discussion about the double-int issue to be added to the types list - it does serve a need that is distinct from what we already have - this is merged.