This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 115 | ← | Archive 118 | Archive 119 | Archive 120 | Archive 121 | Archive 122 | → | Archive 125 |
It looks like there's a fair amount of support for lowering the standards of promotion at RFB. As it looks, the current situation now is that above 90% is a pass and the upper 80's is a discretionary zone. The proposal in front of us right now would make it 85% for a pass and 80-85% as a discretionary zone. I know the comments covered more ground than that but I don't think there's as much support for anything lower (I could be wrong and that's something to still work out). Personally I wouldn't have a problem with 85% pass but am doubtful about confirmations happening closer to 80%...but single percentage points start to get a little nit picky.
So with that said, I have a couple questions. Is there a reason for lowering the standards? Is there a problem it will solve...chronic backlogs, diversity of opinion etc? Or is it just a fairness issue? I see a lot of people saying they are too high but I don't see a lot of reasons why they think that. I'd like to see a little more thought put into what we're trying to do by lowering them, and what the consequences might be if we increase the number of bureaucrats significantly. And would we raise the number significantly if the standards are lowered (would more people be elected automatically just because the promotion standard is lowered?)
I happen to like the "no significant opposition" threshold but that's never been defined very closely. I also think a smaller group of bureaucrats helps us rather than hurts us...RFA is contentious enough without a wider range of bureaucratic opinion thrown in when discussing consensus, reconfirmation etc. Personally I see a danger in having bureaucrats out of touch with a significant minority of editors when it comes to RFA promotions, but others may not see it that way. But I do think that should be a consideration during this conversation. RxS ( talk) 21:10, 6 March 2008 (UTC)
Couldn't the standards of consensus just be the same? Naturally, when commenting on an RfB, you would be more cautious in supporting them than you would in an RfA. By removing the higher consensus standard, the overall standards will still be a great deal higher than adminship standards. Greeves ( talk • contribs) 03:08, 7 March 2008 (UTC)
Can we please not encourage the modern misunderstanding of what the word semantic actually means? Semantics is the meaning that words have. If what words mean is considered to be a minor diversion in a discussion, rather than at its heart, then every discussion is doomed to be a waste of time. -- Malleus Fatuorum ( talk) 00:09, 9 March 2008 (UTC)
Given that we've recently held a bureaucrat discussion on an RFB, I've created a short piece explaining the purpose and process of bureaucrat discussions. I'm intending it purely as a descriptive, not a prescriptive piece. Please have a look, and improve it as necessary. Warofdreams talk 02:02, 9 March 2008 (UTC)
FYI, the discussion and poll regarding the Proposal to make passing rate of RfB < 90% has been given its own page: Wikipedia:Requests for adminship/RfB bar. Please chime in. Kingturtle ( talk) 16:18, 9 March 2008 (UTC)
Anyway, just a thought. Or two. -- Dweller ( talk) 12:05, 10 March 2008 (UTC)
I prefer user:Tangotango/RfA Analysis/Report. Can't we tweak it? Kingturtle ( talk) 14:44, 10 March 2008 (UTC)
OK, before anyone goes all firefox on me, my IE is non-negotiable, meaning I can't change it even if I wanted to. The SQL box is blcoked from view by the table of contents. The good news, I can see the archive box now. But all I see on the SQL box is numbers, no names (left column hidden). Anybody else having the same problem? Keeper | 76 | Disclaimer 14:58, 10 March 2008 (UTC)
Just to make sure people are aware, SQL's gone on Wikibreak. Please read the message on his talk page carefully before attempting to leave him a message. Let's hope he gets back soon, with good news. -- Dweller ( talk) 15:36, 10 March 2008 (UTC)
Conservative as I am on these matters, I am increasingly of the opinion that RfB does in fact present a double hurdle in terms of tough standards and a more universal demonstration of confidence. From our experience of RfA, we know that one way of dispensing with the more arbitrary standards is to have RfAs where they turn up and get stamped upon (eg the 1FA lark that quickly died). So the obvious 'solution' is to fairly regularly have RfBs and try to work out as a community what we do and do not accept as good rationales. One way to perhaps lower the 'activation threshold' for victims at RfB (sorry, did I voice that?) might be, for the next N months, to set a week in advance in which RfB nominations are actively encouraged, with an assumption that this will mean basically no RfBs at other times.
This gives people time to prepare and consider, and also takes away the question of 'when' is a good time to plump for an RfB (and removes the 'now is a bad time because of <political event X>' rationale), and creates a comfort zone in which noone is taken by surprise when RfBs turn up, and noone can be accused of bandwagon jumping. To further reduce loading factors, candidates would be encouraged to prepare their nominations offline, to prevent gun-jumping, and any gun-jumpers would have their entries removed at opening time. There would be no nominators, either, as is customary for RfB and prevents canvassing in advance. There would be no immediate limit on the number of nominations, but if they became overwhelming, we could think of something.
We could make things even easier, by then saying that any (the majority, probably) of unsuccessful candidates are by assumption added to month (now + X)'s list, unless they explicitly withdraw. That takes away the "too soon" thing, for smallish X, and people will get accustomed to returning to RfB.
Once we've overcome some of the RfB interia and uncertainty surrounding support/oppose rationales, we can quietly abandon the RfB Week. Which by then, might have faded away anyway as people become more confident. I'd suggest week beginning Monday 7 April 2008 as the first RfB Week, being a month after the conclusion of this month's. Splash - tk 14:02, 11 March 2008 (UTC)
The RFA report currently obscures most of the archive box on my computer screen. I'm sure other people have the same problem. Someone who has expertise in wiki page design should move SQL's report left or down from where it is. Thanks. Shalom ( Hello • Peace) 08:09, 7 March 2008 (UTC)
Outdenting - If we reverse the order of the report and the archivebox, the archivebox becomes readible - but that's just more space between the page header and the actual discussion. There has to be a way to get the table of contents and the report to sit side-by-side - doesn't there? UltraExactZZ Claims ~ Evidence 16:26, 7 March 2008 (UTC)
I shifted the templates around, so now the Report, Shortcut Link, and Archivebox sit side-by-side-by-side - but it's still ugly as hell. I invite any formatting advice on the matter, as I'm at a loss - but, for now, everything is readable. UltraExactZZ Claims ~ Evidence 14:23, 10 March 2008 (UTC)
Strike that, I managed to track down some code that did the trick. The Bureaucrat's Noticeboard didn't have this problem, so I looked there to find out why. This is the result - the ToC and Report are side-by-side, which brings the discussion that much closer to the top of the page. If there are no objections, I think this will work for the time being, yes? UltraExactZZ Claims ~ Evidence 14:38, 10 March 2008 (UTC)
Obviously, (as his nominator) I welcome User:The Rambling Man's success in his RfB. Equally obvious, there are some users who have a long-standing belief that we don't (and didn't!) need more Bureaucrats. However, thinking about what happened regarding Riana's RfB, the following observations struck me:
While I'm inclined to agree with those who think that the 'Crat workload doesn't demand further RfBs, I for one would be far happier if there were more 'Crats available to debate when these contentious issues come along. Looking at Tangobot's RfA report yesterday, there were several that were 'in the zone', one of which already closed with a need for a consensus judgement. If that had needed a "'Crat Chat"(© Dweller, 2008) we could probably expect no more than 7 or 8 'Crats to be available, especially as the 'Crats rightly feel that they owe it to candidates and the community to come to their decisions quickly.
I'm not saying that more voices necessarily equals better decisions, but I am saying that they'd improve the chances of the best quality of debate and therefore the best decisions.
I'm also not saying that we should dilute the quality of the 'Crat body by appointing willy-nilly any old person.
All I'm saying is, I think we should continue to seek more Bureaucrats and not be satisfied with just TRM being elected.
What do you think? -- Dweller ( talk) 10:12, 11 March 2008 (UTC)
We need more trusted people in trusted positions. That's all I'll say on this :) ~ Riana ⁂ 10:55, 11 March 2008 (UTC)
Give me one good reason why having more would cause problems. Better to have redundancy than insufficiency. Viridae Talk 11:42, 11 March 2008 (UTC)
Personally, perhaps I am a glutton for punishment, but I do plan to resubmit myself to the guantlet in a couple of months, after I (hope) I have fulfilled the respondents' request for more visibility at RfA. But yes, the process is more difficult perhaps disproportional to the tool additions, which is one of the motives for the current discussion about the requirements, I believe. -- Avi ( talk) 12:36, 11 March 2008 (UTC)
The section title is a false dichotomy. We do not need more bureaucrats or admins. But having more of both would be nice. (Otoh, we do need more editors to help us fill gaps we currently have little coverage of). I think also that these kind of debates, apart from coming around more regularly than the phases of the moon, are too heavy on worn rhetoric, and light on ... light. Jimbo's "no big deal" quote especially is used as an appeal to authority as if that settles anything at all. Also, this strange notion of !promotion, to !coin a phrase. Editor → admin grants new powers, new decision making capability and the ability to control, delimit and, with skill, direct the behaviour of others. In most parts of the real world, you'd get a nice new job title for such a change as well as the pay rise. Yes, they are also 'just' cleanup tools, but the fact is that very often that is not the only manner in which they are used (viz. WP:ANI, WP:AN, etc). Then, admin → bureaucrat lands you with the task of deciding on the recommendations of a large collection of people on a key personal question of 'trust' and that coupled with an ability to not cause volcanic eruptions more than absolutely necessary - and knowing how to manage them in advance of them occurring. Again, you'd get another new job title in the 'real' world. In debates such as these, we'd do better to be honest with ourselves about the actuality on the ground, than to ritualistically genuflect at imaginary altars. Splash - tk 14:02, 11 March 2008 (UTC)
It has come to my attention that at least one sole purpose account has been used to anonymously contact users encouraging them to oppose Benjah-bmm27's RfA via the Special:Emailuser function. The full extent of this canvassing cannot be ascertained for sure, though investigations are ongoing. In order to dilute the effects of this attempt to manipulate consensus, I would ask as many users as possible to look at this RfA and evaluate the candidate. To this end, I have extended the RfA so that it has a full day to run. Please take the time to visit this page and provide a fresh perspective on the candidate. I would like to express my thanks to those users who approached me having received the emails in question. I strongly encourage anyone who is the recipient of attempts to influence them off-wiki to support or oppose a given RfA that give rise to suspicion that this part of an organised campaign of advocacy to bring this to a bureaucrat's attention. WjB scribe 23:55, 11 March 2008 (UTC)
Has anyone run a CU on the account that these emails came from, to try and work out who is behind this? dihydrogen monoxide ( H2O) 01:45, 12 March 2008 (UTC)
On my RfB, I got some opposes for saying that the discretionary range was more towards 70-75% than 75-80%. Fair enough, we've always said that it's been 75-80%. Do we actually follow what we say? I went through every single RfA of the past 18 months, and here's something I noticed:
Ten successful RfAs below 75%, some quite a bit lower. Only one failed above 75%. I found this very interesting. Does this mean that we don't actually follow our supposed discretionary range? Where is it exactly? 75-80, 70-80, 70-75, even somewhere else? I just find this very odd that we talk about the rnge being one thing, yet we don't seem to even follow it. If anything 75%'s a pretty rigid number in itself. Where is the discretionary range, and do we need to move our idea of where it is to where it seems to already be? Wizardman 23:18, 12 March 2008 (UTC)
My opinion as expressed as my RfB is that whilst RfAs are not votes, the community's expectations are generally that RfAs below 70% will not succeed and that those over 80% will. I'm not sure that trying to demonstrate whether or not a discretion exists by looking at whether or not it has been exercised is a great idea. Having a discretion means that there are cases where bureaucrats could close the request in a particular way - not that some must do so. The fact that a crat closed a request in one way does not mean that they did not consider closing it in a different manner. But if we are going to look at this statistically, it might be useful to also find out how many RfAs in those 18 months fell into the ranges you are looking at. WjB scribe 23:48, 12 March 2008 (UTC)
Advice to future RfBs; say 70%-80%, like Will did. That way you satisfy reality and the standards that some users like to cling on to (as was shown in Wiz' RfB). dihydrogen monoxide ( H2O) 00:08, 13 March 2008 (UTC)
Yes, you read right! I don't know if this one has been proposed before though. Confirmation of admins certainly has, and has failed. I'd like to propose we reconfirm bureaucrats. Why? We have determined they are supposed to be extremely trusted users (heck, there was an unofficial 90% expectation of support for what is a job that simply involves using a calculator, more even than an arbitrator). We lose arbitrators after 3 years, and they supposedly hold a similar level of trust. Additionally, we elected all but 3 of our current bcrats in 2006 or earlier. They may have been approved with community approval in 2004, but today is a lot different. Admins are admins, and their decisions are reversible. But bureaucrats' decisions are not, generally. This is why we should keep a pool of, say up to 8 bcrats that are fully trusted by the current community and are up to speed with the current norms. Every other position of such trust isn't permanent: as I've said, arbitrator, board, steward etc. Please also read my comments on this page for more of my thoughts on this. Thanks. Majorly ( talk) 15:25, 8 March 2008 (UTC)
As a technical question - it's not really for me to say whether I should be reconfirmed or not - what would be looked for at this reconfirmation? Would the bureaucrat need to demonstrate that the orginally required supermajority still supports them being a bureaucrat? Or would they need to show a level of consensus below this? Or would those opposing need to show a consensus that they should step down? WjB scribe 16:02, 8 March 2008 (UTC)
I believe Majorly's proposal regarding confirmation/recall was brought up on the Bureaucrat's noticeboard just recently if any of you wish to participate there. Wisdom89 ( T / C) 18:42, 8 March 2008 (UTC)
I'm opposed to bureaucrat recall. I like the fact that there's some old hands to prevent some of the modern craziness still around. O:-) -- Kim Bruning ( talk) 18:54, 8 March 2008 (UTC)
Wikipedia's governance is clearly arbitrary and has grown up rather like topsy, without any thought for the long-term. Nothing wrong with that, except that some questionable decisions made in a different environment do not look so very wise today. Take the way that every wikipedia post is filled, from administrator upwards (or should that be !upwards?). If you were thinking of employing a juggler, wouldn't you expect them to be able to juggle, instead of employing them on the basis that you could see no obvious physical impediments to their potential ability to juggle? -- Malleus Fatuorum ( talk) 00:18, 9 March 2008 (UTC)
'How about a term? Each bureaucrat is "elected" for a term of 18 months, after which the user must seek 're-election' Thright ( talk) 15:30, 13 March 2008 (UTC)thright
It's starting to get a little ridiculous now -- the average RFA open right now has 16 questions, with some having as many as 22 questions. Can we come up with some way to curtail these? My initial thought is to keep the standard questions on the RfA page, and any additional questions on the RfA's talk page, or something along those lines, but any other ideas are welcome. Ral315 ( talk) 02:46, 12 March 2008 (UTC)
How about going in the other direction?
Questions seem to be considered a good way of getting an idea about the candidate's suitability.
We could expand the questions into an admin exam. The question-askers could grade the answers to their questions (and others can discuss the appropriateness of the grading ;-) ), and we can then drop the poll at the end.
Does anyone dare try that? :-) -- Kim Bruning ( talk) 03:06, 12 March 2008 (UTC)
How about "how would you deal with situation X" kinds of questions? Make the situation really twisty:
"User X comes along and tells you that user Y is edit warring. You check history, user Y has only done 2 reverts today... also did 2 yesterday. When you check the talk page, both users are being fairly uncivil to each other. User X is also stating that user Y is violating V, NPOV, CIVIL. User :Y replies that she doesn't really know what X is talking about. How do you intend to proceed? What do you intend to achieve with your actions? How will X and Y react to your actions? How successful do you think your actions will be?"
There is no correct answer... but allows you to judge someone to some extent already. --
Kim Bruning (
talk) 04:45, 12 March 2008 (UTC) I always find myself trying to answer this question this kind of question (I enjoy puzzles ;-) ... so if someone wants to start a subthread where they post their answers here or on my talk page, I'll tell you how I figure you did... and possibly argue with others who think they can score you better ;-)
Personally, I find the optional questions asked by other users to be more helpful than the 3 basic ones. The initial 3 questions the candidate can prepare for, and only start the process when they have a good answer. With the extra questions, the candidate must think on the spot. Mr. Z-man 04:56, 12 March 2008 (UTC)
Heyy, you know what would be great? If people actually treated the optional questions as optional. Seriously, it's so annoying see people go 'Neutral until my question is answered'. Uh-uh. Take the time to judge a user for yourself, not wait for her/him to make up cookie-cutter answers to the same questions asked over and over again. ~ Riana ⁂ 06:36, 12 March 2008 (UTC)
Surely the basic difficulty is that the answers to all questions, incuding those posed by individual editors, are in almost all cases readily available and require from a candidate only the ability to read them. The standard questions have been answered, presumably adequately, by every successful candidate, and their RfAs are open to inspection; and even individual editors' questions appear to rcur through a significant number of applications. Furthermore, many answers are already enshrined in the basic Wikipedia framework; for example, the difference between a ban and a block, the meaning of WP:IAR, and so forth. I would concede without argument that any aspiring admin candidate who lacks the skill or initiative to go and search the answers may well thereby disqualify themselves, but I would much prefer it if decisions were made on success or failure with much greater emphasis being placed on admin related contributions rather than a sort of entrance examination. -- Anthony.bradbury "talk" 14:43, 12 March 2008 (UTC)
(<-)Making any of this formalized is a mistake in my opinion. Every wiki editor is different, every admin candidate is different, and wiki-culture itself goes through stages. Each candidate that requests the mop has different strengths and weaknesses—some more obvious than others. Each editor opining on the candidate has different objective and subjective requirements. For eample, if something is important to me, I look for it; if I find it, good, if not, I'll make a note—eithat as part of a S/O/N summary, or as a question. Different editors prefer to ask first, vote later. Candidates themselves respond differently to questions or comments. In a nutshell, we should really leave the system as it is. People who are truly interested in various questions should post them, and if the candidate is interested, they should answer. For example, KimB likes the logical-situational questions that have no direct answers. He should be able to ask each candidate that question. Each candidate should have the right to answer or refuse, and Kim (or anyone) can make their decision based on that. For another example, I don't like asking those kinds of questions as I think there are too many variables that can go into a real-wiki scenario that to extrapolate to real-wiki based on a version here is suspect, so I wouldn't hold a non-answer against the candidate. Furthermore, some users just handle "exam pressure" better than others. The beauty here is in the informality. If we start applying too rigid a structure, we risk losing the forest for the trees (procedure creep, anyone?). I would only caution that failure to answer any optional question should not be viewed ipso facto as a sign of unacceptability. There is much more than questions, usually, with which we can base our opinions. -- Avi ( talk) 21:02, 12 March 2008 (UTC)
In the meantime, perhaps we should consider adding some of the most common RfA questions to the RfA template? For example, the block/ban difference question mentioned above, one about IAR, one about BLP, and perhaps one about admin recall until it becomes less of a hotbed issue. Glass Cobra 01:17, 13 March 2008 (UTC)
I haven't seen colours on the report for ages. Why is the whole of Cobi's RFA highlighted fully in orange? Simply south ( talk) 01:48, 13 March 2008 (UTC)
(indent) I find it ironic that two of the recent failed/withdrawn RfBs were of the first to notice it and respond here. Cobi would be an admin by now. Justin (Gmail?) (u) 04:06, 13 March 2008 (UTC)
For the record, Cobi's RfA is now 3 hours overdue. dihydrogen monoxide ( H2O) 06:52, 13 March 2008 (UTC)
This is regarding Geni's RfA, in the box containing previous RfA's there is a link to User:Geniac's RfA. Is this the same user or a different one? If its the latter then it needs to be removed. Seddon69 ( talk)
I couldn't find instructions on how to handle a malformed RfA. I don't think "The nomination may be considered "malformed" and removed if you do not follow these instructions or transclude the request properly." is clear enough. Removed from where? The list of current RfAs? I found Wikipedia:Requests for adminship/aj00200 but I'm not sure what I was supposed to do with it. -- Geniac ( talk) 17:35, 17 March 2008 (UTC)
Who exactly is allowed to vote/comment in RfB's? -- Camaeron ( talk) 16:15, 17 March 2008 (UTC)
::Logged in users, socks of logged in users, socks of the socks, and of course, anyone who is in conflict with the nominee in an RfC. And anyone who doesn't like Kelly Martin. </sarcasm>.
Keeper |
76 |
Disclaimer 16:19, 17 March 2008 (UTC)
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 115 | ← | Archive 118 | Archive 119 | Archive 120 | Archive 121 | Archive 122 | → | Archive 125 |
It looks like there's a fair amount of support for lowering the standards of promotion at RFB. As it looks, the current situation now is that above 90% is a pass and the upper 80's is a discretionary zone. The proposal in front of us right now would make it 85% for a pass and 80-85% as a discretionary zone. I know the comments covered more ground than that but I don't think there's as much support for anything lower (I could be wrong and that's something to still work out). Personally I wouldn't have a problem with 85% pass but am doubtful about confirmations happening closer to 80%...but single percentage points start to get a little nit picky.
So with that said, I have a couple questions. Is there a reason for lowering the standards? Is there a problem it will solve...chronic backlogs, diversity of opinion etc? Or is it just a fairness issue? I see a lot of people saying they are too high but I don't see a lot of reasons why they think that. I'd like to see a little more thought put into what we're trying to do by lowering them, and what the consequences might be if we increase the number of bureaucrats significantly. And would we raise the number significantly if the standards are lowered (would more people be elected automatically just because the promotion standard is lowered?)
I happen to like the "no significant opposition" threshold but that's never been defined very closely. I also think a smaller group of bureaucrats helps us rather than hurts us...RFA is contentious enough without a wider range of bureaucratic opinion thrown in when discussing consensus, reconfirmation etc. Personally I see a danger in having bureaucrats out of touch with a significant minority of editors when it comes to RFA promotions, but others may not see it that way. But I do think that should be a consideration during this conversation. RxS ( talk) 21:10, 6 March 2008 (UTC)
Couldn't the standards of consensus just be the same? Naturally, when commenting on an RfB, you would be more cautious in supporting them than you would in an RfA. By removing the higher consensus standard, the overall standards will still be a great deal higher than adminship standards. Greeves ( talk • contribs) 03:08, 7 March 2008 (UTC)
Can we please not encourage the modern misunderstanding of what the word semantic actually means? Semantics is the meaning that words have. If what words mean is considered to be a minor diversion in a discussion, rather than at its heart, then every discussion is doomed to be a waste of time. -- Malleus Fatuorum ( talk) 00:09, 9 March 2008 (UTC)
Given that we've recently held a bureaucrat discussion on an RFB, I've created a short piece explaining the purpose and process of bureaucrat discussions. I'm intending it purely as a descriptive, not a prescriptive piece. Please have a look, and improve it as necessary. Warofdreams talk 02:02, 9 March 2008 (UTC)
FYI, the discussion and poll regarding the Proposal to make passing rate of RfB < 90% has been given its own page: Wikipedia:Requests for adminship/RfB bar. Please chime in. Kingturtle ( talk) 16:18, 9 March 2008 (UTC)
Anyway, just a thought. Or two. -- Dweller ( talk) 12:05, 10 March 2008 (UTC)
I prefer user:Tangotango/RfA Analysis/Report. Can't we tweak it? Kingturtle ( talk) 14:44, 10 March 2008 (UTC)
OK, before anyone goes all firefox on me, my IE is non-negotiable, meaning I can't change it even if I wanted to. The SQL box is blcoked from view by the table of contents. The good news, I can see the archive box now. But all I see on the SQL box is numbers, no names (left column hidden). Anybody else having the same problem? Keeper | 76 | Disclaimer 14:58, 10 March 2008 (UTC)
Just to make sure people are aware, SQL's gone on Wikibreak. Please read the message on his talk page carefully before attempting to leave him a message. Let's hope he gets back soon, with good news. -- Dweller ( talk) 15:36, 10 March 2008 (UTC)
Conservative as I am on these matters, I am increasingly of the opinion that RfB does in fact present a double hurdle in terms of tough standards and a more universal demonstration of confidence. From our experience of RfA, we know that one way of dispensing with the more arbitrary standards is to have RfAs where they turn up and get stamped upon (eg the 1FA lark that quickly died). So the obvious 'solution' is to fairly regularly have RfBs and try to work out as a community what we do and do not accept as good rationales. One way to perhaps lower the 'activation threshold' for victims at RfB (sorry, did I voice that?) might be, for the next N months, to set a week in advance in which RfB nominations are actively encouraged, with an assumption that this will mean basically no RfBs at other times.
This gives people time to prepare and consider, and also takes away the question of 'when' is a good time to plump for an RfB (and removes the 'now is a bad time because of <political event X>' rationale), and creates a comfort zone in which noone is taken by surprise when RfBs turn up, and noone can be accused of bandwagon jumping. To further reduce loading factors, candidates would be encouraged to prepare their nominations offline, to prevent gun-jumping, and any gun-jumpers would have their entries removed at opening time. There would be no nominators, either, as is customary for RfB and prevents canvassing in advance. There would be no immediate limit on the number of nominations, but if they became overwhelming, we could think of something.
We could make things even easier, by then saying that any (the majority, probably) of unsuccessful candidates are by assumption added to month (now + X)'s list, unless they explicitly withdraw. That takes away the "too soon" thing, for smallish X, and people will get accustomed to returning to RfB.
Once we've overcome some of the RfB interia and uncertainty surrounding support/oppose rationales, we can quietly abandon the RfB Week. Which by then, might have faded away anyway as people become more confident. I'd suggest week beginning Monday 7 April 2008 as the first RfB Week, being a month after the conclusion of this month's. Splash - tk 14:02, 11 March 2008 (UTC)
The RFA report currently obscures most of the archive box on my computer screen. I'm sure other people have the same problem. Someone who has expertise in wiki page design should move SQL's report left or down from where it is. Thanks. Shalom ( Hello • Peace) 08:09, 7 March 2008 (UTC)
Outdenting - If we reverse the order of the report and the archivebox, the archivebox becomes readible - but that's just more space between the page header and the actual discussion. There has to be a way to get the table of contents and the report to sit side-by-side - doesn't there? UltraExactZZ Claims ~ Evidence 16:26, 7 March 2008 (UTC)
I shifted the templates around, so now the Report, Shortcut Link, and Archivebox sit side-by-side-by-side - but it's still ugly as hell. I invite any formatting advice on the matter, as I'm at a loss - but, for now, everything is readable. UltraExactZZ Claims ~ Evidence 14:23, 10 March 2008 (UTC)
Strike that, I managed to track down some code that did the trick. The Bureaucrat's Noticeboard didn't have this problem, so I looked there to find out why. This is the result - the ToC and Report are side-by-side, which brings the discussion that much closer to the top of the page. If there are no objections, I think this will work for the time being, yes? UltraExactZZ Claims ~ Evidence 14:38, 10 March 2008 (UTC)
Obviously, (as his nominator) I welcome User:The Rambling Man's success in his RfB. Equally obvious, there are some users who have a long-standing belief that we don't (and didn't!) need more Bureaucrats. However, thinking about what happened regarding Riana's RfB, the following observations struck me:
While I'm inclined to agree with those who think that the 'Crat workload doesn't demand further RfBs, I for one would be far happier if there were more 'Crats available to debate when these contentious issues come along. Looking at Tangobot's RfA report yesterday, there were several that were 'in the zone', one of which already closed with a need for a consensus judgement. If that had needed a "'Crat Chat"(© Dweller, 2008) we could probably expect no more than 7 or 8 'Crats to be available, especially as the 'Crats rightly feel that they owe it to candidates and the community to come to their decisions quickly.
I'm not saying that more voices necessarily equals better decisions, but I am saying that they'd improve the chances of the best quality of debate and therefore the best decisions.
I'm also not saying that we should dilute the quality of the 'Crat body by appointing willy-nilly any old person.
All I'm saying is, I think we should continue to seek more Bureaucrats and not be satisfied with just TRM being elected.
What do you think? -- Dweller ( talk) 10:12, 11 March 2008 (UTC)
We need more trusted people in trusted positions. That's all I'll say on this :) ~ Riana ⁂ 10:55, 11 March 2008 (UTC)
Give me one good reason why having more would cause problems. Better to have redundancy than insufficiency. Viridae Talk 11:42, 11 March 2008 (UTC)
Personally, perhaps I am a glutton for punishment, but I do plan to resubmit myself to the guantlet in a couple of months, after I (hope) I have fulfilled the respondents' request for more visibility at RfA. But yes, the process is more difficult perhaps disproportional to the tool additions, which is one of the motives for the current discussion about the requirements, I believe. -- Avi ( talk) 12:36, 11 March 2008 (UTC)
The section title is a false dichotomy. We do not need more bureaucrats or admins. But having more of both would be nice. (Otoh, we do need more editors to help us fill gaps we currently have little coverage of). I think also that these kind of debates, apart from coming around more regularly than the phases of the moon, are too heavy on worn rhetoric, and light on ... light. Jimbo's "no big deal" quote especially is used as an appeal to authority as if that settles anything at all. Also, this strange notion of !promotion, to !coin a phrase. Editor → admin grants new powers, new decision making capability and the ability to control, delimit and, with skill, direct the behaviour of others. In most parts of the real world, you'd get a nice new job title for such a change as well as the pay rise. Yes, they are also 'just' cleanup tools, but the fact is that very often that is not the only manner in which they are used (viz. WP:ANI, WP:AN, etc). Then, admin → bureaucrat lands you with the task of deciding on the recommendations of a large collection of people on a key personal question of 'trust' and that coupled with an ability to not cause volcanic eruptions more than absolutely necessary - and knowing how to manage them in advance of them occurring. Again, you'd get another new job title in the 'real' world. In debates such as these, we'd do better to be honest with ourselves about the actuality on the ground, than to ritualistically genuflect at imaginary altars. Splash - tk 14:02, 11 March 2008 (UTC)
It has come to my attention that at least one sole purpose account has been used to anonymously contact users encouraging them to oppose Benjah-bmm27's RfA via the Special:Emailuser function. The full extent of this canvassing cannot be ascertained for sure, though investigations are ongoing. In order to dilute the effects of this attempt to manipulate consensus, I would ask as many users as possible to look at this RfA and evaluate the candidate. To this end, I have extended the RfA so that it has a full day to run. Please take the time to visit this page and provide a fresh perspective on the candidate. I would like to express my thanks to those users who approached me having received the emails in question. I strongly encourage anyone who is the recipient of attempts to influence them off-wiki to support or oppose a given RfA that give rise to suspicion that this part of an organised campaign of advocacy to bring this to a bureaucrat's attention. WjB scribe 23:55, 11 March 2008 (UTC)
Has anyone run a CU on the account that these emails came from, to try and work out who is behind this? dihydrogen monoxide ( H2O) 01:45, 12 March 2008 (UTC)
On my RfB, I got some opposes for saying that the discretionary range was more towards 70-75% than 75-80%. Fair enough, we've always said that it's been 75-80%. Do we actually follow what we say? I went through every single RfA of the past 18 months, and here's something I noticed:
Ten successful RfAs below 75%, some quite a bit lower. Only one failed above 75%. I found this very interesting. Does this mean that we don't actually follow our supposed discretionary range? Where is it exactly? 75-80, 70-80, 70-75, even somewhere else? I just find this very odd that we talk about the rnge being one thing, yet we don't seem to even follow it. If anything 75%'s a pretty rigid number in itself. Where is the discretionary range, and do we need to move our idea of where it is to where it seems to already be? Wizardman 23:18, 12 March 2008 (UTC)
My opinion as expressed as my RfB is that whilst RfAs are not votes, the community's expectations are generally that RfAs below 70% will not succeed and that those over 80% will. I'm not sure that trying to demonstrate whether or not a discretion exists by looking at whether or not it has been exercised is a great idea. Having a discretion means that there are cases where bureaucrats could close the request in a particular way - not that some must do so. The fact that a crat closed a request in one way does not mean that they did not consider closing it in a different manner. But if we are going to look at this statistically, it might be useful to also find out how many RfAs in those 18 months fell into the ranges you are looking at. WjB scribe 23:48, 12 March 2008 (UTC)
Advice to future RfBs; say 70%-80%, like Will did. That way you satisfy reality and the standards that some users like to cling on to (as was shown in Wiz' RfB). dihydrogen monoxide ( H2O) 00:08, 13 March 2008 (UTC)
Yes, you read right! I don't know if this one has been proposed before though. Confirmation of admins certainly has, and has failed. I'd like to propose we reconfirm bureaucrats. Why? We have determined they are supposed to be extremely trusted users (heck, there was an unofficial 90% expectation of support for what is a job that simply involves using a calculator, more even than an arbitrator). We lose arbitrators after 3 years, and they supposedly hold a similar level of trust. Additionally, we elected all but 3 of our current bcrats in 2006 or earlier. They may have been approved with community approval in 2004, but today is a lot different. Admins are admins, and their decisions are reversible. But bureaucrats' decisions are not, generally. This is why we should keep a pool of, say up to 8 bcrats that are fully trusted by the current community and are up to speed with the current norms. Every other position of such trust isn't permanent: as I've said, arbitrator, board, steward etc. Please also read my comments on this page for more of my thoughts on this. Thanks. Majorly ( talk) 15:25, 8 March 2008 (UTC)
As a technical question - it's not really for me to say whether I should be reconfirmed or not - what would be looked for at this reconfirmation? Would the bureaucrat need to demonstrate that the orginally required supermajority still supports them being a bureaucrat? Or would they need to show a level of consensus below this? Or would those opposing need to show a consensus that they should step down? WjB scribe 16:02, 8 March 2008 (UTC)
I believe Majorly's proposal regarding confirmation/recall was brought up on the Bureaucrat's noticeboard just recently if any of you wish to participate there. Wisdom89 ( T / C) 18:42, 8 March 2008 (UTC)
I'm opposed to bureaucrat recall. I like the fact that there's some old hands to prevent some of the modern craziness still around. O:-) -- Kim Bruning ( talk) 18:54, 8 March 2008 (UTC)
Wikipedia's governance is clearly arbitrary and has grown up rather like topsy, without any thought for the long-term. Nothing wrong with that, except that some questionable decisions made in a different environment do not look so very wise today. Take the way that every wikipedia post is filled, from administrator upwards (or should that be !upwards?). If you were thinking of employing a juggler, wouldn't you expect them to be able to juggle, instead of employing them on the basis that you could see no obvious physical impediments to their potential ability to juggle? -- Malleus Fatuorum ( talk) 00:18, 9 March 2008 (UTC)
'How about a term? Each bureaucrat is "elected" for a term of 18 months, after which the user must seek 're-election' Thright ( talk) 15:30, 13 March 2008 (UTC)thright
It's starting to get a little ridiculous now -- the average RFA open right now has 16 questions, with some having as many as 22 questions. Can we come up with some way to curtail these? My initial thought is to keep the standard questions on the RfA page, and any additional questions on the RfA's talk page, or something along those lines, but any other ideas are welcome. Ral315 ( talk) 02:46, 12 March 2008 (UTC)
How about going in the other direction?
Questions seem to be considered a good way of getting an idea about the candidate's suitability.
We could expand the questions into an admin exam. The question-askers could grade the answers to their questions (and others can discuss the appropriateness of the grading ;-) ), and we can then drop the poll at the end.
Does anyone dare try that? :-) -- Kim Bruning ( talk) 03:06, 12 March 2008 (UTC)
How about "how would you deal with situation X" kinds of questions? Make the situation really twisty:
"User X comes along and tells you that user Y is edit warring. You check history, user Y has only done 2 reverts today... also did 2 yesterday. When you check the talk page, both users are being fairly uncivil to each other. User X is also stating that user Y is violating V, NPOV, CIVIL. User :Y replies that she doesn't really know what X is talking about. How do you intend to proceed? What do you intend to achieve with your actions? How will X and Y react to your actions? How successful do you think your actions will be?"
There is no correct answer... but allows you to judge someone to some extent already. --
Kim Bruning (
talk) 04:45, 12 March 2008 (UTC) I always find myself trying to answer this question this kind of question (I enjoy puzzles ;-) ... so if someone wants to start a subthread where they post their answers here or on my talk page, I'll tell you how I figure you did... and possibly argue with others who think they can score you better ;-)
Personally, I find the optional questions asked by other users to be more helpful than the 3 basic ones. The initial 3 questions the candidate can prepare for, and only start the process when they have a good answer. With the extra questions, the candidate must think on the spot. Mr. Z-man 04:56, 12 March 2008 (UTC)
Heyy, you know what would be great? If people actually treated the optional questions as optional. Seriously, it's so annoying see people go 'Neutral until my question is answered'. Uh-uh. Take the time to judge a user for yourself, not wait for her/him to make up cookie-cutter answers to the same questions asked over and over again. ~ Riana ⁂ 06:36, 12 March 2008 (UTC)
Surely the basic difficulty is that the answers to all questions, incuding those posed by individual editors, are in almost all cases readily available and require from a candidate only the ability to read them. The standard questions have been answered, presumably adequately, by every successful candidate, and their RfAs are open to inspection; and even individual editors' questions appear to rcur through a significant number of applications. Furthermore, many answers are already enshrined in the basic Wikipedia framework; for example, the difference between a ban and a block, the meaning of WP:IAR, and so forth. I would concede without argument that any aspiring admin candidate who lacks the skill or initiative to go and search the answers may well thereby disqualify themselves, but I would much prefer it if decisions were made on success or failure with much greater emphasis being placed on admin related contributions rather than a sort of entrance examination. -- Anthony.bradbury "talk" 14:43, 12 March 2008 (UTC)
(<-)Making any of this formalized is a mistake in my opinion. Every wiki editor is different, every admin candidate is different, and wiki-culture itself goes through stages. Each candidate that requests the mop has different strengths and weaknesses—some more obvious than others. Each editor opining on the candidate has different objective and subjective requirements. For eample, if something is important to me, I look for it; if I find it, good, if not, I'll make a note—eithat as part of a S/O/N summary, or as a question. Different editors prefer to ask first, vote later. Candidates themselves respond differently to questions or comments. In a nutshell, we should really leave the system as it is. People who are truly interested in various questions should post them, and if the candidate is interested, they should answer. For example, KimB likes the logical-situational questions that have no direct answers. He should be able to ask each candidate that question. Each candidate should have the right to answer or refuse, and Kim (or anyone) can make their decision based on that. For another example, I don't like asking those kinds of questions as I think there are too many variables that can go into a real-wiki scenario that to extrapolate to real-wiki based on a version here is suspect, so I wouldn't hold a non-answer against the candidate. Furthermore, some users just handle "exam pressure" better than others. The beauty here is in the informality. If we start applying too rigid a structure, we risk losing the forest for the trees (procedure creep, anyone?). I would only caution that failure to answer any optional question should not be viewed ipso facto as a sign of unacceptability. There is much more than questions, usually, with which we can base our opinions. -- Avi ( talk) 21:02, 12 March 2008 (UTC)
In the meantime, perhaps we should consider adding some of the most common RfA questions to the RfA template? For example, the block/ban difference question mentioned above, one about IAR, one about BLP, and perhaps one about admin recall until it becomes less of a hotbed issue. Glass Cobra 01:17, 13 March 2008 (UTC)
I haven't seen colours on the report for ages. Why is the whole of Cobi's RFA highlighted fully in orange? Simply south ( talk) 01:48, 13 March 2008 (UTC)
(indent) I find it ironic that two of the recent failed/withdrawn RfBs were of the first to notice it and respond here. Cobi would be an admin by now. Justin (Gmail?) (u) 04:06, 13 March 2008 (UTC)
For the record, Cobi's RfA is now 3 hours overdue. dihydrogen monoxide ( H2O) 06:52, 13 March 2008 (UTC)
This is regarding Geni's RfA, in the box containing previous RfA's there is a link to User:Geniac's RfA. Is this the same user or a different one? If its the latter then it needs to be removed. Seddon69 ( talk)
I couldn't find instructions on how to handle a malformed RfA. I don't think "The nomination may be considered "malformed" and removed if you do not follow these instructions or transclude the request properly." is clear enough. Removed from where? The list of current RfAs? I found Wikipedia:Requests for adminship/aj00200 but I'm not sure what I was supposed to do with it. -- Geniac ( talk) 17:35, 17 March 2008 (UTC)
Who exactly is allowed to vote/comment in RfB's? -- Camaeron ( talk) 16:15, 17 March 2008 (UTC)
::Logged in users, socks of logged in users, socks of the socks, and of course, anyone who is in conflict with the nominee in an RfC. And anyone who doesn't like Kelly Martin. </sarcasm>.
Keeper |
76 |
Disclaimer 16:19, 17 March 2008 (UTC)