OAI / OAI/OpenAPI-Specification
Open Community (TDC) Meeting, Thursday 28 May 2026
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 31.2k
- Forks
- 9.2k
- Avg merge
- 6h 37m
- Merged PRs (30d)
- 27
Description
Weekly meetings happen on Thursdays at 9am - 10am Pacific
This agenda gives visibility into discussion topics for the weekly Technical Developer Community (TDC) meetings. Sharing agenda items in advance allows people to plan to attend meetings where they have an interest in specific topics.
Whether attending or not, anyone can comment on this issue prior to the meeting to suggest topics or to add comments on planned topics or proposals.
Meetings take place over Zoom: https://zoom-lfx.platform.linuxfoundation.org/meeting/92028872923?password=9ddcd542-4f5b-484a-a254-e00d8a8b15d8
Accessibility & Etiquette
-
Participants must abide by our Code-of-Conduct.
-
Meetings are recorded for future reference, and for those who are not able to attend in-person.
-
We invite you to feel comfortable to challenge any language or behaviour that is harmful or not inclusive during this meeting.
-
We look forward to your participation, but please consider these acts of etiquette:
- Remain on mute when not speaking to prevent interruptions.
- Blur your background to reduce visual distractions.
- Use the Zoom meeting "Raise Hand" feature to notify the group when you wish to speak.
| Blur My Background | Raise Hand |
|---|---|
Agenda Structure
| Topic | Owner | Decision/NextStep |
|---|---|---|
| Intros and governance meta-topics (5 mins) | TDC | |
| Reports from Special Interest Groups (5 mins) | SIG members | |
| Any other business (add comments below to suggest topics) | TDC | |
| Approved spec PRs | @OAI/tsc | |
| Active Projects | @OAI/openapi-maintainers | |
| New issues needing attention | @OAI/triage | |
| Identify next week's meeting host (2 mins) | All | Comment on next week's agenda |
/cc @OAI/tsc please suggest items for inclusion.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This issue is a Technical Developer Community meeting agenda rather than a code task. Read the agenda table and existing comments first; a contribution would be a relevant topic or comment added before the meeting, with completion shown by its inclusion in the discussion.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100