Wikipedia:Community de-adminship/RfC

This is a Request for comment (RfC) on a proposal to implement Community de-adminship (CDA) on the English Wikipedia. Community de-adminship (a form of Administrator Recall), would be a method for the Wikipedia community to remove the administrator tools from existing Administrators who have lost the confidence of the community.

• You can read the CDA proposal here.
• You can read an F.A.Q., prepared by editors who worked on it and support it, here.

This page opened for comments 18:50, 22 February 2010 (UTC), and will close 23:59, 22 March 2010 (UTC).

The proposal

The community is being asked whether a proposal for community-based removal of administrator privileges, called Community de-Adminship (CDA) should be implemented as policy on the English Wikipedia.

If WP:CDA is adopted this will require two other amendments:

• The Wikipedia:Guide to Community de-adminship will be described as a "guide to current practice" in the same way that Wikipedia:Guide to requests for adminship is at present.
• It will also be necessary to amend the policy Wikipedia:Administrators to include reference to the WP:CDA process. This step will be undertaken as a technical matter at that page as and when needed.

• A selection of userboxes is here.

Closure

When the debate here is concluded, it will be closed in the usual way. If sufficient consensus has not been reached after thirty days, and further discussion would be useful, it will be extended.

If the RfC ends in consensus to implement, such implementation will then be subject to review by the Bureaucrats and Jimmy Wales.

Discussion

Comments by some of the editors who prepared the proposal

See also: Wikipedia:WikiProject Administrator/Five Problems with a Single Solution

This discussion follows on from those at:

• Wikipedia:WikiProject Administrator/Admin Recall
• the associated talk page.

There, a poll was conducted that attempted to evaluate the levels of community support for various proposals seeking to create a method by which the community at large (as opposed to Arbitration Committee) could pass comment on the actions of and if necessary remove the tools from, existing Administrators.

The main conclusions of this poll were as follows:

1. The status quo, (i.e. no such process being available) whilst garnering some support, was very unpopular. 77% of respondents did not support its continuation.
2. Only one proposal achieved a greater degree of support than opposition – "Wikipedia:Community de-adminship" (CDA) – which received a majority of 13, and the support of 65% of those who considered it. This proposed process was designed as a "mirror image" of the existing Wikipedia:Requests for adminship (RfA), and part of its appeal was evidently its familiarity.

The reasons for dissatisfaction with the status quo are complex and varied, but a view was regularly expressed that if the community at large has the authority to appoint administrators through the RfA process, then the community should also be able to remove their powers.

This led to lengthy discussions at:

• Wikipedia talk:Community de-adminship/Draft RfC

which attempted to iron out various issues in the then existing Guide to Community de-adminship. This resulted in:

1. Some wording changes and clarifications as identified above (Section: Update from WT:CDADR). Few of these were controversial.
2. An increase in the nomination period from 3 days to 7 days.
3. More emphasis on pre-nomination attempts to resolve any disputes.
4. Most complex of all, a more specific statement about how the outcome shall be judged. Various options were considered and two specifics are identified as part of this RfC (see below).

In many cases the above discussions were a conflict between:

• The desire to make the process simpler or easier to implement in order to avoid allowing those perceived as having abused their Administrative tools to continue without fear of sanction, and
• The desire to avoid a system in which Administrators, who almost inevitably find themselves taking on potentially controversial tasks on the community's behalf, are discouraged from taking action for fear of reprisals via a Recall method that is too easy for aggrieved editors to make use of when they don't get their way.

The resulting changes to the Guide to Community de-adminship were a compromise between these two poles.

Flaws in this process noted by TenOfAllTrades

Issues of procedural fairness

By far my greatest concerns about this process turn on its gross unfairness to its participants — especially the administrator being examined. The proponents of the process have been very concerned about creating a process which is very rapid, which has a low barrier to entry, which sysops should find genuinely threatening, and which has a 'democratic' appearance. Unfortunately, the result is a process that does not contemplate an administrator who wants to defend his actions, situations where there is misconduct by multiple parties (particularly by the nominators), or any interest on the part of participants in examining the evidence or discussing the situation.

The final accounting

The way in which CDA proposes to close its discussions is flawed and prone to failure.

The role of Bureaucrats

By far the most visible role of Bureaucrats on Wikipedia is in the evaluation of Requests for Adminship and the promotion (or not) of new admins. They have both the technical and policy means to grant the sysop bit within the framework of existing policy. What they cannot do - under policy and by deliberate design of the wiki software permissions - is remove the sysop bit once granted.

What this CDA proposal aims to do is grant bureaucrats a new power to enact desysopping decisions. This represents a substantial expansion and shift in their powers and responsibilities.

Simpler approaches have not been tried

The proponents of CDA have spent a substantial amount of time and effort to construct this elaborate proposal, but we are still left with the serious flaws detailed above. More unfortunately, they have rejected any suggestion that their goals could be accomplished by different, simpler means. Indeed, I believe it is possible to achieve the goals of this process without any need to write new policy at all.

In summary

For this long list of reasons, I find that the proposed process and structure are unfair and untenable, and unlikely to benefit Wikipedia. Virtually all of these points were brought up during discussions about the CDA process, but no resolutions were forthcoming. I must therefore oppose this proposal. TenOfAllTrades(talk) 20:13, 22 February 2010 (UTC)

I'm going to try to refrain from making a habit of disputing every criticism raised, but I do feel compelled to point out one thing. In the second part of the first group, the issue is raised of the conduct of one editor. That editor does not speak for the other editors who support this proposal (as neither do I) and in fact is now an opponent of it. --Tryptofish (talk) 20:23, 22 February 2010 (UTC)

I actually was in the process of amending that out when I saw your comment here. I don't think that this process should be accepted or rejected based on the (mis)behaviour of one individual. TenOfAllTrades(talk) 20:34, 22 February 2010 (UTC)

Thank you for that. If, as the RfC goes along, editors would like for me or other supporters to respond to any of the other points you have raised, I'll be happy to give it a try, but I figure it would be premature and maybe kind of badgering for me to do that now. --Tryptofish (talk) 20:37, 22 February 2010 (UTC)

Thanks for preparing this material. I think there is a lot of meat here: first, with regard to the diminished fairness of this process versus the existing. Second, with regard to the manner in which this proposal, while attempting to derive authority by styling itself as an offshoot or modification of an existing process, actually has little to no relation to any currently existing process; its closest forebear is probably the dramatically failed Wikipedia:Quickpolls. It's quite unpredictable how this will act in practice and the proponents have consistently refused to engage with any attempt to explore this issue. Christopher Parham (talk) 20:25, 22 February 2010 (UTC)

Rebuttal to TenOfAllTrades by Tryptofish

The nature and development of the CDA process

• "The glib assumption that since the effect of the two processes mirror one another then the mechanics of the processes ought to mirror one another too does not stand up under scrutiny." Although earlier versions of this proposal were written as "reverse RfAs", the actual proposal presented here has moved beyond that glib oversimplification. Please read what the proposal actually says. The mechanics of the process are not by any means a mirror of RfA. Anyone can start an RfA, but the barriers to getting a CDA certified are considerable. TenOfAllTrades makes valid points that that the ten nominators should perhaps not !vote, and that there should be a dedicated space on the CDA page for the administrator's response. It is becoming clear that supporters of the proposal are friendly to correcting these two points. However, the fact remains that the community that confers RfA ought to be able to make use of CDA. Being an administrator is not a right.
• Was the process of working up the proposal a mess? No argument from me. I was involved in it from beginning to end, and it often felt like root canal! But we are here to evaluate the proposal, not the proposers, nor the process that led to the proposal. The claims that there were never opportunities to modify the proposal are, however, utter nonsense; indeed, the opportunities probably went on for too long. For editors coming to the discussion of this proposal for the first time, I urge you to read below and see what happens when opponents of the proposal have been invited to make suggestions for improving it. TenOfAllTrades frames the process as being one where he and others offered improvements, but were turned away. While I do not deny that some of my colleagues have been unpleasant at times, the truth is that Ten and others simply said that the proposal being prepared was a waste of time and should be abandoned. I've read the quoted analogy many times, and I still do not get the point of it.
• Please read the FAQ, number 11, for why we have refrained from "naming names" of administrators who might be subject to this process. It has apparently been a strategy of some of the opponents of the proposal to try to bait supporters into naming specific administrators who would be CDA candidates. A very few supporters in this poll have unfortunately done so, and it is worth noting how little other users have endorsed this unfortunate behavior. In contrast, supporters have in no way "repeatedly rejected calls to describe any specific situations" where CDA would apply. We only reject calls to name names, to make personal attacks. I invite you to look at my own comment at "support #1", where I describe non-"bright-line" situations for which CDA is well-suited. The proposal calls for an automatic review after one year or five nominations, and the community can evaluate it by whatever "metrics" the community wishes.

Issues of procedural fairness

• Many of the points raised are stated melodramatically, but do not hold up under scrutiny. The wording in the proposal about accountability for those who start the CDA is actually quite strong, not "vague acknowledgment". Does it really make sense to build into the process a requirement that nominators be evaluated for sanctions as part of the CDA? CDA is no different from any other process of dispute resolution on this project, in reality, with respect to complainant accountability. As with any other process, parties who are observed by members of the community to be acting badly can be brought to the appropriate noticeboard. Will such bad actors tend to make unfair complaints of revenge seeking and such? Yes, but they do that now, and our dispute resolution procedures allow the truth to be sorted out. The actual proposed policy allows for a deliberate and thoughtful discussion of the case, with plenty of opportunity for the accused administrator and defenders to present a detailed rebuttal and have it considered before the polling is closed.
• Canvassing: read the proposal. The accused administrator has plenty of leeway to "canvass" help from those with exonerating evidence. There are significant restrictions on canvassing by those accusing the administrator.
• Despite the claims made, any certified CDA will be well-publicized and will be able to draw a representative portion of the community. Required publicity includes the administrators' noticeboard. Let me repeat: every CDA must be publicized at the administrators' noticeboard, allowing any interested administrator to be aware of the proceedings and to come and rebut any claims they choose. There is every reason to expect that editors will come to the defense of a good administrator unjustly accused. Just look at the responses here at this RfC! It sure looks like there are plenty of community members who are sensitive to the need to come to the defense of good administrators. (Why isn't there some unruly mob pushing this proposal through?) In fact, a case could be made that administrators (some of them, not all!) would vote in a block to provide the 30-40% margin to defeat any CDA.
• The accused administrator does indeed have the opportunity to present a defense. There is an entire section of the page for that purpose.
• The proposal requires discussion on the poll page, while the associated talk page is for peripheral matters. In fact, per !votes and !votes without explanation are to be discounted.
• Not enough time for the administrator to respond? Seven days before the CDA can be certified, and at least seven days before the polling is closed (unless a snow close for "acquittal").
• "[D]o we let the defendant go free, or do we send him to the gallows?" No opportunity for compromise solutions? One can !vote against removal of administrative rights, which is the logical thing to do if one disagrees with de-sysoping, and comment on milder alternatives. Again, discussion, which includes discussion of compromise outcomes, is actively encouraged.
• As for bites at the apple, please read what the proposal actually says about multiple nominations against the same administrator for the same reasons.
• Sensitive, confidential information sometimes comes into play at RfA too. It has been handled there by a trusted person (often a Bureaucrat) reviewing the matter independently and reporting the nature of the situation to the page, without breaching privacy.

The final accounting

• "Are the 'crats expected to determine if a consensus exists, or just to count votes and add a veneer of respectability to the process?" The language of the proposal clearly answers that question: they are expected to determine consensus and not simply count votes. (Those "wild-assed" thresholds went through more hand-wringing discussion than, I don't know what. If you would like to take a look at the sausage-making, you can start at Wikipedia talk:Community de-adminship/Draft RfC/Archive 1#5. Need more concrete percentages for de-sysoping, and go on to Wikipedia talk:Community de-adminship/Draft RfC#January Poll.) If the numbers do prove to need tweaking, that will become apparent through experience, but is it really that difficult for a Bureaucrat to determine consensus here? If, after discounting all the per !votes and out-of-policy statements and ineligible comments and so on and on, there are 70% or 80% of the community saying they have lost trust in the administrator, is it really such a hard call?
• If one Bureaucrat is unsure of the decision, they can consult others or extend the poll period, and there are mechanisms for appeal.

The role of Bureaucrats

• Yes, this would represent an additional role for them. Are they really not up to it? Are they really more fallibly human than Arbitrators? The questioning of Bureaucrats' ability to determine consensus appears to be incredibly overblown.

Simpler approaches have not been tried

• This proposal would not do away with RfC/U or ArbCom. It gives the community an alternative. In developing this proposal, many editors looked at many alternative methods, and they all have shortcomings. (Please see Wikipedia:WikiProject Administrator/Admin Recall. And when you do, please take particular notice of the discussion of the status quo as the first option considered. It was overwhelmingly rejected.) It's easy to say there is some better way, but what is it, and what would it look like after scrutiny like that here?
• This proposal is, in many ways, an alternative to making RfA more difficult. Do we really want to make RfA more difficult? The existence of CDA should actually be a sort of stress-release for RfA, in that a positive RfA decision would not be irrevocable.
• As for how ArbCom is changing, there's an interesting chicken-and-egg phenomenon. I agree that the community as a whole is evolving towards higher standards of expectation, and both this proposal and recent trends at ArbCom reflect that evolution of standards. Perhaps the knowledge that this proposal was being developed was present in Arbitrators' minds; I don't know. Perhaps the very existence of CDA would make the few problematic administrators behave better and obviate the need for formal actions. It's hard to tell. Perhaps this very RfC is contributing positively to this evolution.

In summary

If you haven't already, please read the proposal itself. I think you will see that it is much better thought out than the critics portray it as. And please read the FAQ, as well as the excellent essay Wikipedia:WikiProject Administrator/Five Problems with a Single Solution. It is only fair that the community be able to withdraw its trust, once given. The procedures in this proposal actually make it very difficult to apply CDA frivolously. It will be an improvement over the status quo. --Tryptofish (talk) 06:41, 23 February 2010 (UTC)

Revised and expanded. --Tryptofish (talk) 00:04, 28 February 2010 (UTC)

I hope that readers of the 'Five Problems' essay also look at its talk page, where I (and another editor) raised clear concerns about 'The Fix' described: Wikipedia talk:WikiProject Administrator/Five Problems with a Single Solution. I will avoid a point-by-point counter-rebuttal of Tryptofish in this space, as I feel that readers of this page can compare my comments with his glib dismissals to reach their own conclusions.

I will raise one factual point, however. Regardless of what Tryptofish states above, the sample CDA page (Wikipedia:Community de-adminship/Example) does not now include – and to my knowledge has never included – any space in which the accused admin can offer a statement in his own defense. The proposed policy is equally silent on this point. Whether this oversight is deliberate or accidental, the statement that "[t]here is an entire section of the page for that purpose" is flatly untrue. TenOfAllTrades(talk) 15:07, 23 February 2010 (UTC)

Then please let me clarify. The section to which I referred was the "oppose" section. Now, that said, perhaps you raise a good point, that the Example page should be modified to have a section specifically for the nominated administrator's rebuttal. That would be very easy to add with a simple edit, and is hardly a convincing reason, by itself, to oppose the proposal. And please do not insinuate about "oversight is deliberate". --Tryptofish (talk) 16:35, 23 February 2010 (UTC)

That you believe (or believed until now) that it is appropriate and sufficient for the sole response from the admin on the CDA page to sit jumbled in with the 'Oppose' votes is telling. In any event, being permitted to make a few brief comments in a numbered list of votes is not the same thing as having "an entire section of the page".

When I suggested that the oversight was deliberate, I didn't mean that you were wilfully misstating the content of the proposal. I did mean that leaving out any dedicated space for an admin to respond to the charges might have been a conscious choice to further grease the wheels of a desysopping. TenOfAllTrades(talk) 17:18, 23 February 2010 (UTC)

Who, me? I was just trying to help make a good proposal. --Tryptofish (talk) 17:24, 23 February 2010 (UTC)

In my opinion, both would be extremely helpful: a) to include a prominent space in which the accused admin can offer a defensive statement(s) and b) to enhance the proposed policy to clearly articulate this point. I'd even go so far as to require the accused administrator to make such a statement, however succinct or not so.Duff (talk) 21:28, 26 February 2010 (UTC)

• You can't require a volunteer to do anything. --Hammersoft (talk) 21:33, 26 February 2010 (UTC)

Duff, as discussion here continues, I'm increasing convinced that you are correct. That's the kind of thing Ohm's Law was asking in #Intentions, below. (As for Hammersoft's point about not requiring, I would think that a non-response would be considered as such by the community.) --Tryptofish (talk) 21:50, 26 February 2010 (UTC)

To me, it does seem reasonable to REQUIRE an admin to respond to such a process (should this RfC result in one), once a nomination for CDA has certified and the CDA candidate is under consideration, if they want to keep their buttons. Of course you can't FORCE anyone to respond, volunteer or otherwise. Too, there might arise some now-unforeseen situations wherein the interests of the CDA-nominated admin or of the project are seen as best served by offering no defense. If so, a brief statement to that effect could be required of the admin and any such situations could perhaps be evaluated in context, as they emerged.--Duff (talk) 00:39, 27 February 2010 (UTC)

One issue related to that point, that came up in earlier discussions, is whether an administrator could game the system by choosing not to offer a defense, and then claim that they didn't know the CDA was taking place until it was too late. At the time, the decision of editors discussing the issue was to not require a response, and to trust the closing Bureaucrat to know the difference, with appeal possible in the unlikely event that the administrator really was on a break. (After all, there's a difference between a pre-announced wikibreak during which the administrator has had no user contributions since before the nominations began, and a simple absence of a defense during a period when other edits occurred.) --Tryptofish (talk) 17:35, 27 February 2010 (UTC)

Expression of concern

The "ombox"

Observations re Casliber's comment

(In relation to oppose 34)

Why is the community is reluctant to make such requests [desysops — Coren] to ArbCom? I think it's an interesting observation, and I'd like to understand it better. --Tryptofish(talk) 23:23, 23 February 2010 (UTC)

If I were to venture a guess, I would say that ArbCom's traditional willingness to look at the behavior of all parties when a case request is filed is probably a significant factor (since the filing parties are often involved in a direct personal dispute with the admin in question). When the matter is brought by uninvolved members of the community, ArbCom is much more likely to handle the matter by summary motion instead — especially if the facts themselves are not disputed — but that's a fairly recent development in the procedure and the community is only recently warming up to it. — Coren ^(talk) 01:30, 24 February 2010 (UTC)

This is very interesting to me, and I'd like to pursue it further. Please understand that I'm not finding fault with ArbCom in any of this, but rather, exploring what I think may be good ideas to come out of this poll. If I understand Casliber correctly, he is talking about situations where there might have been good and valid reasons to bring the administrator in question before ArbCom, and, thus, ArbCom would have been quite happy to act. In contrast, I think Coren is talking about situations where the accusers are either misguided or have an ulterior agenda. I agree, and I think pretty much everyone would agree, with Coren that those are cases where the problem lies with the accusers and not the accused. ArbCom is right to look at that. But Casliber's point seems to be about editors who have acted in good faith and who have legitimate concerns, and yet who seem, somehow, to feel inhibited from approaching ArbCom even if ArbCom would have welcomed that approach. I've taught college courses long enough to know that, when something like that happens, there's a problem with mixed signals. Rather than just blaming this on the community, is this a signal of somewhere that ArbCom could do something better? --Tryptofish (talk) 19:34, 24 February 2010 (UTC)

I think it's a matter of perception. Editors, rightly or undeservedly, felt that bringing any admin behavior to ArbCom would result in an extended ordeal that could very well end up having them sanctioned. Because there were basically no mechanisms for a swift resolution without a protracted "full" arbitration case until fairly recently, that perception ended up being accurate enough to discourage filing — even if it was from an editor acting entirely in good faith.

That, and the common misperception that admins are untouchable in practice because of cabals or cliques, probably did more to protect ill-behaved administrator than any genuine reluctance from the Committee to take the bit away. — Coren ^(talk) 01:06, 25 February 2010 (UTC)

Yes, Coren sums it up well - I was going to post something along those lines above. Before I joined the arbitration committee, my impression was that there was a reluctance to review admin conduct (looking back this may have in fact been as much about editor reluctance to notify arbcom as well...). Since then, I have tried to remind the community at large just about as often as I could that the arbitration committee is available to review admin conduct - mainly with the hope that there would be greater fluidity at RfA. My gut feeling is that a few (but not many) editors (based on the greenness of experience and what they bring to RfA) are being given a chance with the mop that might not have been two years ago, but I could be completely wrong about this. Anyway, I have seen large numbers of complaints about admin conduct about where no further action has taken place. Hence I can only surmise this is where the breakdown is occurring. I also believe that the existence of community deadminship will not result in RfA being any easier. Before I joined arbcom, I told all and sundry I'd continue writing articles and participating in community activities - I hate the idea of the committee as shadowy figures who do little else but arbitrate. I get the impression that many of the committee are more visible now (though my lack of involvement in these matters before late 2008 may colour my view....) Casliber (talk · contribs) 01:26, 25 February 2010 (UTC)

One of the best points made by Ten is that this proposal basically gives you a free shot at an admin. If he escapes you are no worse of and can try it again at your convenience. If you take an admin to ArbCom, you are going to find yourself under a microscope as well as him. Note also the disadvantages in responding by the admin that have been pointed out in this proposal. They don't apply in an ArbCom case. --Wehwalt (talk) 01:49, 25 February 2010 (UTC)

Wehwalt, I don't buy the argument that a bad-faith nomination at CDA lets the nominators off scott-free. They would be putting themselves in a very public place, and there would be plenty of opportunity for the administrator's defenders to bring them to the appropriate noticeboard. As I read the oppose comments, it actually occurs to me that bad-faith nominators might end up revealing themselves as the trolls or whatever they are, once and for all, if they make the mistake of starting a bad CDA. In fact, you are (unintentionally) underscoring the kind of misperception that Casliber is trying to correct, I think.

Anyway, thank you Casliber and Coren for your insights here. I continue to find this very helpful to discuss. I want to explore this further. For now, let me please ask this: In the second part of my support !vote number 1, just below, I raise the issue of non-"bright-line" misbehavior. Do you feel that ArbCom is becoming able to work with cases like that? --Tryptofish (talk) 02:02, 25 February 2010 (UTC)

It would be called "revenge" "escalation" and "battlefield mentality" if the admin's friends sought to brink the noms to account elsewhere.--Wehwalt (talk) 02:12, 25 February 2010 (UTC)

But if they were right to bring them to account, that would just be name-calling. --Tryptofish (talk) 02:22, 25 February 2010 (UTC)

Okay, is arbcom able to judge on 'non-brightline' cases? Yes I believe so and I'd say that to me it seemed easier to review and desysop an admin than ban an editor for a significant hsitory of -just-under-the-radar behaviour. In fact, many cases involve examining repeated behaviour over time and judging or grading sanctions often involves looking at past conduct, both before and after warnings etc. in some detail. I can think of several cases rightaway where former conduct has been considered. I'd rather not dredge up specifics here, but I invite folks to review past arbcom cases where an editor may have several findings of fact and often quite a detailed discussion of remedies and alternatives. There is nothing to say that this level of discussion cannot take place in hte process of summarily voting a motion, or alternatively a well-circumscribed case which is a review of admin tools. Casliber (talk · contribs) 02:52, 25 February 2010 (UTC)

I think this is proving to be a very productive line of discussion. (And, of course, I agree, no reason to name names.) So, if it's the case that ArbCom is prepared to deal with non-"bright-line" administrator cases, and, in cases where it is appropriate based on the facts, to remove the sysop tools—to say, in effect, that the individual no longer has the confidence of the community—why then does there seem to be a discrepancy between what ArbCom members (or at least the two members, present or past, in this talk thread) perceive as the situation, and what so many of the community perceive? Why have editors who have had good reason to come to ArbCom decided that they should not, out of fear of scrutiny, when that fear is, apparently, unjustified (for that is what Casliber says he has observed)? I can understand why editors with bad-faith motives would, properly, be dissuaded by scrutiny, but why those with good faith? Is there something about the ways that ArbCom does things, or something about the way it communicates to the community, that could explain that? --Tryptofish (talk) 19:09, 25 February 2010 (UTC)

The road to Arbcom is such a long and tortuous one, all the "have you tried other steps in dspute resolution" - it really is unrealistic to ask editors to jump through so many hoops to put a case in front of an overworked and inefficiently managed body such as Arbcom. DuncanHill (talk) 23:14, 25 February 2010 (UTC)

I've only skimmed through this, but it hits a note with me right now because for the first time ever I feel somewhat interested in actually bringing something up at arbcom. It's really unclear to me how to do so however, or whether or not it would be acceptable/appropriate/useful to do so. There is so much "think about it before filing" stuff in the arbcom instructions that I'm sort of scared to bring the subject up (that and the fact that I'm certain that I'll personally be attacked by the person in question, along with their friends...)
— V = IR (Talk • Contribs) 23:21, 25 February 2010 (UTC)

The problem is achieving a balance between "easy to file" and "orderly process" without encouraging vexatious litigation every time an admin does something one merely disagrees with.

The truth of the matter is that an admin who does things right will unfailingly accumulate opponents over time who have felt slighted by proper decision (or at least defensible decisions) that went the "wrong" way from their perspective. This is why while I agree in principle with a community-driven process to reexamine adminship, I doubt it is even possible to create one that does not open a door to simple vindictiveness and retribution.

Let's face a simple fact: many of the people who anxiously await a process like CDA do so with specific admins in mind they want to get rid of because they, at some time in the past, have ruled one way or another against them. Whether they are honestly convinced that having disagreed with their position is proof of malice or incompetence is irrelevant; as long as a process exist where a minuscule minority of "the community" gets to self-select as prosecutors, that process will be abused for POV pushing, vendettas and retribution. As someone wiser and more experienced than me once said, "When someone screams about 'admin abuse', it's most likely true – they're probably abusing admins again." — Coren ^(talk) 15:03, 26 February 2010 (UTC)

"...many of the people who anxiously await a process like CDA do so with specific admins in mind they want to get rid of because they, at some time in the past, have ruled one way or another against them..." - really ? Perhaps you have some evidence to back up this blatant stereotyping of the motivations of the supporters of this proposal ? Gandalf61 (talk) 15:16, 26 February 2010 (UTC)

Of course I do; it would be difficult to be a sitting member of ArbCom and not be painfully aware of many of the long-lasting vendettas and persistent disputes simmering (or boiling over) in many places. If you expect me to point fingers or name names, however, you do so in vain. Not only would it be very much inappropriate to do so, it is also entirely besides the point: whoever they may be does not bear upon this discussion in the least — the fact that any self-selected minuscule fraction of editors gets to say what "the community" thinks of an admin and decide whether to punish them in its name is. — Coren ^(talk) 15:35, 26 February 2010 (UTC)

You make a rather serious allegation, which you are now unable to provide any evidence for. What a fine example you are. --Malleus Fatuorum 15:37, 26 February 2010 (UTC)

No need to name any names. Just tell us many of the 100+ editors who have voted in support of this proposal below want to "get rid of" specific admins. As you say it is a "simple fact" then presumably you must have a good idea of the figure. Is it 50% ? 75% ? 90% ? Gandalf61 (talk) 15:51, 26 February 2010 (UTC)

I can see six on a quick skim. I doubt it's more than 10% all told, certainly. Many also did not comment either way here — but would nevertheless be available to quickly raises the torches and pitchforks should this (or a similar process) come to pass. — Coren (talk) 15:55, 26 February 2010 (UTC)

"A process exists where a minuscule minority of "the community" gets to self-select" - isn't that true of RfAd? Any process on wikipedia will be subject to a degree of self-selection, and a minuscule minority were involved in electing Arbs, a minuscule minority participate at AN and ANI, or in RfCUs. To say that a process should not be followed because not enough people would use it invalidates all our procedures. DuncanHill (talk) 15:49, 26 February 2010 (UTC)

To a point. That's actually a fair observation in general and part of the fundamental governance problem on Wikipedia. The difference with arbitrators, at least, is that they are not self-selected and are very diverse. Certainly, no group of arbs were ever convened because they had a conflict against a specific editor which — by definition — the people starting and certifying this process would be. — Coren ^(talk) 15:55, 26 February 2010 (UTC)

I think a part of that general problem is that processes are so complicated and off-putting - I had an email discussion with an Arb not long ago in which he agreed that for a particular problem I had in mind, there was no process at all that could be used, because the small-print of those he initially suggested either forbad it or made the process prohibitively restrictive and time-consuming. Processes that were simpler would attract more editors. Unfortunately, processes that are simpler to use and would attract wider participation repel those who fear flaming pitch-forks and the like. DuncanHill (talk) 16:10, 26 February 2010 (UTC)

Hi Coren. I can easily understand where this sort of slanted viewpoint comes from, but you've got to admit that it's a very jaded view which is easily attributable to your own experiences. I don't dismiss that view at all myself, but we tend to deal with the problems of individuals seeking "vengeance" fairly regularly and fairly well (on the whole) on a regular basis already, within processes such as RFC/U and RfA, within Arbcom itself, and even through noticeboards such as AN/I. People are pretty good at recognizing such motivations, largely through personal experiences I suspect, which is why I don't really give that concern much weight. This issue was addressed by the proposal, where it seems to have been decided that Bureaucrats would make decisions on all final outcomes. I've personally thought for while that the mechanisms to handle closing were over-processed and over-wrought, which is what the delay in bringing this to RfA can largely be attributed too I think. Would yourself and others feel more comfortable if this were, for example, simply a step in the path to Arbcom de-admining people based on summary motions? (ie.: placed Arbcom in the oversight role of the process)
— V = IR (Talk • Contribs) 05:01, 27 February 2010 (UTC)

That would satisfy me completely. As I (and other arbs) have stated previously, we would be glad to have a process that is more lightweight than an arbitration request where the community can examine the behavior of admins. At its conclusion, the committee can then either rubberstamp the result (if it is clear either way) or possibly remand to an arbitration case if evidence is in dispute or turns out to be too complicated for a simple yes/no vote.

I'd still have some concerns about the exact procedural details of this proposal (I would suggest, perhaps, that the editors necessary to certify the dispute not count in the vote/poll, for instance); but those concerns are workable and are no longer show stoppers in my mind. — Coren ^(talk) 14:38, 27 February 2010 (UTC)

Yes, Rockpocket suggested that also, in the "neutral" section, about nominators not voting. I think that is one of a number of good ideas coming out of this RfC. --Tryptofish (talk) 16:50, 27 February 2010 (UTC)

Agreed, I think that this is one clear direction forward. An "arbitration light" is what I've envisioned the intent here to be all along, regardless. That Arbcom would welcome such a process is icing on the cake.
— V = IR (Talk • Contribs) 05:08, 28 February 2010 (UTC)

How would such a process differ from the one that I outlined in my objection above — community consensus established through RfC, followed by a request for ArbCom motion (or case, if the issue is sufficiently complex)? Why do we need new policy to accomplish this? TenOfAllTrades(talk) 16:08, 27 February 2010 (UTC)

By being more focused, mostly. RFC tend to be difficult to sit down and evaluate because of the multiplicity of views; especially in controversial or contentious cases. Note that an RfC would do, and probably suffice in a pinch, but I can see why people feel it's a much less than ideal forum. — Coren ^(talk) 17:12, 27 February 2010 (UTC)

So then is there something to work with here, to have a modified CDA that would send its result to ArbCom, where clear-cut cases might be resolved by motion, while complicated ones would be submitted to full arbitration? --Tryptofish (talk) 00:19, 3 March 2010 (UTC)

