Open Community (TDC) Meeting, Thursday 11 April 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	TDC
New issues needing attention	@OAI/triage

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

[lornajane]

Thanks to @duncanbeevers for the new weekly issue template!

[duncanbeevers]

Should OAI apply to FOSS Sustainability Fund?
https://www.opentech.fund/funds/free-and-open-source-software-sustainability-fund/

Eligibility

Release: Software has been released for at least 3 years.
Updates: The project pushes updates at least 4 times a year.
Development: Active coding towards the software has occurred in the last 2 years.
Userbase: The project has a substantial base of active users, if it is an app or other user-facing tool.
Keystone technology: OTF aims to support projects with many dependencies, to maximize long-term impact in the broader FOSS ecosystem.

[handrews]

@duncanbeevers We last released something in 2021... I don't think we can yet claim to push updates 4 times a year! It's more like once every 4 years, historically.

But it does look like they include open standards as well as software so in theory we could apply for it if the project releases more frequently. We'd also need to consider how this would interact with the OAI's relationship with the Linux Foundation.

[lornajane]

For the agenda (but sorry I won't be there myself this week)

• Who and how many people need to sign-off on a PR, exactly? #3581 to update wording for required approvals
• related: check that TSC members all have the correct team/ account membership so that their approvals appear as code owners.

Style clarification PRs #3684, #3685, and #3686

Prepare spec versions for release:

• Move Mutual TLS example from 3.1.0 to 3.1.1 to prepare for patch release #3696
• Backport improved OpenAPI specification intro paragraph from 3.1.1 #3697
• Backport password field instruction improvements #3698

[miqui]

Should OAI apply to FOSS Sustainability Fund? https://www.opentech.fund/funds/free-and-open-source-software-sustainability-fund/

Eligibility

Release: Software has been released for at least 3 years. Updates: The project pushes updates at least 4 times a year. Development: Active coding towards the software has occurred in the last 2 years. Userbase: The project has a substantial base of active users, if it is an app or other user-facing tool. Keystone technology: OTF aims to support projects with many dependencies, to maximize long-term impact in the broader FOSS ecosystem.

TODO: Stu look into it/ draft and bring up to BGB.

[miqui]

TODO: More org owners - ping Neil/Ron.

[miqui]

from @frankkilcommins - needs a token to publish - Neal? Ron?