QUOTE(Moulton @ Tue 15th June 2010, 9:12pm)
QUOTE(Abd @ Tue 15th June 2010, 3:27pm)
Moulton, it seems you think that becoming an administrator is a reward.
It's more like giving an angry child a gun (and telling him not to shoot anyone in anger).
I dunno if SoD learned anything, but I doubt it.
SoD learned that he couldn't outfox SBJohnny. I don't care of SoD learned anything, particularly. He was not there to learn.
"Adminship" is not like giving an angry child a gun, per se, rather adminship given to an immature and angry person is like that. Except, Moulton, it's not a gun and the tools don't allow the child to kill anyone. The problem is lack of supervision. There is nothing wrong with giving admin tools to children on a wiki (not generally, anyway beyond issues of what might become visible to them, etc., I'd want to see parental permission, for example, under the age of consent, and maybe that should be the limit; but maturity isn't automatic with age. I'm living proof!)
These immature administrators on Wikipedia are mostly unsupervised. That's not the case on Wikiversity. Any user who wants to know what's going on there, at this point, can look at Recent Changes. It's easy, there isn't all that much traffic. It's easy to review the logs and see what's been deleted and who has been blocked. If I screw up, I find, it's immediately seen and there is comment and helpful correction. SoD didn't have a chance, and if he'd decided to use those tools improperly, all it would have taken is one person noticing it and complaining. SBJohnny wasn't fooled. He called the bluff of SoD, in one of the more skillful and beautiful pieces of wikipolitics I've seen. Pure benefit, no down side, as long as he was around to watch and handle it. (That would have been the only defect, if he became unavailable.)
And when SoD announced he would be away for a while, SBJ asked him to check in the keys, if he didn't mind.... and if he'd minded, SBJ, I'm assuming, would have taken them anyway. He'd arranged prior consent to SBJ requesting tool return from a Steward, for that to be done. It really should be general for WV admins, with the "probationary custodianship" provision.
I wrote, in my RfA (custodian) there, that any action of mine as a probationary custodian could be reversed by any admin who supported my RfA, and that, if I did not keep this promise, I consented to being desysopped immediately by a bureaucrat on the request of any of these admins. There was a possible attempt to convert this into some kind of prejudice against non-admins which it surely wasn't. I've been explicit that admins have no superior rights except in acting as servants of consensus, which is only provisional and temporary.
This understanding, which was clear to me from early on at Wikipedia, as being the theory behind the adhocracy, I later found wasn't at all understood by many admins. There are quite a few who, based on what they've stated to ArbComm in various cases, should be desysopped based on the danger that they will act as they have claimed is legitimate, until they assure ArbComm they now understand recusal policy and will not violate it. Not a punishment for speech, rather a protection based on clear danger.
But ArbComm is terrified of offending the "critical volunteers." The fact is that there would be more volunteers than the project would need, *if* there were mentored adminship like that on Wikiversity. I see no reason not to do it on Wikipedia. There simply need to be rules for probationary admins, clear ones, and rules for mentorship, with assigned responsibility to watch and review a probationary admin's actions. That review needn't be by an admin, necessarily, but by a trusted member of the community, it's at least as important as the reliability of the admin himself or herself. It's like having watched articles: watched admins. An admin who doesn't want to be watched shouldn't be an admin. I can say, being watched at Wikiversity makes me feel much safer. If I screw up, someone will tell me, quickly. Gradually, that watching will fall away, I assume.
But every admin should have what I'd call a recall committee, a set of active admins who have the authority to immediately request the admin stop some action or class of actions. This would be explicitly accepted, with named admins, as part of the RfA. (They would not be hostile admins, to be sure, but would be those offering to mentor and being accepted in that role, and being responsible to, themselves, not be abusive in that.)
I also argued before ArbComm that any admin should, emergencies excepted, where different rules apply, recuse from using tools with respect to any user who requests it. That was thought preposterous, because recusal is often not understood.... If I block VandalOckSay, and VandalOcksay then asks -- or demands -- that I recuse, I don't therefore unblock! Rather, I make the evidence on which I blocked plain and clear and stand aside, agreeing to not consider reversal of my decision to be wheel-warring. Now, suppose VandalOckSay does this for three admins in a row, say. VandalOcksay remains blocked until a fourth one shows up. And what does this fourth admin do? Obviously, it depends on the evidence, but ... the most likely outcome is far from the victory for wikilawyering that was claimed would happen. VandalOckSay is indef blocked, quite likely.
That's with a large site. On smaller sites, one can't go that far, but an unblocking admin, if there is any reasonal objection to the editor's behavior, would set conditions for unblock that would address this. If the editor refuses to comply, or violates the agreement, that admin could block and recuse on request. Not a good idea for the user unless the user really does feel the admin is biased. And attacking a blocking admin on the basis of bias is absolutely not the way to get unblocked! Almost never works.