You cannot. That's why this is a bad idea. We have an instance of a developer (in good faith!) not determining consensus at the appropriate percentage level (whatever percentage consensus allows this week, sheesh). Saying "ArbCom or Bcrats must review every developer request so they can submit it" is inherently a /bad idea/. I've made quite a few requests for new features, etc...and I didn't ask the en.wiki community first. Under the new system, would that lead to a block? Why can't a well-intentioned user make their own requests, and not have to jump through a million hoops to do so? No one is going to want to fill out a WP:RFARODR (Request for Arbitrator Review of Developer Request) and wait a month for the Arbs to review it just to get stuff done.
It's all adding to the useless bureaucracy.
Always, Chad
On Jan 13, 2008 9:24 AM, Gerard Meijssen gerard.meijssen@gmail.com wrote:
Hoi, In a different thread people told me that you can not make people do things. Things can indeed change.. Thanks, GerardM
On Jan 13, 2008 1:12 PM, Thomas Dalton thomas.dalton@gmail.com wrote:
As far as I know, it is not a role of the arbcom to do such things. It looks weird to add new responsibilities.
It's not a role of ArbCom, no, but things can change. I'm suggesting that it become a role. The alternative is to use crats, as determining consensus is definitely part of their role and this is just applying the same skills to another situation. Personally, I'd rather give the job to ArbCom (assuming they don't have any major objections), but it doesn't really make a lot of difference.
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: http://lists.wikimedia.org/mailman/listinfo/foundation-l
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: http://lists.wikimedia.org/mailman/listinfo/foundation-l