Skip to content
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

Triagers team #37628

Closed
benjamingr opened this issue Mar 6, 2021 · 9 comments
Closed

Triagers team #37628

benjamingr opened this issue Mar 6, 2021 · 9 comments
Labels
meta Issues and PRs related to the general management of the project.

Comments

@benjamingr
Copy link
Member

We have a triagers team, currently containing two members @PoojaDurgad and @RaisinTen - both of which are already collaborators (but were not when they joined the team).

Is that team still required given its members are collaborators with permissions/access to triage? Should we outreach to other contributors and ask them to apply for membership?

@benjamingr benjamingr added the meta Issues and PRs related to the general management of the project. label Mar 6, 2021
@benjamingr
Copy link
Member Author

cc @nodejs/issue-triage (though both members are already pinged :))

@gireeshpunathil
Copy link
Member

retaining the team makes sense to me for a role definition and place holder for future triage work . For the two members, I will leave it up to their decision.

+1 to reaching out to new members who are interested to become traigers!

@targos targos changed the title Traigers team Triagers team Mar 6, 2021
@RaisinTen
Copy link
Contributor

I'm not very sure about this.

Currently, after a nomination is successful, contributors are directly promoted to the role of a collaborator. So, the only way one could become a traiger now is to open a PR asking for the role and get accepted, which doesn't seem to happen a lot.

Should we update the nomination procedure in a way that the contributor first gets the role of a triager and then after a period of time, they get promoted to the role of a collaborator?

@gireeshpunathil
Copy link
Member

  • the triager role is for someone who has little contribution to the project
  • the role helps someone to get started (low barrier to entry) and help the project
  • it helps to get involved gradually, contribute substantially, and become a collaborator

so the role is still relevant, and the project can benefit with triaging. we could strive to get new folks.

@RaisinTen
Copy link
Contributor

In that case, I'm +1 on keeping the team.

@PoojaDurgad
Copy link
Contributor

I would continue doing triaging

@benjamingr
Copy link
Member Author

Should we update the nomination procedure in a way that the contributor first gets the role of a triager and then after a period of time, they get promoted to the role of a collaborator?

Most collaborators don't triage, they contribute in mostly other ways - the number of people I see triaging issues is maybe 10-20% of the collaborator base.

Collaborators do however have all the powers to triage (and more) in the repo.

I think it makes sense (but I don't feel strongly about it) to not have @PoojaDurgad and @RaisinTen as traigers in the team since they are collaborators - instead maybe "promote" them to "manage" the team with @gireeshpunathil and encourage others to become collaborators?

@Trott
Copy link
Member

Trott commented Nov 18, 2021

We seem to have a larger triagers team now so I think this can be closed. But I also don't see anything in the docs about how someone might nominate themselves for a triager role, so maybe that's a gap to fill? (Or maybe it's there and I'm just not seeing it?)

@Trott
Copy link
Member

Trott commented Nov 18, 2021

Oh, I see it now, it's in the contributing guide. I think this can be closed now. Feel free to comment or re-open if I'm wrong about that!

@Trott Trott closed this as completed Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

No branches or pull requests

5 participants