It’s about finding the right balance. It is inevitable that some people will not vote right and miss (to seasoned testing veterans) obvious blockers - that is why we have multiple votes and comments so we could figure out what’s going on. I personally hope that apps like kisstester will make it easier for people to leave feedback and with some automated tests, it will make it less error-prone than the current process.

Now, since this is a crowdsourcing effort, there is no guarantee, just a best effort that very broken or incompliant does not slip through. If it does, we poke the maintainer just as we would on any other fatal bug that might not be apparent when the app was pushed. That’s why super-tester votes are important when an app has only a few votes - if we just lowered vote-requirement, that, low number could be reached "accidentally". This actually works, we have practically halved our locked package numbers since super-tester activity started - but we DO need a lot more user activity so super-tester votes become a last resort method, not a de facto way of getting to unlock.

Khertan, there IS a community vote. I didn’t set these rules in place, some of them I agree with, some I don’t, but what we have is a very general compromise on what is necessary to provide a safe experience and provide us with a "enabled by default" state from Nokia. I very well understand the pain of not having 10 people to vote for you, I myself have such packages. Feel free to lobby for alternate solutions, and if the proposal gains traction, I will be more than happy to hand the new requirements over to Niels.

That said, Battle Gweled is a somewhat special case - when that package was submitted, IIRC the bugtracker rule was not yet perfectly known, optification was still in it’s infancy, etc (note - even Jaffa did a thumbs up on that one ! ). I don’t know if mikkov abandoned it or not, but I did not feel the package be in such a bad shape to require a manual removal.

In any case, we WILL have to come up with a mechanism to deal with orphaned packages (i.e. what to do if a package gets unlocked and the maintaner does not publish it for whatever reason). Thoughts welcome.