Open Community (TDC) Meeting, Thursday 07 March 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.

[AxelNennker]

I would like to talk about Add OAuth2 metadata url.
Especially which document and branch this change might go into.
I created a PR but that was for the wrong branch and @handrews suggested waiting with a new PR until there is some discussion on the issue to open a PR.
I was not able to attend the last community meeting, so the issue was not discussed.

[handrews]

Process:

• Is there an update on the new TSC lineup?
• Use projects for focused, short-term work with a specific audience #3610 We now have two projects set up as a trial run! We might want to quickly look and see if folks like how I set them up:
  • Automation & Infrastructure
  • Contributor Guidance
• 3.x.y patch release approach #3528 (comment) – we have some disagreements over what goes in a patch release

Mechanical:

• Update ReSpec versions #3622

For follow-up:

• Draft proposal for experimental field #2386 – do we now know enough to accept this proposal for further debate?
• Fix incorrect OpenIDConnect discovery url #3607 – updated based on last week's feedback
• Extend Security Scheme Object to support DPoP token specification #3613 – is this ready for PR or should it be discussed in issues more first?
• ciba-grant-3.2.0.md #3615

[lornajane]

Quick note on the proposal process after today's discussion. We should start new ideas off as discussions on this repository, once general agreement is reached, those ideas can become a proposal in a pull request. The proposal has a formalised format, which means we can then use it to make changes to the specification, so it's a good outcome. The idea is to have something that just needs polishing once it's in proposal format.

[AxelNennker]

"discussions" as in https://resources.github.com/devops/process/planning/discussions/ , right?
I only used discussion once in another repository and was ignored. Then I created an issue on what I wanted to discuss and the conversation started.

How about having "Open Community (TDC) Meeting" agenda building as a discussion and not as an issue like this #3614 one?

[handrews]

@AxelNennker

I only used discussion once in another repository and was ignored. Then I created an issue on what I wanted to discuss and the conversation started.

We've had that problem in the past because the roles of discussions, issues, PRs, etc. were not well-defined. This is us starting to define them, based on how we are using them in the OAI/sig-moonwalk repository (which has the advantage of a fresh start).

How about having "Open Community (TDC) Meeting" agenda building as a discussion and not as an issue like this #3614 one?

We are already trying this out in OAI/sig-moonwalk for the Tuesday meetings. If that works out well, we might standardize on that, but folks are used to the issues in this repository and there's no need to disrupt that unless we really think it would be better.