User talk:NoSeptember/Desysop

From Wikipedia, the free encyclopedia

Contents 1 Ed Poor 2 Radiant!'s opinion on the resysop attempts of involuntarily desysopped admins 2.1 Evidence presented by Radiant 2.2 The Adminship Matter 2.2.1 Footnote to the above 3 Arbcom related controversy

[edit] Ed Poor

Ed Poor unsuccessful resysop request: Wikipedia:Requests_for_adminship/Ed_Poor. Phr (talk) 05:57, 13 August 2006 (UTC)

Ed wasn't active at the time, and so never requested the nomination and never accepted it. --Interiot 06:06, 13 August 2006 (UTC)

[edit] Radiant!'s opinion on the resysop attempts of involuntarily desysopped admins

The folowing view of Radiant! comes from Wikipedia:Requests for arbitration/Giano/Evidence

[edit] Evidence presented by Radiant

[edit] The Adminship Matter

The heart of this case, and a perennial cause for dissent in a variety of other forums, is our somewhat nebulous standard for adminship. As we all know, adminship can be granted through the community process at WP:RFA, and can be revoked by the arbitration committee. The problem is that these two forums are increasingly divergent:

• Requests for Adminship has an exceedingly high standard of adminship. It is possible for a nomination to fail on any of a number of relatively unimportant matters, such as editcountitis, lack of a userpage, and using a swearword several months ago.
• Arbitration has, by comparison, an exceedingly low standard of adminship. Although demotion is becoming somewhat more common, an admin has to do some very extreme things before having his status revoked.

A resultant problem is that this is becoming a source of mutual distrust for both parties. It is not uncommon for people who are somewhat in doubt to oppose an RFA because they did not trust the ArbCom to demote the candidate if he does turn out to be problematic later. On the other hand, in the recent Giano debacle it was commented that some arbitrators were reluctant to demote admins because they didn't trust the community to ever reinstate a once-demoted admin.

The circular reasoning is obvious, and the only way to stop the dissent is to reach a compromise. It should be noted, however, that it is not (or not yet) as bad as some people on both extremes appear to think. As I just stated, admin demotion by the ArbCom is becoming more common; and while indeed most renominations of demoted admins have failed, it is important to note that nearly all of the failures were for reasons unrelated to the demotion.

Circular reasoning works both ways. If either party can be convinced to change their standards, the other party will have increased trust in that party and respond by similarly changing their standards. That way we can go back to adminship being No Big Deal. >Radiant< 16:58, 25 September 2006 (UTC)

[edit] Footnote to the above

The below is a list of renominations of ex-admins that failed, but did so for reasons unrelated to the demotion - such as edit warring, sockpuppetry or perceived abuse of process. There are generally a few people that hold a long grudge, but far from enough to sway consensus.

I have ignored the few RFAs that were just a few weeks after the actual demotion (Karmafist, Carnildo 2 and Everyking). I have also omitted the nominations for KI and Pegasus1138 since the public was not aware that these were in fact former admins. And of course I have omitted the nominations that were succesful.

• Aevar Bjarmason failed because a few days earlier, Aevar used his developer status to give himself admin rights in order to perform a block of no particular urgency.
• Chacor failed because of recent issues of edit warring and sockpuppetry.
• Guanaco 2 failed because he was recently advocating that Willy on Wheels should be unbanned, and creating a controversial poll on the subject.
• Guanaco 3 failed because he was not a very active editor in the months before the nomination. When he became an active editor again, his renomination succeeded.
• JTkiefer failed because he had recently failed four other RFAs under a pseudonym.
• Kils failed because he had barely any activity in the year before, and there were civility issues.
• Stevertigo failed because his nomination itself was full of unfriendly statements against the ArbCom, and during the debate he was incivil to several participants.

It seems that any ex-admin demoted by the ArbCom has a snowball's chance of getting reinstated by RFA for the first month or two, and after that is treated by the process mostly like any other candidate. This is good, since an encyclopedia shouldn't hold long-term grudges against enthousiastic contributors.

[edit] Arbcom related controversy

What's the criteria for whether users are listed in the "arbcom related controversy" section? Is it different from the set of people who likely/certainly need to go through normal channels to re-sysop? If not, might those be noted at some point? (though I guess it's possible that only a small handful will be made clear by arbcom, whereas most decisions will be made by crats at the time of request) --Interiot 16:45, 11 October 2006 (UTC)

I use this category for those who were likely to lose their sysop status by the action of ArbCom in a pending case but had themselves desysopped before the case closed. In other words, they would have been involuntarily desysopped had they not acted first.
There are a number of other admins who were involved in cases at the time that they requested desysopping, but there was no indication that ArbCom was about to remove their sysop status in the case (at least not more than just temporarily). These admins are still listed as voluntary desysops. If ArbCom later imposes the requirement that they go through RfA to regain sysop status, that does not change the fact that the actual desysopping was done voluntarily without pending action by ArbCom to desysop. NoSeptember 10:12, 24 October 2006 (UTC)

Well, this list is in your userspace, or I'd edit it. Tony, for one, was surely under the hatchet when he resigned. I know, I was there; I read my way through more wordsmog than an ambulance-chaser blurts out in a month. If he hadn't resigned, he'd have been deadminned.

Once ArbCom rules than a deadminning, however voluntary, was done under a cloud and the subject must re-apply through RfA, it's substantially the same as a direct ArbCom deadmin. WP:HORSE. John Reid 03:48, 2 November 2006 (UTC)

The key is the willingness and inclination of the arbitrators to actually forcably desysop someone. Non-arbitrators outnumber arbitrators by a large ratio, so even if dozens of users call for a desysopping, you have to focus on the inclinations of the arbitrators who will make the actual decision. If you can point to any indication that an arbitrator was inclined to forcefully desysop either Kelly or Tony as a remedy, then a redefinition may be considered. Although a lone arbitrator who is out of step with the others is also insufficient to make the case (note Fred's call for Geogre's desysopping). Also, there is certainly a difference in setting a standard for regaining adminship, and proactively moving to have someone involuntarily desysopped. NoSeptember 14:48, 5 December 2006 (UTC)

Additional note: ArbCom does indicate when it was prepared to desysop someone who resigned first. Note the "Konstable formally desysopped" remedy in a recent case. NoSeptember 09:26, 12 December 2006 (UTC)