Open Community (TDC) Meeting, Thursday 04 April 2024

[github-actions]

NOTE: 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.

Zoom: https://zoom.us/j/975841675, dial-in passcode: 763054

Participants must abide by our Code-of-Conduct.

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	TDC
New issues needing attention	@OAI/triage

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

[lornajane]

I'd like us to talk about preparing what we have for patch releases: #3626 (tl;dr we're going to do 3.0.4 and 3.1.1 at the same time, resetting our github processes at the point of release. There are a few decisions to make about what goes where before someone can do that work).

[lornajane]

Other topics that we could pick up:

• Update 3.1.1 Spec for Style Values #3684, Update 3.0.4 Spec for Style Values #3685 and Update 3.2.0 Spec for Style Values #3686 relate to style values updates (approval from @karenetheridge )
• 3.1.1 discriminator improvements #2618 has enough approvals to merge, any reservations? (the discriminator improvements)

[lornajane]

Made some changes to the monster checklists in #3626 to sync the versions and agreed that this work can now be applied more or less as listed.

[lornajane]

The style values need a small wording update and @mikekistler will update the pull requests to request that and we can revisit.

[lornajane]

We discussed more about our plans to improve the github workflow for developing and releasing specification changes. The information for that is in #3677 but tl;dr the next step is to make a pr documenting the new reality so we can agree what that should be and how to work towards it.

We also discussed that the specification is the priority but that we also need to work to sync up the schemas and maintain them alongside the specifications moving forward. This is an area that we can improve.