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 16 May 2024 #3794

Closed
github-actions bot opened this issue May 9, 2024 · 2 comments
Closed

Open Community (TDC) Meeting, Thursday 16 May 2024 #3794

github-actions bot opened this issue May 9, 2024 · 2 comments

Comments

@github-actions
Copy link
Contributor

github-actions bot commented May 9, 2024

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.us/j/975841675, dial-in passcode: 763054

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
Screenshot of Zoom UI showing the 'Stop Video' and 'Blur My Background' control Screenshot of Zoom UI showing the 'Reaction' and 'Raise Hand' control

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

/cc @OAI/tsc please suggest items for inclusion.

@github-actions github-actions bot pinned this issue May 9, 2024
@handrews
Copy link
Member

handrews commented May 14, 2024

@lornajane
Copy link
Contributor

We did not cover a lot of ground this week, but we had some really good discussions on deeply technical topics.

  • Clarify interoperable parsing expectations (3.0.4 port of #3732) #3772 hinges on the intention (which isn't clearly written) of whether references are supposed to be context-dependent or not. In 2.0, references inlined the target content. In 3.1, the reference behaviour is clearer - but in 3.0, it's not clear. This matters because while we don't want to spend a lot of time on small (but impactful!) details of 3.0, a compliance tool is being created for 3.0 and these details are important.
  • Clarify allowEmptyValue further #3798 discussion concluded with the idea that if the field was called disregardEmptyValues, it would make more sense. The idea is that while in its default state (allowEmptyValues is false) an empty value is an empty value and should be handled as empty, when allowEmptyValues is true then the empty value should be ignored by the server. The use case is browsers sending all fields where some of them are empty.
  • [new] scripts/update-schema-id #3790 is a contribution aimed at helping us move forward with the schemas. However it's written in Ruby which isn't currently a tech stack used in the project. We've asked if it can be changed since adding more and more technical dependencies and requirements to the project doesn't help people to get started or participate.
  • We did merge MAINTAINERS for 3.0.0 #3808 after checking the details of past maintainers
  • We discussed the merits of adding defaults to parameters (currently this is only on schemas) Schema/Parameter default value sig-moonwalk#112 . It's not clear how this should look and since we don't have support in 3.x yet, this issue has been moved to Moonwalk to consider. When that spec takes shape, we'll be evaluating which of those solutions can be adopted by minor or patch updates in the 3.x branch.

@github-actions github-actions bot unpinned this issue May 30, 2024
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