Ongoing issue cleanup

[Helium314]

This issue is to inform about ongoing work that will take a while.

I see myself unable to handle the increased amount of activity in this repository in the past few months, especially because it coincides with me much less time to spend on this project than I had up to ~February.
The usual choice is between developing the app, responding in issues / discussions, and handling PRs. Recently none of those categories got enough attention. Sometimes I can spend ~2 hours on issues and discussions, and in the end I might have answered some questions but that's it. Often it feels like 2 wasted hours that could better be spent on actual development.

While technically things could go on like this, it will result in a bunch of unhappy users (and developers).
A first measure is better organizing issues (and to a lesser extent PRs), in an attempt to reduce the necessary work there in long term. I'm not (yet) going to work on an "issue tree" as suggested in #898, but I will start organizing using labels, and sometimes linking issues or PRs.

Issues

• I will go through all open issues (from oldest to newest) and assign tags where appropriate. New labels will be created where it's suitable, e.g. toolbar, or new layout.
• Whenever it seems necessary, I will edit the first post so it contains what should be done.
• The guidelines in the issue templates will actually be enforced, and I plan to close issues clearly violating the guidelines (mostly regarding the 3 tl;dr points, but also e.g. if the issue just consists of a link).
• Comments not contributing to the issue (e.g. "please implement it" or unrelated discussions) will be hidden.

Pull requests

There are far fewer PRs than issues, but the time needed for handling them can be enormous, so I'll go through them and try prioritizing PRs that are likely less work.

• PRs not referring to an issue with contributor needed or PR labels will get an appropriate label, as they definitely should have lower priority
• PRs going against the contribution guidelines will also be labeled. I'm ok with working on those (at low priority), but there is high possibility of both contributor's and my time being wasted in discussions. (really, this part occurring repeatedly managed to effectively destroy my joy of working on PRs)
• In case of multiple PRs by the same contributor, all except one will be in waiting state (working on too many PRs in parallel can be difficult)
• Bug fixes override this, as they should go first

[devycarol]

I could try and help out by mentioning this post in offending issues that I see. But I don't want to act as "issue police" unless you want me to.

[Helium314]

Thanks. I'd like to first go though the all the issues at least once though. (sometimes I change my mind on various things, and I have the impression I'm not particularly consistent...)