-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Proposal: create a triage team to manage the backlog #34054
Comments
Just for background, we don’t currently use the triage permission level. Refs: nodejs/TSC#712 |
+1 |
@richardlau thanks for linking nodejs/TSC#712. In the meeting, it wasn't clear if this issue should be opened here in the core repo or in TSC, as it would require TSC discussion/approval either way. This might be considered a duplicate. @Trott I'd be curious to know your thoughts on having a triage team now vs a year ago. |
Labeling this for TSC visibility |
I am interested and willing to triage issues in both core and help repos. I have been putting my hands for sometime, but inability to tag, label and close issues limits my work. |
@mastermatt Sorry if I caused any confusion. I linked to the issue in the TSC repo just for some background information. As the repository owners the TSC would have to create the team and grant the triage permission to them. FWIW I think it's a good idea especially if we have people interested in joining such a team as it will be a lower barrier of entry to get involved with the project. We'd probably need some guidelines/onboarding for triage docs created. If I remember correctly from the collab session on Monday Express has such docs -- @gireeshpunathil / @mastermatt could you link to them for reference? |
here is the doc I compiled for express: https://github.com/expressjs/express/blob/master/Triager-Guide.md |
I am cautiously optimistic. |
The role helps triaging issue backlogs effectively Fixes: #34054 Refs: nodejs/TSC#891 PR-URL: #34295 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
The role helps triaging issue backlogs effectively Fixes: #34054 Refs: nodejs/TSC#891 PR-URL: #34295 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
The role helps triaging issue backlogs effectively Fixes: #34054 Refs: nodejs/TSC#891 PR-URL: #34295 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
The role helps triaging issue backlogs effectively Fixes: #34054 Refs: nodejs/TSC#891 PR-URL: #34295 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
This is an extension of the conversation that began in the "Node.js Issue Backlog" session of the Collab Summit 2020, led by @gireeshpunathil.
Creating a Github team under this organization with "Triage" permission level could have benefits to reduce and organize the backlog of over 1200 issues and PRs while also creating an entry point with a lower barrier for those wanting to help with the project.
My first-hand experience lays with being a member of the relatively-new Triagers team for the Expressjs ecosystem.
And I would volunteer to be a member of a similar team here under Nodejs.
The text was updated successfully, but these errors were encountered: