Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Community (TDC) Meeting, Thursday 31 March 2022 #2904

Closed
github-actions bot opened this issue Mar 28, 2022 · 1 comment
Closed

Open Community (TDC) Meeting, Thursday 31 March 2022 #2904

github-actions bot opened this issue Mar 28, 2022 · 1 comment

Comments

@github-actions
Copy link
Contributor

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

F10B5460-B4B3-4463-9CDE-C7F782202EA9

The agenda backlog is currently maintained in issue #2482

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

/cc @OAI/tsc Please suggest items for inclusion

@webron webron pinned this issue Mar 28, 2022
@webron
Copy link
Member

webron commented Mar 31, 2022

Meeting notes:

  • Received updates from several SIGs - Travel, Workflows, Overlays.
  • Shared that we have a new common calendar for OAI-related meetings. The information can be found at this repo's README.
  • We also have a new community repo.
  • Merged a couple of PRs from @namdeirf.
  • Discussed and decided to close Integer enum with named items #681 (explanation in issue).
  • Discussed Support for multiple $refs inside a single object #417: the ticket seems to refer only to multiple references under the paths property. In past meetings, we've already decided to change the behavior of $ref under paths, but making it a single reference or defined paths, but not both. The idea of having multiple $refs is to enable splitting a large document into multiple ones. It's clear that supporting multiple references is a challenge due to potential conflicts (and this is somewhat different than schema definitions). There seems to be a general consensus that this can be solved by internal solutions and preprocessing (so no change in spec is needed). That said, we opened it up to a broader discussion about API definition file sizes and the complexity of navigating such files (also noted: navigating through referenced files is not simple). No resolution was made.

Meeting Recording:
https://zoom.us/rec/share/8MlifknY_lXIxCbxMyjLIk3U0ec-Z7kMIJ4rb1Nfryndq_5K27U7dl1Cnht1NULy.MjwDlVZtPfUCi_VB

@webron webron closed this as completed Apr 4, 2022
@webron webron unpinned this issue Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant