as discussed in this week's meeting, it's time again  to garden our issue
tracker and clean up obsolete issues. We want to find the important and easy
issues that just fell through the cracks, clean up the noise that makes the
issue tracker less useful, and generally get an up to date impression about
what users have trouble with.
I  tagged all issues which haven't been updated in the last 90 days with the
Let's please collectively go through them, and re-triage them:
* For bug reports, make sure that they still apply to current master. If they
do, just drop the review label. If they are fixed, close the issue. If they
need more information how to reproduce, please ask the reporter for clearer
instructions, or whatever else is necessary, label the issue with "question"
and also drop the review label.
* For enhancement reports, also check if they still make sense for Cockpit.
Some of them have been open for years, and we realistically won't get to
them. Some of them may also be too big to be tracked in an issue, and they
need an entire epic about them (and then they need to be reviewed whether we
want to do it at all -- so most likely "no" for most of them).
* At least in the last review round we also had a lot of feature requests for
entirely new pages. Almost all of them should become their own project.
Point to starter-kit and our documentation, and that we are glad to help
anyone with setting up a project, CI, etc., but we can't do all that work
ourselves -- we don't want to become experts and take responsibility for
If everyone can triage 5-10 every day, we should be through in about two weeks.
Of course in the beginning we'll look at the "easy" ones and be faster, and
pace will go down towards the end -- but then we'll already have a much better
 Similar to what we did in January:
 Well, our bots' issues-review script, of course