@nodejs/nodejs-website contribution requirements

[avivkeller]

The @nodejs/nodejs-website team currently includes 18 members. However, it's clear that some of these members are no longer actively contributing. To keep the team focused and efficient, I propose adopting contribution requirements similar to those used by the Node.js core team.

---

To remain a member of the @nodejs/nodejs-website team, collaborators must meet the following activity requirement:

• Must have made at least one commit and/or interacted with at least one issue/pr to a @nodejs/web-infra maintained repository within the last X months.

If a collaborator does not meet this requirement, an automated process will open an issue, prompting the @nodejs/nodejs-website team to review and discuss whether the individual should be removed from the team.

If a member is removed, they must be re-nominated to rejoin the @nodejs/nodejs-website team.

---

While the specific implementation of said policy can be subject to change, I'd appreciate a 👍 👎 on whether you like this idea (since it may affect all of us)

[ovflowd]

FYI I've requested @avivkeller to open this issue on my behalf. I do feel the 6m could be debatable to up to 1y.

[mikeesto]

I think it would be kinder if an attempt is made to contact the individual privately first (e.g. Slack/Twitter DM etc) where possible as an initial step

[avivkeller]

I think it would be kinder if an attempt is made to contact the individual privately first (e.g. Slack/Twitter DM etc) where possible as an initial step

My only concern is that we don't have a shared discussion forum internal to the website teams, so I don't think we wouldn't be able to automate the flagging of inactive users. However, if we get the OpenJS Foundation to add a #nodejs-website-private (or something) Slack channel, we could have the alert(s) posted there for internal discussion with the member?

[bjohansebas]

I’m in favor

we can also use this PR as a guide to create the inactivity policy

[avivkeller]

Okay, since we are generally in favor this, I'll open a PR updating our guidelines and adding an automation.

As mentioned on Slack, we may not need a private channel for discussions, individuals can reach out to maintainers (Brian and Claudio) with private concerns