Skip to content

Node.js's Discord Roles (Sync) #970

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.

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

Open
ovflowd opened this issue May 12, 2025 · 3 comments
Open

Node.js's Discord Roles (Sync) #970

ovflowd opened this issue May 12, 2025 · 3 comments

Comments

@ovflowd
Copy link
Member

ovflowd commented May 12, 2025

Hey folks 👋 I'm opening this on behalf of @VoltrexKeyva.

Since launching the Node.js Discord server, we’ve set up a few roles to help identify collaborators in the Node.js project. So far, we’ve created:

  • Node.js TSC – for members of the Node.js Technical Steering Committee
  • Node.js Collaborator – for anyone in the Node.js GitHub organization
  • Node.js Ambassador – for officially recognized Node.js Ambassadors

The goal was to keep things simple and avoid making fine-grained distinctions that don’t really apply in a social context like Discord. For instance, I didn’t think we needed a separate “Triager” role, since triaging is something specific to GitHub, not Discord.

@VoltrexKeyva suggested that the roles on Discord should better reflect those on GitHub — specifically proposing that we add distinct roles for Core Collaborators and Triagers.

Personally, I’m neutral on this but feel the current roles are sufficient. That said, I’d love input from the TSC on whether we should adjust the role structure.

@ovflowd
Copy link
Member Author

ovflowd commented May 12, 2025

cc @nodejs/tsc

@avivkeller
Copy link
Member

FWIW, these roles reflect the descriptions provided in our moderation policy:

Collaborator refers to any individual with configured triage role or higher in any Node.js GitHub organization repository.

TSC refers to the Node.js Technical Steering Committee.

@ovflowd
Copy link
Member Author

ovflowd commented May 25, 2025

I do agree with @avivkeller here. And since there has been no input from any TSC member, I do believe per lazy consensus seeking they are in agreemeent.

One small @nodejs/tsc bump, and if in another week we don't get any -1, I'll close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants