[meta] Issue & PR cleanup

[GeopJr]

There are 102 open issues and 15 PRs. Many of those either do not directly apply to Tuba (but rather GTK, Libadwaita, xdg), are somewhat duplicates of others, have way too many requests or reports under the same issue, are stalled forever, are abandoned or do not really match what Tuba is trying to be.

They are creating noise preventing me from prioritizing what's really in demand. I would like to clean them up. Close, split, resolve, tag issues and either finish draft PRs or close them.

Maybe a max of 1 month of no-reply to close an issue? Just to be clear, there's absolutely 0% chance an issue will be locked for any reason other than spam. Issues closed due to inactivity (from lack of more info, not when we have enough info to fix it) will be re-opened the moment a reply goes through.

Some issues are just clogging the tracker (and my brain) which leads to important issues not being prioritized. For example, at the time of writing this, I prioritized #200, after 600!! issues (#800) and only because Jeff mentioned on fedi that this is important to him. Similarly, #786 was only done recently because of the spam attacks and someone suggesting it on fedi.

If you are a passerby: Feel free to comment on closed issues or open new ones even though they were closed before. Nothing is set in stone and any suggestions or reports are very welcome!

[LukaszH77]

I'm fine with closing stale issues. It will be healthier for the project and you, I think.

[GeopJr]

I'm under pressure (self-imposed!) to make another release with GNOME 46 which is a bit sooner than I thought 😓

46 stable is due 2024-03-16. Tuba string freeze has to happen 7-10 days sooner (so 2024-03-06 or at most 2024-03-09) for translators to translate everything in time.

Some of the stuff I have to finish for the release are a bit more complex than expected. Filters are already close to 1000 additions and I'm not even done. The new composer has some blockers too...

I should probably take a step back to avoid burning myself out over this, I'd rather make a release when everything is done if it comes down to this, though I'd really love it if it was in the release week :/

The brief TODO for 46/0.7.0 is:

• Filters feat: filters #800
• Composer feat: new composer #623
• Announcement banners feat(announcements): banner and placement #766
• Mute/Block lists [Request]: mute & block lists view #796
• And then any low hanging fruit - which is difficult to distinguish with all the noise in the tracker, hence the reason for this issue

[LukaszH77]

While I understand why you want to release a new version along with GNOME, maybe you should delay it so that you can fit everything you want into it without getting tired and frustrated?

Another option is to limit the new features and move e.g. the editor and the block/mute list to 0.8.0. Even without some of your TODO, Tuba will have another great release.

Remember that your well-being is more important.

[nekohayo]

A technique I typically use for this in projects I manage is to create a label for issues that are caused by third-parties:

• Distro/packaging problem
• User support question
• "Depends on fixes elsewhere" (for upstream issues related to GTK etc.)

...and then when you need to focus, you can do a search in the issues tracker to specifically exclude those labels.