Open Community (TDC) Meeting, Thursday 08 February 2024
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 | |
| 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
Process-y stuff:
- https://github.com/OAI/OpenAPI-Specification/issues/3509#issuecomment-1924641015 – proposal to delete about 20 labels (more to do, but this seems relatively non-controversial)
- We have a bunch of really old branches, some merged, some not but with no PR (and in some cases apparently owned by people who are no longer active with the project). This makes it a bit harder to see what branches are important for new contributors. (thanks to @baywet for bringing up how long the list is)
- Can we delete the merged ones? (I'm happy to do this)
- Can we encourage everyone else to do their work on forks instead so that the main repo branches are only the ones we need for process management? And then delete those branches?
PR merging:
- #3548 – re-submitted and now passing markdown checks! We've merged several other link bugfixes to main without updating the tags, so we should be able to merge this one too (fixing the tags is tracked in issue #3515)
- Arguably, the tags are fine where they are
- The content has not changed, so the tags still identify the correct content
- We just need the ones on main to have good UX == not broken links
- We shouldn't be using GitHub URLs as stable identifiers anyway, for many reasons
- #3554 – unblock multiple merges by always running checks with the js env from main
- #1911 – outdated, should probably be reworked in the framework of #3510; close and track in an issue?
- 3.0.4 versioning policy text. We should either do one of these or decide to not change the text even though it's flat-out wrong now and close both of them
- #3214
- #3219
- #3522 – agenda template changes for these meetings
- https://github.com/OAI/sig-moonwalk/pull/71
- #3551 – update SIG list and improve formatting and links
Perhaps an example to either just include in a patch release for 3.x.x or also a candidate for MoonWalk. #https://github.com/OAI/OpenAPI-Specification/issues/3550
Agenda: https://github.com/OAI/OpenAPI-Specification/issues/3523. Lets try to reach a consensus.