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 18 January 2024 #3496

Closed
github-actions bot opened this issue Jan 11, 2024 · 7 comments
Closed

Open Community (TDC) Meeting, Thursday 18 January 2024 #3496

github-actions bot opened this issue Jan 11, 2024 · 7 comments

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
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
Copy link
Contributor

baywet commented Jan 11, 2024

Adding to the agenda as proxy for @lornajane : Adding more people to the TSC

@baywet
Copy link
Contributor

baywet commented Jan 11, 2024

Adding this PR to the agenda #3497

@lornajane
Copy link
Contributor

(following on from the comment already added by @baywet ) We need to discuss adding people to :

  • TSC
  • maintainers (committers for the repository but not the spec itself)
  • triage (people who can help us manage the issues)

The discussion should take place when we have some sort of quoracy of TSC members present, if that's possible.

My personal feeling is that this should be driven more by GitHub activity and project participation than by meeting familiarity - not everyone is comfortable in the meeting, and the timezone is restrictive for who can be there.

@miqui
Copy link
Contributor

miqui commented Jan 16, 2024

Adding this PR to the agenda: #3413
How do we handle simple/low-hanging fruit PRs like this one?

@lornajane
Copy link
Contributor

#3440 fixes the SPDX identifier links - needs one more review @OAI/tsc

@darrelmiller
Copy link
Member

darrelmiller commented Jan 18, 2024

  • TSC has opened the nomination period for new TSC members. As per the governance process described here https://github.com/OAI/OpenAPI-Specification/blob/main/GOVERNANCE.md#2-adding-members-to-the-tsc If anyone is interested in being a TSC member, please contact one of the existing TSC members.
  • We need to work on the spec.openapis.org page to publish the output of SIGs. Frank/Darrel to collaborate.
  • Should we re-establish the Overlay meetings.
  • Suggestion to use CODEOWNERS to control access for all SIG repos. TSC to approve releases from workflows.
  • Propose change the Charter to replace the TOB with an process that involves the TSC Liasion bringing the issue to the BGB

@frankkilcommins
Copy link
Contributor

Work on OAI websites for publishing specs out of SIGs - OAI/Arazzo-Specification#117

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

5 participants