It looks like there are 2 types of issues that are confining them to testing:

1. applications lacking testing reports
2. applications with problems prohibiting them from being promoted, reported to the developer, but with no response or action from the developer (some up to a year)

Could there be a way to separate the first type from the second? Then the apps in testing that require developer action could be re-directed from the community back to the developer, and the community could see what needs the focus of testing.

Some apps that require developer action in one way of looking at it shouldn't even be in testing any more, because they can't be tested until development issues are resolved. An example is FM Carkit:
http://maemo.org/packages/package_in...fm-carkit/0.4/