Open Community (TDC) Meeting, Thursday 25 January 2024

[github-actions]

NOTE: This meeting is on Thursday at 9am - 10am PT

Zoom Meeting link: https://zoom.us/j/975841675. Dial-in passcode: 763054 - Code-of-Conduct

In order to give some more visibility into the topics we cover in the TDC meetings here is the planned agenda for the next meeting. Hopefully this will allow people to plan to attend meetings for topics that they have an interest in. And for folks who cannot attend they can comment on this issue prior to the meeting. Feel free to suggest other potential agenda topics.

Please submit comments below for topics or proposals that you wish to present in the TDC meeting

The agenda backlog is currently maintained in issue #2482

Topic	Owner	Decision/NextStep
Reports from Special Interest Groups	TDC
AOB (see below)	TDC
Approved spec PRs	TDC
New issues / PRs labelled review	@OAI/triage
New issues without response yet	@OAI/triage

/cc @OAI/tsc Please suggest items for inclusion

[baywet]

Adding to the agenda: since we have automation to open/close agenda issues, should we close and unpin this one? #2482
It seems that people are adding agenda items over there and we miss those agenda items because of it.

[lornajane]

We've got a few PRs that need a TSC member to review/merge:

• URL update Fixed link to SPDX identifiers #3440
• media type example fix Fix JSON media type example #3434

[handrews]

I agree with @baywet , let's close #2482 and continue our current process of adding items on each week's meeting agenda issue. I had no idea that backlog issue was even there (even though it's visibly pinned). While sometimes we have to keep adding the same thing across multiple weeks, that's not a huge burden and it ensures that the agenda is relevant to people who plan to show up for the call.

[miqui]

Adding to agenda: #3413 , #3518, #3509, #3508 (perhaps this should be discussed in Moonwalk Sig) ?

[lornajane]

Quick summary of the meeting (as best I remember it, more comments/additions are welcome):

• TSC is currently open for nominations of new members, the details are in the #spec channel on slack but tl;dr talk to a current @OAI/tsc person to be considered
• Workflows SIG is ramping up for their 1.0 release, with a few issues still to tackle. Everyone welcome at their meetings.
• Moonwalk SIG is getting up and running (and testing the new meetings platform), starting on Tuesday at 9am Pacific time/18:00 CET - no calendar invite yet so block your diaries
• Questions about the new meetings platform, is it compulsory to register for meetings, can we run public meetings that anyone can join?
• After discussion about the long-running agenda item that we often miss new items from, we closed and unpinned Community (TDC) Meeting Agenda backlog #2482 - @lornajane will update the agenda template accordingly.
• We merged Fixed link to SPDX identifiers #3440 to fix a link
• Fix JSON media type example #3434 is either the wrong file or the wrong branch so it needs an update
• Generalize description of password data type #3413 is a good idea but the wording needs work - hoping the author will revisit

We also discussed some existential questions around how we manage the project and direct community members to discussions within 3.x and for 4.x

• Define process for issues addressed in Moonwalk #3508 could use more feedback on the various scenarios, we have a tag for things that have already moved: we will signpost the new discussion, tag and close. What to do with things that could or should move is still under discussion.
• Audit, reorganize, and document labels (and probably also milestones) #3509 is a work in progress and @handrews will keep going with it and come back to us with some recommendations on tags and processes, etc
• Define criteria for filing/closing issues vs discussions #3518 needs your input!! What criteria should we use to identify issues that can be closed?

This last item led into some discussion of setting the direction for potential 3.2 and 3.3 releases, to help us identify which issues may or may not fit those plans. These releases can be used to capture corrections/updates/clarifications of the existing specs, add quality of life improvements that don't require a lot of tooling updates, and also offer features that ease the upgrade path. Painless upgrades is a key feature of the 4.0 goals.

There's still some "governance debt" in the project so we will open our meetings with housekeeping in future (@lornajane is updating the issue template already so will put this there too).

[earth2marsh]

Zoom recording for those who couldn't attend.

[lornajane]

Proposed agenda update is in #3522 - and I edited next week's template to match