maybe slightly offtopic,sorry for that.
But ive been carrying some the thoughts for past few days and just found an opportunity to share and discuss if relevant.

Is there a way to "thumbs up" a "thumbs down" if a QA person realizes that the problem is resolved/invalid ?

Also just as we can track a thumbs down by raising a bug(if bugzilla is mandated in the future though I dont think this is happening at the moment even for packages with a bugtracker link now ) there should also be a way to track it to completion by the QA/Dev who raised/resolved it. Like DEV assigning back the bug to QA with a resolution so the "thumbs down" can either be removed or toggled to "thumbs up". ( manually or auto )

Basically trying to ensure a package doesnt get a "thumbs down" if somebody just feels it does not meet the criteria ( which may be correct/incorrect) and then carry on and may never revisit.
Keeping a framwework to resolve every reported problem on a package is needed IMHO.

If the bug isnt resolved by DEV, and the package gets to extras ( with 10 votes including enough "core" QA votes ) the bugs list may be published as part of release notes, there can be many other actions that can be discussed also.

That also raises another already raised issue about transfer of existing votes to a "new" version of the package that may fix bugs reported.

feel free to dismiss as non-relevant