There are a lot of interlinked issues here, perhaps none of which can be addressed in isolation. To take just one simple example, to prepare an RfC or an ArbCom case against an administrator would require the collection of evidence, which many would see as being "uncollegial" or even an "attack page" if it were done on wikipedia. In contrast, every regular editor has an easily accessible block log, so much easier to make a case. (Don't anyone waste their time telling me that administrators have block logs too; administrators are regularly allowed to get away with things that would have a regular editor blocked.) I am very much coming around to the view that fixed terms for administrators is the only fair and equitable way forward. --Malleus Fatuorum 00:38, 3 March 2010 (UTC)

I couldn't agree more, Malleus. I think the idea of nominators not voting is edging closer to a reasonable proposal, but I don't see any way to keep this process fair without burying it in bureaucracy. I can think of a half-dozen admins who I expect would be on this chopping block fairly quickly because they don't suffer fools gladly, and even though I prize civility and am perpetually amazed by the number of ill-mannered admins, I just think this idea is a case of the pendulum just swinging too far in the other direction. I've had the idea of fixed terms (not term limits, mind you, just the need to give the community another seven days to vouch for your continued adminship every once in awhile) poo-pooed because of its complexity, which I find amazing in light of the phenomenal work going on elsewhere to resolve the unsourced BLP issue. I have to think that fixed terms, though it didn't make it out of committee, would be garnering much more support here than the present idea.--~TPW 06:34, 3 March 2010 (UTC)

Well, the reason that fixed terms "didn't make it out of committee" is that the editors who discussed it then decided that other approaches were better. But I would encourage editors who like the idea to work up a proposal, and put the idea to the test. In the mean time, I'll repeat the question I'm asking here: So then is there something to work with here, to have a modified CDA that would send its result to ArbCom, where clear-cut cases might be resolved by motion, while complicated ones would be submitted to full arbitration? --Tryptofish (talk) 16:20, 3 March 2010 (UTC)

Intentions

Looking ahead slightly, I'd be curious to hear from some people in the oppose camp on what to change to make this more palatable. I'm perfectly willing to admit that I have a somewhat partisan view here, having tossed my hat in the ring on the "Support" side fairly early, but it seems clear to me that a significant portion of the the opposition here is to the current proposal, not the idea itself. I notice that someone has already forked one potential component of this into it's own proposal, but I happen to think that it would be best to keep working on this until most people find it acceptable. Part of the reason that I urged that this RFC be started was to see this exact reaction, so that we could deal with it, so let's try turning the discussion to what changes are needed.
— V = IR (Talk • Contribs) 00:54, 26 February 2010 (UTC)

I agree with and appreciate that. I'd like to add something I also said somewhere lower on the page: if (and I said if) this RfC ends up supporting this proposal, the RfC closure procedure requires review by the Bureaucrats and Jimbo before any implementation might be effected. I would certainly think that issues of this sort would have to be worked out at that stage, and so the kinds of comments Ohms is inviting are exactly what would be helpful. As far as I'm concerned, this RfC is an attempt to make Wikipedia better, not a competition. One thing I think has been pretty clear is that the "example" page needs to have a dedicated space for the administrator's response. I'm pretty sure there are other things about whether the nominators !vote or not, the amount of time for the administrator to respond, and whether there should be appeals to ArbCom. Correct? What else? --Tryptofish (talk) 01:19, 26 February 2010 (UTC)

I fear that asking "What should be the next proposal?" is jumping the gun just a bit. The assumption that the development of new processes is required has been left unexamined. As I note above (in #Simpler approaches have not been tried) we haven't generally been taking full advantage of the existing policy framework. The ArbCom has not demonstrated a reluctance to desysop (even rapidly, by motion) when presented with a clearly-enunciated request.

I don't believe it would be prudent to proceed with another three or four months of bickering proposal development without a clearer picture of what problem needs to be solved. What specific admin misconduct issues are there that the community cannot deal with now? How do we respond to those problems? At least some of the proponents have taken the view that CDA (or a variant thereof) is necessary purely to act as a threat which can be levelled at any admin. Recent events indicate why putting another arrow in the quiver purely for its own sake isn't a good idea — it discourages discussion and the use of less-formal routes to dispute resolution. It encourages parties to immediately escalate to the nuclear option – or at least, to the threat of it – and chokes off reasonable discourse. It's the opposite of the Wiki way. TenOfAllTrades(talk) 14:07, 26 February 2010 (UTC)

So, why not ask the question outright?
— V = IR (Talk • Contribs) 05:18, 27 February 2010 (UTC)

Those questions were asked outright – clearly and explicitly – during the several months this proposal was under development. The proponents have openly and repeatedly refused to discuss any specific misconduct issues that this proposal (or one like it) might be aimed at resolving. The usual reason given (and this is in their FAQ) is that any discussion of specific cases would lead to 'abusive sidetracks' and distract from the discussion. Unfortunately, this approach ensures that the community never gets to see how or even if the process would be useful. TenOfAllTrades(talk) 16:21, 27 February 2010 (UTC)

Actually, there's some framing there. The proponents have refused to name the names of specific administrators for the reasons stated, certainly. But the proponents have not by any means failed to name the kinds of conduct for which CDA is designed. See, for example, my second comments under my Support #1 !vote below. Now, that said, Ten and others who agree with him have every right to choose not to answer Ohms' question. But there is still noting wrong with Ohms asking it. Perhaps some users who oppose the proposal in its present form would like to suggest revisions to it that they would support in the future. That's entirely constructive and reasonable, for those who might wish to do so. That's what makes this process an RfC, and not simply a poll. --Tryptofish (talk) 17:05, 27 February 2010 (UTC)

• There's a number of problems with the entire body of work that went into this. Just one of them is that the RfC was started without any clear statement as to what would constitute acceptance by the community. Are we going to rely on a poll to approve a process that is not poll based but consensus based? This isn't an RfC in any traditional sense. It's a poll, pure and simple. It started out that way and remains that way. There's not much in the way of discussion by the wider community, which is what this RfC should have generated. The blessing this RfC could have been was hamstrung from the beginning. What could have happened was an open discussion about the various aspects of the CdA proposal. For example; "Should a CdA start with ten opposers before certification?" (followed by discussion). From that sort of structure, you could have readily identified what the problem areas are in the current CdA proposal. One kernel of truth that can be ascertained from the polling is that the current CdA proposal, in toto, is fraught with serious problems. But identifying what those problems are is going to be highly problematic. An opportunity was lost here. The community thinks it's voting on approving CdA, and CdA wasn't close to prime time. Now if you try to back up and get some solid discussion going, interest is going to wane. Alternatively, if you try to look at the tea leaves and discern what the serious problems are, then try another poll, the community is going to say "Didn't we just vote on this?".
• So where are we? If this thing breaks 50% by 23:59, 22 March 2010 does it then become policy? What if it sits at 49.9%? A large number of people (myself included) will state that such a major change in policy should require a higher percentage, more like 66%. Note the current bureaucrat unchecking fiasco where there's a larger percentage but heavy dispute over whether consensus exists or not. So who gets to decide an acceptable percentage of support exists?
• Also not addressed in the setup of this RfC POLL is whether or not to throw out votes based on edit counts or time of service (or both). 6 of the supporters and 10 of the opposers fail to meet the threshold of suffrage laid out by the CdA proposal itself. So, do we count people who wouldn't count in a CDA? --Hammersoft (talk) 15:16, 26 February 2010 (UTC)

  It's possible that I'm nieve here, but my personal view of this Rfc (or poll, if you'd like) is that this RFC is merely step one in what will be a multi-part process towards turning this proposal in to policy. It's a mistake, and in my view a somewhat shallow viewpoint (although, understandable, based on past examples), to think that a proposal this large would be adopted after just one RFC. There's obvious support for some sort of "community de-adminship" process, regardless of whether it takes the form of something like the current proposal, some form of "term limits" (or terms of service at all), or something completely different. For those reasons I'm not personally concerned with nuanced interpretations of individual votes, or even the vote totals (as long as they don't break significantly in either direction. I should probably note that, even though I'm a "supporter", it would trouble me to see the voting here break even towards the support column, with the proposal in it's current state). What we need is a hint towards a direction to move forward in.
  — V = IR (Talk • Contribs) 05:17, 27 February 2010 (UTC)

  This proposal has been through several RfCs already. This is the final vote on this proposal, and your vote of 'support' or 'oppose' determines whether or not this becomes policy. It worries me that there is confusion on this point. TenOfAllTrades(talk) 16:06, 27 February 2010 (UTC)

  I can understand how you feel I think, but I don't see anything about this RFC as "final", and there's certainly nothing in the RFC that says "If this doesn't pass, nothing like CDA can ever be brought up again". Matt obviously wants it to be final, for his own reasons, and you seem to have legitimate concerns yourself. I've felt for a while that the "construction phase" for this current proposal had continued on way to long, which is why myself and others urged that this RFC take place. At least after this closes we'll have some legitimate widespread concerns to make informed adjustments on, so hopefully we can run another RFC in 30 or 60 days (after this closes) with changes that would make the proposal easier for more people to support.
  — V = IR (Talk • Contribs) 04:44, 28 February 2010 (UTC)

I don't support CDA in any form (we need to implement fixed tenure terms and admin reviews, and not paper over the cracks) but frankly TenofallTrades, who the hell do you think you are saying "this RfC is the final word on CDA."? If I was supporting CDA I'd have never have let you take control of the RfC the way you have. Your leading "Flaws" list is embarrassing for the proponent who accepted your request to 'respond' before the designated comments section, and you have managed to prejudice the RfC in terms of being taken seriously - the one thing no fair-minded person wanted to happen. Reactions should come after the 'comments', or why is this an RfC (ie "Request for comment") in the first place? Somehow you have made your drop-down "Flaws" so they are not in the page History too - why did you do that? And come to think of it, how did you do that? Some of your arguments against CDA became irrelevant during the process (like the "Mirror RfA" aspect you begin with - something I spent a lot of time arguing against myself), but you still used them for the overwhelming effect. You've been brutal and uncompromising throughout the CDA proposal (though you seem to have kept a lot back for your 'big moment' here), and it's like it's been some kind of moral issue with you. Mark my words - you (an admin - not an arb or crat - just an admin, from early the days of Wikipedia) will be Reviewed at some point in the future, and cut to a term (like every other admin) if it's the last thing I ever help to do here. I get even angrier than you (if that is genuinely possible) when I think how even one admin can manage to wield so much power. 23:48, 27 February 2010 (UTC)— Preceding unsigned comment added by Matt Lewis (talk • contribs) 23:48, 27 February 2010 (UTC)

I'll make an observation that I hope may be informative to editors who come to this page unfamiliar with the discussions that led to the proposal, and who wonder about some of the complaints about the process under which the proposal was written. In my opinion, but I'm biased, the questions Ohm's Law and I asked here are reasonable ones. However, there are also editors including TenOfAllTrades and Hammersoft who sincerely believe that no proposal of this sort would be a good idea. Often, we end up talking past one another. People on "my" "side" would like to get suggestions for improvement. Some of those who disagree with us believe that improvement of this proposal is beside the point. But that doesn't mean that supporters of the proposal are not trying to listen to the opponents.

Anyway, it seems to me to be too early for anyone to be trying to predict the outcome of the poll here, or to be trying to spin the results. For now, I'd rather see constructive discussion about what's best for Wikipedia. --Tryptofish (talk) 18:05, 26 February 2010 (UTC)

• Two things; first, several times now there's been attempts at pigeon holing me as a person hell bent on killing this proposal or anything like it. That simply isn't the case and never has been. I have extremely strong opposition to the way in which this effort has been conducted. It's been highly unprofessional, fraught with cliquishness, poorly thought out and executed, and an utter mess. Which leads to the second point; how are we supposed to interpret the results if we don't even know what the metrics are? You got this RfCPOLL started but haven't spoken at all about what you think success is, how we're supposed to evaluate it, what happens if its met, or not met, or close, or what have you. It's kind of like you walked into a room of 400 people with an idea and said "Hey everyone, what do you think of this?" and everyone started speaking at the same time. --Hammersoft (talk) 18:57, 26 February 2010 (UTC)
• So let's try to answer just one question, just one, in warming our toes at the fire of accountability. Tryptofish, what do you plan to do about the (currently) 18 (about 8% of total) people who have voted in this poll who failed to meet the suffrage requirements of CDA? --Hammersoft (talk) 19:13, 26 February 2010 (UTC)

• I apologize if I misinterpreted or misrepresented your position on CDA. It's not like I can memorize what every editor has said. Your comments above seemed to be critical.
• If I understand your question correctly, you are saying that 18 users have participated in the poll so far who would not qualify to be nominators in a CDA under this proposal. It's not obvious to me that such users should have no right to share their opinions in a discussion about this proposal. As for what I "plan to do", I am taking this RfC, like most things in my life, one day at a time. I suppose that, about a month from now, if the responses here continue to be closely divided between support and oppose, I would tend towards the opinion that it's a bad idea to simply count votes and I would be receptive to discussion of how to proceed with the information obtained from the community in this RfC. It's not like I personally have any sort of magic power to force policies onto the Wikipedia community. That's a long time from now, and I find it premature to be jumping to conclusions. --Tryptofish (talk) 19:28, 26 February 2010 (UTC)

• It was premature to launch this RfC, and yes I am critical. Do you think it would be acceptable to include opinions from an 'editor' who is currently indefinitely blocked and has a grand total of 9 edits? It is not obvious to you that the opinions of the 18 who fail the suffrage metric of CDA have no right to share their opinion, but apparently it is obvious they have no right to share their opinion on CDAs themselves? Moving along; the discussion on how to proceed from this RfC should have occurred before this RfC went live. It's as if an experiment were constructed, but you don't know what the question is. The experiment is effectively useless. I think it would be strongly in your interest to close this RfC, take the results back to the drawing board, learn what you can from it, and apply that to CDA. That would be a good first step. Continuing this RfC carries the impression that should it pass (an as yet unstated metric), it will become policy. That's a grave mistake. --Hammersoft (talk) 19:49, 26 February 2010 (UTC)

I haven't been following the block history of every editor here, but I don't think someone who is indefinitely blocked should edit. Does that somehow render the opinions of all 100+ supporters so far invalid? I didn't say that the editors who would not qualify as nominators have no right to speak here; why do you think I did? I don't think the RfC was premature. There have been some editors complaining bitterly that it should have been started a few months ago and others who complain bitterly that it started too soon. And do you understand the difference, in the proposal, between being a nominator, and being able to !vote in the poll that follows? But I'm very glad to hear that you are not hell bent on killing this proposal or anything like it. --Tryptofish (talk) 20:00, 26 February 2010 (UTC)

• I made no comment regarding any other supports other than the ones who fail suffrage requirements of CDA. Why do you feel their opinions are not valid if they were to speak at CDA but are valid here? --Hammersoft (talk) 20:08, 26 February 2010 (UTC)

Is that what I said? --Tryptofish (talk) 20:11, 26 February 2010 (UTC)

• Why are people with less than 500 edits and three months service not permitted to nominate? --Hammersoft (talk) 20:24, 26 February 2010 (UTC)

Ah, yes! That is because the editors who developed the proposal are convinced that it is very important that nominations for CDA not be made casually, or by editors acting in anger or haste. The 500 edits number was actually discussed at length (link). The concept is that new editors who, in some cases, certainly not in all cases, may present exactly the kind of issues you have just been raising here, should not be in a position to start a CDA if ten more experienced editors do not see the merits in their complaint. Despite all the hyperventilating that has met this proposal, that CDA would result in mobs carrying torches to come after good administrators, the authors of the proposal sure tried hard to make the process difficult to exploit. But that doesn't mean that new editors are persona non grata whose opinions should not count in this RfC. --Tryptofish (talk) 20:36, 26 February 2010 (UTC)

• Why on Earth not? Apparently, they are capable of mob activity and carrying torches to come after administrators. Certainly an outcome of CDA is for the community to come after administrators. So why do you think the <500/3month crowd is suddenly going to be able to behave themselves here, but not there? Why the difference? (and, by the way, we're up to 19 now) --Hammersoft (talk) 20:50, 26 February 2010 (UTC)

I really don't understand what you are asking: are you talking about new editors with fewer than 500 edits, or disruptive editors? And isn't it a bit early to be counting hanging chads? --Tryptofish (talk) 20:56, 26 February 2010 (UTC)

• I'm saying there's an apparent dichotomy that users with less than 500 edits and three months of service are not trustworthy enough to nominate at CDA (torch carrying mob, as you describe) but they are trustworthy enough to comment here, and have an impact on whether this proposal goes forward or not. You've failed to address this dichotomy. I keep asking it, and you keep non-answering it. --Hammersoft (talk) 20:59, 26 February 2010 (UTC)

I'm non-answering it? No, I'm either not understanding your question, or disagreeing with you. (Anyone seeing what I meant above, about editors talking past one another?) And I never said that users are a "torch carrying mob". I said that some of the editors who oppose this proposal have called users that, not that I agree with them as a generalization. Now to answer your dichotomy: yes I feel that the barriers to starting a CDA need to be sufficiently high that editors with fewer than 500 edits (who, again, in the vast majority of cases are not a torch carrying mob) should not be among the ten nominators. And I've shown you the link to the discussion of that point by other editors, not just by me. Nonetheless I see nothing automatically wrong with editors with fewer than 500 edits participating in this RfC. That does not mean that they, or any other subset of the community, will determine by themselves "whether this proposal goes forward or not". Editors with fewer than 500 edits take part in all kinds of discussions on this website, and there is nothing wrong with that, obviously. --Tryptofish (talk) 21:47, 26 February 2010 (UTC)

• Ok, so then why is it not ok for them to nominate? --Hammersoft (talk) 21:52, 26 February 2010 (UTC)

I'm not trying to be dismissive or unresponsive about that, but, truly, I thought I already answered that, very clearly and specifically. Maybe I'm just not understanding something, or not expressing it the right way, so I'll invite other editors to try to answer further if they would like to. --Tryptofish (talk) 21:58, 26 February 2010 (UTC)

Anyway, editors who would like to answer Ohm's Law's original question are still welcome to do so. --Tryptofish (talk) 20:05, 26 February 2010 (UTC)

Suggestions

What we need now is an analysis of the oppose votes to suggest how the proposal might be modified to obtain the necessary support, as it's clear the proposal as it stands doesn't have consensus. Everyking (talk) 01:45, 2 March 2010 (UTC)

Just off the cuff, I'd say the biggest objection is over the potential for a group to defrock an admin for enforcing policy against them, even if the admin did so rightly. Brainstorming for a second, maybe we could allow editors (and their known allies) who were directly affected by a block/article protection/deletion to comment at or even initiate a CDA, but not vote.

Separately, an admin should have a chance to defend his or her actions before the !voting starts -- perhaps put a one-week delay in before the vote starts (or more, if the admin gives a plausible reason for being unavailable). During that week, the admin and any supporters can engage the complainants and address their concerns, possibly avoiding the need for the CDA -- or at least giving them the opportunity to rebut the claims before the community starts weighing in.--Father Goose (talk) 04:39, 2 March 2010 (UTC)

Those sound like good ideas. I'd suggest that editors who were directly affected by the admin's actions should not be allowed to sign the petition calling for a vote—although they could participate in the vote itself. While the proposal currently excludes editors subject to various sanctions, we could also have an exclusion for editors who've been blocked within a recent period of time, perhaps a month or two. Those ideas would tighten up the process to the advantage of admins, so I'd also suggest a modification in the opposite direction: lowering the bar for a successful vote to a simple majority, rather than 65%.

Another idea, which I'm not entirely sure is a good one, but might be worth considering: allow admins facing a vote to resign for a fixed period and then resume adminship later on without a vote. This would hopefully mollify the admin's opponents, while also avoiding the drama associated with a vote, and it would provide the admin a good opportunity to learn from the controversy and return to adminship with a little more wisdom. Everyking (talk) 05:06, 2 March 2010 (UTC)

I've seen quite a few hasty or outright inappropriate blocks, so I wouldn't go by block logs. Even users who have been blocked for legitimate reasons shouldn't be disenfranchised as a result. Blocks are meant to be preventive, not punitive.

Your second idea is called "resigning under a cloud", and is always treated by arbcom as requiring either their approval or the community's to reinstate the admin bit. A failed CDA is a good opportunity for an admin to learn what the community disapproves of, and a successful CDA, even more so. The admin can always reapply for adminship if they demonstrate to the community that they have learned from the experience.--Father Goose (talk) 05:25, 2 March 2010 (UTC)

Yes, it is "resigning under a cloud", but we're talking about new policy here—it doesn't have to follow all the old rules. The idea would provide a specific exception as part of the CDA process, allowing admins to hand back the tools for a fixed period in order to defuse the controversy and avoid the drama of a confirmation vote. Everyking (talk) 05:34, 2 March 2010 (UTC)

The only real drama avoidance would be if the admin gave up the tools indefinitely. I've seen users "retire" while under scrutiny so that an RfC or whatever disappeared, then return to their abuses when the scrutiny was off. Doesn't matter if it's for a fixed period. It's classic gaming behavior, and it is just a source of drama itself.--Father Goose (talk) 07:25, 2 March 2010 (UTC)

A few ideas:

• The proposer of a CDA must notify the admin's Talk, and any timers start then.
• If the admin can't respond in the standard time (proposed 1 week), the admin must not perform any admin action of the same type in the complaint until the admin has responded.
• If the admin does perform any admin action of the same type in the complaint before the admin has responded in the standard time (proposed 1 week), any editor can add a prominent notify to each of the top hear, the header of the "support" section, the "oppose" section and the "comments" / "statements" section saying that the admin has perform this action with first responding to the complaint. All versions of the notice should cite the history of the complaint and the contribs of the admin. AFAIK there is no practical sanction against an admin who delayes responding while continuing the relevant of action. This clause is intended to sway "votes" toward "support" and, if needed, to build a case for desysop at ArbCom. --Philcha (talk) 06:09, 2 March 2010 (UTC)

I'm not so keen on the "must not perform actions" idea -- if the admin is acting rightly, they shouldn't be pulled off the line by a harassing complaint, and if they're acting wrongly, additional actions of that sort just add evidence of misbehavior. If the admin is acting very inappropriately, an emergency de-sysopping is needed, and ArbCom does handle that well. CDA is needed to address more subtle (but still definite) misuses of tools and/or authority, where ArbCom has historically been extremely hesitant to act.--Father Goose (talk) 07:36, 2 March 2010 (UTC)

I'm concerned that a problem admin would just stall for ever. --Philcha (talk) 08:34, 2 March 2010 (UTC)

The CDA would go ahead regardless of whether the admin agreed to participate. I just wouldn't want it to go ahead at a time when the admin wasn't available (on a wikibreak or whatever). If the admin says "I'm not ready" but continues editing, the CDA should proceed.--Father Goose (talk) 09:13, 2 March 2010 (UTC)

How about abandoning the idea as needless bureaucracy, and go back to the RFC route which there were several variations of in the Admin Recall RFC? Basically all that needs to happen to make that work is to clarify the circumstances under which RFC can lead to an Arbcom desysop motion (present case) or reconfirmation RFA (new thing equivalent to CDA, but using existing processes). Rd232 ^talk 09:30, 2 March 2010 (UTC)

Abandoning which idea? Some of the ideas here might be applicable to an "RFC route".--Father Goose (talk) 09:44, 2 March 2010 (UTC)

The idea that should be abandoned is of having a process specifically for "Community De-Admin"ing, rather than having discussion-focussed Dispute Resolution processes from which desysopping may emerge by WP:Consensus as a proposed outcome. Rd232 ^talk 09:52, 2 March 2010 (UTC)

I would welcome more dispute resolution built into whatever CDA/AR process we might ultimately adopt. Though the basic mechanism proposed is the same one we use for determining consensus on any issue where a large number of editors weigh in -- a poll. It's the same mechanism we use to promote admins in the first place.--Father Goose (talk) 10:31, 2 March 2010 (UTC)

I voted oppose in this RfC and haven't been involved in the earlier discussions but what would sway me (and address quite a lot of the other concerns) is something like the following:

• The policy must state the actions an admin would need to take in order for them to become eligible to be nominated for "recall"/"de-admining".

• These would be specific admin actions and not editorial actions. i.e. blocking/protecting/deleting against policy
• Disputes over editorial actions should be dealt with using the methods available for all editors (e.g. mediation, RfC, etc.). Ultimately, if this route takes them to ArbCom, they could be desysopped if consensus is that their editorial actions have tarnished the reputation and trust given to admins.
• The nomination must show evidence that policy has been breached x times (e.g. 5) in a given period (e.g. 4-12 weeks) to indicate a perpetual problem rather than good faith or one off errors of judgement.

• The nomination must have the support of x other editors (e.g. 10) who will sign the nomination.
• The nomination must explictly list the actions that have breached policy
• The nominators are not eligible to vote
• All !voters must make clear if they have had a previous dispute with the admin and whether that involved editorial issues or use of admin tools.
• In determining consensus to de-admin, the crat should give greater weight to opinions of uninvolved admins/editors (i.e. who have never had any previous contact with the admin or nominators).
• The ultimate call of the supporters of this current proposal is that the community must have a mechanism to de-admin those who misuse the tools and therefore it should not be unreasonable to expect a "jury" made up of neutral participants to make the call.

→ AA ^(talk) — 10:01, 2 March 2010 (UTC)

I want to thank the editors above for, in effect, responding to Ohms' question, and this discussion is very helpful. Although I personally am loath to assume the outcome of this RfC when we are only one week into a four-week discussion, I have also been thinking very actively about these questions. I recognize that some of those who oppose the present proposal will never support any revised version, but I also believe that it is becoming apparent here that there eventually will be consensus for an improved version of the present proposal. I also think this particular part of the discussion should take place in the context of the parallel discussion just above, #Observations re Casliber's comment, about ArbCom.

That said, I'd like to ask some questions of editors who oppose the present version, following up on what has already been said:

• I was interested, and actually surprised, when Everyking suggested above lowering the guideline from 65% to 50%+1. Am I correct that this would actually not be popular (it wasn't here)?
• Another related point would be to look at how many editors should participate in a CDA in order for it to be considered successful. I think that it is becoming clear that the 10 nominators should only nominate and not !vote. In earlier discussion (link), it was decided that there would have to be a minimum of 50 users supporting the de-sysop motion. (Disallowing the nominators would effectively raise that number to 60.) Should that number be adjusted further upward? Doing so may address the concern that parties with agendas might overtake the process.
• I think it has become absolutely clear that there must be a place for the administrator to respond and sufficient time to do so. Noting the issues raised above, would the following be a workable approach? There should be a dedicated space on the CDA page for the administrator's response. The nomination cannot be certified until either one of the following: either (1) the administrator has entered a response there (or stated explicitly that they do not intend to do so), or (2) seven days have elapsed from the time a notice of the CDA was placed on the administrator's user talk.
• How about also having a space on the CDA page where the administrator may list all "support" !voters whose !votes the administrator wishes to challenge? The closing Crat would decided whether those challenges are valid.

--Tryptofish (talk) 18:04, 2 March 2010 (UTC)

I think implementing the fourth point might prove counterproductive. At heart, a RFA/R ("Requests for administrator recall" is my preferred terminology, see [10]) process that depends on a certain number of participants or a certain percentage of supporters is ultimately a vote. If it is to be a vote, I think we would do better with a flexible vote based upon discussion rather than a inflexible one where every vote is argued and contested. Having the sysop challenge individual votes rather than general arguments shifts the focus away from the substance of the argument to the vote itself (i.e., who made it, how did they word it, and so on). -- Black Falcon ^(talk) 20:57, 2 March 2010 (UTC)

I'm just thinking out loud here. I'm not sure how one gets away entirely from a poll of some sort, without it simply becoming RfC/U. My thinking is that it is good to give the administrator a way to refute what many opponents have expressed concerns about: editors coming to the CDA-or-whatever-we-call-it with axes to grind. Some people commented just above that anyone who has had prior contact with the administrator should be excluded from the process. I can see all kinds of problems with that. I was thinking that the administrator should, instead, have an opportunity to point out that certain users have agendas, but I'm open to other, more discussion-oriented, ways of accomplishing that. --Tryptofish (talk) 22:01, 2 March 2010 (UTC)

Ah, I understand, and I agree with you on the point of excluding or discounting comments by those who have previously interacted with the admin. A straight RfC/U is my first preference, but I was thinking of a structure similar to RfA (a vote, but at least somewhat discussion-based), where candidates can convey their viewpoints regarding the rationale behind particular votes by responding to questions posed by participants or posting in the "Discussion" section. Of course, at this stage, I too am just thinking out loud. :) -- Black Falcon ^(talk) 23:25, 2 March 2010 (UTC)

Adding a fifth bullet point to my four just above:

• How about changing the closure of the process to being a referral of CDAs that get more than 50% support to ArbCom, instead of having the Bureaucrat determine directly that there will be de-sysoping? (See also Coren's comments in the section about Casliber's comments, above.) --Tryptofish (talk) 22:21, 2 March 2010 (UTC)

Why?

Reading and replying to some of the above started me thinking about the reasons why I support something along the lines of this proposal. It's possible that a large part of my view comes from an American civics upbringing, because the main issue that leads me to support something such as this proposal is the idea of checks and balances. The fundamental problem that I see is that, like it or not, we (arguably) have two "camps" of people on Wikipedia now: editors and admins. Now, obviously, the overlap in those groups is actually 100% (you can't be an admin without being an editor, really), and I'll be the first to state that it's a bad idea to paint whole groups of people with a single brush. However, while thinking about this specifically from a group dynamics perspective, it's a decidedly good thing to use such classifications. The main reason for the bad feelings surrounding and inherent in this topic, which are easily discerned in many of the replies from both camps throughout these pages, is the simple fact that one group has a certain power dynamic, while the other group doesn't. The easiest solution to something like that is actually to empower some third group or organization (in this case, it'd be the policy behind a process) to oversight one of the other groups. The fact is that Wikipedia is growing up, and something along the lines of this proposal is simply a component of that growth process.
— V = IR (Talk • Contribs) 05:35, 27 February 2010 (UTC)

The ArbCom is a third group – vetted very thoroughly by the community through a month-long inquiry and election process – empowered to oversee adminship. It is by far the most brutal and rigorous examination process that we have for filling any position of trust on Wikipedia. All Wikipedia editors (admins or not) are allowed to vote in ArbCom elections, provided they meet some very minimal standards for project participation. Non-admin editors are free to run as candidates as well, though none have so far been successful. Any Wikipedia editor (admin or not) is permitted to bring a case before the ArbCom.

The fact is that Wikipedia is growing up, and it has matured past the need for shoot-from-the-hip frontier justice and mob-with-torches lynching parties. We have established formal institutions to handle complex, emotional, otherwise intractable disputes through a reasoned, measured, deliberate presentation and evaluation of evidence, governed by elected, impartial representatives of the community. Individual Wikipedia editors – all of them – have the opportunity to indirectly influence the course of Arbitration through participation in the prior dispute resolution leading up to a case (intervention with involved parties, AN/I discussions, RfC, etc.) and to directly affect the course of a case through making their own statements, presenting evidence, and offering suggested remedies and findings of fact.

Now, while the ArbCom is what I would call an established process, that should not be mistaken for an ossified one. The ArbCom has been steadily taking a number of incremental steps to increase both their openness and their accessibility. Recent years have seen cases handled in a more transparent fasion, through open workshop pages and visible Arb voting and discussion of remedies (among other tweaks). More cases are being handled speedily by open motion, rather than through the full rigamarole of a case.

Sometime along the lines of this proposal would be a step backward, not forward. TenOfAllTrades(talk) 16:01, 27 February 2010 (UTC)

Maybe that's the intent, for Arbcom to be the third group, but speaking for myself I just don't see it that way. There's certainly nothing apparent in their policy which specifically places them in an administrator oversight capacity. The few times that they've taken it upon themselves to remove administrative privileges from someone seem to be exceptional incidents rather then normal process. To tell you the truth, I don't really see how Arbcom is all that relevant, to be blunt. They only ever do anything for an infinitesimal fraction of issues, and they are hardly effective at resolving those issues anyway. The only meaningful effect that I've ever noticed Arbcom having is as a "super administrator" intimidation threat, but I've never really seen anything come from that.

We do agree that Wikipedia is growing up at least, and that it's time for the "frontier justice" stuff to end. Something along the lines of this proposal, or the ideas which got it started at least, are what Wikipedia needs in order to further that. It's good to hear that Arbcom is apparently making changes (I'll take your word on that). I wouldn't mind making something like this an "arm of arbcom", or "appendix" to it, or whatever, and from what you're saying here it sounds like that might be acceptable to them as well. If Arbcom is supposed to be about admin enforcement then we should use them for that anyway.
— V = IR (Talk • Contribs) 04:59, 28 February 2010 (UTC)

The specific identification of ArbCom's (sole) role in desysopping is in Wikipedia:Administrators#Removal of adminship (desysopping). TenOfAllTrades(talk) 06:40, 28 February 2010 (UTC)

Call a vote a vote

It seems to me this is a straight up-and-down vote. You need a certain number to start a recall and a certain number for the recall to pass. If it was a discussion we wouldn't need those numeric requirements; it could just be framed as a discussion, and state that consensus would dictate the outcome. Call a spade a spade. Don't try to dress this up in WP:CONSENSUS clothing by calling them "!votes" when they're clearly intended to be counted as votes. If voting is always an insurmountable problem, then this proposal shouldn't be acceptable the way it is presently worded. If voting is sometimes okay (and that does seem to be the case) then it shouldn't be a problem to acknowledge it. —DragonHawk (talk|hist) 01:41, 1 March 2010 (UTC)

• Thank you DragonHawk. I tried to highlight this in the Intentions section above, but you did it far more succinctly. If an editor has only 490 edits, and gets harshly bitten by an administrator, they can't help nominate a CDA. Their opinion is not worth as much as a person with 510 edits. It is a vote, and some voters are more equal than others. --Hammersoft (talk) 16:05, 1 March 2010 (UTC)

I feel like some of us are talking past one another. See WP:POLL#Straw poll guidelines for how Wikipedia does and does not use !votes, and see the actual language of the proposal. How, exactly, is the last sentence of that actual language, for example, what you are claiming? The proponents of the proposal are not trying to mislead or mislabel, although the opponents apparently are. --Tryptofish (talk) 17:41, 1 March 2010 (UTC)

• Mislead? Mislabel? I don't think so. Wikipedia:Guide_to_Community_de-adminship#The_nominators, first bullet item says (and I quote) "with accounts at least three months old and with at least 500 edits." I'm not making this up. --Hammersoft (talk) 18:20, 1 March 2010 (UTC)

DragonHawk was asking about vote versus !vote, not what you call "suffrage". --Tryptofish (talk) 18:30, 1 March 2010 (UTC)

Create a permanent admin record for complaints and praises

I am neutral to the case. There should be a de-adminship process, and users might be able to nominate, However:

• The number of users and edit count should be defined more thoroughly, 500 edits with anti-spam and 50 edits in article creations are not equal. It is time wikipedia should separate or even replace edit count concept with contribution count.
  • We should review edit count policies, and strictly separate edit counts for AFD etc. discussions, SPAM related reverts, scripted edits with actual content creation or improvements. There are users with top edit counts who doesn't even create or edit content of even a ten percent of their edit counts.

• WP:Canvas is still a vague term and not a well defined policy itself which should be reviewed. There should be an easier way to auto-notice all involved or previously edited users in wikipedia without any user intervention for all kinds of processes about articles and people including AFD, TFD, RFA, other wiki-wide decisions etc.

• We should also discuss all RFA process from start to end. Because after a while only privileged users who get along with previous admins becomes nominated and elected in RFAs. Being elected as adminship without any high-number actual content creation to wikipedia should be prohibited. Don't tell me it is, it is sure not by example case.
  • Also RFA process should result by number of mistakes a user had, instead number of edit count etc. Simply because many users-admins tend to delete complaints from their user talk instantly and noone bothers checking page history

• User involvements are necessary yet open to misuse. Also if de-adminship process not works, admin and his admin-friend group will hold grudge and will try to find a way to punish nominators somehow. Happened before and will sure happen in the future. We still have many blood feuds in wikipedia among many users.
  • There should be a permanent admin record and complaint/praise section, where users can vote admins' record or add their negative experiences with them which admins themselves cannot delete and regularly gets reviewed by a team of selected admins for a long term tracking of admin behaviours.
• Admins tend to delete talk page complaints, sometimes even the most productive criticism, like rest of some regular users. Permanent admin record should prevent this "remove criticism" and cover up approach.

• There should be a higher council and space in wikipedia for wiki-wide cases, where users can state their opinions and inform all wiki-community about the ideas or solutions they provide if users subscribed to that channel. Currently wikipedia processes are no-different than real world government institutions. The voting and debating should me faster and easier.

Updated below debate and create a new section for proposal. Kasaalan (talk) 10:38, 2 March 2010 (UTC)

Discussion of permanent admin records

Thank you for this feedback. I'm especially intrigued by your suggestion about a "permanent record", sort of like a continuously-archived Wikipedia:Administrator review for every administrator. In my opinion, that's an idea that definitely merits further discussion. --Tryptofish (talk) 18:27, 28 February 2010 (UTC)

Note: my comment, moved to here, was that I support "further discussion", not that I am supporting some sort of as yet unwritten proposal. --Tryptofish (talk) 18:19, 2 March 2010 (UTC)

That's another non-starter in this best of all possible wikiworlds. Block logs are maintained as permanent record of misdeeds of the plebians, but no similar record is maintained of the misdeeds of "the most trusted members of our community". They walk away unblemished; that's the way it's designed to work. We all know of many administrators who if they weren't in office would have block logs even longer than mine. --Malleus Fatuorum 22:02, 28 February 2010 (UTC)

I would support a permanent page documenting past issues that were supported by evidence, not something that anyone with an ax to grind can put something on though. You hear all sorts of unsubstantiated spite being tossed around and that is of no real value. Chillum ^{(Need help? Ask me)} 15:33, 1 March 2010 (UTC)

Yes, I agree with that. --Tryptofish (talk) 18:03, 1 March 2010 (UTC)

Definitely a good idea. Entries posted to the permanent record should probably be moderated by some group in order to ensure accuracy and readability of the complaint/praise, without trudging through pages and pages of ranting. ...but what do you think? ~BFizz 14:50, 2 March 2010 (UTC)

Needs to be properly thought out, I hope you are not planning to try to implement based on this? Call it a straw poll, if that. I can think of a number of objections, but I'd rather give people the opportunity to come up with a full fledged proposal before tossing darts.--Wehwalt (talk) 11:58, 2 March 2010 (UTC)

It doesn't have to be visible to all users. Maybe only admins should access to such data. Yet an admin record is crucial. There are admins who even instantly delete users' criticism about them to keep their record clean. Admin record is way better than community de-adminship process. Kasaalan (talk) 13:00, 2 March 2010 (UTC)

No such thing. Admins lack the power to delete stuff permanently. Any other user can look at what they've deleted from their talk page. And it's not like people don't have memories.--Wehwalt (talk) 16:41, 2 March 2010 (UTC)

You are wrong. Admins deletion of complaints appear in history, yet admins' talk pages are frequently edited so it remains hidden in history even if you watch the page it is hard to be aware of such actions, so it is not about memory. So do you claim any other user has to track and review 1000s of edits in history to check whether an admin is deleting user complaints or not. What a waste of time. Kasaalan (talk) 11:23, 3 March 2010 (UTC)

No, for the same reasons the main proposal wouldn't work: invites drama without any real benefit. Also punishes admins who do necessary work in heated or conflict-filled areas. Hopelessly midguided. Andrew Lenahan - Starblind 17:05, 2 March 2010 (UTC)

No. Recipe for drama, and also redundant. Every admin action is already reviewable by other admins, and anyone who suggests that admins are never held accountable hasn't read ANI. (Granted screaming "admin abuse" there is less likely to yield results than a proper arbcom case, but it's still pretty common). -- Bfigura ^(talk) 17:49, 2 March 2010 (UTC)

The "real benefit" that Andrew is not seeing is a central location to review an administrator's actions. ANI, talk pages, and a person's memory are all disjoint and none are standardized or unified into an easy-to-review format. ...but what do you think? ~BFizz 18:03, 2 March 2010 (UTC)

Yes, at least there should be a track page for formal procedures. Adminship requires another level of neutrality in my opinion, especially controversial cases. Most of the new users aren't aware many of the wiki features or pages. Also most of the tools are 3rd party and not implemented into standard wikipedia features. Kasaalan (talk) 11:18, 3 March 2010 (UTC)

Generally, user talk pages should serve this purpose, containing various conversations as well as notices of AN & ANI discussions, RFCs, and being named as parties to arbitration. If admins are using deletion or protection to remove valid criticism from their talk pages, reports of such should be taken to ANI. Christopher Parham (talk) 19:03, 2 March 2010 (UTC)

It's an interesting idea, and kudos to those who thought of it, but it strikes me as an inefficient and problematic approach to the problem of sysops abusing or misusing the tools. Firstly, problem sysops constitute a minority of all sysops, so it is inefficient to implement a program that requires work to be carried out for all ~1,700 of them. Secondly, it is much easier to document negative incidents than positive incidents, since it is the negative incidents that create controversy and the positive incidents that usually pass unnoticed. Without some mechanism to counter this, the records will inevitably become skewed and fail to present a balanced overview of sysops' records. -- Black Falcon ^(talk) 22:36, 2 March 2010 (UTC)

Those are very good points. On seeing both sides of the issue, I tend to agree that this would be inefficient. --Tryptofish (talk) 22:40, 2 March 2010 (UTC)

Anything related to users or privileged users tend to be misused anyway. The issue is which solution leads less abuse. Except swears and insults, especially admins shouldn't delete their talk page criticism anyway. Yet that is not the case, like the rest of the users admins tend to erase records, on the other hand if they do not delete them somehow while rest deleting such complaints it appears even a good admin gets complaints than the rest of worse admins. De-adminship by 10 votes will not work anyway, first it is near impossible to gather 10 votes by independent users at the same time, on the other hand if users are related somehow or has single purpose accounts, whether they camouflage it or not, it is too easy to gather even 100 people to file a de-adminship which will lead POV accusations against admins. If there will be a de-adminship process the vote system should be time independent. Yet remember both hidden vote and open vote like both limited-time and permanent complain systems for de-adminship has their own drawbacks. Kasaalan (talk) 11:08, 3 March 2010 (UTC)

Is the assertion that sysops tend to routinely blank criticism from their talk pages rather than archiving it based on concrete evidence or just a personal perception? I follow quite a few user talk pages (of admins and non-admins) and, with the exception of blanking posts that contain incivility or personal attacks, I rarely see the phenomenon that you describe. -- Black Falcon ^(talk) 20:54, 3 March 2010 (UTC)

Yes I have come up with the cases, even though I generally do not watch user pages. But I am not telling this for that admin did this or that, so do not expect me to post examples, yet my example cases are not imaginary but real world ones. And let alone the personal attacks, I have come up with deletion of just criticism. Also if some post contain personal attack or swear, admin should remove only that swear and leave the comments and criticism.

Moreover even if no admin delete such complaints, who may search 1000s of talk pages to find such cases anyway. So create a permanent admin record for complaints and/or praises whether it is just visible to other admin, higher admins or all users. Kasaalan (talk) 12:19, 4 March 2010 (UTC)

I've yet to see what useful purpose this would serve. Most admins do not seek other office, so it would not be useful for voters. If we had a reconfirmation process, it might be useful for !voters. But so far as I can see, in the system we now have, such a system would have the sole purpose of gathering people's grievances, justified or no, in one place, without anything to do with them.--Wehwalt (talk) 14:54, 4 March 2010 (UTC)

Improper forum for discussion of permanent admin records

This RfC started to ask a single question. Now, after nearly 300 people have voted, we introduce another motion? No, this isn't the proper forum and anything generated from this should grow into its own future RfC. --Hammersoft (talk) 13:37, 2 March 2010 (UTC)

A clear consensus has not been reached on this proposal; this one is relevant to the idea of admin accountability, where better to discuss it? ...but what do you think? ~BFizz 14:43, 2 March 2010 (UTC)

What I don't want to see happen is for people to review the above at some point and where there is a large majority one way or another and have people point to this and say "But we had consensus!" literally hundreds of people who might be interested in this discussion have already visited this page and already departed. It's a separate issue, a separate proposal, and it should be discussed on its own. --Hammersoft (talk) 17:29, 2 March 2010 (UTC)

I agree with Hammersoft that this must not be treated as an actual motion, but I also think it's entirely reasonable to have discussion of the idea, for the purposes of (1) informing thought about the actual motion on this page, and (2) perhaps working towards another proposal, but one that would have to have its own RfC in the future. --Tryptofish (talk) 17:28, 2 March 2010 (UTC)

This RfC seems to have failed to gain consensus by any reasonable measure. There's no need to have two similar polls ongoing at the same time. As for the reason to have separate locations: so it's clear what people are actually being asked, and so that everyone doesn't hit tl;dr. Also, I would imagine it's generally a bad idea to "try and inform thought about the actual motion" after 300 people have already !voted. -- Bfigura ^(talk) 17:32, 2 March 2010 (UTC)

Bfigura, that's why we !vote and not vote. We are one week into a four-week discussion, and no one knows whether, for example, the discussion will close as "fail" or as "no consensus". Opponents do us all a disservice by trying to call the "vote" before the !vote is over. Discussion is a good thing, unless one just doesn't want the subject discussed at all. --Tryptofish (talk) 18:17, 2 March 2010 (UTC)

This RfC wasn't setup as a discussion. It was set up as a vote. --Hammersoft (talk) 18:23, 2 March 2010 (UTC)

Only in your framing of it. --Tryptofish (talk) 18:25, 2 March 2010 (UTC)

From this comment above, there are ~15-20 people (I think it's less actually; counted 12) discussing this proposal. From this comment down, there's nearly 300 people voting. You think this is a discussion? A format like this would have been considerably more helpful. --Hammersoft (talk) 18:29, 2 March 2010 (UTC)

I didn't call this a vote, I explicitly said !vote. However, given that this has largely been treated as a poll (based upon the number of people !voting versus discussing), changing the parameters of a poll after it's started isn't a great idea. (Nor would it be a good idea in a discussion, since many people aren't going to return to see the revised instructions, especially in a page as large as this.) -- Bfigura ^(talk) 18:40, 2 March 2010 (UTC)

What are we arguing about here? One user took it upon themselves to set up this part of the discussion section as if it were a poll on a proposal about permanent records, when that proposal hasn't been written yet, and moved some comments by me and others, saying that we liked the idea of discussing the concept further, and formatted those comments as though they were !votes. It then devolved into complaints about, what?, the section here?, this page in its entirety? Let's please just agree that no one is putting forth a formal proposal on permanent records for administrators. --Tryptofish (talk) 19:14, 2 March 2010 (UTC)

• Hell if I know at this point. An editor made this section today, 2 March 2010, yet there's a lower series of comments from people in February. I think it's been refactored too much. I suggest pushing it to the talk page or its own nascent RfC. --Hammersoft (talk) 19:29, 2 March 2010 (UTC)
  • Yes I made the section today with an updated proposal, since I was neutral first, yet as the way it is community de-adminship will only create more confusion. I explained why. Kasaalan (talk) 20:43, 2 March 2010 (UTC)

Testing hypotheses

Since I'm trained as a scientist, I tend to think in terms of hypothesis testing. A hypothesis that has been stated again and again on this page is that CDA would bring forth some sub-population of the Wikipedia community that would dominate the CDA process and be opposed to good administrators. To quote from TenOfAllTrades' opus above: "the self-appointed Guardians of the Faith. They have strong (and often negative) opinions about admins collectively and the concept of adminship, and they have found in CDA an opportunity to proclaim on their particular hot-button issues. This group will be the only one which watchlists the CDA page and actively tracks new cases; they will form their own somewhat isolated, somewhat insular community around CDA." Apparently such users would make it impossible for a badly-justified CDA nomination to be defeated by the right-thinking community.

Well, it seems to me that this hypothesis has been tested, over the past week, at this page. If the hypothesis were true, then these Guardians of the Faith would have overwhelmed the poll and given the support section a sweeping majority. Ironic, huh. --Tryptofish (talk) 21:01, 2 March 2010 (UTC)

This page was advertised in the watchlist notice, CENT, and every major community noticeboard, getting about 300 participants so far. Do you sincerely believe that particular CDAs would get a similar level of advertisement or consequent participation? Christopher Parham (talk) 22:17, 2 March 2010 (UTC)

The version of the proposal that is proposed here requires that each CDA be announced at the Village Pump, the administrator notice board, and the bureaucrat noticeboard. It also requires, at a minimum, that it be supported by 50 editors and 65% of all participants, which means that 77 editors would have had to participate (65% of 77 equals 50). Since whatever may eventually become policy is going to be modified from what is proposed here, all of that can be adjusted. CDAs could be announced on CENT or elsewhere. The 10 nominators likely will not be able to !vote. We could, perhaps, make a minimum of 100 supporters; with 65% (if we don't raise that as well), there would have to be 154 participants at a minimum. These things are all soluble. In no way do they support the "hypothesis". --Tryptofish (talk) 22:32, 2 March 2010 (UTC)

It would probably be unreasonable to expect that every one of these requests would be announced via the watchlist notice, but I think that doing so is the bare minimum necessary to get it noticed fairly and give the opportunity to reasonably forbid all forms of canvassing. I only came here because of the watchlist notice; I am sure that there are a number of editors who mostly prefer to spend their time in the article space and they should have just as much notice as the more community-oriented editors.--~TPW 06:55, 3 March 2010 (UTC)

Are you really suggesting that users who stand in opposition to the "Guardians of the Faith" are the ones who only see watchlist notices? I would think watchlist notices would be more likely to attract the attention of editors who are not tuned in to policy-related notice boards, and who, thus, would be more likely to be unsympathetic to "the establishment". And I'm pointing out that, nonetheless, the pattern of responses here tends to pull the rug out from under the claim that the Wikipedia community turns into a torch-carrying mob at the mention of de-sysoping. --Tryptofish (talk) 16:14, 3 March 2010 (UTC)

Poll

Support

1. Support. It makes very good sense that the same community that confers administrator status at RfA should have the ability to retract that status when confidence has been lost. This proposal have been very carefully thought through, incorporating lessons learned from previous proposals. I urge editors to actually read the proposal: I think that you will find that many of the criticisms raised by opposers are actually not problems with the proposal as it is written. --Tryptofish (talk) 19:05, 22 February 2010 (UTC)

   Now that I've had a chance to read the comments so far from those who oppose the proposal, I'd like to add this to my own comment. I note the large number of users who state that ArbCom is already sufficient to handle the problem, and that this proposal would add nothing further that would be good. As editors worked on the early stages of this proposal, one idea that was much discussed was that of "bright line" misconduct by administrators, situations where an administrator unambiguously does things that violate policies of administrative conduct. I think there is consensus among both supporters and opponents here that ArbCom is, in fact, becoming very effective at dealing with that. But CDA addresses something else. There are a small number of administrators, certainly a small and unrepresentative minority, who make patterns of doing things that do not quite cross a bright line, but which leave substantial numbers of community members with a bad feeling about how things work at Wikipedia. They may be chronically incivil in ways that don't require AN/I sanctions but which are hurtful to other editors. They may POV push, or be imperious in the ways that they edit. Please don't get me wrong: this is not the same thing as someone who has a bad day and gets hot under the collar and makes a blunt remark once. It's not the same thing as someone who consistently makes difficult calls and does so in a professional way, even though it makes enemies. And I believe strongly that most of the community, far from being a mob, can readily distinguish the former from the latter. Just look at the "oppose" and "neutral" sections of RfAs. It is very common for editors to bring up issues that are not bright-line, and we accept the ability of the community to assess such things at RfA. The community should be able to assess this later, as well. --Tryptofish (talk) 19:53, 24 February 2010 (UTC)

2. I agree with Tryptofish. This proposal provides a very moderate process--at least two thirds of the community need to disapprove of an admin for desysopping even to be considered. Ucucha 19:26, 22 February 2010 (UTC)
3. Support. ArbCom could be in the business of evaluating whether admins who haven't directly abused the tools have nevertheless lost community trust, but is poorly poised to do so and a separate process is better. This is not a response to a particularly recent or major crisis but simply remedying the mistake made when initially designing the RfA process: the community grants adminship but cannot take it away. Eluchil404 (talk) 19:32, 22 February 2010 (UTC)
4. Support The details don't really matter, since they will be changed after this is adopted regardless. The fact that "administrator" privileges are effectively given permanently right now is simply too problematic. This process is way over-processed right now, and I in no way endorse it's current structure, but even an imperfect system is better then nothing.
   — V = IR (Talk • Contribs) 22:06, 22 February 2010 (UTC)

   But how can we have a simple CDA process? The details are everything, surely. To adopt it first and work on it later cannot be right. There are other Admin Recall solutions that can be worked on (including RfA), so it is not really 'CDA or nothing'. Matt Lewis (talk) 22:13, 22 February 2010 (UTC)

   Effectively, yes, it is indeed CDA or nothing at this point, since no other proposals have received anywhere near the same degree of traction. Beyond My Ken (talk) 01:33, 23 February 2010 (UTC)

5. Support a CDA process. The actual details of the process will be subject to modifications and evolution over time but this is a good place to start. — Martin (MSGJ · talk) 22:46, 22 February 2010 (UTC)
6. Support per Martin. Willking1979 (talk) 23:17, 22 February 2010 (UTC)
7. Support a CDA process. Bureaucrats have earned ridiculously high support and trust from the community; granting them the power to remove the sysop bit will do more good than bad. In my mind, this is comparable to the re-evaluation of featured articles. Standards have changed, and the community continues to evolve. Details will be ironed out through RFC processes like this one. ...but what do you think? ~BFizz 23:28, 22 February 2010 (UTC)
8. Support. The core problem with RfA is that it does not allow us to be bold in electing admins because we cannot revert our decision later should it prove to be a mistake. Is CDA a perfect way to remedy this? No. But it's a reasonable approach. RfA is deeply imperfect itself, but as yet we have developed no better process for appointing admins either.
   I think RfA could be much improved, and the admin ranks greatly broadened, just by giving us the option to withdraw our trust from candidates, once we saw that it was being abused. It's unreasonable to expect us to be able offer our trust to any candidate on an irrevocable basis. Admins serve at the discretion of the community -- yet the community has no ability to enforce that discretion.
   As a recently appointed admin, I want the community to have the power to hold me to their standards on a ongoing basis. If they can be trusted to give me the tools, why can they not be trusted to withdraw them if I fail to live up to their standards? "Admin immunity" has to come to an end. CDA is long, long overdue.--Father Goose (talk) 23:32, 22 February 2010 (UTC)
9. Support on the basis that, however imperfect this is at the start it will become better as time passes, and a process for formal revocation of use of the tools is most assuredly required. Fiddle Faddle (talk) 23:44, 22 February 2010 (UTC)
10. Support. My principal objection would be that with a sufficiently noticed poll, a majority should be adequate to remove tools, or even less than that when well-supported by cogent arguments, that's enough hysteresis for protection against frivolous removal. But this proposal is better than nothing, clearly. It provides for self-review, and if it turns out to be damaging, that can be fixed. There will be no mass removals from this process without that additional review of how it is working, good design. --Abd (talk) 23:45, 22 February 2010 (UTC)
11. Support, I think Father Goose puts it extremely well. It has long struck me as ridiculous that the community has had no workable method of establishing loss of trust in admins, and this has actually harmed the standing of admins in general. DuncanHill (talk) 23:49, 22 February 2010 (UTC)
12. Support Accountability is the issue here. Community de-adminship will hold admins accountable to the community and will help prevent them from taking actions that don't have the community's support. Of course the details would have to be worked out not to prevent witch-hunts and the like, but it is important to have a way for the community to recall an admin who hasn't performed to an acceptable standard. ThemFromSpace 00:02, 23 February 2010 (UTC)
13. I don't agree with the idea that this is redundant to ArbCom procedures--it's useful to have a community-driven process, because it's important to decentralize power and because often ArbCom is bogged down or moves slowly. Just because relying on them has worked sometimes in the past (and I'm sure sometimes it has not worked, too) doesn't mean it's going to continue to, or that it's going to be as good as if we had an additional, community-driven process. I don't expect to see a lot of desysopings from this since the bar is really high for passage and since consensus is so hard to obtain on this project, but it's better than nothing (and that's why I don't share the concerns of some opposers that this process will make it too easy to deadmin people who don't deserve it). I'm also seeing in the opposes some quibbles with the procedure, from people who don't object to the notion fundamentally. I think that type of thing may be throwing the baby out with the bathwater and preventing progress. delldot ∇. 00:10, 23 February 2010 (UTC)
14. support this isn't the same as arbcom. Arbcom can be slow and they can reject cases the community wants heard.--Crossmr (talk) 00:16, 23 February 2010 (UTC)
15. Support This sounds like a good idea, as long as it is not abused. Brambleclawx 00:26, 23 February 2010 (UTC)
16. Support I think that one of wikipedia's biggest problems is that it is extremely hard to oust a poor admin. Santa Claus of the Future (talk) 00:37, 23 February 2010 (UTC)
17. Reluctant Support. I don't believe that arbcom is an effective agent of desysopping. Those who lose the bit tend to be admins with years of abusive behavior. Being a bad admin is not enough; you basically have to beg to have your powers revoked, and be friendless in terms of the committee. IronDuke 01:09, 23 February 2010 (UTC)
18. Support The appointment of users as, essentially, admins for life, is, I believe, harmful to the community and the project, and since there is no move afoot to require re-certification after a certain amount of time, there needs to be a mechanism in place for recalling adminstrators who have overstepped their bounds or misused their power. The current proposal may have flaws in it, but at this time it's the only game in town, and I think it's preferable to have a procedure in place that can be tweaked once its flaws become evident in operation, as opposed to deep-sixing in advance it over some hypotethical flaws that never get confirmed. (The bird in the hand...) Beyond My Ken (talk) 01:31, 23 February 2010 (UTC)
19. Support As has been pointed out, the details are not set in stone. I do not accept that the community as a whole can't be trusted to recognize bad faith nominations of CDA. We are able to sniff that sort of thing out in every other community forum. Opposers who oppose on that basis show a stunning lack of faith in the community. Gigs (talk) 01:34, 23 February 2010 (UTC)
20. Support - The community should have a method of removing the sysop bit just as they have a hand in granting it, and it should not require ArbCom to do so. -- Atama頭 01:36, 23 February 2010 (UTC)
21. I support per above. Leave Message, Yellow Evan home
22. Support. It's a great start. As IronDuke said, there have been admins with years of abusive behavior that are allowed to continue. This needs to stop. --Kbdank71 02:02, 23 February 2010 (UTC)
23. Support the concept The details can be ironed out once there is consensus on whether there should be a de-admin process at all. I strongly believe that admins should vote in a separate section in this RfC. Many will have valid opinions both in favour and opposition to this proposal, and their voices should be heard, but I can't help but suspect that admin opinion will differ significantly from non-admin opinion. The distinction is clearly relevant. WFCforLife (talk) 02:08, 23 February 2010 (UTC)
24. Support. --Echosmoke (talk) 02:13, 23 February 2010 (UTC)
25. Support. This is something that absolutely needs to happen. I'd prefer that the terms were modified to make desysopping easier—I don't like the requirement of having 65% support the desysopping—but this would be a big improvement over the current situation. Everyking (talk) 02:19, 23 February 2010 (UTC)
26. Support. There is vaccum on cases where there is community loss of trust and not so clear abuse of tools. That vaccum is not currently dealt with by ArbCom. Sole Soul (talk) 02:38, 23 February 2010 (UTC)
27. Support per Father Goose. Bsimmons666 (talk) 02:39, 23 February 2010 (UTC)
28. Support. It's a shame that this proposal clearly won't pass, as it or something like it is absolutely necessary to restore faith in wikipedia's fractured system of governance. --Malleus Fatuorum 02:54, 23 February 2010 (UTC)
29. Support Effective tenure for life at being an admin has to end, or the RfA process will increasingly grow to resemble, well, real deliberations over tenure. Ray^Talk 02:55, 23 February 2010 (UTC)
30. Support The community granted the powers of an admin to a user, so it should have the ability to revoke those powers. There should be enough eyes on the process that admins will not be bounced out for no good reason, nor will accusers be allowed to go on a witch hunt without consequences. — MrDolomite • Talk 03:01, 23 February 2010 (UTC)
31. Support I'm surprised to see such a lack of faith in the community. Surely the "unruly mob" concerns apply to RfA as well? What about implementing CDA on a trial basis, at least? Dabomb87 (talk) 03:15, 23 February 2010 (UTC)
32. Support more accountability sounds good to me—Chris!_c/t 03:24, 23 February 2010 (UTC)
33. Support I have seen repeated abuse from an admin (imposing his POV and get away with it) so this policy would have came very handy to stop this kind of abuse (as he had the unconditional support of his admin pals, though, it took a couple years for him to finally be de-adm).--Mariordo (talk) 03:46, 23 February 2010 (UTC)
34. Support per above and the fact that people should be able to have a say in this process. Kevin Rutherford (talk) 03:51, 23 February 2010 (UTC)
35. Support per Mariordo and Tryptofish. BejinhanTalk 04:50, 23 February 2010 (UTC)
36. Strong Support: This really needs to happen to curb the abuse by a few. Ret.Prof (talk) 05:08, 23 February 2010 (UTC)
37. Support. Administrators like Arthur Rubin have proven that we need such a policy. There have been times in the past when administrators have been abusive on an ongoing basis and editors have complained of bias in enforcing rules against such administrators. Rather than imposing lighter sanctions, what I've noticed is that fellow administrators will sometimes judge the level of offense to be less than what it really is, sort of covering up for them in a way... or in other cases, letting the abuse go on longer than they would with the ordinary editor. A policy like this will help to counter such abuse. ClimateGate (talk) 05:20, 23 February 2010 (UTC)
38. Support. But just why Jimmy Wales should have any special right of review, when he has proved incompetent at using the block button himself, is a mystery. I strongly object to that aspect. The previous supporter's example of Arthur Rubin is spot-on, BTW. Tony (talk) 07:05, 23 February 2010 (UTC)
39. Support Solid proposal overall, and well worth the effort. Cheers. NJA (t/c) 07:53, 23 February 2010 (UTC)
40. Support There may be one or two specifics in the proposal I don't agree with but the overall proposal is fine. Davewild (talk) 08:17, 23 February 2010 (UTC)
41. Support. This isn't perfect, and there are some valid concerns from those opposing, but I do not see this as a great threat to admins who do basically good work, nor as a process ripe for gaming that will be used to settle grudges (there are protections against that). ArbCom has been doing a better job of late dealing with problematic admins, but there's no question that a good chunk of the non-admin (and indeed admin) corps here at en.wikipedia think we need a community process for desysopping. I agree with that, and can pretty easily live with this proposal. I would add that I'm a bit bothered by some comments in the oppose section that suggest 65% non-support from the community is not sufficient to warrant a desysop. We would be talking about dozens of editors (more than 50) and two-thirds of the total saying, "this has gone too far, you are done with adminship." I think it's considerably harder to get those kind of numbers than some opposing might think, and personally I feel that even if 30 some editors who represent only 50% of the total are commenting in favor of desysop the admin should resign, because ultimately one's status as an admin is based on community trust, not on the fact that an RfA was successful once upon a time. While admins who work in difficulty areas deal with a lot of complaints about their actions, there's quite a gulf between saying "you screwed that up" and "turn in the bit right now"—at least for most editors who would bother to take the time to participate in a process like this. I think this thing is worth a shot. --Bigtimepeace | talk | contribs 08:21, 23 February 2010 (UTC)
42. Support because it reduces the amount of power the arbitration committee has, even if it's not that good an idea. Gurch (talk) 08:21, 23 February 2010 (UTC)
43. Support because I have come across a couple of idiot admins in my time on Wikipedia (proving that everyone is human, even admins) so having an easy way to remove them is a good thing.--Simple Bob (talk) 09:13, 23 February 2010 (UTC)
44. Support In the absence of term limits, something like this is a necessary check on the "Admin for Life" syndrome. Mojoworker (talk) 10:12, 23 February 2010 (UTC)
45. Support It's a start. The Wiki way is that the process will be modified as it goes along, and stopped completely if it goes wrong. We wouldn't have much on Wikipedia in terms of articles or processes if everything had to be word perfect before it was started. It's interesting to recall why Wikipedia was started - because Nupedia was too bogged down in an extensive peer-review process and was not moving forward. The community wants this process - let's get it moving. This is a decent workable proposal. My guibbles are wordings which make it appear that the process is current practise, or any parts of the process are the result of working consensus. It should be run as a beta version, with a full awareness of everyone involved that the process itself is up for discussion. SilkTork *^YES! 10:34, 23 February 2010 (UTC)

    "The community wants this process - let's get it moving." - I would argue by the results of this poll so far, the community most certainly doesn't want this process. Ryan Postlethwaite^{See the mess I've created or let's have banter} 11:06, 23 February 2010 (UTC)

    I've do have a couple of points on the SilkTork's above comment because it appears sensible in many respects (I may have said a lot of it myself at one point):

    1) Regarding the detail being ironed out later, well ok to a degree - but some of it (like admin and canvassing) needed at least some serious work beforehand. I'd like to see at least a possible solution to the various problems before pushing the CDA. It is worrying that so many weak compromises had to be in the proposal (words like "admin must be editing recently" are just too ambiguous). I've seen a little evidence that things would be easier during (or after) a CDA trial to be honest, and it would be a while before every important facet of CDA is covered by examples of use. Is waiting for admin to be put up for CDA the best way to adapt the CDA? I'm not sure it is. Even labelled 'trial', CDA will likely be too disruptive imo, because of what I have come to believe are intrinsic flaws.

    2) Regarding the community 'wanting' CDA - I do very much agree that the community want to see changes regarding admin, but I haven't seen enough evidence that they are particularly crazy about this particular method, despite the expected and understandable support votes. The "Reverse RfA" idea of CDA just didn't take off. CDA doesn't address all the concerns directly, like giving admin 'terms' instead of that "job for life" for example. CDA is a bit of a bandage on a structural problem, in many ways, and a bandage we can't keep clean. I'm not against any form of Admin Recall, I just haven't seen CDA stand up to the various criticisms (or enough attempts to make it stand up to them), and I cannot see CDA better withstand criticism simply for it being trialled. I've seen too much blind faith in CDA coming good, and it's been too protected, quite fiercely so at times. Matt Lewis (talk) 11:28, 23 February 2010 (UTC)

46. Support. It's logical. The community must have the power to change its mind. We can tweak the process once we see how it works. It would be interesting to see how many of the oppose votes come from admins. --Michael C. Price ^talk 11:51, 23 February 2010 (UTC)

    But who are the 'community' who can vote someone in and then can change its mind? 'Community' is a useful general term for a 'broad consensus' here really: so a community "changing its mind" is a situation where a there is a new consensus to remove an admin. While the idea of reverse voting is fine in principle, I good idea alone is just not good enough: the guaranteed negatives of a CDA process (resulting from how the consensus is achieved) far outweigh the possible positives.

    I do hope that this RfC pushed Wikipedia into publically looking at some much needed (and often discussed) changes: Set terms for adminship and a review process for existing admin. I think for that, the time has now come. Well, perhaps not immediately, but it can't be too far off now surely. Matt Lewis (talk) 12:15, 23 February 2010 (UTC)

    Interesting indeed. As at the time of this posting 52% of the oppose votes come from administrators, with only 27% supporting. Kind of obvious who "the community" is I think. --Malleus Fatuorum 16:04, 23 February 2010 (UTC)

    Too early to tell. I've answered this more in Comments below, where you've mentioned it again. Matt Lewis (talk) 19:11, 23 February 2010 (UTC)

47. Support. Administrators should be directly accountable for their actions and potentially will return power to a disenfranchised community from controlling administrators and cabals. TorstenGuise (talk) 12:19, 23 February 2010 (UTC)
48. Support The community give the tools so the community should be able to decide if they retain the tools. Also it will be interesting as stated above to see the amount of Admins who will oppose. Mo ainm (talk) 12:32, 23 February 2010 (UTC)
49. Support I think whichever beaureaucrat, steward, closing this poll, should research how many of the votes in either direction are sockpuppets, as this is a very weighty important poll. In any case, I personally view this, as, although it might warrant some small changes here or there, the best solution so far to some important problems (see Five Problems with a Single Solution), by the way thanks to commenters urging me to temper this comment's earlier form. :p sometimes I put my foot in my mouth. --Lyc. cooperi (talk) 12:45, 23 February 2010 (UTC)

    Five Problems with a Single Solution is a good argument that some form of deadminship was needed, and were this only a poll an whether, in-principle to support such an idea, I would supoort it. But this is a poll on a specific, detailed proposal. That proposal does not look like being the solution envisioned by "Five Problems" to me -- indeed one of the points in "Five Problems" was that any "RfDA" process must be appealable to arbcom, which this process is not. Any supporter ought, IMO to consider not just the need for a deadminship process, but the merits and flaws of the specific proposed process. You may have doen so, but your comment, like many above, does not mention those merits and flaws at all. DES ^(talk) 13:35, 23 February 2010 (UTC)

50. Support. Many ArbCom desysop motions have been on the basis that a specific administrator has lost the community's trust. Clearly ArbCom thinks admins should serve at the will of the community. A poll like the proposed CDA is a much better way of gauging the community's will than the opinion of fifteen individuals of what that will is. --GRuban (talk) 13:39, 23 February 2010 (UTC)
51. Support. Necessary. The standards have been quite high after extensive preliminary polling and discussions to prevent abuse. Pcap ping 14:13, 23 February 2010 (UTC)
52. Support The community decides who becomes an admin, the community deserves the right to desysop. I think this proposal works as well as any we could come up with. Angryapathy (talk) 15:49, 23 February 2010 (UTC)
53. Support A community process to remove adminship is, in my opinion, an important part of having a community-led wiki. Orpheus (talk) 16:32, 23 February 2010 (UTC)
54. Support I think the points made about indirect effects of having CDA in place are important, i.e. that it can take some pressure off the RfA process, no longer being irrevocable, and so on. Also, the argument back and forth about whether the Admin being recalled can respond, is overblown. I think it's obvious the Admin should respond and should be given a prominent section in which to do so, not buried down within the Opposes. But that is a technicality about operation of the CDA process, which would rapidly be amended to allow special designation of the Admin's response. --doncram (talk) 17:12, 23 February 2010 (UTC)
55. We have long been in the vicious cycle that RFA keeps raising the bar for prospective admins because of how hard it is to get rid of problematic admins, and that the ArbCom often shies away from de-adminning people because of how hard it is for them to regain the mop. Indeed, RFA success rates are at an all-time low. We need to break the cycle, both because adminship is No Big Deal, and because accountability is a Good Thing. >Radiant< 17:36, 23 February 2010 (UTC)
56. Support. Adminship is granted via a bureaucrat's evaluation of a community discussion, so it should be possible to remove it the same way. Many of the criticisms of the current proposal are generic fears that could be directed at any proposal. There will likely be problems and "growing pains" to work out, but none of the specific concerns are significant enough to keep me from supporting. --RL0919 (talk) 17:57, 23 February 2010 (UTC)
57. Support. It should never be up to a bureaucrat whether or not an official can be removed. I don't think it should be a simple thing to remove an admin's rights, however, as a community, we should have a say in whether or not it happens. J DIGGITY (U ¢ ME) 19:35, 23 February 2010 (UTC)

    You are aware that under current proceses no Bureaucrat ever desysops an admin, although the ArbCom as a group can and do desysop admins for cause? Under the proposed CDA process a Bureaucrat would make the decision as to whether the community discussion did or did not constitute consensus to desysop. DES ^(talk) 22:46, 23 February 2010 (UTC)

58. Support --Addihockey10 22:33, 23 February 2010 (UTC)
59. Support ... Smarkflea (talk) 22:38, 23 February 2010 (UTC)
60. Support. Not a perfect proposal, but workable and is an improvement over the status quo. Nsk92 (talk) 23:08, 23 February 2010 (UTC)
61. Support. We've a got a few too many runaway admins, and I'd like to see a more community-based approach to dealing with the problem. I wonder how often this will be used, but it's always good to have more arrows in our quiver. — Bdb484 (talk) 23:24, 23 February 2010 (UTC)
62. If there is community consensus to remove an admin, why not remove the admin? --SB_Johnny | ^talk 00:29, 24 February 2010 (UTC)
63. Strong support Salute to the admins, who supported the proposal!--Mbz1 (talk) 00:40, 24 February 2010 (UTC)
64. Weak Support. I think this particular proposal is flawed, probably unnecessary, and likely ineffective - I doubt that, if implemented, it would ever lead to a successful desysop. But I'm supporting it on principle, because I still think the idea of having a de-adminship procedure is basically a good one. This proposal isn't great, but I support trying it out for a brief period at least, in the hope that it might lead to a functional system being developed at a later date. Robofish (talk) 00:45, 24 February 2010 (UTC)
65. Support The more democracy, the better. This would be a positive step. ^rossnixon 01:35, 24 February 2010 (UTC)
66. Support Absolutely per SB_Johnny. If there's consensus to remove an administrator then they should be removed without ArbCom having to step in.--Giants27(Contribs|WP:CFL) 02:59, 24 February 2010 (UTC)
67. Support - I've been holding back on this vote 'till the 'crats weighed in, but feel the time has come to speak up. As some here know, I have been involved in the early and middle stages of Cda but withdrew towards the end for reasons beyond the scope of a !vote notice. It is enough to say that I believe Wikipedia has a hefty problem and that I'm not alone in feeling that way. This version of Cda is not my favorite, but a decent-sized tally, even should the Cda fail, will give us something to build on and send a message that there are a goodly number of editors who feel the current system needs improvement. My best to all concerned with the issue, regardless of their point of view. Jusdafax 03:17, 24 February 2010 (UTC)

    FWIW, a 'crat weighed in at oppose #44 :) -- Avi (talk) 06:21, 24 February 2010 (UTC)

    And I see Dweller at #104. I have said from the start of my involvement with Cda that bureaucrat opposition (voting as a 'crat or not) would kill my support. Since the gap to 50% in this RfC continues to widen, the point is moot. I'm going to refocus on administrator term limits. Jusdafax 19:56, 24 February 2010 (UTC)

68. Support as completely obvious. No admission process for anything is perfect. There obviously needs to be some way to get rid of problematic administrators or people who just aren't cut out for the position. If having an adminship is "no big deal" then it should be no big deal to revoke it, too. SnowFire (talk) 06:27, 24 February 2010 (UTC)

    I'm sorry, CDA cannot be used just to remove admin who aren't 'cut out for the position'. It is either a misunderstanding of CDA, or a con to say that it is. CDA would be damaging to Wikipedia, as dodgy admin can say "Look the system in fair! Vote me out if think you can!" when with CDA the system would not be fair, and people cannot vote them out. How will that make Wikipedia a better place? It's a step to a more solidly corrupt state. You can try for a CDA, but that in itself will only cause so much drama that all the extremely daft admin involved would prejudice the running of Wikipedia before, during and after the CDA. And if the admin has enough mates, you simply wouldn't win. The Bureaucrats couldn't judge that kind of thing anyway - so CDA simply won't happen. Admin are beyond canvassing (or any mid-range) rules, so CDA couldn't work until admin in general are better quality people, and that needs to ahppen via a different route to CDA. Matt Lewis (talk) 10:08, 24 February 2010 (UTC)

69. Support: I agree with constructively critical comments above that this isn't the best possible version of admin recall, but any version is a step in the right direction. The current system's just dysfunctional. By way of real-world analogy, in those democratic legal systems in which judges are appointed/elected for life, there is generally a way for the people to take a judge back out of office for abuse of power. — SMcCandlish Talk⇒ ʕ(^Õل^ō)ˀ Contribs. 06:36, 24 February 2010 (UTC)
70. Support: The community confers the privilege, it is the community's responsibility to take it away.Likebox (talk) 06:40, 24 February 2010 (UTC)
71. Support: Checks and balances, an important part of an open encyclopedia. Poulsen (talk) 08:33, 24 February 2010 (UTC)
72. Support The community should be able to move administrators in both directions, in and out. Graeme Bartlett (talk) 10:05, 24 February 2010 (UTC)

    Comment to above few votes: CDA simply cannot be used as a 'reverse RfA'. And isn't CDA trying to 'paper over the cracks' anyway? Many (if not most) of the 'oppose' arguments say that CDA will damage Wikipedia, and are not arguing that is should not be allowed in principle. Would people consider actually offering a fixed term to admin, rather a "job for life"? And instead of 'patching up' an archaic system with a well-meaning but toxic 'CDA' process, actually address the problems directly? There are proposals like 'Admin Review' processes too, where admin get reviewed. All of those are less destructive to Wikipedia in general than the CDA process. It they don't work, then maybe we should look at a form of 'admin recall' (and there are much better ones than this CDA). Matt Lewis (talk) 10:08, 24 February 2010 (UTC)

73. Support Something is better than nothing. This might not be perfect, but at least this can be worked on, and will make RfA less insane.Headbomb {^ταλκ_{κοντριβς} – WP Physics} 10:25, 24 February 2010 (UTC)

    I hope that people saying it can be "worked on later" are prepared to donate their magic wands! I put hours into trying to make CDA work, and it has flaws we could not resolve, which are simply insurmountable given the desperate state of adminship that we have (admin themselves will wreck CDA). Adminship needs to be changed from the ground up - we need to make it a fixed term, and subject to review. After a number of previous attempts to do so, someone just ran this CDA proposal with clear holes in it, and with various elements that did not meet consensus. A lot of issues were in the end simply denied. The "we can sort it all out later" philosophy, after hitting dead ends, is just foolishness given the seriousness of the process itself, and the stumbling blocks faced. The creation of this proposal failed consensus at various points in its making, and consensus being the glue that holds Wikipedia together, that in itself is a bad sign. Matt Lewis (talk) 11:11, 24 February 2010 (UTC)

74. Support In general I support the idea as deadminship is not really ArbCom's role and another mechanism needs to take its place. That said, simply adding a board of Bureaucrats to report such problem admins could easily lead to appropriate RfCs or a nomination to remove the "bit", or summary dismissal. I do NOT support this as the best method around, but that it is A method and the concept is both sound and necessary. — BQZip01 — ^talk 16:49, 24 February 2010 (UTC)

    Sounds to me like what you are saying is "Fleas on cats are a serious problem. It has been proposed to solve the problem by throwing cats into furnaces. I do NOT support this as the best method around, but that it is A method and the concept is both sound and necessary."--Wehwalt (talk) 17:05, 24 February 2010 (UTC)

75. Support This seems more Democratic and fair.IzzyReal hunts idiots (talk) 20:40, 24 February 2010 (UTC)
76. Weak support. A community-based administrator recall process is long overdue. ArbCom, an appointed body which itself consists entirely of administrators, cannot substitute for the wider community. That said, I do have concerns about this proposal. First, it requires a consensus for desysopping, "reaching (as a rule of thumb) at least 65% of the total !votes polled". Then admins need only 35% support to retain adminship. I think that's far too low; I would require a consensus in the other direction, so that to keep their position, admins would need 70-80% support, just like at RfA. Second, the proposal says that the 10 nomination signatures must occur "within a period no longer than seven days", but I cannot tell whether this period has a minimum duration. If not, I am concerned that discussion and polling could start before the administrator has had time to respond to the nomination. Personally, I prefer my own proposal, User:Tim Smith/Administrator-initiated recall. Nonetheless, if implemented, this one could be improved and clarified over time, so I support it over the status quo. Tim Smith (talk) 21:03, 24 February 2010 (UTC)

    The signatures could be collected in 10 minutes, but can't be certified for at least one week, so the accused admin will always have at least 1 week to prepare and 1 week for the process itself under this proposal. CRGreathouse (t | c) 16:04, 25 February 2010 (UTC)

    There's nothing in the proposal to prevent certification immediately after the 10 signatures are gathered. The seven day discussion and polling period would then begin. A safeguard like the one you mentioned was suggested, but was not incorporated into the proposal. Christopher Parham (talk) 16:40, 25 February 2010 (UTC)

77. Support. Seems to have adequate safeguards; provoking an admin into an abuse would be easier and more satisfying than pushing such a de-admining through. --Gwern (contribs) 21:12 24 February 2010 (GMT)
78. strong support I think that if an administrator went vandal he should be stopped, without waiting for other administrators.--RIVER^{Babble at my brooks} 21:56, 24 February 2010 (UTC)

    In the rare case that an administrator goes "vandal", how does initiating a 7 day community discussion address the need of not "waiting for other administrators"? --Allen3 ^talk 22:05, 24 February 2010 (UTC)

79. Support but with changes as per Tim Smith - Stillwaterising (talk) 22:24, 24 February 2010 (UTC)
80. Support. It's flawed, but it gets the ball rolling slowly in the right direction. Something has to be done to loosen the "pry my buttons from my cold dead fingers" mentality, and every journey begins with a single step. – iridescent 23:04, 24 February 2010 (UTC)
81. Strong Support. I can't believe this wasn't in place already. For what reason should we unconditionally trust the admins? We should be able to recall them. Kelseypedia (talk) 23:23, 24 February 2010 (UTC)
82. Support For all the reasons presented above. iadrian (talk) 00:41, 25 February 2010 (UTC)
83. Support Not the perfect system, but would be an improvement. I don't believe POV groups can hijack the process; they will provoke a reaction against themselves. Johnbod (talk) 03:49, 25 February 2010 (UTC)
84. Support -- Community Recall fits the Wikipedia philosophy. Pete Tillman (talk) 05:13, 25 February 2010 (UTC)
85. Support power to the people. CRGreathouse (t | c) 07:20, 25 February 2010 (UTC)
86. Support After looking at the vote analysis script results (see comment at the bottom of the page). Too many "oppose" votes came from admins. Clear conflict of interest / neutrality violation. --Dc987 (talk) 08:14, 25 February 2010 (UTC)

    • Agree that the non-admin vs. admin !vote gulf is strikingly wide at the moment. I have added the script link to the top of the page with the other links there. Jusdafax 09:36, 25 February 2010 (UTC)

    Not the best reason to do that surely? People need to read the voting comments without prejudice, so I've deleted the top link (it's at the bottom of the page anyway, and discussed in Talk too). Matt Lewis (talk) 10:23, 25 February 2010 (UTC)

    I'd just like to comment that I agree with Matt about that. This should be a month-long discussion, not a minute-by-minute horse race. --Tryptofish (talk) 19:15, 25 February 2010 (UTC)

87. Support, with some reservations. As of today, admins are almost completely unaccountable, and this has to change. The problem with this proposal is that it makes the recall a traumatic process. Being an admin is still seen as some kind of god-given right, so it will be necessary to have some "due" process to recall them. The opposite should be true: nobody has a right to be an admin; they are provisionally vested with some authority. They consequently should have terms and be automatically de-admined at the end of the term. Then they should be reconducted, if and only if, there is a consensus that they are good admins. Ninguém (talk) 10:27, 25 February 2010 (UTC)
88. Support. When an admin no longer has the trust of the community, the community needs a way to remove them. I would hope that if this process were to be put in place, admins would also be far less likely to abuse their privileges. Wine Guy~Talk 10:49, 25 February 2010 (UTC)
89. Support. RfA rates have been dropping, because at present admins are effectively for life. So in the long run the CDA proposal will help RfA rates as well as get remove of bad admins. There are a few bad admins, who do harmful dispropionate to their number. ArbCom will be need in some cases, for example there a clique of admins / or non-admins with drudges. But ArbCom can be be slow. A procedure at as fast RfA is needed. --Philcha (talk) 12:50, 25 February 2010 (UTC)

    What evidence do you have for your first statement? Is this just speculation on your part? --Hammersoft (talk) 13:54, 25 February 2010 (UTC)

90. Support Currently, when there is a problem with an administrator, the only channel available is to request input from other administrators. Because of concerns about wheel warring and sometimes and "old boys club" atmosphere, most administrators have been reluctant to look into issues involving potential admin abuse. I believe this policy takes the burden away from administrators and gives the community a chance to weigh in. This policy is long overdue. Wapondaponda (talk) 10:49, 25 February 2010 (UTC)
91. Support I second that. Openskye (talk) 12:06, 25 February 2010 (UTC)
92. Support as one of the key principles of any wiki, and one that is oft quoted at RfA, is that anything that can be done can be easily undone. This puts the ability to undue an action right where it belongs - with those who are able to do that action in the first place. If the community has the ability to grant Admin, it must have a parallel process to remove that status. The proposal itself is detailed and contains adequate protections for administrators to avoid nuisance requests. Jim Miller ^{See me | Touch me} 16:12, 25 February 2010 (UTC)
93. Support--Cube lurker (talk) 16:22, 25 February 2010 (UTC)
94. Support This isn't my preferred solution, as I believe it is flawed and a huge drama-magnet, but it is perhaps a move in the right direction. I still would prefer that adminship have set a set term length, after which an admin would be able to apply again, if they choose. Sχeptomaniac^{χαιρετε} 18:39, 25 February 2010 (UTC)
95. Support - Per the many good points made above. —mattisse (Talk) 19:54, 25 February 2010 (UTC)
96. Support - in practice, I doubt it'd occur except in truly exceptional circumstances. But it's the morally right thing to do. WilyD 20:45, 25 February 2010 (UTC)
97. Support via numerous good statements above. --Merovingian (T, C, L) 21:38, 25 February 2010 (UTC)
98. Support We need a process. This one seems as good as anything else. Arbcom gets rid of those who go _way_ over the line, but we need something to remove those who often go just a bit over the line. Hobit (talk) 22:32, 25 February 2010 (UTC)
99. Support. A means is needed for dealing more effectively with the very few rogue admins. Xxanthippe (talk) 23:48, 25 February 2010 (UTC).
100. Support. There is nothing I like less than a "for life" appointment. The fact that all these nice people gave so many good reasons to get rid of it is just icing on the cake. J.M. Archer (talk) 00:34, 26 February 2010 (UTC)
101. Support--I support the proposal. I believe an important new feature of this policy is that it allows a bottom-up proposal from non-admins, and then allows the outcome to be determined via a very open emergent process. N2e (talk) 01:09, 26 February 2010 (UTC)
102. Strong Support well, it's better than nothing. We need some form of de-adminship other than Arbcom or RFC.--Coldplay Expért ^{Let's talk} 01:15, 26 February 2010 (UTC)
103. Support - Furthermore, I am surprised to find out that there is no formal process to remove sysop equivalent to RfA. Obviously, the emergency, temporary etc processes should remain in force --Jubilee♫clipman 02:19, 26 February 2010 (UTC)
104. Support - I prefer the more democratic approach, but I seriously do not expect to see much in the way of community response. Most people do not participate and those with the administrator inclination do. My limited experience with internal procedures against an abusive administrator shows that existing Administrators protect their own. Therefore we do need additional tools to try to sidestep that gauntlet.Trackinfo (talk) 05:03, 26 February 2010 (UTC)
105. Strong Support a while back there was a certain extremely stubborn admin (who will remain unnamed) who deliberately did not engage in straightforward conversation and refuse to date and time stamp his comments. despite many concerns raised, we could not apply de adminship. worse still he became an admin years ago before any stringent WP:RFA criteria was set. LibStar (talk) 11:37, 26 February 2010 (UTC)
106. Switching to support. I believe all the issues I've had have been fixed, and while I don't like the general idea of desysopping good admins, I figure that's no reason to oppose this policy for serious circumstances. ALI ^{nom nom} 13:33, 26 February 2010 (UTC)
107. Support - better than current situation; adequate safeguards. Admins are not a vulnerable minority that needs protection, and the wider community is not a pitchfork-waving mob (well, not often ...). Gandalf61 (talk) 14:28, 26 February 2010 (UTC)
108. Support --Ysangkok (talk) 16:17, 26 February 2010 (UTC)
109. Support - I am an administrator, and I would be willing to submit to this process. If the community has a serious concern over the behavior of an administrator, then the community should have a forum - short of Arbcom - to allow their voices to be heard. In many cases, I don't believe it's any better to have 18 members of Arbcom decide rather than have a larger portion of the community decide whether someone keeps their bit. Karanacs (talk) 17:25, 26 February 2010 (UTC)
110. Support -- Admins need to be held responsible by the community. Even if the mechanism isn't used often, it offers an additional incentive for admins to maintain a collaborate relationship with the Wiki community. Uncle Dick (talk) 20:48, 26 February 2010 (UTC)
111. Support - I must have become recently sensitized to seeing uncivil behaviour and biased judgement from a number of active admins, to such an extent that I am puzzled at how some people managed to become admins in the first place. Any community must have appropriate checks and balances to stay healthy. This process is obviously not perfect, but it provides a way for action to be seen to be done. The structure makes it unlikely that a single-minded mob would kick out admins on partisan grounds, though no other system could guarantee to always stay absolutely free of group-think issues. Ash (talk) 23:11, 26 February 2010 (UTC)
112. Icewedge (talk) 00:51, 27 February 2010 (UTC)
113. Support - A positive step to a better wikipedia. No admins are superior than the community. Arteyu ? _{Blame it on me !} 04:52, 27 February 2010 (UTC)
114. Support - We really suck at dealing with admins who should really just be normal editors. - Peregrine Fisher (talk) 06:24, 27 February 2010 (UTC)
115. Support - any social community that elects a subgroup that holds particular powers or responsibilities should have a standard mechanism for periodically (re)choosing those individuals. These things are usually called elections, and in all democratic communities, the people who stand for these roles are generally volunteers, as at Wikipedia. As a political scientist in a democratic country, i am amazed at the amount of heat this debate generates. I've heard many of the arguments, but remain of the view that all admins should have to put their hands up every, say, three years, and see if they still have support. All the arguments about it being a volunteer community etc are not relevant in my view. However, since there is no widespread support for such a measure, i will support any proposal that begins to make re-evaluation of an elected/vetted sub-group more possible. This is a small step in the right direction, but bigger steps will be needed in future. hamiltonstone (talk) 10:36, 27 February 2010 (UTC)
116. Support - Truly non-abusive administrators have nothing to fear in de-adminship processes. \ Backslash Forwardslash / (talk) 11:21, 27 February 2010 (UTC)
117. Support -I personally have had some good exchanges with adms, but several bad exchanges with those who were arrogant and opinionated. I would like to have a chance at a recall vote of both groups. รัก-ไทย (talk) 13:51, 27 February 2010 (UTC)
118. Support With reservation concerning witch hunts. Overall, I would loosen both the election and removal processes for admins. Ceoil ^sláinte 14:41, 27 February 2010 (UTC)
119. Support. The arbitrary misuse, and occasional abuse, of misplaced authority by admins is unreal at times. I am not necessarily thinking of English WP here. Presumably any change of policy will apply generally across all projects of WP? Varlaam (talk) 17:57, 27 February 2010 (UTC)

     About applying to other projects, this RfC is only with respect to the EN WP. Other projects would have to decide for themselves. --Tryptofish (talk) 18:18, 27 February 2010 (UTC)

120. Default to support, I don't oppose and am not neutral. However, there was a chaotic tinge to the process that led to this particular iteration of a CDA-method RfC. My sincere hope is that this !vote will serve as a catalyst for all editors, opposers and supporters to agree to work together on something much more viable during 2010. Tryptofish, TenOfAllTrades, Ben MacDui and Jehochman for example could attempt to find common ground and work together to meet the desires of many to counterbalance the unfortunate current perception that has been expressed of admin-for-life/run-amok possibilities within the present project governance/maintenance structure. Sswonk (talk) 18:02, 27 February 2010 (UTC)

     It's still early in this RfC, but I'm happy to work with those who will work with me. --Tryptofish (talk) 18:21, 27 February 2010 (UTC)

     Yes, it is early, apologies for throwing this RfC under the bus so quickly. For those viewing this comment in the future, at the time of my !vote (included) the count was 120 support to 134 oppose. I will be happy if the support increases significantly beyond that and am encouraged that, at a total minimum, impetus toward future implementation of CDA can start here, regardless of the outcome of this RfC. Having a community elected position which does not allow for a future simple community based mandate is counter-intuitive and we should remedy that sooner rather than later. Sswonk (talk) 19:01, 27 February 2010 (UTC)

     No problem, no apology needed. You said it in the spirit of constructive discussion, rather than the minute-by-minute horse race that I've been cautioning against. (But since you brought it up, I'll point out again that the "motion to close" last month was leading decisively for the first few days, only to be rejected 2:1 as time went on.) Anyway, I stuck my neck out on this, and I'm getting quite used to being under the bus. :-) --Tryptofish (talk) 19:09, 27 February 2010 (UTC)

     The problem I see with the seeking 'common ground' approach is that I just can't foresee any variation on this process that would satisfactorily resolve the concerns I raise above, or acceptably answer the questions posted in Wikipedia:De-adminship proposal checklist. In order to modify this proposal to have sufficient checks against abuse and make it fair to all participants, we'd have to change it sufficiently drastically that it would no longer be any faster or more open than the existing de-adminship processes and tools. (I refer again to the alternatives that I offer in my rebuttal.)

     I will note that the "admin-for-life/run-amok" perception shouldn't in itself be a justification for developing new policy — and especially not bad policy. If we grant (for the sake of argument) that there is a widespread perception of 'lifetime admins run amok', it should trigger a calm, rational, fact-driven examination of the perceived problem. The community needs to figure exactly what the issues are. What problem admins have we dealt with successfully, and how does that differ from the situations where we have failed to do so? How do we define a problem admin, and why types of (mis)conduct warrant desysopping? Have our existing processes failed to respond correctly to problems, or have these processes simply not been used (or not been used correctly)? Can our existing policies and processes be tweaked to resolve these issues, or do we need genuinely new and separate mechanisms to fix the problems? If we find that there are really only a few admins who would be the focus of a new process, does it make sense to establish a whole new regulatory framework with all its overhead and drama?

     Unfortunately, there has been a preference to shortcut that rational discussion of problems, expectations, experience, examples, evidence, and desired results. Over and over again, we've jumped past the analysis of the problem directly into attempted solutions. These proposals will continue to fail because they don't know what problem they aim to solve — or even if the problem exists in fact or primarily in perception. TenOfAllTrades(talk) 20:06, 27 February 2010 (UTC)

     As I said above, I'm happy to work on ideas. I can't help observing how the response to Sswonk's suggestion resembles the "health care summit" that just occurred a few days ago in the U.S. --Tryptofish (talk) 21:04, 27 February 2010 (UTC)

