Nominating @MattIPv4 as `web-admin`

[ovflowd]

I'm nominating Matt to be part of the @nodejs/web-admins group within Node.js Web Team. Matt has contributed to Node.js for several years so far and has contributed actively to our web efforts for a few years so far. Matt has extensive experience with project management (maintaining Hacktoberfest), web infrastructure (with his work at DigitalOcean and Grafana andf Node.js) and is someone I trust to make good decisions and to be able to steer our teams when needed.

Right now only me and @bmuenzenmeyer are the "admins" which puts us on a bus-factor situation. Having @MattIPv4 as part of the Web Admins team ensures we're not too biased, have a successor in case either me or Brian need to become unavailable or decide to leave and he's someone extremely trustworthy.

cc @nodejs/web-admins / @nodejs/tsc

[MattIPv4]

Thank you :) Happy to step up and be an extra pair of hands + brain available for admin tasks to help reduce the load on both of y'all.

[flakey5]

Big +1

[MattIPv4]

Looks like there haven't been any objections so far. How long do we want to leave this open for? I don't think we have a documented nomination period; looking at core collaborators, they use a week. Do we want to wait until the next web-team meeting?

[avivkeller]

Do we want to wait until the next web-team meeting?

Without any objections, I don't think we have too, but we should wait until the TSC meeting in a few days concludes

[mcollina]

No quorum in the meeting, we will adjourn for the next.

[joyeecheung]

Coming in from the TSC meeting since it's on the agenda: what's the web-admin team for? why does the decision need to be make by the TSC? From https://github.com/nodejs/web-team/blob/main/PERMISSIONS.md it listed admin - does that mean it "has access to add/remove people in other web-related teams but not really responsible of concrete things in the scope of other web-related teams"?