Open Community (TDC) Meeting, Thursday 31 October 2024

[github-actions]

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

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.

[ralfhandl]

Publish 3.1.1

• Update ReSpec-rendered specification versions #4159 - latest.html is now 3.1.1

New branch strategy

• Use "future-proof" glob pattern for markdownlint #4160
• Describe new spec branch and file layout #4154
• Define and document branch strategy for the spec, both development and publishing #3677

Schema development process

• schemas: add WORK-IN-PROGRESS placeholders, don't mention patch numbers, update terminology #4146
• main: move YAML examples to test fixtures, remove examples folder #4166
• Schema Publish workflow #4162
• gh-pages: skip dialect base & meta base #4164
• Define and document our schema publishing process #3715
• Schema development: main or branch, in parallel or at release time? #3716

[lornajane]

Discuss #4154

[handrews]

I'd like to come up with an overall strategy for what lives in which repository, branch, and directory, and why. I'm finding it hard to evaluate PRs making changes in these areas because they do not feel like they are part of a coherent strategy, which means I can't tell if they are aligned with our strategy or not. I would like to tackle any repository migration or splitting now, or at least ensure that our short-term changes are not going to be undone or taking in yet a different direction in the very-slightly-longer-term.

I know folks want to get on with 3.2 (as do I), but we're arriving at the end of the year, with the usual drop in participation for December (I do not expect to be available much during that month). I think it would be better to take the time to sort out our infrastructure fully now.

[lornajane]

• Remove 3.1.0-specific words from the README #4168 to remove references to 3.1 as being current from the README (there's a wider principle here about trying to make static files not contain point-in-time information, but mostly I just tried to make the file a little better)

[lornajane]

As requested by John, we'll create a new public repository to use for the "landscape" of paid members to support better automation of displaying those members on the website and keeping the list up to date. We'll need help though - @darrelmiller or @earth2marsh who may have enough access to create this repo!

[earth2marsh]

Repo created!