Open Community (TDC) Meeting, Thursday 21 September 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
Process for merging SIG work	TDC
Evaluating context of referenced fragments	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

[lornajane]

Can we discuss how approved changes to the special interest projects get merged? Who has commit access on the workflows / overlays / other projects? And how do people step in or out of those responsibilities? Is this written down somewhere (I didn't find it yet)?

Very specifically, could someone please either merge or close OAI/Overlay-Specification#18 ?

[darrelmiller]

@lornajane Yes. That would be a good topic. I had not seen that there had been a sign-off on that PR. I just merged it. I've been waiting forever to be able to merge that :-)

The only problem I see is that currently we are not going to have quorum of TSC members today, so we probably won't be able to make a binding decision.

[duncanbeevers]

Separation-of-concerns:

• linting
• validation
• normalization

openapi-ts/openapi-typescript#1344

[handrews]

@duncanbeevers it's particularly notable that they characterize "hinting" (which appears to be the sort of parse-out-from-the-fragment parsing that I said would be complex and problematic) as a "mistake." Assuming I'm understanding that correctly, they seem to have arrived at the same opinion I hold regarding that process, except after implementing a fair amount of it. It also contradicts the "naive" approach that you were championing.

I have never actually looked at what ReDocly does (I was trying to avoid mimicking any particular tool with OASComply)