Skip to content

Open Community (TDC) Meeting, Thursday 05 May 2022 #2923

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

Closed
github-actions bot opened this issue May 2, 2022 · 1 comment
Closed

Open Community (TDC) Meeting, Thursday 05 May 2022 #2923

github-actions bot opened this issue May 2, 2022 · 1 comment

Comments

@github-actions
Copy link
Contributor

github-actions bot commented May 2, 2022

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 May 2, 2022
@darrelmiller
Copy link
Member

  • What should the next version of the spec be? A major or minor release?
  • Do we want to do a major release that would allow a significant restructuring
  • What would major restructuring enable? Better reuse. Current paths design is limiting us when identifying operations. Simplifications? rpc styles?
  • Could this group do things that help 3.1 adoption? Should we?
  • Targeting 4.0, doesn't necessarily prevent us from later deciding to create a 3.2 with non-breaking change.
  • What would be the big problems that 4.0 could solve?
  • See issue Big thoughts for 4.0 #2925

@webron webron closed this as completed May 9, 2022
@webron webron unpinned this issue May 9, 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

2 participants