Skip to content
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

meta: move one or more TSC members to emeritus #43897

Closed
wants to merge 1 commit into from

Conversation

nodejs-github-bot
Copy link
Collaborator

This PR was generated by tools/find-inactive-tsc.yml.

@nodejs/tsc @ronag

Since 3 months ago, ronag attended 3 out of 13 meetings and voted in 0 of 3 votes.

@nodejs-github-bot nodejs-github-bot added meta Issues and PRs related to the general management of the project. doc Issues and PRs related to the documentations. labels Jul 19, 2022
@ronag
Copy link
Member

ronag commented Jul 19, 2022

I'm still active...

@ronag ronag closed this Jul 19, 2022
@mcollina mcollina deleted the actions/inactive-tsc branch July 19, 2022 09:58
@Trott Trott restored the actions/inactive-tsc branch July 19, 2022 18:28
@Trott
Copy link
Member

Trott commented Jul 19, 2022

I'm still active...

The TSC Charter specifies that removal in this situation is automatic:

A TSC member is automatically removed from the TSC if, during a 3-month period,
all of the following are true:

  • They attend fewer than 25% of the regularly scheduled meetings.
  • They do not participate in any TSC votes.

So, this PR is not a proposal or suggestion. It is an announcement of an automatic process. (The process is automatic and specified as such in the TSC Charter because we are terrible at doing this otherwise.)

The thing to do is for the remainder of the TSC to vote on reinstating you immediately. I'll tag this with tsc-agenda and add "reinstating @ronag" to the agenda for tomorrow's meeting. Hopefully a quorum is at the meeting and we can get it done then.

A second thing to do might be to re-evaluate the criteria. I wouldn't want to over-correct for a single false-positive, though.

@Trott Trott reopened this Jul 19, 2022
@Trott Trott added the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label Jul 19, 2022
@aduh95
Copy link
Contributor

aduh95 commented Jul 19, 2022

Can Robert vote for his own reinstating? Otherwise he will be kicked out by the bot automatically right away for the same reason 🙃

@Trott
Copy link
Member

Trott commented Jul 20, 2022

Can Robert vote for his own reinstating? Otherwise he will be kicked out by the bot automatically right away for the same reason 🙃

I can't tell how serious the question is so I'm going to answer it earnestly and be the kind of insufferable pedant that one is always sure to forget to include on party invitation lists.

No, he can't vote because he's not on the TSC technically.

However, it stands to reason that the 90 day windows starts when one is added to the TSC, so subsequent bot-removals can be closed.

If he attends tomorrow's meeting, that is likely to get him above the 25% threshold and it shouldn't be a problem. (I didn't check to confirm that this is correct, but it seems more likely than not. He has attended 3 of the last 13 TSC meetings.)

If we end up voting on something else (like the CPC seats) and he's at tomorrow's meeting, that could be a vote he can participate in as long as we reinstate first (which is one of the reasons I inserted it at the top of the agenda).

If I ever do get an invitation to anyone's parties ever again, I promise to NOT talk about this at the party. (Probably.)

@cjihrig
Copy link
Contributor

cjihrig commented Jul 20, 2022

Maybe we should have an action in place to warn a TSC member that they are pending removal ~1 month before this action would open the PR to remove them. (Not volunteering to implement this 😄 .)

Trott added a commit to Trott/io.js that referenced this pull request Jul 20, 2022
Trott added a commit to Trott/io.js that referenced this pull request Jul 20, 2022
@Trott
Copy link
Member

Trott commented Jul 20, 2022

Maybe we should have an action in place to warn a TSC member that they are pending removal ~1 month before this action would open the PR to remove them. (Not volunteering to implement this 😄 .)

As a first step, #43913 adds a verbose flag that outputs the attendance and voting data.

@Trott
Copy link
Member

Trott commented Jul 20, 2022

Voted to reinstate. 🎉

@Trott Trott closed this Jul 20, 2022
@targos targos deleted the actions/inactive-tsc branch July 20, 2022 15:14
@Trott
Copy link
Member

Trott commented Jul 20, 2022

Robert seemed to be a victim of "not voting" as there are several TSC members who have attended fewer meetings in the past 90 days, but they've voted on things. Here are the attendance counts for the past 90 days:

{
  aduh95: 5,
  apapirovski: 1,
  BethGriggs: 11,
  BridgeAR: 4,
  ChALkeR: 5,
  cjihrig: 7,
  danielleadams: 4,
  fhinkel: 3,
  gireeshpunathil: 4,
  jasnell: 2,
  joyeecheung: 5,
  mcollina: 5,
  mhdawson: 7,
  RaisinTen: 7,
  richardlau: 11,
  ronag: 3,
  targos: 2,
  tniessen: 5,
  Trott: 8
}

(Geoffrey Booth is not included because he has not yet been a member for 90 days.)

Richard Lau and Bethany Griggs neck-and-neck for best attendance!

@gireeshpunathil
Copy link
Member

@Trott - can you pls double check the values or the logic that apply on it? because when I manually counted, I got 6, not 4 (13/07, 29/06, 22/06, 01/06, 27/04, 20/04)

@Trott
Copy link
Member

Trott commented Jul 20, 2022

@Trott - can you pls double check the values or the logic that apply on it? because when I manually counted, I got 6, not 4 (13/07, 29/06, 22/06, 01/06, 27/04, 20/04)

@gireeshpunathil You're not listed in the minutes in 2022-06-22.md. Is that a mistake in the minutes? (The program checks the minutes to determine attendance.)

20/04 is 91 days ago so isn't included.

@gireeshpunathil
Copy link
Member

ok, understood. when I looked at the 22/06 minutes, I saw my name, but on a closer look, looks like the list contain absentees as well, below the list of those present, and that confused me. thanks for clarifying Trott!

nodejs-github-bot pushed a commit that referenced this pull request Jul 22, 2022
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Tierney Cyren <hello@bnb.im>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
danielleadams pushed a commit that referenced this pull request Jul 26, 2022
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Tierney Cyren <hello@bnb.im>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
targos pushed a commit that referenced this pull request Jul 31, 2022
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Tierney Cyren <hello@bnb.im>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
targos pushed a commit that referenced this pull request Jul 31, 2022
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Tierney Cyren <hello@bnb.im>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
targos pushed a commit that referenced this pull request Aug 1, 2022
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Tierney Cyren <hello@bnb.im>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Fyko pushed a commit to Fyko/node that referenced this pull request Sep 15, 2022
Refs: nodejs#43897 (comment)

PR-URL: nodejs#43913
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Tierney Cyren <hello@bnb.im>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
guangwong pushed a commit to noslate-project/node that referenced this pull request Oct 10, 2022
Refs: nodejs/node#43897 (comment)

PR-URL: nodejs/node#43913
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Darshan Sen <raisinten@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Tierney Cyren <hello@bnb.im>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations. 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