121. Support We'll just have to make sure the process won't be too long or too difficult to start, and also that it will finally be effective.--Michael X the White (talk) 21:07, 27 February 2010 (UTC)
122. Strong support We've needed a way to desysop admins without ArbCom for some time now. This would also free up ArbCom for more important tasks. -- Sk8er5000 (talk) 23:10, 27 February 2010 (UTC)
123. Strong support -- This is an excellent proposal. I agree with Tryptofish's comments above. ...If the community can be trusted to vote for someone to be a sysop, then they can be trusted to recall them. That is how any serious democratic institution works. Stripping the community of recourse after they've voted someone into office doesn't benefit the community at all. ...Claims that this will "discourage editors from acting boldly" are unfounded. It will only discourage them from acting irresponsibly and inappropriately. The community will not de-sysop them unless they act this way -- they won't de-sysop them for acting boldly. How do I know this? That is, how do I know that the community won't irresponsibly revoke admin priveleges from people when they don't deserve to lose them? Because the Wikipedia community is mostly decent and fair. That's why the encyclopedia doesn't totally suck ... Claims that this would "increase drama", I don't believe are well founded either. This wouldn't magically create new "drama" -- it would just relocate a certain type of drama that's already taking place to a different spot ... it might even reduce drama by allowing people a proper outlet for serious problems that they are having. -- Jrtayloriv (talk) 08:24, 28 February 2010 (UTC)
124. Support, as the need for this should be glaringly obvious. Bullying administrators are a serious problem for this project, and there needs to be some way that all of us plain ol' editors can remove the extra buttons at the top of their screen, that seem to empower them in their bullying ways. It's long since past, the time when adminship was no big deal. Now, there exists a number of administrators who view their adminship as some kind of "badge" by which they get to "police" other editors, instead of a mop, to be used to clean up messes. This has to end, and this proposal -- doomed, though it may be by the "blue wall" of administrators lined up against it -- is a good start. Scottaka UnitAnode 16:22, 28 February 2010 (UTC)
125. Support not a perfect proposal, but I think it will work. It has the checks and balances required to make it hard to game the system and in the end it will be up to the Crat. Hopefully we never have to use it. -- RP459 ^Talk/_{Contributions} 16:47, 28 February 2010 (UTC)
126. Support The idea of introducing greater accountability into the system appears to be a good one. The CDA will need to be handled responsbibly (same as RFAs) and I think the community has shown itself mature enough to handle that process well enough. It is clear that abuse of this process should not be tolerated nor do i expect it will be. My only suggestion would be that Admins should all be subject to re-evaluation after a fixed period of time (every 2-3 years) as I find that service as an Admin has a lot of similarities to the teaching profession - namely length of service is directly correlated with influence but not necessarily correlated with performance. Something to think about. |► ϋrбanяeneωaℓ • TALK ◄| 20:26, 28 February 2010 (UTC)
127. Support If we had 2-yr admin term limits (perhaps with a simple vote for all re-affirms, without all the Q&A stuff that goes in RfA's), this would take care of itself. The fact that we have to do this re-call stuff in the first place, is a result of WP's poorly-thought-out "admin for life" policy. SBHarris 23:15, 28 February 2010 (UTC)
128. Support If we can't have term limits, then we must have this possibility. Hepcat65 (talk) 01:57, 1 March 2010 (UTC)
129. Support I strongly support the proposal because a lot of administrators had taken bad decisions. When questioned why a certain action was taken, in response to this I got an answer " You will be banned from furhter editing for being uncivil". They should be held accountable for all the actions they take and if an administrator does not follow the principles, he/she should be removed as an administrator and all the priviledges should be snapped. Nefirious (talk) 04:22, 1 March 2010 (UTC)
130. Support I completely support this proposal, as I believe there needs to be greater accountability for administrators. The CDA is a great proposal, which allows the community to put a check on those we originally gave our confidence vote to; I think it's only fair that we have the right to remove that confidence ourselves instead of relying on ARBCOM. -- Nomader ^(Talk) 05:19, 1 March 2010 (UTC)
131. Support. Unfortunately, this is obviously not getting consensus to implement it. I fully support it as admins, like myself, should be accountable. --Bduke (Discussion) 09:16, 1 March 2010 (UTC)
132. Support. It seems measured, transparent and if it is found to be abused then those abusing it can be taken to task, nothing to fear here. Unomi (talk) 15:04, 1 March 2010 (UTC)
133. Support. A reasonable proposal that has been long discussed and is well thought out; it will make life better for all (except rogue admins) users of Wikipedia. LK (talk) 15:40, 1 March 2010 (UTC)
134. Support per above and because I dislike "for life" appointments —Preceding unsigned comment added by IsaacLey (talk • contribs) 00:32, 2 March 2010 (UTC)
135. Support Let's have some accountability. It just might concentrate the minds of the more infantile admins. Writegeist (talk) 19:09, 2 March 2010 (UTC)
136. Support No block-ability without accountability. I don't buy the lynch mob argument. I trust the community to spot and outvote a lynch mob. MoreThings (talk) 15:09, 3 March 2010 (UTC)
137. Support. As per Tryptofish. — SpikeToronto 19:00, 3 March 2010 (UTC)
138. Support I'm open to recall, and have gone through the (eventually unsuccessful) process once already. The procedures set out seem to have a reasonable chance of bringing a desirable outcome.--SarekOfVulcan (talk) 22:02, 3 March 2010 (UTC)
139. Support As I said in one of the earlier incarnations of this, ArbCom should not remain the only recourse for the community to rescind the trust it gave at RfA. Admins currently get voted in, but lacking term limits and reconfirmation votes, it is immensely difficult to remove one that no longer behaves to the standards he displayed and claimed to uphold on his election as long as he doesn't engage in glaring misconduct. The notion that one is pretty much seated for life unless one goes on a rampage is IMO tightly related to the current climate at RfA, the drop in active admins, but also in the us vs. them perception that is prevalent in pretty much every single policy discussion on this site and that stiffles progress, innovation or attempts at reform in areas that sorely need it. Is the proposal perfect? Not yet. It needs more safeguards against revenge for the infamous difficult blocks, EEML-type coordination, and unpopular but necessary AE actions. But we have to start somewhere, and this looks like the least unlikely proposal for a foreseeable future. MLauba (talk) 22:46, 3 March 2010 (UTC)
140. Support. Removal of admin access happens when you have a consensus against you. Handling a controversial issue properly may alienate some users who will oppose you, but it will hardly turn the entire Wikipedia community against you. When dealing with a controversial issue causes most of the community to lose trust in your ability to wield the admin tools, it is most likely because you handled the issue poorly. Most of the people I see on RFA/AFD/ANI and other discussions argue decently, and it is unfair to call them part of a "lynch mob". We have informal processes on WP:ANI for imposing community bans, and a process here should not be nastier than that. Sjakkalle (Check!) 08:30, 4 March 2010 (UTC)
141. Support. A step forward to providing checks and balances of power among editors and admins. jmcw (talk) 11:35, 4 March 2010 (UTC)
142. Support I understand many of the oppose concerns, but I think the Wikipedia community is smart enough to recognize the gaming and elevate concerns if neccessary. Many are treating this proposal as THE only way to remove an admin and not an additional tool. I can see at this point the proposal does not have much confidence from the community, but I do support.--v/r - TP 14:06, 4 March 2010 (UTC)
143. I support this proposal with the understanding that it will still be worked on to incorporate some of the great modifications brought up by parties on all sides of the issue. — Bility (talk) 16:40, 4 March 2010 (UTC)
144. Support the principal that Admins. are ultimately responsible to the community. This is only true if there is some mechanism by which ordinary eds. can enforce a desysop sanction directly. Good points made by opposers which would need to be accomodated, but on balance my take is to support this proposal. RashersTierney (talk) 16:55, 4 March 2010 (UTC)
145. Weak Support. I agree with the criticisms about the process being something of an ordeal. I generally favor a system where if a dozen or so editors in good standing request that admin stand down, then the admin should either stand down, or go through a RfA. That way if an admin has been under a lot of stress, and has made more mistakes than usual, s/he can take a few months to recover, and then face a RfA. The process under discussion here creates, by default, a stage in between the petition and the RfA, which I think is unnecessary - if anything there should be a RfC before the petition. Anyway, I'm weakly supporting, because I agree with the general idea, if not the details. PhilKnight (talk) 17:36, 4 March 2010 (UTC)
146. I support the Wikipedia:Guide to Community de-adminship. – Athaenara ✉ 20:28, 4 March 2010 (UTC)
147. Support Wholeheartedly This approach is fair, balanced, requires sufficient evidence of chronic problems with a nominated admin, and long overdue as a codified process. --BlueSquadronRaven 20:40, 4 March 2010 (UTC)
148. No Monarchs for Life! A lot of admins should be desysopped. Wikipedians need to get serious about doing something about worthless or rogue admins, or nothing can be done about rogue rank-and-file editors. The mop is meant to be used, and used responsibly, and a higher level of behavior should be expected of admins. Currently, people won't go to admins about Wikipedians that are problems for the project, because so many admins are problems for the project. There are admins with no time to look into anything they're making a decision about, and that don't even know Wikipedia's policies and guidelines, but they've got no problem throwing their weight around. Others are activists using and abusing policies and guidelines for their own ends, and they make 'friends' and allies. People see this and they withdraw from the project, as I did. Wikipedia's a huge game and the admins are doing nothing about it. (They know how to play it.) -- Rico 23:29, 4 March 2010 (UTC)
149. Support. I can't see a trial of this damaging WP. At least that way we'll have a better feel for whether the process works (or needs refining).  HWV258.  00:17, 5 March 2010 (UTC)
150. Support. My experinece with adminstrators has (with a few exceptions) been one of arrogance and inability to consider the observations of those outside their own ranks. Having recourse held over their heads will increase their ability to listen and to think. Brews ohare (talk) 02:23, 5 March 2010 (UTC)

Oppose

1. ArbCom have been more willing to desysop administrators who have shown to use the tools poorly. Generally speaking, if an RfC comes to the consensus that an administrator no longer holds the trust of the community, ArbCom will desysop them. I don't personally believe there is a problem to fix. I fear that if this proposal was to move forward, a lynch mob mentality would result and administrators who deal with controversial issues would regularly be brought through the community deadminship process. I also fear that administrators who make one mistake would also be sent through the deadminship process. All in all, I believe it will lower morale in the admin corps. Whilst the RfC, then to ArbCom route might not be ideal, I believe it serves as a good check and balance. Ryan Postlethwaite^{See the mess I've created or let's have banter} 19:09, 22 February 2010 (UTC)
2. This proposal is likely to be harmful on a number of levels, discouraging administrators from boldly responding to sensitive and complex issues, while encouraging those who would use wiki-process to pursue personal grudges and vendettas. The current system, meanwhile, is humming along very nicely. I know of no administrator in the past 2-3 years whom ArbCom did not desysop, when presented with evidence of flagrant abuse of the tools, or place on probation which would lead to desysopping "next time," when presented with evidence of severe error or other inappropriate use. Christopher Parham (talk) 19:21, 22 February 2010 (UTC)

   Of course if one is an administrator for life, then the current system is humming along nicely. But this view is not held by everyone, as many of us see significant problems. Egregious cases of admin abuse are in fact quite rare, but administrators frequently make poor choices, that may include favoritism or a lack of impartiality. Because poor decisions that are not egregious are tolerated by other administrators, certain administrators continue to make these poor decisions, and some start believing that their behavior is acceptable. It is because of these poor decisions that some editors hold personal grudges and vendettas against certain administrators. If an administrator is competent, fair and impartial then I see no reason why reasonable editors will hold a grudge against him or her. Because administrators are not accountable to the community, many administrators are too quick to pull the trigger when a problem arises, and fail to consider other ways to resolve problems that don't leave a bitter taste in anyone's mouth. By implementing the CDA, I believe admins will be more thoughtful about the decisions they make. As for Arbcom, the process works well for egregious violations, but Arbcom is somewhat mysterious, distant and isolated from the wider community. Consequently admin abuse may persist for a long time before it gets to Arbcom level. Wapondaponda (talk) 15:09, 26 February 2010 (UTC)

   Perhaps you could point to some of the instances in which you attempted dispute resolution against an admin who made such poor decisions, but the current system failed to act in the way you desire. A good example would be an RFC where the community clearly indicated that an admin had made repeated errors, but where a later ArbCom case did not result in desysopping. Christopher Parham (talk) 16:09, 26 February 2010 (UTC)

   As previously mentioned, it is usually egregious or persistent breaches that tend to gain attention, enough for an RFC to be created. Other activities that involve poor decision making are simply forgotten, by most except maybe the aggreived parties who then hold grudges. I do not have a major problem with decisions made by Arbcom, however most grievances never get to arbcom. Wapondaponda (talk) 18:36, 26 February 2010 (UTC)

   An RFC requires a mere two users to be confirmed; an incident so forgotten that it didn't meet the two-user hurdle does not sound to me like one demanding removal of the bit. If these grievances aren't getting to ArbCom, it's not because of a flaw in the system, it's because of the unwillingness of the offended parties to work through the dispute resolution process. Christopher Parham (talk) 13:58, 1 March 2010 (UTC)

3. For the reasons exhaustively detailed above (#Flaws in this process noted by TenOfAllTrades) I must oppose this proposal. TenOfAllTrades(talk) 20:14, 22 February 2010 (UTC)
4. Oppose: I've put a lot of work into CDA since I found it flagging a little in a 'Motion to Close' at the end of Dec (over 100 hours - and this is important to note), and a lot of it is still in there. In my experience the proposal hasn't been that carefully considered (serious discussion on the central Canvassing issue was very 'last minute'), and at least one major consensus has been ignored - the desire for a higher 'threshold' percentage (it was clear to me that 85% was the conservative 'mean average' of the voting results - not 80%, but the vote itself was disputed. A lot of people preferred the Bureaucrats to make the full decision, not the "percentages" so-to-speak, and felt the threshold shouldn't be too low). During my work on CDA, I have defended CDA quite passionately at times (eg "don't so be angry and cynical in your opposition", "we must give it a go" etc), but my eventual realisation is that CDA cannot work. A CDA-related AN/I on me made me realise what I had been blind to: the rapid amount of support (almost instant support) designed with no other intention than to get a decent editor into trouble. Selfish perhaps - but it was a real epiphany regarding CDA. It wasn't the editors that concerned me (I expected certain people to turn up) - it was the admin involved in it all. It was so unpleasant that I asked myself "does Wikipedia really need this?". A decent Canvassing section (and despite attempts, this CDA proposal doesn't quite have one) can possibly prevent a number of editors causing mayhem even before an official CDA starts (enough to be worth trialing CDA anyway). But it cannot stop admin - who are easily in contact - behaving badly, and supporting each other instinctively, and as various 'favours', as they so often do. We cannot be in denial about these things. Admin are editors too, and are fully capable of attacking another admin unfairly (and extremely bitterly too), and I cannot believe that any Bureaucrat would want that to be played out in such a public forum. CDA will prejudice Wikipedia itself - before, during and after the CDA, and the Bureaucrats decisions could become impossible to make fairly. The Crats just wouldn't be interested in it... Matt Lewis (talk) 20:29, 22 February 2010 (UTC)

   I worry that chasing decent-but-awkward admin will even be the 'norm' with CDA nominations, as most of the 'canny' admin could easily escape CDA anyway. Decent admin are easier to catch because they don't wriggle so much. CDA is not the only possible version of Admin Recall though, and RfA (the actual 'Request For Adminship' process) can still be improved, regardless of any form of Admin Recall that might be around. Basically, CDA is an unwashable bandage on a structural complaint. We need to get to the root of the problem: the quality of the RfA process (esp in the past, where it was much easier to become an admin), and the actual wisdom in actually awarding someone we don't really know such a veritable booty in the first place, eg such powerful and varied block tools, and a "job for life" over a sensible fixed term. Matt Lewis (talk) 20:29, 22 February 2010 (UTC)

5. Oppose: I largely agree with TenOfAllTrades's analysis. I also feel that there's far too much drama on Wikipedia already, and CDA would simply add to this, without, I think, giving us much benefit in return. Scog (talk) 21:31, 22 February 2010 (UTC)
6. To be direct, I simply don't trust the Community to not abuse this ability. They (collectively; as one) are too quick to rush to judgment (generally speaking). Given the arbitration committee's willingness to desysop as of late, as Ryan P. points out above, I'm comfortable that any administrators who really should have their rights removed will have them removed. - Rjd0060 (talk) 23:08, 22 February 2010 (UTC)
7. A solution just screaming out for a problem.--Wehwalt (talk) 23:11, 22 February 2010 (UTC)
8. Oppose - I agree with a lot of what TenOfAllTrades has said. I also take issue with the supporters' proposed stance of "working out the details later". This is certainly a case of where the details matter, and at present, this is only going to lead to more drama. (Note: this doesn't imply that I have a solution, only that I think the proposed idea is worse than doing nothing). -- Bfigura ^(talk) 23:12, 22 February 2010 (UTC)

   Not true that supporters all think details are to be done later. --Tryptofish (talk) 23:15, 22 February 2010 (UTC)

   While I'm not trying to say that all supporters were in favor of working out the details later, at least two currently are. I'm merely stating that I disagree with them (not trying to put words in anyone's mouth). -- Bfigura ^(talk) 23:18, 22 February 2010 (UTC)

   I think it should be clear that the details can change, through normal processes of consensus for change. The long build-up to this proposal might give some the idea that it is now "finalized". No policy or process on Wikipedia is ever finalized. Gigs (talk) 01:37, 23 February 2010 (UTC)

   I understand. But if we implement a flawed CDA policy (like this one), the flaws won't get fixed until after they've been used to axe an admin or two. I don't see a reason to risk the damage, since I haven't seen any persuasive arguments as to why CDA is needed in the first place. -- Bfigura ^(talk) 04:30, 23 February 2010 (UTC)

   On thinking about this further, I'd like to make an observation. The procedure for closing this RfC requires that, if (and I said if) the proposal is supported, it must still undergo review by Bureaucrats and Jimbo before any implementation would be possible. I would suggest that revisions to the proposal that acquire consensus during this poll would need to be incorporated at that step. Now, please don't get me wrong: I'm not saying that editors should !vote for anything on faith or that they cannot logically oppose it on this basis. But I am pointing this out for any editors who might be interested, or who may wish to advocate for such changes. --Tryptofish (talk) 19:22, 25 February 2010 (UTC)

9. Bureaucracy creep. The ArbCom is perfectly sufficient. Kafziel ^{Complaint Department} 23:14, 22 February 2010 (UTC)
10. Oppose: I believe the net harm to the encyclopedia will outweigh the benefits of weeding out a few bad apples. ArbCom is sufficient, and I hate to see abuse paralyze the already understaffed and overworked admin corps. bahamut0013^words_deeds 23:15, 22 February 2010 (UTC)
11. Oppose I was expecting to support CDA. After reading the comments by TenOfAllTrades above, i think the current proposal is fatally flawed. I do think that a revised proposal, which deals with some or all of his concerns, might be worth enacting, but in light of the recent Craigy144 case, i am not convinced that there is as much urgency about this as IMO there once was. DES ^(talk) 23:16, 22 February 2010 (UTC)

    I want to be clar, i suport the idea of CDA in principle, i have long though that some sort of community-driven process for removal of admin tools was needed. But I can't support thsi proposal, particularly not on a promise "oh we'll fix the details later". And the problem was worse when the ArbCom would only desysop for the most egriguious misuse of the tools. DES ^(talk) 00:55, 23 February 2010 (UTC)

12. While the proposal has some subconscious immediate appeal (live by the sword, die by the sword), the fact that no bright line is drawn—nor is there a mechanism proposed for defining one—makes this difficult to support. At a minimum there ought to be a mechanism to attract the attention of a random sampling of impartial editors to review the CDA, and a clear mechanism for them to interact with the agrieved (including none at all) and agree on the true facts of the matter, and how that relates to a de-sysopment verdict. —EncMstr (talk) 23:41, 22 February 2010 (UTC)
13. I agree with many of TenOfAllTrades's points, especially those regarding procedural fairness. I'm also not a big fan of the "requiring 10 people to support before the process actually starts" part. On one hand it helps to prevent frivolous requests, on the other hand, it runs the risk of starting inertia toward support before the process even begins. One of the main reasons that ArbCom elections switched to a secret ballot was so that the early voters wouldn't have the ability to set inertia and have their comments in the prominent position at the top of the section where they might have a disproportionate effect on later voters. This has a similar risk, except it would always force it in one direction. Given that ArbCom seems more willing to deal with cases through motions, I don't think this process is necessary as it may have been a year or so ago. Mr.Z-man 23:45, 22 February 2010 (UTC)
14. I'm very much worried about any proposal which would place administrators at the mercy of any mob that has an agenda to push. I would support a proposal for some sort of streamlined (and more orderly) RfC-like mechanism which makes the community's will known — something which this proposal approaches — but not make it binding without the check and balance of the committee being the final word.

    Frankly, the relative inertia of the committee in cases of desysoping is a good thing; and there is nothing that would prevent the committee to simply "rubber stamp" by motion the result of any process that was fairly run and where concerns were properly heard. — Coren ^(talk) 23:51, 22 February 2010 (UTC)

15. I like the general idea of community-driven de-admining, but cannot support this proposal. In particular, I'm sure we would see admins who take action against any large, vocal group facing CDAs, causing a natural reduction in admin boldness. (This is a corollary to TenOfAllTrades's point about procedural fairness.)
    Designing a robust CDA procedure would be quite difficult and (I suspect) not a productive use of our time. I think Coren's suggestion (immediately above) is a much better option. CWC 00:14, 23 February 2010 (UTC)
16. Oppose- I agree with many of the points put across by TenOfAllTrades. I believe ArbCom is sufficient in dealing with admins who should have their adminship removed. I think the system proposed would be too easy to abuse. ^OohBunnies!...speak 00:39, 23 February 2010 (UTC)
17. Oppose drama magnet. Andrew Lenahan - Starblind 00:39, 23 February 2010 (UTC)
18. I am afraid that this will become Wikipedia's grand theater of High Drama. I am also concerned that editors who have been justifiably sanctioned by administrators, including some who are very frequent guests at AN/I and similar fora, will use this mechanism against good cops. There are plenty of persistent troublemakers with more than the requisite account age and edit count, and well more than 10 of them can be rounded up in short order. I don't want administrators, or other editors for that matter, spending unnecessary time in recall proceedings, when they can better spend that time enforcing Wikipedia's policies and guidelines and improving Wikipedia's articles. The existing mechanisms are sufficient to deal with the very small minority of administrators who abuse their authority or tools.—Finell 00:56, 23 February 2010 (UTC)
19. I count two critical flaws. First: the committee is an important check on any movement that seeks the removal of administrator rights, but it is entirely ignored in this proposal as it stands. Second: the proposal holds that 65% in support of a desysopping means that there is a consensus to remove sysop rights. Hardly—anything lower than eighty would be unacceptable.

    A community de-sysopping process should exist. And this proposal has clearly had a lot of work put into it. (Those editors who are its proponents have my thanks for their efforts in tackling what has long been an elephant in the room.) But a CDA process must incorporate a requirement to have the advice and consent of the arbitration committee in relation to every desysopping, as otherwise we will suffer quite grievously from the problems that Ryan Postlethwaite and Coren envisage. And we need to set the bar much, much higher, to reduce the incidence of trigger-happy desysoppings. A good start, but adjustments are needed. AGK 00:54, 23 February 2010 (UTC)

20. Oppose - This seems less like a reasonable tool for quality control and more a way for people angry at admins to go on the offensive. I see the word "community" in here but I'm not seeing the mechanism that somehow accurately represents the will of something so large. Is there no intermediate step that could be tried first before resorting to this mob magnet? Rob Banzai (talk) 01:00, 23 February 2010 (UTC)
21. I oppose out of one specific concern that I don't feel can be adequately expressed by this or many other CDA proposals. I mean very well for those who deliberated upon the topic and worked and compromised to get this package of a proposal. I hope this process serves as a model for processes in the future. Regardless, my concern is that this role is not only handled by the Arbitration Committee competently, but more fairly than a community de-adminship process could. While arbitration cases by design scrutinize each party as the embattled editors they are, CDA is inherently biased towards the administrator; even if the nominees are scrutinized, it's the administrator whose name gets put on the CDA and its the administrator around whom all discussion is focused. This is especially problematic in cases where a lynchmob goes after an administrator who made a controversial yet appropriate decision. Because of these things, I feel I must oppose for now. harej 01:12, 23 February 2010 (UTC)

    • If you "mean well for those who deliberated upon the topic", perhaps you can explain why a Wikipedia admin sees fit to place a bogus 'Om box', clearly designed to cast discredit on this RfC, at the top of the page in its opening hours? I'm sure many besides myself will find your answer of interest. There is also a specific section regarding this issue, above. Jusdafax 06:19, 25 February 2010 (UTC)

22. Oppose - On balance this seems more troubling than helpful and as someone has said, a drama magnet. I am not convinced that there is a sufficient problem requiring this particular solution. I am happy to allow arbcom to handle wayward admins. JodyB _talk 01:21, 23 February 2010 (UTC)
23. Oppose - Leave it to arbcom, there is no need for an additional layer of drama. Letting admins run the gauntlets to see if they make it to the other side is not the way to go. -- Kim van der Linde ^{at venus} 01:29, 23 February 2010 (UTC)
24. Oppose - I don't see a need for it and as many have highlighted above, ArbCom can deal with this issue effectively and in a balanced manner. If anything is needed then it would be an extension and formalising of an ArbCom process. → AA ^(talk) — 01:34, 23 February 2010 (UTC)

    Having read other comments and opinions, I want to add that what I think could work is an "admin suspension" policy as a compromise, with ArbCom having the final say on either re-instating or revoking admin rights permanently. Pre-requisites for initiating this action would be clear evidence that admin tools have been abused on a number of occassions and could in fact be a quicker route to "suspending" abusive admins than this proposal suggests but I still oppose this process as it is too easy to be abused by blocs of editors with a grudge and will keep admins away from dealing the controversial subjects. → AA ^(talk) — 09:41, 23 February 2010 (UTC)

    Wouldn't it be possible to achieve exactly the same thing by modifying the "appeal" section of this proposal to add an automatic, required, appeal to ArbCom? --Tryptofish (talk) 19:24, 24 February 2010 (UTC)

    That may be so (or may not be) but what we are discussing is the proposal as presented and as such it does not have this or other sufficient safeguards. If this is to become policy, it needs to be sufficiently workable in the form presented without a need to re-engineer the policy substantially. Having taken another look at it, it strikes me as flawed since nowhere does it provide the criteria upon which the CDA process should be initiated and why ArbCom is not capable of dealing with it. This, I think, is a fundamental requirement that needs to be stated. → AA ^(talk) — 20:21, 24 February 2010 (UTC)

25. I oppose this due to the numerous flaws pointed out above by TenOfAllTrades.--Rockfang (talk) 01:46, 23 February 2010 (UTC)
26. Oppose, with reservations. Although the community gives the admin bit, you might assume it should also be able to also take it away. However, in my experience, it does not take much effort for a momentum to develop against an admin who, although generally competent, has made a few bad decisions. ArbCom emergency de-sysopping exists if that gets gross, and Arbcom can apply conditions for re-sysopping. Otherwise, RfC and RfArb exist. I don't think we need further process as an unnecessary layer of bureaucracy. Rodhullandemu 01:53, 23 February 2010 (UTC)
27. Oppose due to terms of process, though I may support an alternate form of community de-adminship. The currently stated requirement of "most of those above approximately 80% support for removal are passed, while most of those below approximately 65% fail, and the area in between is subject to Bureaucratic discretion" leaves an excessively large amount of discretionary power to 'crats, in my opinion. Policy that spells out the possibility of de-adminship with 65% (or near it) support is ludicrous. If that's the criteria, ArbCom alone is a much better solution than the proposed process. Steven Walling 01:55, 23 February 2010 (UTC)
28. Oppose - I agree with Tenofalltrades' arguments sufficiently to give me serious misgivings about this proposal. A modified Arbcom process might serve the community better. dramatic (talk) 02:35, 23 February 2010 (UTC)
29. Oppose No ta, bad idea and open to manipulation and agenda driven desysopping. The Arbs are willing to desysop for cause so what problem are we solving here? Spartaz ^Humbug! 02:39, 23 February 2010 (UTC)
30. Oppose. I could see this being open to some abuse as per Spartaz, plus, the arbitration committee is willing to desysop for cause. Removal for cause by ArbCom makes sure that all other methods were exhausted, and establishes firm grounds for removal. This proposal seems to make the administrator position into political office rather than something closer to civil service. SchuminWeb (Talk) 02:47, 23 February 2010 (UTC)
31. Oppose. Popularity contest. Hesperian 02:52, 23 February 2010 (UTC)
32. I've been on the fence over this whole issue for a while. Ryan's points above, combined with Tenofalltrade's arguments have convinced me that it is a bad idea. Personally, I think that ArbCom does a perfectly fine job of desysopping admins who have actually done wrong, without getting the ones who just made bad decisions. I fear that if this proposal is enacted, a few admins will get their rights revoked for less than what they get now, which is perfectly fine. This is a well-thought out and well-intended proposal, but I cannot support it. (X! · talk)  · @174  ·  03:10, 23 February 2010 (UTC)
33. Oppose A bad idea on several counts. Most obviously because it's not as if we have dozens of rogue admins running around damaging wikipedia. Arbcom, and the common sense of admins who resign, seems to do the job fairly well. But, beyond that, we hardly need more processes floating around and politicizing wikipedia. Enough time is already spent on various processes (navel gazing at WT:RFA is the prime example) and we definitely don't need more work for admins responding to questions and defending their actions in a desysop poll of sorts. One must bear in mind that this is a volunteer effort and adding more layers of non-encyclopedic work is hardly the direction we should be moving in. Finally, Wikipedia:Community_de-adminship/FAQ#7._Q:_Is_CDA_is_trying_to_resolve_any_existing_problems.3F is full of wishful thinking. One could argue the opposite on "beneficial" claims made there. Rather than act as a 'beneficial deterrent' it might be a detrimental deterrent with admins unwilling to take tough decisions. It might also be a 'detrimental deterrent' to running for RfA - why bother if ten editors and their socks can put you through the mill all over again. --RegentsPark (talk) 03:11, 23 February 2010 (UTC)
34. Oppose having been on the arbitration committee and in my time (and afterwards) there tried to highlight arbcom's role in reviewing admin tools, I can confidently say it is the least drama-inducing way of reviewing admin tools. The main problem I have noted in the past 12 months or so is a reluctance for the community to request a case of reviewing tools to the arbitration committee, not the committee's reluctance to take them. Another observation made while I was involved was that one of the areas where wikipedia needs admins the most is the trouble-spots, that is, articles and subjects which have been the subject of arbitration cases and are under some form of probation. It is these areas where admins using tools can quickly come under fire from one (or both) 'sides' if they have made actions viewed as unpopular. I fear a bloc of editors, especially eloquent or political ones, could easily take revenge by a path such as this. Hence this proposal could worsen admin shortage in wikipedia's sore spots. Casliber (talk · contribs) 03:22, 23 February 2010 (UTC)

    Moved relevant threaded discussion to talkpage — Coren ^(talk) 00:56, 25 February 2010 (UTC)

    Now at #Observations re Casliber's comment, above. --Tryptofish (talk) 01:49, 25 February 2010 (UTC)

35. Oppose. This was never a viable proposal (with this much discussion above, I have nothing to add on the subject of why that is), and it has been frankly disheartening to see editors with good intentions continuing to push refining it when any number of people have pointed out that fine details aren't what dooms such proposals. I hope the editors involved (who have, I repeat, good intentions) will accept at some point that it's time to stop moving on this. My apologies if the previous sounds patronizing; I don't know how else to say it, and it needs to be said. — Gavia immer (talk) 03:58, 23 February 2010 (UTC)
36. Oppose—see my detailed rationale. Chick Bowen 04:16, 23 February 2010 (UTC)
37. Oppose. I'm against this for the same reason I support Life time appointments for Supreme court. If a single controversial action by an Admin can bring down wrath of a small group of editors, and then have a single beaurocrate make a up/down vote it corrupts the integrity of the adminship. I'm all for oversight but this method would cause admins to play ball to much to accomodate everyone, or worse it would cause them to not take an action strictly to maintain their position rather then because it is the right thing to do. Smitty1337 (talk) 04:17, 23 February 2010 (UTC)
38. Oppose. Far too many flaws as pointed out by TenOfAllTrades (talk · contribs). — ξ^xplicit 04:38, 23 February 2010 (UTC)
39. Oppose. User:TenOfAllTrades has pointed out many flaws that need to be dealt with, including the "10 votes in the hole" problem and the short time limit.--TorriTorri^{(Talk to me!)} 04:46, 23 February 2010 (UTC)
40. Oppose. Would open a new arena for massive drama and would politicize adminship to an unacceptable degree. If there were multiple, recent instances in which ArbCom had failed to act when desysopping was clearly appropriate, I'd reconsider. But WP isn't a popularity contest, and this would be simply one more way to distract from building and maintaining the encyclopedia. Rivertorch (talk) 04:48, 23 February 2010 (UTC)
41. Oppose. This proposal is an invitation to mischeif and creates a disincentive for admins to take necessary actions that are not also popular. There is already sufficient procedure to rein in truly rogue admins. This process will snare some bold admins and turn others into capons. David in DC (talk) 04:53, 23 February 2010 (UTC)
42. If Matt Lewis is out then I'm definitely out, and I was never in in the first place. Ten has it pretty well nailed. Franamax (talk) 05:02, 23 February 2010 (UTC)
43. Oppose. I simply don't see where there are all of these cases where there has been refusal to remove admin privileges when adequate evidence has been provided. We can't risk admins becoming timid when difficult decisions have to be made and we should avoid yet more layers of rules and yet more places for people to argue when they should be writing an encyclopedia. SteveBaker (talk) 05:24, 23 February 2010 (UTC)
44. User:TenOfAllTrades and User:Matt Lewis echo many of the concerns I have had since this proposal was raised. Speaking as an editor, I feel that the proposal's problems outweigh its benefits, and would still prefer to see a subcommittee of arbcom serving to expedite Admin-abuse issues. Speaking as a bureaucrat, should this pass, I will accept the community's decision and do my best (as always) to implement the community's consensus in any CDA discussions. -- Avi (talk) 05:27, 23 February 2010 (UTC)
45. Per many of the above comments, there are simply too many potentials for abuse in this particular process as set forth now. I have no blanket opposition to such a process, but really: some of the concerns TenOfAllTrades lists above are dead simple--like the right of the admin to respond to the accusations--and the fact that they remain outstanding and unresolved demonstrates that this is not yet ready for adoption. Jclemens (talk) 05:45, 23 February 2010 (UTC)
46. Oppose Too much potential for gaming. Not going to touch other arguments, due to my Conflict of Interest. SirFozzie (talk) 05:53, 23 February 2010 (UTC)
47. Weak Oppose I think that the concept of community requested de-adminship is valid; however the details of this particular proposal need work. I didn't see anywhere in the proposal where the administrator can defend him/herself. Notanonymous0 (talk) 06:34, 23 February 2010 (UTC)
48. Oppose CDA would be too vulnerable to political games. Further, a pressing need for this policy has not been demonstrated as we already have systems in place to de-admin that can work faster than the proposal. AzureFury (talk | contribs) 06:35, 23 February 2010 (UTC)
49. Oppose Spartaz's point about manipulation is well-made. Opening the de-admin process to community vote would expose Wikipedia to a new kind of troll: people who vote in CDA polls to de-admin someone purely for their own amusement and attempts to cause as much havoc with the process as possible. It will be next to impossible to weed out such under-the-radar-flying troublemakers. 3.14 (talk) 06:49, 23 February 2010 (UTC)

    About that new kind of troll: Please note that it is actually quite easy to pull up the user-contributions of such a person and see this kind of single-purpose account pattern, and the proposal as written specifically instructs the closing Bureaucrat to discount !votes from such SPAs. --Tryptofish (talk) 19:44, 25 February 2010 (UTC)

50. Oppose, when an admin goes off the rails, there are many ways to get them to stop. Blocking or banning come to mind. Community disapprobation is also a powerful tool. Then there is arbcom, which I consider to be functional enough to handle a real problem admin. This proposal will only handle admins who rub people the wrong way but operate within the rules. We need more people like that, not less. Speciate (talk) 06:52, 23 February 2010 (UTC)
51. Oppose per what Ryan Postlethwaite, MrZ-man, and others have said. The proposal seems to have too much room in it so that the system can be gamed, more drama can be had (than is necessary), etc. Killiondude (talk) 07:18, 23 February 2010 (UTC)
52. Opppose. I can only see this as causing more problems and more drama than it seeks to prevent. Someguy1221 (talk) 08:04, 23 February 2010 (UTC)
53. Oppose, this proposal will guarantee that any unpopular but needed tasks will never get done. It also is extremely prone to provide agenda-driven grief and drama to last for at least a couple of buckets of popcorn per week. Titoxd^{(?!? - cool stuff)} 08:57, 23 February 2010 (UTC)
54. Oppose. This is why we have ArbCom. They are there to review the evidence dispasisonately, this process can be abused by grudge-bearers and will deter admins from taking necessary but unpopular actions. There has been no significant delay in ArbCom desysopping abusive admins in recent times. There is merit in suspension of tools during consideration of arbitration cases on abuse of tools, I think that is the only change we actually need here. The complexity of the proposal is an excellent indication that this is an issue fraught with massive difficulties, and in the heat of the moment we, as a community, are spectacularly bad at handling nuanced situations. I commend also Ten of All Trades' exceptionally thorough review, which points out numerous serious and inherent flaws in the proposed process. So, leave it to the arbitrators. Guy (Help!) 09:22, 23 February 2010 (UTC)
55. This just inflates the idea that adminship is a big deal. There need not be a bureaucratic process to remove what should be and always have been janitorial tools. WP:RFA and adminship in general should be reassessed such that the "power" and/or stigma should not be attached to a "Block" button, a "Delete" button, and a "Protect" button. Adminship should be easier to take away and give, like it is on nearly all of the other Wikimedia projects. As it stands, the arbitration committee and processes do a good enough job removing the tools when the community feels it is necessary as I am very well aware.—Ryūlóng (竜龙) 09:38, 23 February 2010 (UTC)
56. Oppose this particular method, per WP:DRAMA. It's possible that a reasonable CDA could be developed (although I can't imagine what it would be.) — Arthur Rubin (talk) 09:56, 23 February 2010 (UTC)
57. Oppose Arbcom appears to be handling this already --Magicus69 09:59, 23 February 2010 (UTC)
58. Oppose the problem with compulsory de-adminship processes is that many administrative actions, even if done perfectly, will make an administrator a lot of enemies. If these enemies decide to use the de-adminship process then the administrator will end up in a long, drawn-out fight to save their neck and with no guarantee that dispassionate members of the community will outnumber those with grudges. We already have people supporting this proposal "because admin X would be a good candidate for it". With ArbCom this problem does not arise, because if the people with grudges can't present solid evidence then the case will be declined quite quickly. The proposed process doesn't offer any way of countering this problem, and the removal percentages have been imported from RfA - which is a different process entirely. Hut 8.5 10:01, 23 February 2010 (UTC)
59. Oppose Bureaucrats not competent to close. Hipocrite (talk) 10:04, 23 February 2010 (UTC)
60. Oppose — In reading through all of the comments here, I'm reminded of a famous saying: "What is right is not always popular; what is popular is not always right". By placing the actions and decisions up to a popular vote through this process, elements of the community can and will seek to substitute its opinion for the judgement of an administrator. The admins were all elected or selected by the community to exercise their individual judgements. Many times a single admin will be called upon to make a single decision. That's why we as a community have them in place. The RfA process is designed to vet them for sound judgement in the first place. Yes, I acknowledge that good people don't accept nominations at RfA, and I acknowledge that the community, in good faith or otherwise, as individuals give the bit to people who turn out to be bad choices. I came here today thinking that I would be supporting the proposal, but I can't in good conscience let factions of aggrieved editors use CDA as a forum to seek retribution and retaliation against administrators that utilize the tools given to them, in good faith, for the benefit of the encyclpedia. Looking to the US Constitution for an example of guidance, members of the federal judiciary "shall hold their Offices during good Behavior" (US Cont. Art. III Sec. 1). This does not make them immune to being removed, rather they must be impeached by the House of Representatives and convicted by the Senate. The analog on Wikipedia already exists in RfCs referred to the Arbitration Committee. We already have the tools and the people in place to impartially judge administrator action, so this proposal is instruction creep and bureaucracy creep. Returning to the quote I used to open my comments, popular opinion may not provide the right solution in a situation. In all actuality, the right solution will likely ruffle feathers from time to time. Imzadi1979 (talk) 10:16, 23 February 2010 (UTC)
61. Oppose This seems to be a solution looking for a problem to solve, and would serve no purpose other than to make it easier for disruptive editors to harass admins. I agree with Hut 8.5's comments above - by the nature of the job us admins upset disruptive editors, some of whom bear grudges (which extend to a genuinely irrational level with surprising frequency), and there's no need to give these editors extra opportunities for disruption when ArbCom and the various appeals processes provide a high level of protection against irresponsible admins. Nick-D (talk) 10:19, 23 February 2010 (UTC)
62. Oppose It would be too vulnerable and would create a space for political games and possible abuse. ArbCom is sufficient. - Darwinek (talk) 12:13, 23 February 2010 (UTC)
63. Oppose - I appreciate the need for the community to be able to remove admins, but this process still smacks of knee-jerkism for all the work that was put into it. Permitted canvassing makes it to easy to game the process or turn it into a popularity contest (a clever user can coach people on what to say to keep their opinions from being discounted) and shunting the admin's defense to the talk page really is a big deal. Instead of canvassing I'd rather the nominating editor have to gather signatures the same way they do for an RfC, and once certified there should be a site-wide notice about the CDA, just like there was for this RfC. ArbCom has the ability to act swiftly in emergency situations, so we can take the time to work out a process that provides a bit more room for due process than this.--~TPW (trade passing words?) TPW is the editor formerly known as otherlleft 12:48, 23 February 2010 (UTC)
64. Oppose - I wouldn't be an admin (not that anyone would ask) for all the tea in China. Sometimes the get it wrong. Mostly they get it right. We don't need this. Fmph (talk) 13:11, 23 February 2010 (UTC)
65. Oppose - I trust the current ArbCom, and this is quite enough for me.--Fox1942 (talk) 13:42, 23 February 2010 (UTC)
66. Oppose per previous comments I've made regarding the development of this proposal (in particular the way less bureaucratic and otherwise more desirable alternatives were sidelined after the first Administrator Recall RFC) and its outcome. Rd232 ^talk 13:54, 23 February 2010 (UTC)
67. Oppose - Just don't like the what the community gives, the community can take away sort of thinking. The community attracted to this sort of procedure have the potential to turn it into a kangaroo court. Admins on the whole do a pretty good job and as volunteers they dont need a vehicle such as CDA being available to editors with axes to grind. The existing procedures (RfC escalating to ArbCom) are by far the best way to deal with admins perceived to be not up to scratch. --Bill Reid | (talk) 14:25, 23 February 2010 (UTC)
68. Oppose - The proposal introduces new levels of complexity to wikipedia's existing byzantine order. I'm also a fan of KISS which this violates. -Quartermaster (talk) 15:04, 23 February 2010 (UTC)

    Oppose There are perfectly good means of desysopping a problematic admin. This proposed process feels too vulnerable and easily abused to be an improvement on the current system. ALI ^nomnom 15:18, 23 February 2010 (UTC)

    Switching to support. I believe all the issues I've had have been fixed, and while I don't like the general idea of desysopping good admins, I figure that's no reason to oppose this policy for serious circumstances. ALI ^{nom nom} 13:32, 26 February 2010 (UTC)

69. I used to support a form of a community de-adminship, but the flaws that Ten of All Trades points out in the current proposal are too serious to ignore.  Sandstein  16:26, 23 February 2010 (UTC)
70. Oppose There is already too much drama in the many venues for Wikipedia processes, and I think this will just add to it, taking resources away from other, needed, areas. I was almost convinced by the 'review' after five CDAs, or one year, but it's the drama leading up to an official CDA that will be so time consuming. And we already have a remedy for this procedure. Sorry supporters, I oppose. DD2K (talk) 16:57, 23 February 2010 (UTC)
71. Oppose — It should be substantially more difficult, and more objective, dispassionate, and neutral, to remove an administrator than it is to create one. By creating an administrator we are, by definition, moving away from the pure-wiki ideal by entrusting them with additional powers to act in those situations where ordinary editors cannot be trusted not to abuse those powers. Administrators — and I am not one — need the freedom to act without fear of having to defend themselves except in those rare instances when they have, in fact, abused their trust. ArbCom works just fine for that. — TRANSPORTERMAN (TALK) 17:04, 23 February 2010 (UTC)
72. Process creep. Besides, we don't want any popularity contests. -- Y not? 17:41, 23 February 2010 (UTC)
73. Oppose - This measure will force admins to either avoid areas involving contentious decisions or spend half their time defending themselves against vengeful editors. Bms4880 (talk) 18:10, 23 February 2010 (UTC)
74. Oppose - CDA in theory is a very good idea. This proposal in reality is a half-baked mishmash of poorly thought-out ideas that actually wouldn't achieve its aims in most circumstances, and is extremely prone to abuse. If we really want admins to never make a contentious decision again, this is the way to go. Black Kite 18:50, 23 February 2010 (UTC)
75. Oppose - I don't see any evidence that the existing channels of RfC, noticeboards, emergency de-admining, and ArbCom are broken or insufficient. Of the very few WP admins I've encountered that I felt were unsuitable for the job, all but one are no longer administrators (and I'm not sure that the one can't be chalked up to a temporary bout of jackassery). Should an admin step out of line there are a dozen more who are available to intervene. I think this proposal addresses a perception rather than an actual problem, namely that admins have unchecked power and potential to abuse. In reality, there are plenty of checks and they are working. In this proposed process, I fear there aren't enough checks to keep it from being hijacked for abuse, as a vehicle to air grievances regarding editing disputes, or as a forum for people who have authority issues and want to use it to take perceived authority figures down a peg just for kicks. I'm sure you could find ten users who don't like any administrator, and if you can't, that just means that the admin is either new or isn't doing his or her job and is dodging potentially controversial problems. Gamaliel (talk) 19:14, 23 February 2010 (UTC)
76. Oppose - Agree with most of the opinions in this section, including: CDA being a good idea in theory but in writing a different story. As stated by someone above, the community grants Adminship to individuals and should (again in theory) have the ability to remove said Adminship but I, as well as others it seems feel this particular process of CDA might be too easily abused. These among other issues have forced to oppose. Jeffrey Mall (talk • contribs) - 19:17, 23 February 2010 (UTC)
77. Oppose. Moar drama plz. Recognizance (talk) 19:22, 23 February 2010 (UTC)

    Well said. And funny, too. David in DC (talk) 04:09, 24 February 2010 (UTC)

    No, actually, rather childish, much like the "ombox" stunt. --Tryptofish (talk) 19:25, 25 February 2010 (UTC)

78. Oppose lol, I like Recognizance's succinct statement. Unnecessary, will almost certainly lead to abuse. Dougweller (talk) 19:32, 23 February 2010 (UTC)
79. per SteveBaker. -Atmoz (talk) 19:42, 23 February 2010 (UTC)
80. Oppose. I am not inherently opposed to such a process, just to some of the details of this one. We should not enact a flawed process with the vague promise it will probably get fixed later. I agree that rogue administrators must not be allowed to go around using the tools to further their own interests, or to bully and abuse, but there appear to be other adequate means of stopping such behavior. Some of the provisions are thoughtful, such as requiring 10 editors to initiate the procedure, and requiring a supermajority to desysop, but I have real concerns about the vagueness of the canvassing provision. It would be all about "getting out the vote" and efforts to notify those likely to vote pro or con the de-adminning. It is vague as to how many editors the accusers may contact soliciting signatures, and it is vague as to how many editors the defendant may contact. This is quite unlike the RFA process, where I understood it was improper to contact others to go and participate, or even to place a notice on ones talk page that RFA was underway. Many parts of Wikipedia where editors !vote or where their arguments stack up pro and con are very thinly attended, and mention of a CDA on a project page, in a newsletter sent out to people interested in some particular thing, or even in forums outside Wikipedia could bring in enough votes to oust a good administrator (or contrariwise to keep a bad one). Fix the canvassing provision, and make sure there is an adequate way for the accused to defend himself, before trying again to create such a process. Would each CDA be listed in a box on the side of many commonly looked at pages, such as the "Centralized Discussions" box shown on the AFD log page, or at WP:AN? (Curiously, current RFAs are not listed there). Edison (talk) 19:49, 23 February 2010 (UTC)
81. Oppose Excessively bureaucratic and moving WP even further away from the anyone can edit ideal. While does an editor have to have 500 edits to nominate instead of 490? Just more elitism creeping in WP.Gerardw (talk) 19:58, 23 February 2010 (UTC)
82. Oppose - At first I liked the idea, but TenOfAllTrades' arguments regarding potential for compromise, single point of failure, and RfC/Arbcom alternative are very solid. Tryptofish just dismissed the compromise issue as "nonsense" and missed the point entirely about single point of failure (that a beaurocrat may be sure about their decision when they shouldn't be). --Explodicle (T/C) 20:55, 23 February 2010 (UTC)

    I'm certainly capable of missing things, but I did attempt to respond specifically and accurately. Some of the criticisms really are nonsense, in that they factually misrepresent what has happened or what the proposal actually says. About having a compromise short of de-sysoping, the proposal allows editors who favor an outcome short of de-sysoping to !vote against the CDA (since they do not support the idea of removing administrative rights), and comment exactly on what they would advocate instead. (In fact, I pushed for adding that to the proposal.) And if a Crat makes a wrong decision (something I honestly find unlikely), it will be very public, much as a badly closed RfA would be, except even more conspicuous. --Tryptofish (talk) 21:05, 23 February 2010 (UTC)

    How do you figure that beaurocratic failure is unlikely? These CDAs are going to be a huge mess of drama (albeit warranted) so it will be much harder to find consensus than with an RfA... and good luck proving them wrong even if it's transparent. Also, !votes aren't a sufficient answer to the problem of polarized-by-design Support and Oppose camps; minority opinions will seldom gain enough consensus for a beaurocratic response. --Explodicle (T/C) 17:40, 24 February 2010 (UTC)

83. Oppose RfC plus ArbCom, or ArbCom alone in emergencies, are just fine. I am not aware of a single case where this method failed. There is too much politics and drama already; people should focus on article writing rather than playing survivor. Crum375 (talk) 22:09, 23 February 2010 (UTC)

    To be fair, cases where admisn are generally ulpleasent or bitey to many people, make poor decisiosn with some consistancy, etc, but where no one instance is glaring or way out of line, are not well handled by the current system. DES ^(talk) 00:32, 25 February 2010 (UTC)

84. Oppose for the reasons so clearly stated by Ryan Postlethwaite and TenOfAllTrades. The current processes for removal of a rogue sysop have generally worked adequately in recent times, and the downside potential of this proposal outweighs any possible benefit.  JGHowes  ^talk 22:35, 23 February 2010 (UTC)
85. Oppose, for the same reason why elected judges are a bad idea. This process would force administrators to worry about the political ramifications of their actions, rather than concentrating on being an impartial arbiter of policy. The RfC/Arbcom alternatives are far better practice. –Grondemar 22:40, 23 February 2010 (UTC)

    That doesn't really make sense, as administrators are elected at RfA. Or are you also against that? --MalleusFatuorum 23:29, 23 February 2010 (UTC)

    My reference to "elected judges" wasn't in reference to RfA (which I have no problem with), just this proposal. Like how judges who face reelection sometimes make politically-popular yet legally-questionable rulings, administrators if this system passes will be tempted to avoid making difficult policy calls in order not to make enemies that could bring them before this process. For example, an administrator might be more reluctant to protect a page or make appropriate blocks in the middle of an edit war between two nationalistic factions, fearing that one or both of the factions will drag him into CDA. I don't think that's desirable. –Grondemar 05:09, 24 February 2010 (UTC)

    Your position makes no sense. You're apparently uncomfortable with judges being elected, but completely oblivious to the fact that administrators are also elected. Live in your own world, I prefer mine. --Malleus Fatuorum 05:30, 24 February 2010 (UTC)

    There is a difference between judges elected once, but never needing to face re-election, and those who are subject to periodic re-election and/or popular recall. The latter might well temper justice with political calculation more than the former. That is, i think, Grondemar's point. DES ^(talk) 00:32, 25 February 2010 (UTC)

86. Oppose per Ryan Postlethwaite, Christopher Parham, Crum375, Grondemar, et al.. While I like the idea, it's not needed and could be dangerously abused. The new ArbCom system needs to be tried first. RfC is also there. I don't want to have both eyes on a recall, but I'm open to the idea of recall. I make a lot of controversial blocks and deletions, and do not want that held against me. Bearian (talk) 22:52, 23 February 2010 (UTC)
87. Oppose In principal I would support a CDA proposal provided it was fair and I thought it might work as well as Arbcom, which for all its flaws is not known for reluctance to desysop admins. This proposal has some positive features, it has moved partway in the direction of giving crats greater discretion over remedies, but this needs more fleshing out and doesn't fit well with the current structure which is overly focussed on one remedy - desysopping. Now it's a racing certainty that those who file a CDA will do so because they consider that a desysopping is appropriate, but views in the community are liable to vary from filing a sockpuppetry case against the ten filers to community ban for the admin - with every conceivable shade of grey in between. I'm not convinced that the response to that should be to widen crat discretion, rather it should be to spell out that participants are being asked two very different questions. Is this admin at fault? and What should be done about it? Then let the crats work out the consensus. That could be as simple as only 55% consider that user:example merits a desysop, but a further 20% support admonition and a topic ban from Diesel trains, and 92% support a topic ban on the ten nominees from all steam train articles. But this proposal fails on several counts: Ten people are allowed to canvass on one side but only one on the other? The defendant and anyone choosing to defend them can't do so on the page but only on the talkpage? However those flaws could be easily remedied, rather more serious is the issue of gaming. Wikipedia Review already has way more influence on this site than I think is healthy, and they aren't the worst out there. I know this may sound paranoid, but we do need to be aware that there are sites out there that want to take us down, whether for the lulz or because our neutrality offends their world view; This proposal simply makes us and especially any admin willing to use the tools in contentious areas, way too vulnerable. I think this scheme could be less gameable if we required nominators to verify their identities with the office, but once we get to that stage, we seriously have to ask what is so wrong with Arbcom? ϢereSpielChequers 23:26, 23 February 2010 (UTC)

    If user:example dares to edit another article about either diesel OR steam trains, outright banning from the 'pedia would be appropriate, and assassination would not be beyond consideration! Edison (talk) 04:14, 24 February 2010 (UTC)

    Given my own recent experiences, I totally hear you about those lulz, but I'd like to clarify a few of the other things you said. The proposal does allow users who oppose de-sysoping to comment that they prefer, instead, an admonition or topic ban, etc., but I think it would put a difficult and unanticipated task before the Bureaucrats, if they have to decide amongst various possible resolutions (and who carries it out, if they don't?). About the canvassing points you raise, the ten people are only permitted to canvass enough to amass that first ten, whereas the administrator is essentially unlimited. And, although discussion here suggests that a section ought to be created on the CDA poll page for the administrator's defense, there is already an "oppose" section where extended comments are encouraged, and so it is untrue that the defense gets sent off to the talk page. --Tryptofish (talk) 23:41, 23 February 2010 (UTC)

    I hadn't spotted the bit about only permitted to canvass until they achieve the first ten, and agree that sounds a little more balanced than I thought. However it leaves us with a proposal that I consider nigh on unworkable. Stopping a canvas operation at a set point is a recipe for Dwamah and disputes as to whether it was done to excess, and allowing the admin whose judgement is in question to break the normal rules of canvassing is bound to end in tears. I appreciate that the admin can respond in the oppose section, but still think they need their own response section. As for the difficulty of achieving alternative resolutions in CDA, remember Arbcom already can do this - and what would be the point of this system if it didn't aspire to be as good as the current system? ϢereSpielChequers 18:58, 25 February 2010 (UTC)

88. Oppose. This seems to be a wholly flawed system. J Milburn (talk) 00:39, 24 February 2010 (UTC)
89. Oppose. Proposal places all administrators at risk as conflict is inherent in administrative actions. I would, however, support a "term limit" proposal for all administrators, perhaps two to three years. The former administrator would then have the option of returning to an active editor's status or opening a new RFA to provide the community an opportunity to evaluate the Administrator's accomplishments and limitations. WBardwin (talk) 00:53, 24 February 2010 (UTC)
90. While I support the intention, I oppose this specific proposal per the concerns raised above.radek (talk) 01:15, 24 February 2010 (UTC)
91. Oppose. The current system where the Arbcom can desysop is working fine. If it ain't broke, don't fix it. RFC/U and AN/I already provide opportunities for comment on questionable administrator actions. Ngchen (talk) 01:50, 24 February 2010 (UTC)

    It works fine until you get on the wrong side of an administrator. See how "fine" it works after that. --Malleus Fatuorum 01:55, 24 February 2010 (UTC)

92. Oppose. Per all the above. We have ArbCom. -FASTILY ^(TALK) 03:36, 24 February 2010 (UTC)
93. Oppose. TenOfAllTrades's discussion sums up why this should not be enacted. -- ArglebargleIV (talk) 03:56, 24 February 2010 (UTC)
94. I oppose this concept. DS (talk) 04:45, 24 February 2010 (UTC)
95. Oppose. While I support the concept in a general sense, I feel that this proposal is not the way to go about it for the reasons others have raised. Probably a better idea would be to have each admin have their status re-confirmed (or taken away) by a regularly-scheduled community process every few years. (Give an admin an an initial renewable term of 2 years, for instance.) Good Ol’factory ^(talk) 07:20, 24 February 2010 (UTC)
96. Daniel (talk) 09:55, 24 February 2010 (UTC)
97. Oppose If an admin abuses the tools there are ways of dealing with it. I see this CDA process as an unnecessary mess. Polargeo (talk) 10:52, 24 February 2010 (UTC)
98. Oppose. WP:CREEP, redundant with ArbCom.--M4gnum0n (talk) 12:23, 24 February 2010 (UTC)
99. I believe that some system of de-adminship would be good, but this is not it. There are flaws in this proposal, something which even the supporters accept. We can talk about formal reviews, "developing as we go" and easily making changes, but how much time and how many RFC's would be required to actually make a decision? Something of such importance and significance should be better developed before we adopt it, or we'll have lost a number of good admins while we are still perfecting the proposal. Most admins (including myself) stick to relatively uncontroversial areas, and we have very few who are willing to make contentious decisions. I don't think we need to discourage them by hanging this over their heads. Also, some of the support !votes seem to be based on a lack of trust in ArbCom, without even considering the actual proposal. A large part of the community are not exactly fans of ArbCom, but I don't really see why we can't trust them with de-sysoping somebody when required. The general argument seems to be that ArbCom will deal only with issues where the admin has violated policy, but not where he has lost the community's trust. Why would somebody lose the trust of the community unless what he's doing is wrong? I can't think of a situation where it would be appropriate to bring something to CDA when it would be rejected by ArbCom, and not even a hypothetical situation has been presented by the proponents as far as I know. ≈ Chamal ^talk ¤ 12:57, 24 February 2010 (UTC)
100. Oppose reluctantly. We do need an easier de-adminning process than we have at present, but one that largely relies on polling is not desirable since I'm afraid that that will end up promoting greater cliquishness, strategic and defensive administering, politicking, drama, further dearth of admins in POV and sock-infested areas, and leave bad-blood in its wake irrespective of whether an admin loses her bit or not. Any de-admining process needs to rely on rational discussion, and assessment of strength of evidence and arguments rather than raw numbers (compare from, FA promotion process, and Arbcom setup). Abecedare (talk) 13:27, 24 February 2010 (UTC)
101. Oppose As unfashionable as it may sound, I believe that any CDA proposal needs to offer a modicum of protection for admins from spurious claims. These processes are always going to be painful for the candidate - just as RfA is - and we need to ensure that there is a legitimate grievance or misuse of their position before the voting! kicks in and that the votes! are made on such a basis. This proposal overly favours the nominator and, as far as I can see, does little to offer a platform for the admin even to defend themselves. My other concern is, just as RfA attracts its crowd, a regular core of voters would emerge with their own standards and POVs - there would be precious little "community" about it. CDA would need to be primarily discursive in order to be effective at weeding out the bad admins. A straight up or down vote is wholly unacceptable, we need to know why people are voting the way they are - just as we do at RfA. Especially with CDA, there are going to be people upset by legitimate admin actions and admins need to be protected from that; people could oppose if an admin took the other side in a discussion and we would be none the wiser. As it stands, this proposal could enforce an unbalanced pseudo-RFA on any admin at any time on the whim of a core of agitators - I am not suggesting all claims would be such, but you could find 10 people to back any POV, especially in contentious areas. In order for it to work, CDA would need to offer a fair and level playing field, I do not think that this is it. Rje (talk) 14:40, 24 February 2010 (UTC)
102. Oppose Wiki.en has already an efficient and functional ArbCom which hadles these issues. A CDA could become a powerful weapon in the hands of trolls and their supporters. We don't need and we don't want ours administrators to be afraid of these people. I think that the seting up a process like that will certainly shy sysops away from dealing with sensitive problems. I agree with Rje and others who say CDA will always be harmful for the candidate even when the request is ill-formulated. Adminship is not only about popularity. Lechatjaune (talk) 16:10, 24 February 2010 (UTC)
103. Oppose As an editor, persuaded by some of Ten's arguments. As a Crat, I currently have no opinion. --Dweller (talk) 17:12, 24 February 2010 (UTC)
104. Oppose. I admire that the community has worked hard to come up with this. However, it's an unnecessary increase in bureaucracy. We already have processes in place that can achieve the same end: Arbcom and RfC, per TenOfAllTrades.

     I also worry about attempts to game CDA. -- Flyguy649 ^talk

105. Oppose I don't feel the assumed problem is a huge deal, although I acknowledge that it is there, but also that ArbCom has been dealing with it rather well. Regardless, I came here to support this, as a less-than-perfect alternative but an alternative nonetheless. Sometimes the bureaucracy of options is a good thing. However, less-than-perfect is not always a net positive, and TenOfAllTrades has utterly convinced me that this is the case here. I think that analysis could set a good framework for how an eventual process might look, but after reading all the above comments I must admit to now being more partial to the RfC->ArbCom route than I was previously. I'll also add that I don't think CDA would be prohibitive toward administrative actions. ~ Amory (u • t • c) 21:08, 24 February 2010 (UTC)
106. Oppose This proposal is a problem masquerading as a solution. The number of recall attempts on administrators open to recall has been very limited. The number of those that got little to no support has been quite high - indicating a significant proportion of attempts here would be wasteful. Assuming for the case of argument that this would open up the process to a total of 4 times as many admins as have been open for recall, it would likely result in only a couple admins deadminned a year. The Arbcomm is already doing that.... This process would deter administrators from working in troubled areas with longstanding disputes (nationalist, political, fringe science), many of which have editorial cabals. Only some of those cabals come to light, often years after the cabals behavior violates guidelines (for example see the history of disputes over Eastern Europe). I thus conclude that this process will make the Wikipedia editing environment worse. GRBerry 21:21, 24 February 2010 (UTC)

     I need to point out a flaw in the first part of your analysis. Open to recall is a voluntary system for administrators to join. By and large, those who do elect to join are excellent administrators, whereas problem administrators essentially never join. How many administrators de-sysoped by ArbCom were members of open to recall? The extrapolation is not valid. --Tryptofish (talk) 21:33, 24 February 2010 (UTC)

107. Oppose As detailed above, this proposal creates more problems than it attempts to solve. --Allen3 ^talk 22:07, 24 February 2010 (UTC)
108. Too much potential for abuse, for being used as a vendetta or another forum to shop. I don't see strong evidence that existing means for desysopping are insufficient, so this seems to be a solution without a problem to solve. rʨanaɢ ^talk/_contribs 22:30, 24 February 2010 (UTC)
109. Oppose - potential for too much drama. Connormah (talk | contribs) 23:05, 24 February 2010 (UTC)
110. Oppose - It has too much drama. December21st2012Freak ^{Talk to me} at 00:39, 25 February 2010 (UTC)
111. Oppose - good on paper until you realise Wikipedia is edited by humans. You can easily get enough users to certify, then possibly even to desysop. Sceptre ^(talk) 00:53, 25 February 2010 (UTC)
112. Oppose per all of the above. Samwb123^{T (R)-C-E} 01:10, 25 February 2010 (UTC)
113. Oppose If it ain't broke, don't fix it. We have a perfectly good system for desysop, no need to create a new one, which as stated above, could possibly be abused.  Ronhjones  ^(Talk) 01:21, 25 February 2010 (UTC)
114. Oppose. On the fence to begin with, but skimming through the "supports" (a good example being #37) solidifies my gut feeling that this would be used by the willfully ignorant and superstitious as a bludgeon against any admin who dares defy their various pet whitewashing attempts. These various fringe groups have a demonstrated record of intense tenacity (for evidence, take a cursory look at WP:RFARB, where fringe-warring is at the root of two of the three currently open cases, and one of the three recently closed cases), a level of tenacity which I wager far outpaces that of clueful members of the community. Hence, any proposal which boils down to "!votes" will have an automatic oppose from me for this reason (and, yes, I do recognize the slight grain of irony in that statement :-) ). Net time sink with no real point, ArbCom can handle (and has handled) the admins who are an actual drain on the project (rather than a drain on the energies / ego / self-love of fringe pushers). Badger Drink (talk) 01:31, 25 February 2010 (UTC)

     Thank you for your support :-) — Arthur Rubin (talk) 03:38, 26 February 2010 (UTC)

115. Oppose per various reasons above. I trust the Arbitration Committee on removing admins, and I think that this proposition is a dangerous turn from discussion and debate to a majority-rules atmosphere. I think the only way I would support this would be to see convincing examples where ARBCOM members have failed to handle an admin situation properly. Sorafune +1 01:58, 25 February 2010 (UTC)
116. Oppose per harej. This is way to one-way centered, and puts the microscope from the community on the administrator without necessarily looking at the causes. In my opinion, the Arbitration Committee can handle this just fine as of now, and has in the past. Forums like this, are also a very easy way to instigate forum shopping, and vendetta searching, and this very proposal could easily be gamed for those very two purposes. "If it ain't broke, don't fix it." — Coffee // have a cup // ark // 04:49, 25 February 2010 (UTC)
117. Oppose - there will only a consensus to remove an admin when it is so blindingly obvious that arbcom would do it anyway. This will cause drama and make no difference to the ease of removing under-performing admins.—Preceding unsigned comment added by Scott MacDonald (talk • contribs) 09:51, 25 February 2010
118. Oppose This moves us away from the examination of evidence as it is related to policy and community expectations and turns it into what will surely be a huge dramafest where the most vocal group wins. I have not yet seen any examples of what this new and extensive process with solve that our existing process does not. Chillum ^{(Need help? Ask me)} 14:57, 25 February 2010 (UTC)
119. Oppose Per TenOfAllTrades, and the many that can be summarised by "if it ain't broke". (At the same time, I am very close to !voting Neutral.) What I think lets this proposal down the most is that it is over-boiled, and as a result would be self-defeating. Rather than arriving out of current practice, it is a whole package presented as-is. The numbers (65%/80%) are arbitrary and the process was conceived in isolation. Before we introduce something like CDA, I would prefer that it was (a) seen to be necessary in practice and (b) based on what is known to work in practice. I'm unconvinced of both but I will focus my comments here solely on (b). We have ArbCom, we have RFC/U - we even have ANI. Under the CDA proposal, it would take a minimum of 33 or of 50 !voting editors to de-sysop an editor. I am unconvinced that so many editors would participate in a discussion at any of those venues except in the most exceptional of circumstances (in which case, I think the editor in question would be de-sysop'ed anyway). As such, I think that CDA would introduce a process that would be incapable of doing what it would be supposed to do. Let's start off working with the current processes - What are the problems with them? How can they be built upon? Foremost, I think there needs to a be an improvement in culture towards aminship - including among (some) editors with admin privileges. It is really is no big deal. -- RA (talk) 22:39, 25 February 2010 (UTC)

     About some of things you said about the process leading to this proposal, please read the FAQ linked to at the top of this page, which briefly recounts, and links to, what was actually a very extensive and open process leading to this proposal. --Tryptofish (talk) 23:11, 25 February 2010 (UTC)

     My experience with that very extensive and "open" process was being told that this page is for developing the proposal and that my opposition to the idea was not welcome, and that there would be time for that at the RFC. Not exactly a consensus driven proposal, more like something developed off to the side without regard to criticism now presented as a finished work for the community to examine. Chillum ^{(Need help? Ask me)} 00:10, 26 February 2010 (UTC)

     Chillum, at this point I can no longer remember the specific exchange to which you refer, nor can I do anything about what any other editor might have said to you. But I can say that quite a few of the users who oppose here came to that discussion and said things to the effect of this proposal is never going to be any good, so shut down any work on it now, and were told that they would be welcome to make constructive criticisms on how to improve it, but that it would be unhelpful simply to say that it was bad without suggesting improvements. Now, that said, I can see as this RfC goes along that there were probably cases, for example where it may have been pointed out that there should be a dedicated place on the "example" page for the administrator's response, where suggestions were made in passing during confrontational negative comments, and may have been quite literally overlooked in the heat of the discussion. I, for one, am still receptive to such suggestions now. --Tryptofish (talk) 00:20, 26 February 2010 (UTC)

     

     To all who worked on bringing Community De-Adminship to RFC, for your effort, good will, determination and teamwork, I award to you (all!) these barnstars. -- RA (talk) 00:35, 26 February 2010 (UTC)

     (edit conflict) I appreciate that. I followed the discussion (at a distance) since the start of December and participated once or twice. I would like to clarify that I think that a great deal of work has been put into the proposal by those involved and that I appreciate their efforts, good will, intelligence and determination. Whatever my opinion about the final proposal, I think all of those involved in crafting the proposal and bringing it to the community deserve a very hearty round of applause and so I would like to offer to you all this barnstar. -- RA (talk) 00:35, 26 February 2010 (UTC)

     You excel yourself Ranpahiati. Teamwork! It was 80-90% bickering over proposal pushing v consensus building, as you couldn't fail to notice. This RfC eventually happened suddenly, partly because of the threat of a 'counter RfC' from one single editor. There was a number of outstanding concerns, and with only a small consensus on the chosen content between a couple of editors left in the room. As someone who is highly suspicious of barnstars at the best of times, is there a way of rufusing this one? Matt Lewis (talk) 11:25, 26 February 2010 (UTC)

120. Oppose. Initially I was prepared to support, weakly. But the flaws noted by TenOfAllTrades are too worrying, and the replies to those concerns were not comforting. The protection offered by the process for muck-splattered Admins in the more unpleasant areas of Wikipedia are minimal. Sabine's Sunbird talk 02:57, 26 February 2010 (UTC)

     Additional thought - my concern with this proposal is not so much that a decent admin will get de-syoped. This seems unlikely. It is that it will provide another tool to harass a good admin by POV pushers and other assorted troublemakers. Even if the admin survives, it will be a stressful and unpleasant experience (like RFA), and it will consume time that could be used for something more constructive, like, I don't know, building an encyclopaedia. The barriers for entry are quite low in this process. The process suggested needs serious tweaking to improve protection for good faith admins from the wiki equivalent of frivolous lawsuits. Making barriers to entry harder for well known trouble makers (EDIT, actually re-reading proposal suggests that obvious trouble makers will be barred. I still worry that unobvious ones won't) and some kind of double jeopardy to prevent repeated harassment might be a start. Sabine's Sunbird talk 01:24, 1 March 2010 (UTC)

     Please see Wikipedia:Guide to Community de-adminship#Before nomination, the last paragraph, with respect to double jeopardy. You and I are discussing this at greater length at my user talk, but I'll point out that other editors have said here, correctly, that administrators get harassed like that every day anyway, but CDA can bring that sort of thing to a place where there is a procedure to deal with it, releasing the steam built up from valid complaints, and putting to rest the complaints that are not valid. --Tryptofish (talk) 17:59, 1 March 2010 (UTC)

121. Oppose per the above. Spencer^{T♦Nominate!} 03:25, 26 February 2010 (UTC)
122. Oppose: Not only no, but Hell No. We've already seen that the community can't be trusted when it comes to choosing admins - a straight vote overwhelmingly dominated by bullet voting, "optional" questions that are nothing but, ambushes and hazing. In my observation, many of the most vocal advocates of community de-admining fancy that an admin's stepped on their toes at one point or another. If people feel that there isn't enough desysopping going on, work to strengthen/broaden the existing means; we don't need red meat thrown in the water. Wikipedia isn't supposed to be about voting. Why is RfA, and this proposal, curiously exempt from that ideal?  RGTraynor  06:59, 26 February 2010 (UTC)
123. Oppose I would support a community-based deadminning system, but this is not such a system. This is a community-based drive-by shooting system, and is especially unfair to arbitration-enforcers and admins working in ethno- or sci-political areas (which normally have a "Me-versus-them" style to begin with). One of the things that needs to happen to fix it is that the admin needs to be able to respond to accusations right on the page, where it'll be most visible to onlookers who'd otherwise have only one side of the debate and decide based upon that. —Jeremy ^{(v^_^v Boribori!)} 10:36, 26 February 2010 (UTC)
124. Oppose Introduces a labor intensive, less efficient method of desysopping than currently exists. FloNight♥♥♥♥ 13:19, 26 February 2010 (UTC)
125. Oppose basically per TenOfAllTrades's analysis. To go a little further: this method remains too open to gaming by POV-pushers. There are many areas of the 'Kipedia in which there are gangs of POV-pushers who'll try to take down any admin who stands in their way, and yes, some of these gangs are large enough that even if some members end up disqualified from certifying one of these recall efforts, enough will remain. The mere fact that the vast majority of cries of admin abuse on ANI are frivolous complaints from those who just didn't get their way leaves me hesitant about any form of community-based recall, and this one does nothing to alleviate my concerns. No, I'm afraid I cannot support. Heimstern Läufer (talk) 13:53, 26 February 2010 (UTC)
126. Oppose Strongly. People will gang up on admins, as has been previously said. The Red Queen (talk) 19:58, 26 February 2010 (UTC)
127. Shifting the power from impartial arbiters towards those who are more likely to be prone to bring personal vendettas with a lynch-mob mentality is a recipe for unnecessary drama. Spellcast (talk) 20:48, 26 February 2010 (UTC)

     How can the arbiters be considered impartial when they are themselves administrators? --Malleus Fatuorum 23:57, 26 February 2010 (UTC)

     Why do you assume they won't be impartial just becase they have the same slightly expanded set of tools? Admins aren't the Borg, acting as one like a horde of army ants. Sabine's Sunbird talk 01:21, 27 February 2010 (UTC)

     I am assuming nothing, simply pointing out the obvious fact that adminstrators judging the behaviour of other administrators is not exactly a model designed to win friends and influence people. --Malleus Fatuorum 02:10, 27 February 2010 (UTC)

     By arbiters, I mean ArbCom. They're the most trustworthy group here to evaluate evidence in making a decision to deysop, unlike the general community, where users are more prone to demand deysops based on personal conflicts. Spellcast (talk) 02:15, 27 February 2010 (UTC)

     You're entitled to your opinion, of course, but until I see non-administrators on ArbCom I will ignore it as mere propaganda. --Malleus Fatuorum 02:24, 27 February 2010 (UTC)

128. Oppose Not because I think Arbcom is doing a fine job dealing with admins (much the opposite), rather because this version offers no meaningful protection for admins beset with vendettas. We often bemoan the shortage of admins willing to work in controversial areas. At the same time we propose to make it easier for those with a grudge to tie up admins with frivolous process. Cognitive dissonance, anyone? Short Brigade Harvester Boris (talk) 00:53, 27 February 2010 (UTC)

     It's clear that you don't understand the meaning of the term "cognitive dissonance", but you have reminded me of an article I've been meaning to invest some time in, so thanks for that. --Malleus Fatuorum 01:07, 27 February 2010 (UTC)

129. Oppose- I don't find it necessary and it could be dangerous.  franklin  04:36, 27 February 2010 (UTC)
130. Oppose- I'm not against the idea in principle, but the process suggested does seem to be somewhat biased against the admin. In particular, a clearer way for the accused to rebut evidence is, in my view, needed. I'm afraid they need to go away and think about this a bit more before I can Support it. Anaxial (talk) 07:45, 27 February 2010 (UTC)
131. Oppose I too support this in principle, but the process laid out here is too flawed. AniMate 08:18, 27 February 2010 (UTC)
132. Oppose. The problem that this proposal is intended to counter is much less than it was a few years ago. The proposal would encourage the gathering of mobs and I find the cure to be worse than the disease. Sam Blacketer (talk) 14:57, 27 February 2010 (UTC)
133. Strong oppose I do not feel it is appropriate for the non-administrator community to have the power to desysop administrators. It is better the way it is currently, with Jimmy Wales and the ArbCom being responsible for de-sysoping abusive administrators. Immunize (talk) 16:10, 27 February 2010 (UTC)
134. Oppose I cannot see how this proposal has gotten to a vote with all the controversy surrounding it. The current system may not be the best, but if we are replacing it with something that is even more debated, it is just asking for more trouble. --Willy No1lakersfan (Talk - Contribs) 16:30, 27 February 2010 (UTC)
135. Oppose Unnecessarily complicated. There are positives in this proposal, but the negatives outweigh them. Townlake (talk) 18:07, 27 February 2010 (UTC)
136. Oppose While I feel that there should be a mechanism for the community to revoke admin rights, and that this should not ultimately be in in the hands of arbcom, the current proposal is clearly bad. Any mechanism that proposes a vote immidiately after an on wiki conflict should not be implemented. Polls should be a mechanism to start a process, not a mechanism to reach a result. Taemyr (talk) 19:05, 27 February 2010 (UTC)

     I understand your larger point, but I want to correct what you said about "immediately after an on wiki conflict". The proposal as written would not allow a successful CDA immediately after a conflict between users and an administrator. There must have been evidence of going through the prior steps of dispute resolution, or the attempted nomination cannot be certified. --Tryptofish (talk) 19:15, 27 February 2010 (UTC)

     I mean immidiately after in the sense that the process will be based on a specific insidence and will be driven by parties who are partisans. That there is a slight delay since the witch hunters will need to go trough the motions to show that they have tried dispute resolution helps, but does not eliminate the underlying problem. Taemyr (talk) 00:41, 28 February 2010 (UTC)

137. Oppose - having ArbCom de-sysop abusive administrators works well enough. Unfortunately, I can only see such a process encouraging more conflict among editors. Arbitrarily0 ^(talk) 19:44, 27 February 2010 (UTC)
138. Oppose - the proposal is instinctively appealing as others have commented upon (if community can offer up, via RfA, people it wishes to trust with the mop, then likewise should be able to seek the return of the mop to the cupboard). However the process is flawed for the bias that a single large group of editors involved in a single topic can mount a larger challenge to an Admin who strays into their field of action (consider an admin protecting or acting on a topic about Israel objected by pro-Israel editors, or the equivalent for Palestinian / Macedonia / abortion / alternative-medicine topics). Conversely, an Admin making repeated mischief across several small scale disputes will fail to antagonise enough (10) editors for them to be allowed to nominate a CDA case. We have mechanisms in place for dispute resolution of AN/I for single admin action review: other Admins can reject a cohort of editors aggrieved by the Admin's action in their territory, or agree with them and seek to reverse an admin decision... and of course blocked users can request Template:Unblock by other admins. If we believe that most Admins are good, and as an overall group an asset to the project, then AN/I seems in cases of minor slipups a reasonable means to undo mistakes. But for more serious issues the community has very careful elections for ArbCom whom we hold up to make judgements and take action on our behalf when an issue is brought before them (we are all familiar with past actions being taken over misuse of admin tools in content disputes and admins being defrocked). The mechanism of this proposal also seems inflexible (if only for single purpose to vote on whether to de-admin, then issues of policy interpretation discussion, of the Admin's approach to explain & educate on policy and warn erring-editors, of their impartial consideration etc will not be included) - and RfC seems a well tested and familiar mechanism to explore and discuss wider views. Clearly in a RfC about administrator's tool-use, widening to discussing content issues would seem off-topic and unhelpful – perhaps some rephrasing at the description of WP:RfC might strengthen the weakness some obviously feel with that avenue ? As others mention above, the ArbCom is able to look at issues (rather than just vote numbers who all respond "per...") raised in large scale disputes and able to take evidence in private (check-user, etc). Does anyone know where a RfC concluded a strong consensus for de-admin, that ArbCom did not at least accept for consideration? and if the answer to that is yes, then what are we saying: "we don't trust the ArbCom", or we routinely want to be able to bring forth some wikilawyering group-impeachment against the ArbCom itself? This (CDA) is a flawed solution for a problem that already has one (RfC and then ArbCom). David Ruben ^Talk 00:28, 28 February 2010 (UTC)

     David, I'd like to correct one thing you said about inflexibility. The proposal as written actually does provide for outcomes short of de-sysoping. Users who favor milder sanctions can !vote against the CDA (which is logical if they oppose full de-sysoping), and comment on what they would like to see happen instead. If that ends up being the consensus, then the CDA will have provided a clear rationale for pursuing that. --Tryptofish (talk) 18:20, 28 February 2010 (UTC)

139. Oppose. I can see that a lot of hard work has gone into this proposal, and I do not question the good faith of the many editors who have devised it. However, there is no way that any process such as this can avoid becoming a tool capable of being abused by lynch-mobs, and even if those lynch-mobs are unsuccessful the possibility will have a chilling effect on admins willing to venture into zones of conflict. I agree with the oppose by Ryan Postlethwaite at the top of this section, and particularly his point that we already have a way of removing admins: RfC, then ArbCom. It's slow, but it has been used successfully against admins who have gone rouge. This proposal will cause more problems than it solves, and while arbcom is not perfect, it does ensure some separation of powers. --BrownHairedGirl (talk) • (contribs) 00:54, 28 February 2010 (UTC)

     How does ArbCom ensure "some separation of powers"? It is made up exclusively of administrators. --Malleus Fatuorum 01:01, 28 February 2010 (UTC)

     Simple: an RFC is how the community makes a preliminary assesses whether there is a case to be heard, and if the community thinks that there is, then the evidence in the case is brought to a separate small group for a decision. This is what happens with courts: anyone can bring a case, but judges make the decision .. except that these judges are elected.
     Arbitrators do not have to be admins, and some have not been; however the community repeatedly elects admins to arbcom. If you think that this is A Bad Thing™, then blame the community for repeatedly doing this Bad Thing™ ... but that rather undermines empower-the-community-because-arbcom-is-too-pro-admin argument, doesn't it? --BrownHairedGirl (talk) • (contribs) 03:00, 28 February 2010 (UTC)

     What I find so strange about that line of argument is that administrators only choose to trust this mythical "community" when it suits them, i.e., at RfA. After that it's who gives a monkeys about what the proles think, they can't be trusted. --Malleus Fatuorum 03:05, 28 February 2010 (UTC)

     You're still missing something. If (as you claim) admins get elected and then go power-mad, why do members of this same wicked grab-the-mop-then-machine-gun-the-crowd cabal keep on getting elected to arbcom by this downtrodden community? --BrownHairedGirl (talk) • (contribs) 03:49, 28 February 2010 (UTC)

     One of us is certainly missing something, that's quite evident. Are you claiming that administrators aren't elected? --Malleus Fatuorum 04:17, 28 February 2010 (UTC)

     No, of course I'm not. I thought that maybe you had a serious point to make, but if you just want to play games, I'll leave you to it. --BrownHairedGirl (talk) • (contribs) 04:22, 28 February 2010 (UTC)

     I'll leave playing games to you, you do it so well. Tell me, who was the last non-administrator of ArbCom? --Malleus Fatuorum 04:26, 28 February 2010 (UTC)

     This is a specious reasoning at best, and sophistry at worst. Of course our most trusted group(arbcom) is going to be selected out of the larger group of trusted people(admins). If someone does not have enough community trust to be an admin they will not get into arbcom, this is just basic logic. What exactly does your point intend to prove? Chillum ^{(Need help? Ask me)} 21:28, 28 February 2010 (UTC)

     I fall at the first hurdle, which is your assertion that administrators are "the largest group of trusted people". I wouldn't trust many of them even if I actually knew who they were and could see their hands at all times. If you, for instance, believe that you're one of wikipedia's "most trusted", then I would invite you to test your thesis by standing at RfA once again. --Malleus Fatuorum 21:48, 28 February 2010 (UTC)

     Yes, but you have trust issues. Chillum ^{(Need help? Ask me)} 15:24, 1 March 2010 (UTC)

     How come you're allowed to make personal remarks? --Malleus Fatuorum 16:39, 1 March 2010 (UTC)

140. The process could be easily abused, and I echo what BrownHairedGirl noted so well above. Furthermore, I find that ArbCom works well enough in emergency situations and I do not see the need for a more complicated process. Malinaccier (talk) 02:17, 28 February 2010 (UTC)

     This proposal is clearly not intended to deal with "emergency situations", but with ongoing low-level abuse. --Malleus Fatuorum 21:54, 28 February 2010 (UTC)

