What to do with old issues?

[Mierdin]

There are a LOT of issues in this repo, and I've intentionally held back on pruning them because they're still good ideas, even if they're still up for grabs. I don't really feel like outright closing them is the right call, but it would be nice to have a separation between urgent issues like bugs and maybe things that have imminent work on them vs things like "this would be a good idea to tackle someday". Currently everything is piled together.

There are a lot of issues that currently have little to no description, that I or someone else opened just to track a potential content idea for later. It would be nice to keep the issues more or less focused on bugs to fix, or lesson ideas that are being fleshed out or discussed.

One option is to close stale issues but also add a label like "archived" which indicates that it's inactive but can be re-opened if someone wants to tackle it. This relies pretty heavily on convention however, and not everyone will be "in the know".

Maybe another option is to have a markdown file in the repo with old lesson ideas? Then people can add/remove via PR as they wish.

Yet another is a wiki page on this repository that is open for all to edit.