proxmox bugzilla open tickets reduction effort - how to start/proceed?

[RolandK]

hi,

for a long time, i'm a little bit annoyed that there is quite a reasonable number (2724) of open , unresolved tickets in proxmox bugzilla at https://bugzilla.proxmox.com

i don't want to blame proxmox team here, but my question is , how we can put some systematic work into this to better get rid of open tickets which constantly re-appear on every search but which are either outdated , invalid or simple being overseen/forgotten for long.

i don't want to poke into proxmox team's "business" here but as this is opensource and also a community project, i wonder how other community members see this and would like to help to do anything about it to reduce number of orphaned/outdated tickets.

i want to start this effort in agreemend/consent with proxmox team and i think it's best to know all the do's and don't around that, so any feedback for this would be welcomed.

 

[fiona]

Hi,

for a long time, i'm a little bit annoyed that there is quite a reasonable number (2724) of open , unresolved tickets in proxmox bugzilla at https://bugzilla.proxmox.com

a large part of that is feature requests and that is not a bad thing in itself. Many things are easy to request, but a lot of effort to actually implement. There's a wide variety of uses cases and wishes.

i don't want to blame proxmox team here, but my question is , how we can put some systematic work into this to better get rid of open tickets which constantly re-appear on every search but which are either outdated , invalid or simple being overseen/forgotten for long.

If they really are outdated, feel free to close them with a hint to re-open if still an issue in current versions. Should be a few years old IMHO, otherwise it's better to just request the current status from the reporter if you have reason to believe it might have changed.

You can filter your search by product/component and also bug vs. enhancement request. You can sort by changed date. This should already take you a long way!

What also helps is to categorize bugs correctly if you are confident that it's currently filed in the wrong place or improve bug titles when they don't convey the actual issue. That being said, it's often a bit subjective, so it should be cases where it's obvious that it's an improvement.

There's also a lot of tag:start-contributing bugs which can be a great starting point for external contributors too.
https://pve.proxmox.com/wiki/Developer_Documentation

The actual "issue" is that there is just much more demand for features than can currently be tackled at once. Proxmox is still a relatively small company.