141. Oppose. I completely agree with BrownHairedGirl and TenOfAllTrades. The current system works fine for Admins that have gone crazy. But there are so many problems with CDA. Two of them are 1) the process goes straight into voting without any examination of evidence, 2) it can easily be abused be people ganging up on certain admins. Of course there are many other reason too. I strongly oppose. —Preceding unsigned comment added by Cityscape4 (talk • contribs) 06:04, 28 February 2010 (UTC)
142. Strongly Oppose this proposal. The idea of community control of adminship is attractively symmetric (thought the community doesn't select admins as things stand, so there's a logical problem with that impulse), and might even be reasonable. This proposal doesn't implement any such thing. First, it's a poll, explicitly so, and WP policy should not be made this way. Certainly not policy this important. There is no clear procedure nor standard for taking action even so, were it to pass by general acclaim, something which obviously will not be happening. Active admins doing good work are necessarily going to piss folks off. Some of them reasonable, some not so much. The proposed arrangement lends itself to misuse by the not so much crowd, of whom WP has at least its share. Active admins do thankless work for the benefit of the community and should not be set up for knee-capping by those annoyed enough to do some retaliatory drive-by shooting. Admins who have really gone off the rails may indeed need a snubber, but this proposal is not a reasonable candidate. Arbcom difficulties notwithstanding. Resort to "higher authority", even if not specifically authorized (eg, 'crats or stewards or even Jimbo), would seem to be a more sensible approach, however wanting from some idealistic perspective. ww (talk) 07:02, 28 February 2010 (UTC)
143. Oppose Its an invitation to more politics. Noodle snacks (talk) 10:00, 28 February 2010 (UTC)
144. Strongly Oppose. I wouldn't want the nominated user to have a list of people to target in response to a desysoping, especially since it would make a person more angry than losing an RFA. To prevent that, the system must be designed so that the reasons are provided anonymously, unlike our normal methods of consensus building. --Sbluen (talk) 11:40, 28 February 2010 (UTC)

     You bring up an interesting scenario. In fact, I would argue that having the nominations in public, rather than anonymously, actually provides a safeguard against bad nominations. A lot of the criticisms of this proposal have not really come to terms with this fact, making it sound like it would be too easy for ten malicious users to gang up on an administrator. --Tryptofish (talk) 18:14, 28 February 2010 (UTC)

     Sorry, but I don't think anyone should face losing their admin bit based on accusations and not be able to face the accuser. The idea of adding anonymity to the mix just turns an angry mob into an angry mob wearing hoods. Chillum ^{(Need help? Ask me)} 21:33, 28 February 2010 (UTC)

     I understand that people would still be blamed for it. But this idea avoids having the executioners being executed, as has happened historically. --Sbluen (talk) 09:32, 1 March 2010 (UTC)

     Just to be clear: I think requiring nominators to be identified is a good thing. --Tryptofish (talk) 17:51, 1 March 2010 (UTC)

145. Oppose Too much potential for abuse, could easily lead to people nominating CDAs if they dislike a admins decision against them. Frozenevolution (talk) 21:19, 28 February 2010 (UTC)
146. Oppose current proposal. I do think some important points are raised by this, and I generally think there should probabbly be something more than what we have now, but I don't think the current wording is the right thing for Wikipedia. • It's got the feel of a vote trying very hard to call itself not-a-vote. If voting is okay (and I think sometimes it is (although this may not be one of those times)), then we should call it a vote. If voting is not okay, this proposal should be rejected as currently worded. • It's also a bit too bureaucratic for my tastes. • I suspect something more along the lines of a third-party-nominated Wikipedia:Administrator review would be more approrpriate for the consensus process that embodies the wiki way. • I do think the people who have worked on this are to be commended. I really think they were working in good-faith and trying to come up with a solution they saw as right; it just isn't the right thing for Wikipedia. —DragonHawk (talk|hist) 01:59, 1 March 2010 (UTC)

     Even though we disagree (see discussion higher on this page), I thank you for the kind words. --Tryptofish (talk) 17:49, 1 March 2010 (UTC)

147. Oppose ArbCom does a good job in the extreme cases where deadminship is actually needed, and I feel like this process just exposes admins to pointless wikilawyering from troublesome users.QuattroBajeena (talk) 04:51, 1 March 2010 (UTC)

     This is an unlikely venue for a new user's 12th edit. --Malleus Fatuorum 15:58, 1 March 2010 (UTC)

     See the "Intentions" section above. The person who posted this RfC feels we shouldn't be discounting people's opinions here based on edit count. Or, do you want to have suffrage requirements for this vote? If so, what would you have those be? --Hammersoft (talk) 16:07, 1 March 2010 (UTC)

     Would you not agree that this is an unlikely venue for an editor with only 11 edits, and that (s)he seems strangely familiar with the work of ArbCom? Has QuattroBajeena voted before under a different username? --Malleus Fatuorum 16:24, 1 March 2010 (UTC)

     Ok, I ask again; where would you like to draw the line in the sand? What suffrage requirements would you like to impose on this vote? There are currently 23 voters in the vote who failed to have one or both of 500 edits or 90 days of service at time of voting. Is that the line in the sand you'd like to draw? By the way, this particular editor's 12 edits is not the lowest edit count of people who have voted here. --Hammersoft (talk) 16:27, 1 March 2010 (UTC)

     You seem determined to miss the point. I have made no comment about suffrage and have no opinion on a minumum number of edits. I am simply suspicious of a new editor who displays such a deep understanding of the workings of Arbcom and such a strong opinion on this proposal after only 11 edits and a few days of editing. You may be more trusting than I am, of course. --Malleus Fatuorum 16:46, 1 March 2010 (UTC)

     You see determined to insult me. How pleasant. How about I say you seem determined to fail to understand the question I am asking? You are apparently saying this editor should probably be ignored in their vote, but can't decide what the criteria should be for ignoring any other votes. Or, do you want to just ignore this vote and not worry about 4 other editors with less than 100 edits, or the 22 others that fail the suffrage requirements for nominating a CDA? --Hammersoft (talk) 17:18, 1 March 2010 (UTC)

     I am astonished at your accusation that I have insulted you, when you have quite clearly mounted your hobby horse and are riding away into the distance on it. I have already told you that I have no opinion on the suffrage issue, and it is only you that has the bee in their bonnet about ignoring votes; I have said no such thing. If you choose to reply again, please have the kindness to respond to what I actually said, not what you think I've said. To state it bluntly, I am suspicious that user QuattroBajeena is not what he or she appears to be, and may be a sock of someone who has already voted. I couldn't care less about the other 22 you allude to, and nor do I have any suffrage requirement, as you persistently and mistakenly keep trying to claim that I do. Argue about suffrage with someone who actually has a view on it, not with me who couldn't care less. --Malleus Fatuorum 17:43, 1 March 2010 (UTC)

     You had me up until comments about me riding a hobby horse, and I stopped there. If you can't understand the basic concepts of WP:NPA, we have nothing further to discuss. --Hammersoft (talk) 18:07, 1 March 2010 (UTC)

     The outcome of this RFC is hardly going to turn on a single possible sock vote (which was clearly Malleus' concern). How did this turn into a bad-tempered discussion about suffrage? In any case, whether someone has enough info for an WP:SPI or not, this discussion would be better left here. Rd232 ^talk 18:57, 1 March 2010 (UTC)

     For the record, I found this via the link at the top of Tryptofish's talk page, which I found via goons.--QuattroBajeena (talk) 05:14, 3 March 2010 (UTC)

     Really? Well, that's interesting, at least to me. --Tryptofish (talk) 16:22, 3 March 2010 (UTC)

148. Oppose per Ten. --BozMo talk 12:08, 1 March 2010 (UTC)
149. Oppose Noting that I respect those who worked on this and would have supported something like this 2 years ago but we now have a competent ArbCom and I think the concerns noted on this RfC outweigh the need for this process. Vyvyan Basterd (talk) 18:47, 1 March 2010 (UTC)
150. Oppose. Someone, I forget who, made a good point. The project is screwed without admins willing to make decisions most people won't like, and it's easy to worry that a community process could be used to settle grudges. Şłџğģő 03:17, 2 March 2010 (UTC)
151. Oppose. This seems like a way to upset the balance by introducing more Wikipolitics and to punish administrators for doing their job, which is sometimes unpopular. The current oversight system is adequate. RJC ^Talk_Contribs 03:54, 2 March 2010 (UTC)
152. I agree with TenOfAllTrades that we would do better to use the already-existing, simpler, and less bureaucratic means of revoking the admin bit from problem sysops based on a consensus reached by the community. Namely, the five-step process of: (1) engaging with the sysop; (2) inviting a new perspective from one or a few neutral, uninvolved editors; (3) initiating a discussion at an appropriate community noticeboard (such as the Administrators' noticeboard or AN/I); (4) initiating a user request for comment for broader community input, if necessary; and (5) filing a request with ArbCom to review the discussions and implement the community consensus via a motion.
     The Guide to CDA indicates already that a CDA request should be preceded by discussion with the sysop (#1), efforts at appropriate dispute resolution (#2, #3, and/or #4), and "substantial community discussion at a suitable venue" (#3 and/or #4). Could CDA be useful? Yes. Could CDA be abused? Yes. Is it worthwhile to establish an additional process, with its accompanying bureaucracy and problems (see 'Flaws in this process noted by TenOfAllTrades'), merely to bypass ArbCom? No, in my opinion.
     Despite my opposition to this proposal, I want to commend those who worked to develop it; the process was imperfect (as most are), but it was characterized over its course by commitment in good-faith to accuracy and transparency. -- Black Falcon ^(talk) 06:24, 2 March 2010 (UTC)
153. Oppose: A lot of the support for this proposal seems to be moral/ideological - "The community makes Admins, so the community should be able to break them". But with the limited resources we have available, I'm much more interested in practicality, and I am unconvinced that there is any practical need for this. In the time I've been following RfA discussions there has been an awful lot of "there's something wrong" hot air, but very little in the way of practical suggestions, so on those grounds I do commend the authors of this proposal for actually trying to do something. However, I just see it as addressing a problem that doesn't really exist, while the major problem is the shortage of admins. The suggestion that CDA will allow editors to be more bold in their RfA !votes is interesting, and it might well have that effect, but I think with the threat of a CDA nomination continuously over their heads, it is likely to make admins themselves less bold and less likely to deal with contentious issues, and will lead to fewer admin candidates in the first place. I just don't see Wikipedia being plagued by rogue admins, and I remain unconvinced that the current admin recall process is broken - the consensus/ArbCom process seems fine to me, and I've seen it work quite satisfactorily. -- Boing! said Zebedee 08:13, 2 March 2010 (UTC)
154. Oppose Will create a new drama scene, as per many editors above. Wikipedia is not a stage for drama. _LDS (talk) 16:12, 2 March 2010 (UTC)
155. Oppose I fail to see how this won't add more drama to wikipedia.--LexCorp (talk) 20:38, 2 March 2010 (UTC)
156. Oppose I don't trust the community enough for something such as this. And I dislike the concept of a poll to de-admin someone. –turian^{обсудить} 22:58, 2 March 2010 (UTC)
157. Oppose as a solution looking for a problem. ArbCom has shown itself to be fully capable of desysopping users whom it sees as unfit to hold the tools, and this will ultimately divert more editors from editing into dramafests and will dissuade administrators from taking unpopular but correct decisions while discharging their duties. Stifle (talk) 10:44, 4 March 2010 (UTC)
158. Oppose per the reasoning given by TenOfAllTrades. I would be more inclined to support if there was a way to combat the potential lynchmob mentality - perhaps we could say that if you support the CDA, and the community disagrees, then you get a 1 year block from editing on Wikipedia? At least that way, if you put an admin up for potential de-sysop, you are taking a risk if it goes wrong! Only kidding - but it seems to me that the process is stacked against the admin, with no comeback to the editors putting the admin through all this. -- PhantomSteve/talk|contribs\ 10:52, 4 March 2010 (UTC)
159. Oppose We should not make it any harder for admins to make already difficult decisions. This could be used as just another way to retaliate against someone whom you disagree with.Doc James (talk · contribs · email) 11:08, 4 March 2010 (UTC)
160. Oppose per TenOfAllTrades, but I also want to emphasise what Boing! said Zebedee has said above. I don't believe that there is a big problem that needs fixing, and I think the fix would create more problems than already exist. I don't see any evidence of a lot of Admins running amuck (or even a few) and I have seen quite a few Administrators lose their tools when they have created problems. We do have a shortage of active Admins and if this gets worse it will be to the detriment of Wikipedia. I think many Administrators tend to avoid difficult issues already (and I include myself at times) and we can't afford to create a mechanism that will make this worse. Dougweller (talk) 11:39, 4 March 2010 (UTC)
161. Oppose per RGTraynor and Ryan Postlethwaite. I think the current system has been working adequate. Admins that need to be removed have been getting removed. As RG said, the community has long been shown when choosing admins to not be very capable with the tendancy to band wagon jump, this will just be more of the same and will lead to people who shouldn't lose their mop being stripped. As the person above me has said, this will lead to admin avoiding difficult decisions even more so than they already do. -DJSasso (talk) 13:55, 4 March 2010 (UTC)
162. Oppose per Ryan Postlethwaite. The benefits that this proposal would bring do not outweigh the problems that it is likely to create. As an admin who works in controversial areas such as arbitration enforcement, I would be much less inclined to perform my community- and ARBCOM-sanctioned duties were this proposal to be passed. The lynch mob mentality that Ryan mentioned will happen and would simply be an extension of the tag-team mentality that is already prevalent around many content areas of Wikipedia. Don't think for a second that the counterargument to this point is that those who oppose the tag-team would take up an admin's defense; these groups are only interested in putting their POV first, not in putting the encyclopedia first. If given the opportunity, I can guarantee that two opposing sides of a POV dispute would band together to desysop an admin that has impeded both sides' POV pushing. I feel that if this proposal were to pass, that too many of our best administrators would be put in a position like this. The current procedures for desysoping functions well and well enough for what Wikipedia needs right now. Ioeth (talk contribs twinkle friendly) 14:40, 4 March 2010 (UTC)
163. Oppose mostly per TenOfAllTrades. I would have been one of the first opposers, but I wasnt aware this vote was going on until I saw a link on someone else's talk page. —Soap— 16:25, 4 March 2010 (UTC)
164. SUPREME OPPOSE. This is a horrible idea. Our administrators are tasked with making unpopular decisions all the time, this concept is flawed from the inside out. We should be putting our energy into demanding FLAGGED REVISIONS, not harassing our hard working admins. JBsupreme (talk) 16:38, 4 March 2010 (UTC)
165. Oppose. The imapct on admins with this in place is incalcuable. Is it productive to have admins having to think about a decision, no matter how correct, subjecting them to a process like this? How many wrong decisions or actions would this wind up causing? In the end one needs to ask, is this a solution in search of a problem? I'll acknowledge that some admins are bad but the current process seems to be able to deal with this. Vegaswikian (talk) 16:53, 4 March 2010 (UTC)
166. Oppose Existing processes, such as ArbCom, are perfectly effective tools for removing Sysop tools where needed. This is process creep and a needless drama magnet that will be less about effectively removing tools from sysops that are not using their tools correctly, and more about a venue to give editors a chance to gang up and bitch about admins they don't personally like. We already have enough places to do that at Wikipedia, and we don't need more. If an admin needs the tools removed, and other venues for correcting behavior of the admin have been exhausted, then there will also exist enough material for a valid arbcom case. --Jayron32 19:05, 4 March 2010 (UTC)
167. Oppose I do not necessarily oppose a procedure of this sort, but I do oppose this particular proposal. The requirements for start a poll are considerably too low, and the requirements for desysop are somewhat too high. Almost any active admin will have 10 people who do not like them, and most of us will have 10 people who do not like them sufficiently to initiate a desysop procedure. But I do not think there is any active admin who would not have support from only 20 percent of the community, and I am not sure that there would be any who would not have support from 1/3. This will result in a considerable increase in drama--there will be many nominations, and people arguing extensively about merits of individual actions and general character, and probably none of them will actually have a result of removing someone who ought to be removed. the net effect will there for an increase in the level of expressed hostility towards each other, and to no purpose. RfCs are already bad enough in this respect, which is why most people have learned to never bother commenting there. The one feature that rescues this is the requirement to review the process after 5 nominations, which will at least restrict the harm to only the first five individuals. What might I support? perhaps requiring 20 nominators, not 10, and not all of whom have interacted with the admin in the same specific issue or article, the period of discussion extended from 7 days to 14 , nobody except the nominee permitted to make more than two comments, and at least 100 (not 50) negative votes. I would also support changing and the desysop range to 50% for bureaucrat option, and 70 percent for automatic removal-- I cannot see how anyone with support of less than half the community should continue in a position of authority. What do I think would happen with the changes: we might have in the first year 3 or 4 certified cases, 1 or 2 or which would lead to removal. What would have happened if we didn't do it to these admins? Probably the same 1 or 2 would have been deadmined by arb com. then what would be the point--it will hardly save them much work. The point would be to allow the community to think it had a significant role. Is that enough reason to do this? DGG ( talk ) 19:37, 4 March 2010 (UTC)
168. Oppose. This proposal seems to be a solution in search of a problem, and tailor-made to be used in service of personal vendettas. The purpose of this system—removing admin privileges from admins who have abused them, and the threat of such action to prevent such abuses—is already a function of ArbCom. If ArbCom isn't being used effectively for that, then perhaps ArbCom needs some fixes, or at least clarification (I'd say the latter isn't even in question; trying to figure out how to officially handle disputes is like being lost in a maze). Establishing yet another, more hasty and unbalanced, parallel process is not the answer. It just makes the system even more complicated for no real gain. — Gwalla | Talk 21:01, 4 March 2010 (UTC)
169. Oppose. I'm not at all convinced that there's a need for this at this time. Ten's arguments laid out above are compelling, and for me much more persuasive than the rebuttals. I also have, as per Bearian above, huge worries that were this to be implemented, the number of admins willing and making difficult decisions would drop noticeably, with all the attendant issues that that would raise. GedUK  22:03, 4 March 2010 (UTC)
170. Oppose This process has too many unresolved issues for me to support its implimentation. I look to the bias in canvassing, the ability for the process to be gamed by Cabals and the complete lack of sanctions within the proposal for such actions. Once this process is implimented there is no turning back , there is no way undo the damage that will be done to people who have worked hard to make wikipedia what it is. Therefore we must ensure that when we do such damage we do it in good faith. To that this or any similar proposal must be robust, it must be able to stand up to scrutiny, it must be fair to all parties, it must not do damage we cant fix. During the formulation discussions canvassing has been repeatably scrutinised, its been descibe as being one of the insuperable flaws of this process[11] and CDA has proven to be fundamentally flawed re canvassing[12] these arent comments by people opposed to the process but people who have driven its development and a recently as the day this poll commenced. Gnangarra 01:53, 5 March 2010 (UTC)

Neutral

1. Personally, I've never had a problem with an administrator & so there's not much chance I'd nominate one for CDA. Having said that, if this CDA passes or fails? I won't complain eitherway. GoodDay (talk) 19:29, 22 February 2010 (UTC)
2. Neutral. While having this method to de-sysop ones who seem to be unfitting for this "rank" seems to be a good idea, I don't think someone who would actually be prove to be incompetent would be given sysop rights. SpecB (talk) 23:23, 22 February 2010 (UTC)

   A desysopping process would be more likely to have as its subject administrators who had lost the trust of the community in their fitness for office than administrators who were incompetent. As you say, those who can't do their job usually don't get elected. AGK 01:06, 23 February 2010 (UTC)

3. I like the idea, but the opposers bring up good points. There needs to be a better defined plan to limit abuse of a de-adminship system. Griffinofwales (talk) 00:13, 23 February 2010 (UTC)
4. Neutral as I am fine with whatever the community decides. ···日本穣^? · 投稿 · Talk to Nihonjoe 01:36, 23 February 2010 (UTC)
5. Neutral in principle I approve of the idea of the community of editors having a greater say in who holds the reigns of power, but there are just too many doubts in my mind, raised by TenofAllTrades. And admittedly, coming from a limited perspective, while I have disagreed with only a very small number of admin calls, I have never really seen something that would make me want to recall one. I might be more open to a different plan.LonelyBeacon (talk) 03:13, 23 February 2010 (UTC)
6. I generally feel that posting a "neutral" is pointless and I very rarely do it, but I find myself torn here. Although I wrote one of the early proposals and participated in the initial discussions, I did so only because it seemed to me this was something a lot of users wanted and it was important to get it right, not because I think we are overwhelmed with bad admins. I have since developed serious concerns that any such process can and will be abused no matter what safeguards we may try to place on it, and I for one do not wish to be party to a witch hunt. There are most certainly a few users who can't wait for this to be implemented because they hold a grudge against one or more specific admins, and the last thing we need is more drama. Also, it does seem that ArbCom has been willing to deal with more f these cases and to handle them in an expedient manner that reflects the communities will. On the other hand, it's hard to argue with the idea that the community grants adminship and should therefore be permitted to revoke it without being forced to appeal to ArbCom. So, I'm just not sure which way to swing on this. Beeblebrox (talk) 03:23, 23 February 2010 (UTC)
7. The admins who are not fit to be admins in the eyes of the community, would never respect any CDA proposal, whether the community supported it or not. These are the admins who have contempt for the community and think interpretation of policy has nothing to do with the community at all. The community is an irritant to them once they have their bit. It is just sad that some of them are so far up the food chain that even arbcom will not touch them either. It's rotten to the core. Still, 'no big deal', and all that BS. MickMacNee (talk) 11:05, 23 February 2010 (UTC)
8. While a community de-adminship process is needed, what is actually missing is a more formal process for enabling the community to administer any and all user sanctions, rather than just a de-adminship process. I developed a model Recall/De-adminship process a few years ago while the ArbCom RFC was active here: User:Amerique/Community_recall, but basically quit working on it after coming to the realization that what was actually needed was a viable system of "Community Arbitration," (or "ComArb!") something similar to ArbCom process with evidence, workshop and decision pages but allowing for participation of all editors in good standing in crafting all binding decisions, retaining the ArbCom as a court of appeals or for dealing with cases involving information that couldn't be discussed on wiki. The development of such a system would empower the community to take disciplinary matters into its own hands and thereby lighten ArbCom's caseload. (But I don't have the time to develop it myself so anyone interested would have to work on it if they want to see anything like this become a pragmatic possibility in the future.) Amerique^dialectics 11:32, 23 February 2010 (UTC)
9. opposers have legitimate points, i agree with the goal of the proposal, but find it insufficient. I would recomend upping both edits and period of heavy contributing. Lynch mobs are too easily created.Weaponbb7 (talk) 19:07, 23 February 2010 (UTC)
10. There is always the rule of unintended consequences with, on paper, good ideas. I would say that at least 95% of admins are doing a great job and would have no worries. However, there are always a few bad apples that need to be held accountable and "admin for life" can be more detrimental if those few are allowed to abuse their power. I think it would be better to limit terms of admins to 2 or 3 years and can reapply after the term is up. After this time, quite a few may not want to be admins anymore, many will be reconfirmed with ease, but at least those few troublesome ones will have a much harder time getting reconfirmed. I think that is the better solution. MrMurph101 (talk) 19:17, 23 February 2010 (UTC)

    About term limits, that's something that appeals to me too. However, I don't see how one could apply that retroactively to administrators already sitting. --Tryptofish (talk) 19:37, 23 February 2010 (UTC)

    If it were up to me, the current (active) admins would start their term when this rule would go in effect. Any inactive admin, say one that hasn't done anything for 6 months to a year or more would have to reapply if they're still interested. However, this could mean a deluge of RFA's when all these terms are up so perhaps those who have been admins for less than a year will get the full term and those that have been longer than a year get a half term. MrMurph101 (talk) 19:47, 23 February 2010 (UTC)

    In a term limit set up, I would suggest using each admin's "anniversary" of their "ascension" as the cut off date. Those who have served the 2 or 3 (or whatever) years would lose their mop on their next anniversary. Then thy could decide whether or not to reapply. This would stagger the administrative changes throughout the year. WBardwin (talk) 06:17, 24 February 2010 (UTC)

    Exactly, and well said. This simple method may be the next focus of those editors concerned with the current 'admin for life' status quo. If the many-month process of this current version of Cda proved anything, it seems to me the central lesson is the simpler, the better. Jusdafax 18:20, 24 February 2010 (UTC)

    You have, I hope, reviewed the math at WP:PEREN#Reconfirm_administrators and considered what doubling or tripling the number of candidates at RfA might do to the process? For example, I think we could reasonably expect that doubling the number of candidates would halve the time and effort that the community can put into reviewing any one of them -- unless increasing bureaucratic overhead (at the expense of writing the encyclopedia) is an acceptable, if unintentional, consequence in your mind. WhatamIdoing (talk) 06:39, 25 February 2010 (UTC)

    Looking at your link was of interest. I happen to strongly disagree with the premise and wording of that statement, and feel that should be reviewed. This is not the right place for a lengthy discussion, however, and as I suggest below, you may wish to comment further at Wikipedia talk:WikiProject Administrator on 'WikiProject Administrator/Term Limits: a proposal'. I should add that the section is just getting started. Jusdafax 06:55, 25 February 2010 (UTC)

11. My own personal opinion on this is in favor, however I also recognize that this has the potential to cause a large amount of drama...enough of a potential for me to !vote neutral. As it is, Category:Wikipedia administrators open to recall seems to be a less dramatic way. I will consider my opinion on this more in the coming days, and may end up leaning either way. Ks0stm ^(T•C•G) 19:52, 23 February 2010 (UTC)

    By way of shamelessly lobbying you, open to recall works very well for good, responsible administrators who choose to use it, but, as something that is completely voluntary, is of no effect at all for administrators who choose not to use it. --Tryptofish (talk) 19:20, 24 February 2010 (UTC)

12. The idea has merit, but lacks a decent structure. Aiken ♫ 21:05, 23 February 2010 (UTC)
13. I agree with the principle of a framework for CDA, and enabling WP to be self-policing. However, I do not see here a framework for fair governance of that objective. I see points on both sides of this issue; however I do not feel comfortable with a blind approval of the proposal, nor do I feel I have a viable alternative thought through with which to conscientiously oppose it. Alvincura (talk) 22:44, 23 February 2010 (UTC)
14. Both sides make good points. Doc Quintana (talk) 23:17, 23 February 2010 (UTC)
15. Neutral. I generally support the concept of CDA, however I don't believe this current proposal is nuanced enough to do the job. Considering TOAT's criticisms, there appears a few checks and balances that could be adopted to make this less prone to lynch-mobbing. For example. If the wider community (rather than the self-selected group that would likely bring a CDA and vote on it) really felt an admin required de-sysopping, then there should be no issues with separating nomination and voting. That is, the ten nominators should not be permitted a vote. Instead they should put their case and let the rest of the community decide. In summary, I think this is a decent place to start, but the process needs work. Rockpocket 02:54, 24 February 2010 (UTC)

    That's an interesting idea: that the ten nominators would not !vote. Hmm. --Tryptofish (talk) 19:17, 24 February 2010 (UTC)

    I would also add that I envisage that the admin him or herself wouldn't be permitted to !vote either (he or she would put their defense and let the community decide). The 10:1 ratio appears fair to me because it essentially removes any "lynch mob" influence from the !voting equation and, in most cases, would leave the decision up to the community independent of the individuals involved. As an admin, I would be happy for my tools to be reviewed under this scenario, because if I take out the 10 people that have a serious axe to grind yet still have a significant proportion of the community think I'm are unfit for the job, then I'm probably unfit for the job. Rockpocket 20:00, 24 February 2010 (UTC)

16. Neutral As an admin who is happy to participate in the recall process, I'm not sure a 'formal' recall process is needed. Although, I note of the near 900 admins on the system, a bare 200 make themselves 'open to recall'. The reason I've gone 'neutral' on this, is I foresee a process that may be open to abuse; and I'm not sure there's really a problem - there have been admins who have been de-sysoped for abuse - and if it needs to be done, it probably needs to be done quickly. Kbthompson (talk) 11:02, 24 February 2010 (UTC)
17. Neutral - I am not against an admin recall process per se, and I have historically given support to such a process. However, I cannot ignore or dismiss many of the concerns of the opposition to this particular proposal. I'm not really concerned that good admins will loose their adminship by this process as proposed; the minimum super-majority and 50 editors support required will probably be rarely achieved, and even that is subject to bureaucrat discretion. In comparison my recall process is 10 certified editors and a tie or simple majority in support of removal, with no further discretion. The concerns I have are more the possibility of lots of unnecessary requests, the problems of RfA re-appearing and possibly getting worse with CDA, and I don't think the issue of canvassing has been fully settled. I am becoming more open to wider reform of adminship on Wikipedia, such as introducing fixed terms. Camaron · Christopher · talk 19:15, 24 February 2010 (UTC)

    • You may be interested in the discussion at Wikipedia talk:WikiProject Administrator on 'WikiProject Administrator/Term Limits: a proposal'. Jusdafax 22:12, 24 February 2010 (UTC)

18. Neutral This proposal won't make de-sysopping any easier than the current option, but adds more trees to the jungle. Choyoołʼįįhí:Seb az86556 ^{> haneʼ} 23:12, 24 February 2010 (UTC)
19. Neutral As the proposed policy aggrandizes new powers to the Arbitration Committee clerks and Bureaucrats; I wear both of those hats and the groups are sufficiently small that it would appear improper were I to take a persuasive position. MBisanz ^talk 06:51, 25 February 2010 (UTC)

    I'm sorry, but I'm missing the part where it gives power to clerks. Mind linking me? Regards, NativeForeigner ^Talk/_Contribs 07:03, 26 February 2010 (UTC)

    Clerks are given authority to certify nominations and initiate polling. Christopher Parham (talk) 14:22, 26 February 2010 (UTC)

20. Neutral I can't really say that I oppose, because it does seem like a reasonable way of getting rid of th ebad ones, however it might end up being a Popularity Contest type-thing and might not turn out so well. So in the end, I just say I could care-a-less what happens. PlyPlay665 (talk) 04:45, 26 February 2010 (UTC)
21. Neutral I'm going to take a Churchillian stance on this issue. I believe that some admins may well abuse their privilages and use their position to bias articles, projects and other features of Wiki that are of personal interest. However, this may lead to perfectly capable and Wiki-abiding individuals (admins) being subject to removal from their position, in which thaty may well serve to help the site. Perhaps a further investigatiion is in order. I propose that installing a more efficinet security and scrunity system (perhaps a board of Wiki-security guards) would be effective in reducing abuses of privilages. Conducting a 1-month trial run is probably the best idea. My regards to the person who came up with the idea, of course. --Aubs 400 (talk) 15:27, 26 February 2010 (UTC)
22. Neutral ... I can't support per all the gigantic gaps in logic, reasoning and due process that TenOfAllTrades discussed at the top. On the other hand, I can't flat-out oppose since the core concept of the proposal is to follow community consensus and not leave things to ArbCom, and there was (though perhaps somewhat flawed) lengthy community discussion before this RfC began. I agree that there should be "some" (I use that loosely) way to reel in so-called rogue admins without ArbCom, yet I fervently disagree with the idea of a 'Crat closing these discussions as it effectively reduces the importance of a majority vote in ArbCom to a lone 'Crat or at best a "crat chat". As such, neutral but wanted to comment on this important matter. How about focusing on some absolutes that are entirely inappropriate that would likely lead to a CDA and define them as subject to a warning escalation system, ending in desysopping... such as use of tools to unblock oneself, perhaps? ♪ daTheisen(talk) 05:21, 27 February 2010 (UTC)
23. Neutral For many reasons. There should be a de-adminship process, and users might be able to nominate, However:
    • The number of users and edit count should be defined more thoroughly, 500 edits with anti-spam and 50 edits in article creations are not equal.
    • User involvements are necessary yet open to misuse. Also if de-adminship process not works, admin and his admin-friend group will hold grudge and will try to find a way to punish nominators somehow. Happened before and will sure happen in the future. We still have many blood feuds in wikipedia among many users.
    • Canvas is still a vague term and not a well defined policy itself which should be reviewed. There should be an easier way to auto-notice all involved or previously edited users in wikipedia without any user intervention for all kinds of processes about articles and people including AFD, TFD, RFA, other wiki-wide decisions etc.
    • We should also discuss all RFA process from start to end. Because after a while only privileged users who get along with previous admins becomes nominated and elected in RFAs. Being elected as adminship without any high-number actual content creation to wikipedia should be prohibited. Don't tell me it is, it is sure not by example case.
      • Also RFA process should result by number of mistakes a user had, instead number of edit count etc. Simply because many users-admins tend to delete complaints from their user talk instantly and noone bothers checking page history
    • There should be a permanent admin record and complaint section, where users can vote admins' record or add their negative experiences with them which admins themselves cannot delete and regularly gets reviewed by a team of selected admins.
    • We should review edit count policies, and strictly separate edit counts for AFD etc. discussions, SPAM related reverts, scripted edits with actual content creation or improvements. There are users with top edit counts who doesn't even create or edit content of even a ten percent of their edit counts.
    • There should be a higher council in wikipedia for wiki-wide cases, where users can state their opinions and inform all wiki-community about the ideas or solutions they provide. Currently wikipedia processes are no-different than real world government instutions. Kasaalan (talk) 14:45, 28 February 2010 (UTC)

    Thank you for this feedback. I'm especially intrigued by your suggestion about a "permanent record", sort of like a continuously-archived Wikipedia:Administrator review for every administrator. In my opinion, that's an idea that definitely merits further discussion. --Tryptofish (talk) 18:27, 28 February 2010 (UTC)

    That's another non-starter in this best of all possible wikiworlds. Block logs are maintained as permanent record of misdeeds of the plebians, but no similar record is maintained of the misdeeds of "the most trusted members of our community". They walk away unblemished; that's the way it's designed to work. We all know of many administrators who if they weren't in office would have block logs even longer than mine. --Malleus Fatuorum 22:02, 28 February 2010 (UTC)

    I would support a permanent page documenting past issues that were supported by evidence, not something that anyone with an ax to grind can put something on though. You hear all sorts of unsubstantiated spite being tossed around and that is of no real value. Chillum ^{(Need help? Ask me)} 15:33, 1 March 2010 (UTC)

    Yes, I agree with that. --Tryptofish (talk) 18:03, 1 March 2010 (UTC)

Comments

• If the number of regular contributers continue to stabilize, the admins group will gradually become the largest group in Wikipedia. They will become "the community". Sole Soul (talk) 03:08, 23 February 2010 (UTC)

  No, it won't. Most people aren't and never will be administrators. Gurch (talk) 08:23, 23 February 2010 (UTC)

I mean the people who participate in discussions, like the current unreferenced BLPs discussion and this discussion. Sole Soul (talk) 08:49, 23 February 2010 (UTC)

While our total number of admins is still growing, and the number of active admins recently revived slightly, we currently have 881 active admins, down from over a thousand at its peak. Without a major change at RFA I don't see admins being anything other than a dwindling minority in the foreseeable future. ϢereSpielChequers 14:15, 23 February 2010 (UTC)

The number might stabilize, but the people who make up the number won't. The number stabilizing just means that the number joining is equal to the number quitting. There will still be "new" regular contributors, and old ones will still retire. Mr.Z-man 14:58, 23 February 2010 (UTC)

You both have points. But generally, being an admin is directly proportional with factors like your frequency of editing, participation in discussions and the years of being a member; and inversely proportional to other factors like the number of blocks. These factors make admins like a pool of the fittests that is gradually increasing. Sole Soul (talk) 12:26, 24 February 2010 (UTC)

If the de-facto criteria for adminship were stable then I'd agree that the pool would gradually increase. But the expectations at RFA have been rising for some time now - once it was possible to pass with three months tenure and less than a thousand edits. Now it takes a rare candidate to succeed with less than four thousand edits and only six admins created their accounts less than a year ago, three of those are bots and one one of the others is a new account for a returning admin. ϢereSpielChequers 19:39, 25 February 2010 (UTC)

If it's really true that administrators are a "pool of the fittests [sic]", then God help wikipedia if that's the best it has to offer. --Malleus Fatuorum 19:46, 25 February 2010 (UTC)

“ It is no big deal. ” — Jimbo Wales

• There isn't anything wrong with that, so long as they are all competent... It'll just eliminate backlogs. NativeForeigner ^Talk/_Contribs 05:21, 23 February 2010 (UTC)
  • Addendum: I do in fact realize that his really doesn't hold true anymore. In an ideal world, it would, but in this time and place it does not. However, if as the above user indicated everyone would be admins, they would have gained community trust, been seen as competent, and it wouldn't be a problem. PLUS that will never happen (as far as I'm concerned) NativeForeigner ^Talk/_Contribs 04:07, 25 February 2010 (UTC)

You do realize that the earth isn't flat, right? This quote was from years ago when it was no big deal. This page has a few sentences on the subject. - Rjd0060 (talk) 12:25, 23 February 2010 (UTC)

Perhaps, what's needed is for administrators to face re-elections. GoodDay (talk) 15:45, 23 February 2010 (UTC)

I was thinking that as well, and I'm sure it was raised in the early discussions. I recently discovered that the Urban Dead wiki now has a full-fledged community appointment process that includes an automatic process of comment in order for them to keep the bit. They took the good from here and ran with it.--~TPW (trade passing words?) TPW is the editor formerly known as otherlleft 17:03, 23 February 2010 (UTC)

I have made the same comment elsewhere recently. Even the President of the United States only gets a four year term. If adminship is "no big deal", then why is it a "for life" appointment? Jusdafax 17:08, 23 February 2010 (UTC)

About regularly-scheduled re-elections, there was (big surprise!) a lot of discussion of that earlier. The problem (among others) is that, with the number of administrators, it would take multiple simultaneous re-elections ongoing for several years just to get through the administrators we have now. The numbers are impractical. By the way, please note this: a reconfirmation RfA would require the administrator to get approx. 70% support, whereas CDA would require only approx. 30% support. --Tryptofish (talk) 17:12, 23 February 2010 (UTC)

That's certainly what's needed, but equally certainly it's not going to happen any more than this proposal is going to go anywhere. Telling that over 50% of the opposers are administrators, with only 27% supporting don't you think? --Malleus Fatuorum 17:15, 23 February 2010 (UTC)

I've actually been pleased with how many administrators have worked on and supported this proposal. I'm not making any predictions about the outcome here, but I do remember that the notorious "motion to close" was passing by a wide margin about 24 hours after it opened, but as time went on, it was rejected two-to-one. --Tryptofish (talk) 17:21, 23 February 2010 (UTC)

I personally think the standard of adminship on Wikipedia is overall far too poor (unsustainably so in fact - something has to give eventually), but I don't find this statistic (as it stands) remarkable either way. If you study CDA it has clear downfalls - you either want to trial it, or you don't. Even when I supported CDA, I sat enough 'in the middle' to see that their were valid arguments both ways. Administrators are obviously less likely to want to trail something that could easily prejudice their very job: a few bad CDA's could make every admins life difficult, and the residuals (specifically from inter-admin disharmony) are too hard to prevent and manage. The Crats won't allow CDA anyway, as you know (and rightly so imo - such important things have simply got to be right). It is best to make changes to Wikpedia that no-one can so easily challenge - there are plenty of other routes towards change. Matt Lewis (talk) 19:19, 23 February 2010 (UTC)

Turkeys don't vote for Thanksgiving, that's perfectly clear and what will scupper this proposal. Personally I'd be happier with fixed terms. That way at least the poor admins (of which there are far too many, just not so egregiously bad that ArbCom would be prepared to take action against them) would at least not be around for ever. --Malleus Fatuorum 19:25, 23 February 2010 (UTC)

I favour fixed terms too (Wikpiedia has to lose this 'job for life' nonsense), and an Admin Review too. Maybe they could cross in some way. When we have a reasonable Admin structure for the first time in Wikipedia's history (Wikipedia needs to adapt as it grows if nothing else), then we could look at whether we need a singular Admin Recall or not. Likelyhood is that the current version of admin recall (rfc/u with arbs) would then actually suffice. Matt Lewis (talk) 19:53, 23 February 2010 (UTC)

Fixed terms are exceptable, but not term limits. Afterall, I can't visualize anybody serving as Administrator, as long as Robert Byrd has served (and continues to serve) as a US Senator. -- GoodDay (talk) 19:56, 23 February 2010 (UTC)

I concur that there should not be term limits but they should be fixed like I said above. MrMurph101 (talk) 20:40, 23 February 2010 (UTC)

I'm also in favor of creating terms (not term limits) for administrators. I haven't seen much traction on the idea, though. It seems a number of people seem to think complicating the proposal with enforced breaks or something similar will make it better. I disagree, as I think it only makes the idea more difficult to support for those who might otherwise consider it. All we need is a simple term (2 years sounds good), and a plan for transition.

It would be interesting if some admins would consider voluntary terms to begin with, much as we have the voluntary admin recall process. If some admins were to reject voluntary recall in favor of stepping down or resubmitting an RfA after a specified period of time, it might open editors up to the idea of admin terms in general. Sχeptomaniac^{χαιρετε} 18:56, 25 February 2010 (UTC)

I strongly support a fixed mandate for admins (say two years) with a minimum interval between successive mandates (say one year). Knowing that one will be a plain user at least 1/3 of the time would hopefully prevent an otherwise very human tendency of all bureuacrats, namely making rules that increase the power of bureaucrats. Then perhaps we would not need special procedures for de-adminship. Should this be a separate RfC? All the best, --Jorge Stolfi (talk) 13:28, 24 February 2010 (UTC)

Question: just to clarify, are the votes above in regards to the process described on Wikipedia:Guide to Community de-adminship? --SB_Johnny | ^talk 22:07, 23 February 2010 (UTC)

The poll above, yes. --Tryptofish (talk) 22:25, 23 February 2010 (UTC)

• Should polls and votes of this sort really be taken seriously? What's to prevent someone from voting multiple times under their 16 or 42 different sock puppets they've been using for years. It's naive to think that doesn't go on. And it only takes a few people. Vicericecake (talk) 08:41, 24 February 2010 (UTC)

See Wikipedia:Polling is not a substitute for discussion. Long story short: we don't make decisions by majority vote, we use polls to look for a consensus. CWC 09:02, 24 February 2010 (UTC)

• One way would be to randomly draw 200 (say) voters among the regular editors, urge them to vote, and count *only* their votes. One may define "regular editor" in any reasonable way (e.g. "anyone who did at least 50 edits in four out of the last six months"), as long as it does not unduly bias the sample towards admins. --Jorge Stolfi (talk) 13:28, 24 February 2010 (UTC)

• No position creates so many enemies as the ArbCom membership. Yet, two incumbent members (Kiril and Coren) had the largest votes in the last election. Sole Soul (talk) 12:51, 24 February 2010 (UTC)

• Comment Without making a comment about THIS proposal, in Wikipedia we should always work together. As we start making more legal type provisions to desyop, we must eventually have provisions to balance them, such as block or other provisions to those who falsely accuse the admin. In essence, if you sue and lose, you have to pay all of the legal expenses for both sides. This is not the case in the USA but is the case in several countries. Let's try to work together instead of wiki-suing each other. Perhaps, require discussion with the penalty of block if there is anything but civility? Suomi Finland 2009 (talk) 16:09, 24 February 2010 (UTC)

It's interesting to note that some of the voters using Support,Oppose and Neutral are saying exactly the same thing: "I support admin recall, but CDA is not the best method.", or "I support admin recall, but this CDA proposal isn't good enough". Admin might be more inclined to say it in Oppose (or Neutral) than say it in Support. Editors might be inclined to do it the other way. Rather than just tolling the votes, the main thing to extract from this RfC is whether people are saying they want to see changes or not. Matt Lewis (talk) 17:06, 24 February 2010 (UTC)

If I was an admin, I would say the same thing. It does not look good if you say it flat out. AGF makes us sometimes forget human nature and social theories. Sole Soul (talk) 19:01, 24 February 2010 (UTC)

Sounds like spinning to me. This proposal is going down in flames. And yet, we are starting to hear from those creeping from the wreckage, saying "well, it shows the community really wants change" or "a majority of non-admins supported" (not sure on that, it is fairly close right now). When this RFC closes, as it appears unsuccessfully, take some time off from it. Build an encylopedia. Get some perspective. Then, and only then, consider whether you can come up with a proposal which avoids the very real flaws. I myself might be more prone to support if there was a gatekeeper, some initial evaluation, rather than a rush to mob justice.--Wehwalt (talk) 17:12, 24 February 2010 (UTC)

Agreed. The correct way to see if people want changes or not is to ask that question. Reading the tea leaves from a different tea-cup (apologies for the messy metaphor!) only leads to failed proposals. --RegentsPark (talk) 17:19, 24 February 2010 (UTC)

What sounds like spinning? Reading the results? I don't support any version of CDA, but it's the end of the line for the status quo on WIkipedia as far as I'm conerned. Admin have got to the point where they routinely spout such unconsidered and rude nonsense that it's a serious danger to Wikipedia. Matt Lewis (talk) 17:35, 24 February 2010 (UTC)

That may be your considered opinion (which is not particularly important), and it may very well be a consensus opinion (which would be important). Either way, survey design is already a complicated art and drawing conclusions about things that have not been the focus of the survey is never meaningful. --RegentsPark (talk) 17:41, 24 February 2010 (UTC)

I'm afraid that you simply reinforce the case that Matt Lewis makes with your "your opinion isn't important" comment. I'd suggest that it's your opinion as an administrator that isn't important on this issue. --Malleus Fatuorum 17:46, 24 February 2010 (UTC)

Perhaps you misunderstood my point (or perhaps not). Matt said that Admin have got to the point where they routinely spout such unconsidered and rude nonsense that it's a serious danger to Wikipedia. My point is that he is entitled to his opinion (who isn't) but whether that is the general consensus or not needs to be ascertained, and this survey is not designed to do that. I'm not sure why you bring up my being an administrator because this is a fairly obvious element of survey design and is not an 'admin opinion' (whatever that might be). --RegentsPark (talk) 18:01, 24 February 2010 (UTC)

• Comment, I added a quick script to analyze the !votes [13]. Nakon 17:29, 24 February 2010 (UTC)

That's useful, thanks. That's me at no. 4 btw - my attempt at a paragraph has bamboozled the script! (needless to say I'm not an admin). I'll duplicate my signature. Matt Lewis (talk) 20:07, 24 February 2010 (UTC)

Thanks Nakon! I've taken the liberty of putting a link to your script at the top of this page, since it is of high importance. Best, Jusdafax 09:23, 25 February 2010 (UTC)

• Better check your script, there's at least one admin in support that wasn't marked, so there could be others. --SB_Johnny | ^talk 11:52, 25 February 2010 (UTC)

I believe I have ironed out most of the bugs in the script. Please let me know if I've missed something. Nakon 01:38, 26 February 2010 (UTC)

• • This is propaganda, premised on the view that admin opposes are a sort of "turkeys not voting for Christmas" thing. Opposes (from admin and non-admin) are generally based on reasoned arguments, notably a) that the process is dangerously flawed, b) that better alternatives for such a process exist, c) that the need for such a process is vastly exaggerated, since Arbcom mostly does well enough. To which I add (others seem less to have picked this point up) that the process of development of this CDA proposal, in sidelining the discussion and other options arising from the Administrator Recall RFC, is a perfect example of how a very small group of editors can set an agenda. Rd232 ^talk 14:46, 25 February 2010 (UTC)
    • Are you speaking as one of the turkeys? --Malleus Fatuorum 15:00, 25 February 2010 (UTC)
      • If you're asking if I'm an admin, yes. If you're asking what my alternative proposal was, see Wikipedia:WikiProject_Administrator/Admin_Recall#Option_11:_AdminRFC.2BRFA. incidentally, Nakon's script is pretty redundant to the existing Javascript that shows admin usernames in blue: just add importScript('User:Ais523/adminrights.js'); to your monobook.js. Rd232 ^talk 15:44, 25 February 2010 (UTC)

I doubt myself, Malleus and Tryptofish have anything in common (ie three people in this discussion alone). CDA was a railroaded to some degree - but most people sat and watched it happen. I no longer support any form of CDA, but I can still see that some admin are treating the support for this proposal with contempt. For voting for a Community de- Adminship?? C'mon. That kind of arrogant and OTT attitude will only help bring about the invitable. Change. Whatever that change turns out to be, Wikipedia is creaking (warping, frankly) for the need of it. Matt Lewis (talk) 21:15, 25 February 2010 (UTC)

After reviewing the pros, cons, and discussion of this proposal, I have organized my thoughts about a parallel, though unrelated, proposal that attempts to accomplish some of the same positive outcomes of this proposal while avoiding some of its pitfalls, via fixed terms for adminship. My ideas can be found at User:B Fizz/Admin for X years. Please feel free to copy its content to somewhere more appropriate, to discuss it here or on its corresponding talk page, or to print it out and burn it, as you see fit. In any event, I would appreciate your feedback. ...but what do you think? ~BFizz 22:48, 25 February 2010 (UTC)

Something needs to change, and to pacify those who are so worried about "drama" I'd be prepared to consider a fixed admin term of two years or so as an alternative to the inevitable battle that will result if this proposal is railroaded by the incumbent administrators. --Malleus Fatuorum 01:01, 26 February 2010 (UTC)

• Nakon's script shows the split between admins and non-admins, though the gap seems to be closing slightly -- non-admin support is up 3% to 54% from when I !voted, while admin support is up 5% to 24% in the same period. CRGreathouse (t | c) 03:06, 26 February 2010 (UTC)
• Well, obviously a lot of people don't care for this idea too much. I hardly think it's the best thing since the bread and the slicing and all of the wonderful sandwiches that followed, but I also think that it's basically okay, that we need something along these lines, and that this is as close as we've gotten, which does count for something. Apparently roughly 3 of 4 admins are opposing this proposal, and while there are certainly valid reasons to do so, I think the "ArbCom is doing fine with de-adminship" argument (which is quite prevalent) is problematic and gets right to the heart of the debate. There's a valid point to that argument, particularly since I happen to think that ArbCom is getting better about desysoping admins who lose "community" support. But for many editors (mainly non-admins) that just is not good enough. Right or wrong, this fact cannot be wished away—many good editors feel we need a communal mechanism to recall admins who are effing up. For admins to oppose this CDA idea and say "ArbCom is doing fine with that desysop thing" is frankly a bit tone deaf, irrespective of whether it is "right" or not. It's quite easy when one is an administrator to say, "no, what we've got now is okey dokey," because admins do not as a rule deal with the kind of situations that non-admins deal with, including: unjustified (or at least questionable) blocks, sometimes gratuitous warnings about behavior regardless of experience level, a general sense that their views might count for less than that of another editor with whom they disagree simply because said editor is an administrator, etc. It's difficult for administrators (and I speak from at least some experience here) to remember what it's like to not be an admin, and to not have what is undoubtedly a bit of a magic cloak (for lack of a better term) protecting you from "attacks" by other editors, but also from your own screwups. The inability—and in a way it's somewhat unavoidable and not entirely anyone's "fault"—of admins to identify directly and viscerally with the concerns of non-administrators with respect to the issue of lack of accountability for admins is a serious problem, and unfortunately it does generate ill-will and regularly exacerbates any number of individual incidents. I also think it's why a lot of the opposition to this proposal from admins, while generally well reasoned and in perfectly good faith, is inevitably going to sound like self-serving, I-don't-hear-your-concerns justification for the status quo to the many editors who find the status quo unacceptable. That's not necessarily fair, but it's also not at all an invalid way to feel about the discussion if you're a non-admin who has been concerned with this issue for months or even years.. --Bigtimepeace | talk | contribs 07:53, 26 February 2010 (UTC)

As an admin who voted no, I would say this: I would be minded to support if there was a clear showing of a problem this could cure, and if there was a gatekeeper, such as, say, a committee of crats, who would have to certify evidence of misconduct before a CDA vote could commence, and who would also oversee the process and its fairness (such as the timing of the vote, allowing the defense on the same page as the vote, etc.).--Wehwalt (talk) 13:19, 26 February 2010 (UTC)

Which is to somewhat miss the point I think, at least under the present system where all of the bureaucrats and all of the ArbCom members are administrators. --Malleus Fatuorum 15:29, 26 February 2010 (UTC)

I did a random unscientific sample of editors who voted "oppose" and found 100% of them were administrators. Isn't there some sort of conflict of interest. Who wouldn't want privileges for life. It is like asking a dictator whether he would like to hold free and fair democratic elections. Wapondaponda (talk) 15:24, 26 February 2010 (UTC)

As of now, 56 of the 125 opposes (~45%) are not from admins. Nakon 16:19, 26 February 2010 (UTC)

Maybe it's because administrators understand just how bad of an idea this is? Their experience in working in the filthy trenches where they volunteer their time almost certainly has an impact on their opinion of this proposal. Conflict of interest? I think not. Is an administrator stripped of any right to have any say on anything having to do with administratorship? Come on. --Hammersoft (talk) 16:23, 26 February 2010 (UTC)

Its good to know that some non-admins oppose the CDA. Still the majority of votes, 55% are from admins, which still says a lot. As for volunteering in the filthy trenches, aren't all wikipedians volunteers. Surely, aren't most of wikipedias 3 million articles written and edited by ordinary wikipedians. Don't ordinary wikipedians revert vandalism or report vandals. I think administrators should have a say, but we know by the very nature of this proposal, which in essence involves removing some power from administrators and giving it to the community, what the default opinion is — Preceding unsigned comment added by Muntuwandi (talk • contribs)

• The filthy trenches I was referring to are places where non-administrators can not tread; blocks, page protections, deletions, etc. This proposal doesn't remove any "power" from administrators. The notion that administrators have some special "power" is utterly false. They have and do work at the behest of the community, working within guidelines and policies. They can't just do whatever the hell they want. That kind of power does not exist for anyone, even Jimbo. Attempting to color this poll as some kind of class warfare is improper. --Hammersoft (talk) 18:04, 26 February 2010 (UTC)

The trouble with "random, unscientific polls" is that they are random and unscientific. They lead to dangerously incorrect conclusions. As it happens, I !voted "Oppose" and I'm not an admin - so for sure your conclusion is incorrect. Furthermore, you didn't do the opposite test - suppose that close to 100% of the "Support" votes were also admins - wouldn't that completely overturn your 'iffy' conclusions? Where is your control data? Perhaps you should look at some other polls - perhaps Admins vote to support the status quo in almost every similar poll? Bottom line: I don't know whether you're right or wrong - and neither do you - so either do a proper test (which on such a small sample really requires you count all of them) or forget this unsupported presumption of bias. SteveBaker (talk) 03:11, 27 February 2010 (UTC)

Why all the emotion? The scientific method depends on random sampling, but that's clearly not possible in this case. Those most likely to be aware of or to care about this discussion are administrators, those with most to lose. Those of us who aren't administrators know there's no way they're going to vote for Christmas. --Malleus Fatuorum 03:33, 27 February 2010 (UTC)

Nakon, there seems to be something wrong with your script, RayAYang registration date is on 1 Jan 1970? It can't be true. Arteyu ? _{Blame it on me !} 05:01, 27 February 2010 (UTC)

There was a bug in the API where users without a registration date would have the current time returned as their registration date. It appears this bug was fixed very recently to show 1970 (unix timestamp "0") as the registration date. I have updated the script and it is now pulling the correct registration date. Nakon 01:26, 28 February 2010 (UTC)

Malleus, correlation and causation are not the same thing. When you say administrators have the "most to lose" (like another seven days out of my life, which I'm not sure I would bother to do again), you are correct in a way. However, would you agree that it's also true that admins who are active in general have displayed general concern fot the working of the encyclopedia over an extended period of time? Would you agree that admins in general tend to have greater than average exposure to the various facets of what this sausage factory actually does? Are admins as a group equal to or greater in experience than the "average" or "median" editor, and relatively comparable to the sizable corps of long-tenured non-admins in terms of experience? 'Cause then what you're saying sounds to me an awful lot like a sample of experienced editors is concerned about the implications of a proposal that is not fully thought-out and could do harm if implemented. You conflate a wish to accept proper scrutiny with a desire to avoid any scrutiny, but that is just a supposition. Citation needed. Franamax (talk) 04:35, 28 February 2010 (UTC)

Rather a rambling and confused question, to which I can only answer no insofar as I understand it. --Malleus Fatuorum 05:09, 28 February 2010 (UTC)

• Proposal name - who came up with "Community de-adminship" - a truly horrible phrase, what happened to Plain English ? Our other proposals are phrased as polite considerations, i.e. "Request..." (RfA, RfC), so starting with "R - -" seems consistent. While this seeks the opposite of granting adminship, and the obvious opposite of "for" is "against" (rather than neologism of "de-"), "Request against adminship (RAA)" would imply objecting to an editor yet to be made an admin. Instead, this seeks the removal/revoking of admin flag already granted - so why not "RRA" ("Request removal adminship ", or "Request revoking adminship" if one prefers) ? David Ruben ^Talk 00:56, 28 February 2010 (UTC)

• You mean something like "Request for Administrator Desysop - WP:RFAD or WP:RFA/D" ? (talk→ BWilkins ←track) 13:23, 28 February 2010 (UTC)

Adminstrator Recall, would've been my choice. GoodDay (talk) 17:23, 28 February 2010 (UTC)

The answer is that User:Uncle G came up with the name, in the original draft of what became the proposal here. At Wikipedia:WikiProject Administrator/Admin Recall, that original version, under that name, was compared against numerous other proposals (as "option 4"), and the name has stuck since then. But there's no reason why we could not change it going forward. --Tryptofish (talk) 18:34, 28 February 2010 (UTC)

• This proposal has failed. Plain and simple. That should be the end of it. I am concerned that I am now reading a lot of rhetoric that casts the failed poll as Stage 1; and apparently Stage 2 is figuring out how, and how much, to fiddle around the edges of the proposal, in order to produce something that can be rationalised as having enough support and little enough opposition to jam it through anyhow. Hesperian 11:15, 4 March 2010 (UTC)

I don't think CDA will get enough votes to 'pass', but this RfC isn't about ignoring people just because they don't get to 70-odd percent in a poll. My forecast is that it on closure CDA will actually be ahead, but not enough to pass. This is a 'Request for comments', and a number of people have said similar things regarding future changes in the Support, Oppose and Neutral polls. We are here to listen to the comments, and as many people should have their say as possible.

Regarding 'fiddling' with the CDA proposal - unfortunately it was rather incomplete, so nobody can stop anyone from doing that. I suggest we wait for the 28 days to elapse and then decide whether it will be worth trying to improve CDA, or whether to look at other matters (and there is enough will for that without any doubt at all). My vote is to move on to 'fixed admin terms' and a workable 'review' system. For me, CDA is papering over the cracks, and mix of the paste will never be quite right. Matt Lewis (talk) 11:39, 4 March 2010 (UTC)

There is already a discussion on fixed admin terms at User:B Fizz/Admin for X years, but the subject is a perennial and I'm not convinced that the proposal there currently deals with enough of the past objections to have much chance of achieving consensus. As for continuing with this RFC, some of the opposes are because of particular concerns about this proposal, so if you can address those concerns without losing some of the support it would be reasonable to come back with a revised proposal. But my reading of it is that there isn't a potential compromise that would get consensus support. Alternatively why not try and test the existing RFC & arbcom processes? I see some real anger and resentment in the support section, but I wonder how much of that is from cases where Arbcom has decided not to desysop an admin or even declined to take the case, and how much from incidents where no-one has filed an RFC, or even where no-one has complained to the admin concerned. My impression is that it isn't Arbcom, but I'd be interested in some stats on this, perhaps someone could do a survey of the supporters to find out what stages of the process they have used, at what stage they think the current process fails, and at what stage they have seen it fail? ϢereSpielChequers 12:47, 4 March 2010 (UTC)

• You raise some interesting points. It should be readily possible to determine what supporters have been involved in RfCs, and then from there what RfCs were related to administrator behavior. --Hammersoft (talk) 14:46, 4 March 2010 (UTC)

• Yes, but I think it would take some sort of survey to determine how many had got no further than complaining to an admin on their talkpage, or even had a grievance against an admin but not gone as far as to complain. I think we also need to know how many support this because they have experience that leads them to be dissatisfied with the current desysopping process, and how many because in principle they prefer a direct community based system as opposed to an indirect system whereby the community elect Arbcom and Arbcom desysop when necessary. I have a theory that the oppose !voters are more likely to have voted in Arbcom elections than the support voters, and that of those who have voted both in this poll and the Arbcom elections the Opposers in this election are more likely to have seen candidates they support actually succeed in the arbcom elections (though I'm something of an exception as I think the candidates I supported last time didn't fare that well). But I don't think the community should simply ignore the fact that almost half the participants in this RFC wanted to completely replace our current desyopping process with a radically different one. Though I'm uncertain at present whether what we need to do is encourage those who want change to file RFCs against admins they disapprove of, try to reform the current desyopping process or !vote or stand in the next arbcom elections. ϢereSpielChequers 15:25, 4 March 2010 (UTC)

• Lots of interesting theories to consider there. These sorts of questions may possibly be answered by careful analysis of this RfC. I've started to do some of that work, as nobody else has apparently. It will take some time to distill the comments here into something more quantitative. I really, really, really wish that this RfC hadn't been set up as a poll on the overall concept, but more like a traditional RfC. It would have made this step so much easier. --Hammersoft (talk) 15:55, 4 March 2010 (UTC)

• As to projections that this will clear 50%; a week ago the percent of support (not including neutrals) was 45.9%, with 19 votes needed to get to 50/50. Right now, it's 46.9%, with 19 votes needed to get to 50/50. The approach to 50/50 is asymptotic. In the last 7 days, the support has held between 45% and 48%. So a week has gone by, and effectively nothing has changed. Meanwhile, participation in the poll has tapered off. Today's seen a slight bump up in voters, but not significant. We're 10 days into this poll. That pattern is set. The die is cast. This proposal as it stands has failed. --Hammersoft (talk) 14:46, 4 March 2010 (UTC)

A sizeable amount of people are Opposing (and voting Neutral for) this specific CDA proposal, but not CDA in general. I don't think any form of CDA can work, but certainly over 50% of the voters in this RfC (as it stands) would accept some form of CDA. With that in mind, anyone calling this RfC "dead in the water", or denying the right for the CDA proposal to adapt to criticisms of it, is ultimately just winding up the great many supporters of CDA. Is that a clever thing to do? No - it is clearly foolish. Impatience to remove these kind of motions (similar to starting them), and Wikipedia, really do not go well together. Matt Lewis (talk) 20:03, 4 March 2010 (UTC)

The vote (in terms of just counting names in Support and Oppose) is still pretty close, and will run for another 3 weeks. I don't want to see CDA happen (Id rather 'fixed terms' and some form of 'admin review') - but if this RfC suddenly reaches the wider community, things could change drastically within a single day. To ignore that is just illogical (if people prefer that to "foolish"). Really - who knows what will happen? Matt Lewis (talk) 20:40, 4 March 2010 (UTC)

• Suddenly reaches the wider community? What? There's already been more than 350 unique contributors to this page. It's been posted all over the project. Everybody who was involved in the draft RfC knows about this RfC. The idea there would be a sudden shift in support is statistically highly unlikely. Regardless, the characterization of the outcome of this poll, regardless of who is saying it, is not based on any evidence yet produced. --Hammersoft (talk) 20:51, 4 March 2010 (UTC)

Hesperian commented above that there is supposedly some plan to "jam it through anyhow." I want to say, loudly and clearly, that I have, and am aware of, no such plan. It dismays me to see some editors trying, day after day, to spin this proposal as something that has been snow-rejected by an overwhelming majority of the community. I conjecture that, with emotions unfortunately running high, some opponents are concerned that such a jam-it-through plan is underfoot, and are trying to prevent it by exaggerating the direness of the situation. So, please, hear me again: no one is going to try to claim that the community has approved a proposal that does not have consensus! But, to use Hammersoft's numbers just above, the 45-48% of the community who are supporting deserve to be heard too, and they are saying that the opponents' claim that the status quo is entirely satisfactory does not have consensus either. My best guess, looking ahead, is that there will be, after the month of this RfC ends, nothing enacted from here, but rather, further work by interested editors. I'd guess that some editors are going to work on some kind of fixed term/reconfirmation system, and I'll predict that it will fail. I'm pretty sure that I and some others will look very carefully at the comments, and not just the numbers, here, including those that are still to come, and come up with a significantly changed version of this proposal, which would have to be put, again, before the community from scratch in order to be adopted as policy. Between now and then, it might be more productive to stop trying to spin the !vote, stop trying to question the motives of those with whom one disagrees, stop trying to argue that this or that sub-group of the community should not "count", and, instead, think about how to constructively improve the status quo, if one is interested in doing so. --Tryptofish (talk) 17:53, 4 March 2010 (UTC)