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

Proposal: create a triage team to manage the backlog #34054

Closed
mastermatt opened this issue Jun 25, 2020 · 9 comments
Closed

Proposal: create a triage team to manage the backlog #34054

mastermatt opened this issue Jun 25, 2020 · 9 comments
Labels
tsc-agenda Issues and PRs to discuss during the meetings of the TSC.

Comments

@mastermatt
Copy link

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.

@mastermatt
Copy link
Author

@richardlau
Copy link
Member

Just for background, we don’t currently use the triage permission level. Refs: nodejs/TSC#712

@gireeshpunathil
Copy link
Member

+1

@mastermatt
Copy link
Author

@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.
Now that the permission setting isn't new or in beta on Github and other communities are picking it up with success, do you still think your comment holds true? ("I think our current situation in the main repo is fine, at least for now.")

@gireeshpunathil
Copy link
Member

@mastermatt -

  • I meant to ask to open this issue here itself, in the core repo.
  • I don't think this is a duplicate:
    • the referenced issue is closed 10 months ago
    • the triage role raises to relevance in the current context (for both backlog & CI)

Labeling this for TSC visibility

@gireeshpunathil gireeshpunathil added the tsc-agenda Issues and PRs to discuss during the meetings of the TSC. label Jun 26, 2020
@HarshithaKP
Copy link
Member

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.

@richardlau
Copy link
Member

@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?

@gireeshpunathil
Copy link
Member

@Trott
Copy link
Member

Trott commented Jun 30, 2020

@Trott I'd be curious to know your thoughts on having a triage team now vs a year ago.

I am cautiously optimistic.

cjihrig pushed a commit that referenced this issue Jul 23, 2020
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]>
MylesBorins pushed a commit that referenced this issue Jul 27, 2020
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]>
addaleax pushed a commit that referenced this issue Sep 22, 2020
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]>
addaleax pushed a commit that referenced this issue Sep 22, 2020
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tsc-agenda Issues and PRs to discuss during the meetings of the TSC.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants