Skip to content

@nodejs/nodejs-website contribution requirements #7767

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.

Sign up for GitHub

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

Jump to bottom
Open
avivkeller opened this issue May 21, 2025 · 5 comments · May be fixed by #7775
Open

@nodejs/nodejs-website contribution requirements #7767

avivkeller opened this issue May 21, 2025 · 5 comments · May be fixed by #7775
Labels
meta Meta Issues for Administration of the Website Team

Comments

@avivkeller
Copy link
Member

avivkeller commented May 21, 2025 •
edited
Loading

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:

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)
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Node.js Website May 21, 2025
@avivkeller avivkeller added the meta Meta Issues for Administration of the Website Team label May 21, 2025
@ovflowd
Copy link
Member

ovflowd commented May 21, 2025

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

@github-project-automation github-project-automation bot moved this to 📋 Backlog in Node.js Website May 21, 2025
@mikeesto
Copy link
Member

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
Copy link
Member Author

avivkeller commented May 21, 2025 •
edited
Loading

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
Copy link
Member

I’m in favor

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

@avivkeller
Copy link
Member Author

avivkeller commented May 21, 2025 •
edited
Loading

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

@avivkeller avivkeller linked a pull request May 23, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meta Meta Issues for Administration of the Website Team
Projects
Node.js Website
Status: 📋 Backlog
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(meta): require collaborators to be active nodejs/nodejs.org
4 participants
@ovflowd @mikeesto @avivkeller @bjohansebas