Skip to content

[meta] Issue & PR cleanup #803

Open
Open
@GeopJr

Description

@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!

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions