GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — meta: move one or more TSC members to emeritus by nodejs-github-bot · Pull Request #43897 · nodejs/node

Conversation

@nodejs-github-bot

@nodejs-github-bot nodejs-github-bot commented Jul 19, 2022

Copy link
Copy Markdown
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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@nodejs-github-bot
meta: move one or more TSC members to emeritus
243907a
@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 Node.js documentation. labels Jul 19, 2022
@ronag

ronag commented Jul 19, 2022

Copy link
Copy Markdown
Member

I'm still active...

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@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

Trott commented Jul 19, 2022 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

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.

tniessen and richardlau reacted with thumbs up emoji
All reactions
  • 👍 2 reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@Trott Trott reopened this Jul 19, 2022
@Trott Trott added the tsc-agenda Issues and PRs to discuss during Technical Steering Committee meetings. label Jul 19, 2022
@Trott Trott mentioned this pull request Jul 19, 2022
Node.js Technical Steering Committee (TSC) Meeting 2022-07-20 nodejs/TSC#1261
Closed
@aduh95

aduh95 commented Jul 19, 2022

Copy link
Copy Markdown
Contributor

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

mcollina reacted with heart emoji
All reactions
  • ❤️ 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@Trott

Trott commented Jul 20, 2022 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

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.)

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@cjihrig

cjihrig commented Jul 20, 2022

Copy link
Copy Markdown
Contributor

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 😄 .)

gireeshpunathil, mcollina, and aduh95 reacted with thumbs up emoji
All reactions
  • 👍 3 reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Trott added a commit to Trott/io.js that referenced this pull request Jul 20, 2022
@Trott
tools: add verbose flag to inactive TSC finder
c3c7c44
Refs: nodejs#43897 (comment)
@Trott Trott mentioned this pull request Jul 20, 2022
tools: add verbose flag to inactive TSC finder #43913
Merged
@Trott

Trott commented Jul 20, 2022

Copy link
Copy Markdown
Member

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.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@Trott

Trott commented Jul 20, 2022

Copy link
Copy Markdown
Member

Voted to reinstate. 🎉

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

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

Trott commented Jul 20, 2022 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

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!

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@gireeshpunathil

gireeshpunathil commented Jul 20, 2022

Copy link
Copy Markdown
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)

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@Trott

Trott commented Jul 20, 2022 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
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)

@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.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@gireeshpunathil

gireeshpunathil commented Jul 20, 2022

Copy link
Copy Markdown
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!

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

nodejs-github-bot pushed a commit that referenced this pull request Jul 22, 2022
@Trott
tools: add verbose flag to inactive TSC finder
5fbf33e
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Tierney Cyren <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
danielleadams pushed a commit that referenced this pull request Jul 26, 2022
@Trott @danielleadams
tools: add verbose flag to inactive TSC finder
17a4e5e
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Tierney Cyren <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
targos pushed a commit that referenced this pull request Jul 31, 2022
@Trott @targos
tools: add verbose flag to inactive TSC finder
822fa99
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Tierney Cyren <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
targos pushed a commit that referenced this pull request Aug 1, 2022
@Trott @targos
tools: add verbose flag to inactive TSC finder
01a4434
Refs: #43897 (comment)

PR-URL: #43913
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Tierney Cyren <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
@tniessen tniessen mentioned this pull request Aug 30, 2022
meta: move one or more TSC members to emeritus #44447
Closed
guangwong pushed a commit to noslate-project/node that referenced this pull request Oct 10, 2022
@Trott @guangwong
tools: add verbose flag to inactive TSC finder
491e092
Refs: nodejs/node#43897 (comment)

PR-URL: nodejs/node#43913
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Darshan Sen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Tierney Cyren <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

doc Issues and PRs related to Node.js documentation. meta Issues and PRs related to the general management of the project. tsc-agenda Issues and PRs to discuss during Technical Steering Committee meetings.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

6 participants

@nodejs-github-bot @ronag @Trott @aduh95 @cjihrig @gireeshpunathil
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.