Andrew Garrett wrote:
I've today developed an extension based on Special:Makesysop that may be a solution to the problems (at least on en: ) with the process of gaining adminship. Part of the problem with adminship is that it is somewhat difficult to remove. This extension may change that. The extension, as currently configured, allows local bureaucrats to desysop a user. I believe that this is sensible. If we can trust bureaucrats to set the sysop bit, why shouldn't we trust them to remove it? Additionally, desysopping is quite a political issue, and generally requires the intervention of somebody *familiar with the situation*, not an outsider who has simply been informed. Therefore, I suggest that we use this extension to allow Bureaucrats to desysop users in serious cases of abuse of powers. A different process for desysopping may need to be developed to accompany this - and a policy on when bureaucrats may use this ability.
Questions, comments and requests for demonstrations are more than welcome.
I welcome this, and fully agree with your analysis. Any project that is big enough to have at least two bureaucrats should be big enough to establish its own policies on this.
There are really two very different cases where the right to desysop. Abuse of powers is one of those situations, as you have described. Another situation might be extended absence. In this case the individual would only need to shoe that he is back and active to the satisfaction of a bureaucrat to have the status restored.
Ec