Extension talk:EmergencyDeSysop

Regarding the bureaucrat caveat: if it's possible to abuse it, they will. They'll write it up as a policy, and then sysops will be asked not to do it themselves, they'll just request that a bureaucrat do it and then routinely resysop themselves. Bureaucrats will ask "why do we have to go through a complex and counterintuitive process in order to desysop someone?" And then there will be pressure on developers to open up desysopping for bureaucrats using the normal user interface. -- Tim Starling 06:43, 30 October 2008 (UTC)
 * Agreed, this extension only makes sense when the political configuration is such that bureaucrats are allowed to desysop at will. Tisane 16:51, 24 March 2010 (UTC)

Does not work
Actually tried testing this out; I couldn't get it to work. I get: Fatal error: Call to a member function commaList on a non-object in /var/www/w/extensions/EmergencyDeSysop/SpecialEmergencyDeSysop.php on line 104 With trunk. Any ideas would be appreciated. Jake Wartenberg 02:38, 31 May 2009 (UTC)

Suggestion
Why not, instead of making the sysop who uses this sacrifice his bit, give each sysop one credit, which he can "spend" to desysop another admin? A bureaucrat can later give him another credit for future use, but no sysop can ever have more than one credit at any given time. This is assuming a system in which bureaucrats have power both to promote and demote admins; otherwise, desysoping by admins will inevitably throw the system out of balance. Tisane 11:54, 26 March 2010 (UTC)