You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Open Community (TDC) Meeting, Thursday 27 February 2025 #4373
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.
Note: I have updated this PR to make defaultMapping apply to cases where the discriminating value is not explicitly or implicitly mapped, in addition to the original case of no discriminating property.
dev: sync with main #4383 - can we document the everyday/expected merge workflows? These are hard to review as pull requests and once a change is accepted on a "left hand branch" (according to the diagram in the contributing file), they don't need more signoff.
We talked a bit about moving changes from main to dev, and from dev to specific dev versions, and how to effectively review a pull request in this situation where it is difficult to verify that all incoming changes are appropriate and already approved. There's some suggestion that changes that go to main and then need to go to dev should be immediately applied to both branches. We have some tooling options.
After we talked about how we could identify the security use cases, @mikekistler created an issue on the learn site, go there and comment with what you use in your own API descriptions: OAI/learn.openapis.org#126
Activity
mikekistler commentedon Feb 20, 2025
Note: I have updated this PR to make defaultMapping apply to cases where the discriminating value is not explicitly or implicitly mapped, in addition to the original case of no discriminating property.
ralfhandl commentedon Feb 20, 2025
Schema development & publishing
spec.openapis.org
Style guide
baywet commentedon Feb 27, 2025
I'd like to talk about max/min and data types
lornajane commentedon Feb 27, 2025
We talked a bit about moving changes from main to dev, and from dev to specific dev versions, and how to effectively review a pull request in this situation where it is difficult to verify that all incoming changes are appropriate and already approved. There's some suggestion that changes that go to main and then need to go to dev should be immediately applied to both branches. We have some tooling options.
lornajane commentedon Feb 27, 2025
lornajane commentedon Mar 5, 2025
After we talked about how we could identify the security use cases, @mikekistler created an issue on the learn site, go there and comment with what you use in your own API descriptions: OAI/learn.openapis.org#126