[Epic] Triage old issues in this repository

[yuvipanda]

Context

This repository has 388 open issues right now. Many of these are stale, out of date or not actionable. Having this many open issues makes it hard to have a realistic backlog, especially given many of these are stale. It takes constant triaging and grooming to keep our list of open issues manageable. But before that, we need to have a round of going through and cleaning up existing issues. This is difficult work!

Proposal

I propose we go through all the open issues, and take one of the following actions:

1. Close as completed - something we have done already, let's celebrate, mark as done.
2. Close as duplicated - link to another issue (in the same or different repository) tracking the same thing, and mark as closed. Prefer leaving open the issue that has had the most useful activity.
3. Close as no longer relevant - due to decisions made since the last activity on this issue, it is no longer relevant. Write a short comment stating this, and close. Can be re-opened if someone disagrees.
4. Copy into ProductBoard as a feature request insight - if this is a feature request, copy it into the appropriate productboard feature as an insight, and link back to the ticket before closing.
5. Close as not planned - Some things are just not going to be things we're going to be able to do in the near or medium future. We thank the issue for giving us ideas, and close them. They can be re-opened if necessary.
6. Describe action items in the issue body - if this issue should continue to stay here, it must have an Action Items section in the issue body, with an active list of things that must be done to close the issue. This can be time consuming, but worth it for keeping the issue list manageable.

Updates and actions

No response

[yuvipanda]

I would like to do a 4h round on this as a first pass, but it'll have to be put through our sprint planning system.

Update: I don't think this should be something I do, but a shared team exercise. I uncookielick this!

[jmunroe]

Should a similar review should be made of our other repositories as well?

As a I scroll through infrastructure I see some issue which I recognize as being duplicates of ideas captured elsewhere. Please let me know if joining co-working session to triage these old issues would be helpful.

[yuvipanda]

I've updated (4) (feature request) to incorporate product board.

[yuvipanda]

I've started doing this on and off, moving things into productboard as appropriate.

[yuvipanda]

Issue tracking making productboard more publicly visible at https://github.com/2i2c-org/meta/issues/900

[yuvipanda]

I've converted this into an epic, and split #3789 off into its own subtask.