Nope it's not the point of the voting system. It's not even a true voting system, it is a clearly described way to evaluate certain strictly defined quality conditions for a package. Those are to be read in http://wiki.maemo.org/Extras-testing/QA_Checklist.

Again, this thread been started by MT on behalf of a decision done by council publicly, based on an evaluation that's already finished. And it's clearly adviced to MT in the meeting where we decided about this that we shall ask a last time
if there are any technical concerns about removing *patch pkgs from extras and extras-testing repos
nothing else, nothing beyond, not whether or not it is a good idea, just technical concerns ((sidenote to estel: when we asked MT in last meeting about that topic, *he* pointed us to *this* thread, so I think it's absolutely fair to say that maybe MT has picked the wrong topic))

Thanks for staying on (real) topic.
The thread's topic >>Should Tech Staff and/or Council Remove Dangerous Packages From Extras and Extras-Testing?<< is bogus, since that's never been a question. We *must* remove those.

cheers
jOERG

ps: no, >>general consensus was to revisit exact rules about things forbidden in packages, and giving time for developers to fix it, then starting to take action.<< must been based on a last check some years ago or in some unrelated domain. Neither do rules need any revisiting (see above), nor has there been any known consensus to do that. And developers have explicitly announced that they won't fix anything, in this particular case we talk about here. Consesnus in the council meeeting deciding on it been that *patch will get removed from extras and extras-testing, and we just go here and ask a last time if we have missed out on some technical implications in this.

Nope, there are clear rules (http://wiki.maemo.org/Extras-testing/QA_Checklist) and testers are supposed to obey those. If testers fail and do a fake approval based on doing developer a favour, if then somebody like sixwheeledbeast comes up with a proper bug report (http://talk.maemo.org/showthread.php?p=1328060) and developer answers he can't fix the bugs (http://talk.maemo.org/showpost.php?p=1328130), when further the bug report clearly shows that there are critical issues with the package, then we don't need to publish new rules or anything, and we don't need to give developer another chance to react. What we must do is remove those packages from extras and extras-testing repositories. It has been discussed thoroughly and comprehensively on a public council meeting, and we decided upon it there. Now e're going to execute that decision. Time for discussions been before and during that meeting.

cheers
jOERG
[edit: just a footnote - I'm not a friend of spending weeks to set up rules for each niche case that shouldn't even happen if the already existing rules wouldve been followed. Rather allow those who care about stuff to handle things according to the particular case and trust in their common sense. We already spent hours to decide how to handle this particular case, and we discussed it with quite a number of community people in public, before we decided. I don't see the point in making that another ruleset, rather make sure we never again need to deal with a similar situation. I.E. review testing rules, who may test and how results of testers get handled]