Reduce number of issues

[gitjeff05]

Is there a current process to remove stale issues? There are a lot of open issues in this repo. Would it be wise to tag issues as stale and then remove them if there is no more activity after a month of being tagged?

A simple query shows ~440 issues that have not been updated in 400 days and have fewer than three comments/reactions:

Filter: is:issue is:open comments:<3 reactions:<3 updated:<=2019-12-29

[agoose77]

Periodically, I review the JupyterLab bug tracker and try to add context / reproducers / suggestions to help reduce the workload. Unfortunately, I don't have the permissions to triage the issues myself. I can see that there are different "teams" within the JupyterLab org to perform tasks like triage, but there is no information concerning how one might join such a team.

Additionally, it might be worth adding some kind of "urgency" labels that help the dev team to identify which issues are most concerning, even when they remain open for a long time.

@jasongrout I'm tagging you on this because you mentioned it in the weekly dev meetings last month, I wonder if there have been any developments in this direction? I found this article which discusses how flutter organise their issue tracker.

[blink1073]

Hi @agoose77, I've invited you to the triage team. Do you want to submit a PR adding language to our contributor guide that suggests that org members who want triage access open an issue requesting it?

We've talked about assigning priority to issues before, but had decided against it. @ellisonbg I think you were involved in that conversation, I can't remember the full reasoning. I agree it is worth re-visiting given the number of open issues.

[agoose77]

@blink1073 that's very helpful, thank you very much!

I will add this to my todo list :)