Skip to content

doc: clarify details of TSC public and private meetings #58925

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented Jul 2, 2025

Alternative to #58837

To be clear, I don't think any changes to our governance doc are needed, but others have proposed edits and additional requirements. This PR represents the version of those changes that I think would be better if any changes are made at all. See the discussion in #58837 for background.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Jul 2, 2025
@jasnell jasnell added the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label Jul 2, 2025
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

jasnell and others added 3 commits July 2, 2025 06:12
Co-authored-by: Antoine du Hamel <[email protected]>
Co-authored-by: Antoine du Hamel <[email protected]>
jasnell and others added 2 commits July 2, 2025 08:50
Co-authored-by: Joyee Cheung <[email protected]>
Co-authored-by: Joyee Cheung <[email protected]>
Copy link
Member

@joyeecheung joyeecheung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly LGTM, thanks. Still have a suggestion to align it with what we are already doing since that seems already good enough + a wording suggestion to make it more accurate.

Comment on lines +135 to +139
For the private portion of the meeting, the TSC chair ensures that someone
documents only the final disposition of any decisions made during the meeting
and ensures that those are shared with all TSC members via a private discussion
channel such as the TSC private email list. These summaries are not to be made
public unless all TSC members present during the meeting agree.
Copy link
Member

@joyeecheung joyeecheung Jul 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For the private portion of the meeting, the TSC chair ensures that someone
documents only the final disposition of any decisions made during the meeting
and ensures that those are shared with all TSC members via a private discussion
channel such as the TSC private email list. These summaries are not to be made
public unless all TSC members present during the meeting agree.
For the private portion of the meeting, the TSC chair ensures that someone
produces a summary of the discussions, gets it reviewed by the attendees
before the meeting ends, and shares it to all the TSC members once approved
by the attendees via a private discussion channel such as the TSC private
mailing list. The summary may be made public if there is consensus within the
TSC to make it public.

I think this is closer to what we have already been doing e.g. the chair posts a quick draft of the summary to the Zoom chat, either written by themselves or someone just verbally draft it in the meeting for the chair to type, and ask for objections/feedback on the spot before the meeting ends to post it afterwards.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re: this part of the suggestion: "The summary may be made public if there is consensus within the TSC to make it public." ...This is not adequate, I think. The agreement needs to be among all the people who were in attendance, not just TSC members.

Copy link
Member

@joyeecheung joyeecheung Jul 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For the private portion of the meeting, the TSC chair ensures that someone
documents only the final disposition of any decisions made during the meeting
and ensures that those are shared with all TSC members via a private discussion
channel such as the TSC private email list. These summaries are not to be made
public unless all TSC members present during the meeting agree.
For the private portion of the meeting, the TSC chair ensures that someone
produces a summary of the discussions, gets it reviewed by the attendees
before the meeting ends, and shares it to all the TSC members once approved
by the attendees via a private discussion channel such as the TSC private
mailing list. The summary may be made public if there is consensus within the
TSC and the non-TSC attendees to make it public.

Oh right I forgot about the invited guest part. I think this should suffice (the original wording excluded TSC members not attending the meeting from the consensus of disclosure after they already see it, which seemed unintentional, at least not necessary IMO).

Co-authored-by: Joyee Cheung <[email protected]>
Copy link
Contributor

@ShogunPanda ShogunPanda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project. tsc-agenda Issues and PRs to discuss during the meetings of the TSC.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants