Open TSC Meeting, Thursday 27 August 2020

[MikeRalphson]

NOTE: This meeting is on Thursday at 9am - 10am PT - click for local time
Zoom Meeting link: https://zoom.us/j/975841675

In order to give some more visibility into the topics we cover in the TSC 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 TSC meeting

Topic	Owner	Decision/NextStep
Webhooks/callbacks/ReadOnly/WriteOnly	@webron	Clarify that JSON Schema annotations do not have explicit semantics defined by OpenAPI.
Revisit #1809 server variable enum guidance	@webron	Ron will turn SHOULD into MUST
Agree location / wording of 1.2 EOL notice, close #2312	@OAI/tsc	Define process for making spec versions obsolete/deprecated. Define what obsolete and deprecated means. Update specs with status. Add to development.md (Looking for volunteers to write something)
New issues / PRs labelled review	@OAI/triage
New issues without response yet	@OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

[lornajane]

We didn't have facilitators in the meeting today so we cut it short. Perhaps these agenda items could run into next week?

[MikeRalphson]

@lornajane have rolled over this issue to next week. Ta!

[Relequestual]

Topic: JSON Schema consuming tools / implementers forum.

A fair amount of work went into JSON Schema draft 2019-09 to enable the formal proposal for inclusion in OAS.
Now achived with 3.1, we (JSON Schema) need an approach to iliciting feedback on specific issues moving forward.

JSON Schema draft in progress (2020-something) includes numerous fixes and clarifications on the back of discussing with one or two implementers and consumers, but we want to make it possible for all those who have a stake in JSON Schema to be called to review and feedback on specific issues and pre releases.

Considering using github teams (which now includes discussions). Slack is emphermal.
Open to other suggestions.

[MikeRalphson]

Apologies @Relequestual I saw your comment but forgot to mention we had an additional agenda item. Can we discuss next week?

[Relequestual]

No problem. Yeah of course =]