meta: move one or more TSC members to emeritus

[nodejs-github-bot]

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

@nodejs/tsc @fhinkel @jasnell

Since 3 months ago, fhinkel attended 2 out of 10 meetings and voted in 0 of 5 votes. Since 3 months ago, jasnell attended 2 out of 10 meetings and voted in 0 of 5 votes.

[jasnell]

This is a bit silly, I think. The bot is likely being too aggressive. For instance, it says that I didn't participate in votes such as legendecas' tsc nomination but that's not really true. I clearly +1'd the nomination in the nomination mail thread which absolutely falls into the spirit of participation. The other votes it says I haven't participated in include my own renomination the last time the bot flagged me. Granted, I have had a standing conflict for tsc calls themselves but I'm clearly still active even if at a much lower level. Given that, I'd like to suggest we reconsider how this bot determines activity level.

[bnoordhuis]

I'd kind of forgotten the rules around membership so in case anyone else's memory is as terrible as mine:

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.

---

I have had a standing conflict for tsc calls themselves

They're on a rotating schedule, aren't they?

[Trott]

it says that I didn't participate in votes such as legendecas' tsc nomination but that's not really true. I clearly +1'd the nomination in the nomination mail thread which absolutely falls into the spirit of participation.

"Participation" is not a factor. It was removed from our charter by the CPC because it is so vague as to be useless. With hand-wavy "participation" as an out, the supposedly-automatic removal rule was invoked exactly 0 times, even when we had someone on TSC who had completely vanished from the project for two years.

The need to either vote or attend 25% of the meetings is codified in our charter. We cannot change that without CPC approval. (I'm opposed to changing the requirements unless it is to strengthen them, for what that's worth.)

We're going to switch up the meeting times again in about a month (because daylight savings is coming to an end in the northern hemisphere) so I'm optimistic that if we all update the availability spreadsheet, attendance will become easier.

I also expect a vote or two soon, and any single vote in a 90-day period is enough to not get flagged.

[Trott]

Ref: #44447