Misplaced Pages

talk:Requests for adminship: Difference between revisions - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 16:34, 10 January 2014 editNorth8000 (talk | contribs)Extended confirmed users, New page reviewers, Pending changes reviewers, Rollbackers84,160 editsm →A perfect example of the RFA problem: fx typo← Previous edit Latest revision as of 15:04, 25 December 2024 edit undoLowercase sigmabot III (talk | contribs)Bots, Template editors2,292,502 editsm Archiving 2 discussion(s) to Misplaced Pages talk:Requests for adminship/Archive 270) (bot 
Line 1: Line 1:
{{pp-move-indef}} {{pp-move-indef|small=yes}}
{{Skip to bottom}}
{{info|This is '''not''' the page to nominate yourself or another editor to be an administrator. '''To do so, please ].'''}}
{{info|This is '''not''' the page to nominate yourself or another editor to be an administrator. '''To do so, please ].'''}}


{{RfA Navigation|WT:RFA}} {{RfA Navigation|WT:RFA}}
{{RFX report}}
{{User:TParis/RfX_Report}}{{Misplaced Pages:Requests for adminship/Recent}} <!-- {{User:X!/RfX Report}} {{User:SQL/RfX Report}} {{User:Tangotango/RfA Analysis/Report}} -->
<big>Current time: {{FULLDATE|type=wiki}}<br />{{purge|Purge this page}}</big> <div style="float:right; text-align:right">''Current time is {{CURRENTTIME}}, {{FULLDATE|type=dmy}} (UTC)''. — {{purge|Purge this page}}
</div>
__TOC__
{{Misplaced Pages:Requests for adminship/Recent}} <!-- {{User:X!/RfX Report}} {{User:SQL/RfX Report}} {{User:Tangotango/RfA Analysis/Report}} -->
<div style="clear:both;"></div>
{{User:MiszaBot/config {{User:MiszaBot/config
|archiveheader = {{aan}} |archiveheader = {{aan}}
|maxarchivesize = 200K |maxarchivesize = 200K
|counter = 228 |counter = 270
|minthreadsleft = 5 |minthreadsleft = 2
|minthreadstoarchive = 1 |minthreadstoarchive = 1
|algo = old(10d) |algo = old(31d)
|archive = Misplaced Pages talk:Requests for adminship/Archive %(counter)d |archive = Misplaced Pages talk:Requests for adminship/Archive %(counter)d
}} }}
{{archive box|
{{archives|auto=no|search=yes|list=]{{,}} ]{{,}} ]{{,}} ]{{,}} ]{{,}} ]{{,}} ]{{,}} ]{{,}} ]{{,}} ]{{,}} ]
{{flatlist|
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
*]
}}
---- ----
{{center|Most recent<br />{{Archive list|start={{#expr:{{#invoke:Archive list|count}}-9}}}}}}
{{{!}} style="text-align: center; background: none"
}}__TOC__
{{!}} colspan=10 {{!}} Most recent
{{!}}-
{{!}}
{{Archiveline|set=Wikipedia_talk:Requests_for_adminship/Archive_|number=21|next=220}}
{{Archiveline|set=Wikipedia_talk:Requests_for_adminship/Archive_|number=22|next=230}}
{{!}}}
}}

==North's proposal (merely an outline) Analysis & solution to fixing the RFA and admin cadre issues==

With the RFA process broken down, right now the main criteria for who is in the admin cadre is "got in back when it was easy". And the second criteria for new ones is "kept their head low" / having avoided contentious situations. Impacts have already been felt and will get worse. The other problem is a complete blending of:
*Type #1"no big deal" tool belt functions with
*Type #2 other "big deal" "judge" type immense powers given to these folks (such as being able to sanction established individual editors, close complex and contentious discussions). This is conferred also by policies and practices, not just by software definitions of the tool belt.

===Solution: 30,000' view===

Many of the problems stem from "bundling" these two things together. On the cadre side, folks meeting the low "no big deal" bar back then have been given immense powers with really no basis. Some that are not suitable for this task have done significant harm to editors. Conversely, the "immense powers" has supported the RFA process being immensely restrictive, albeit in a way that misses the mark. A thorough analysis makes the solution (at least in general terms) clear:

*Split the role. But the needed split is NOT by software defined tools, it is between Type #1 and Type #2 above.
*Type #1 needs a lower threshold to get in. Type #2 needs a high but more "on target" threshold to get in.

===Solution: 20,000' view including implementation===
====Phase 1====
*Define the qualities needed for Type #2 (beyond the Type #1 qualities which are also required) Define the situations that will require a person with these individual qualities. These may include things like wisdom, kindness, fairness, thoroughness (when needed), a decision-making process which includes first learning and confirming everything that is relevant and then a very sound decision making process, self control in that they never do anything really bad, extensive knowledge of policies and key guidelines, and of how how they are applied in practice, Design a framework for the RFA Type 2 process that will guide the discussions and voting to be more around the desired qualities (including history etc. to build the case that they have those qualities. Compared to the current process, these will remain just as tough but more on-target.
*Decide on details to lower the threshold for Type #1, and make it more targeted on the qualities needed. The two main qualities are competency and trust that they will not use the technical capabilities of the toolbelt to do harm. Design a framework for the RFA Type 1 process that will guide the discussions and voting to be more around the desired qualities.
*Write policies and guidelines covering the above, to take effect after a 1 year delay.
*Give better names to Type 1 & 2. Example: Type #1 = administrator, Type #2 = Yoda.

====Phase 2====
Announce that exactly 1 year from then, all current admin positions (that have not been transitioned to type #2) will become type #1.
For the one year period, Type#1 RFA continues with the current process, possibly with stopgap refinements to be more "on target". The Type #2 RFA process starts rolling, and non-admins who pass this receive the Type #2 status plus receive the tool belt (if they don't have it already)

====Phase 3====

At the one year point, implement the remainder of the above, including the looser standards for Type #1, and requirement that only Type #2 folks can do type #2 jobs.

====COI note====

It should be noted that since current admins would lose and need to "re-apply" for a few powers that they already have, they have an inherent high risk of COI regarding this new idea and such should be declared and taken into account in any discussions.

By North8000

=== Discussion ===
I am guessing the above was written by ]?

As for the "split" I've tried that several times, in several ways. I haven't despaired of it yet, though it's funny that I try one way, and feedback is to try another way, then I try an rfc that new way and the feedback is to try the way we tried in the first place : )

I do think that the user-right and responsibility breakdown at ] is probably the best place to split, but implementation seems to be difficult since (among other things) there are those who fear what may result '''''for them''''' if such an option is implemented. Adminship for some is apparently territorial. And also worth noting that everyone has an opinion, so if a proposal would appear to stand in the way of someone else's proposal, that "someone else" will kneejerk "vote" against.

And of course the whole question of "granting", when dealing with deleted content. So to be implemented it would need to be a discussion like RfA, where the community vetts the candidate. This was apparently revisited recently concerning whether the arbcom election met that requirement in regards to CU and OS.

Enough time has gone by that I may try another rfc in the near future, but I have a few other things I'd like to catch up on first : ) - <b>]</b> 17:18, 24 December 2013 (UTC)

:Yes, I posted it....had "North" in the title but forgot to sign. I thought of another more incremental step towards the above. That would be to define the qualities / credentials for #2, (I'm thinking immense experience and understanding of how Wikipediia works, very strong and careful approach to analysis, fairness, unemotional impartiality, impartiality, a kind person, etc.) some mechanism to review and "bestow" that certification (no tool changes required, it could even be a project page or something) and informally those folks with be most trusted for the really difficult situations. Then, if works, something like the above transition could happen later.<b><font color ="#0000cc">''North8000''</font></b> (]) 18:05, 24 December 2013 (UTC)

== Updating the counts ==

Why does nobody ever do it right? I don't mean to be grouchy, honestly, but I'm always having to finish the job. So can I politely remind people of what needs to be done when updating the counts after closing an RFA? For example, for a successful RFA...
#Add a new line for the candidate at ] (or whatever year it is), adding a new month header if necessary.
#Update the number of successful candidacies in the month header.
#Update the total number of successful candidacies for the year-to-date at the top.
#Head over to ] and update the number of successful candidacies for the month there too.
Number 1 always gets done, but almost nobody ever manages to do all of the other three.
<p>Thanking you kindly, GrumpyBoing (aka -- ] (]) 10:49, 8 December 2013 (UTC))
:I'm pretty sure I did do that for Callanecc's RFA. Nobody ever speaks up when it's done correctly. Anyway - just fix it instead of grousing about it. ''']'''] 00:41, 9 December 2013 (UTC)
::{{ping|Boing! said Zebedee}}. I can answer this but its going to sound a bit snarky. The reason it isn't being done right, is the same reason many other things aren't getting done. It is a somewhat technical task to do, remembering to do all 4 of those tasks and frankly, the RFA system largely stopped promoting technical editors to admins years ago. Now, in order to be an admin, you have to be a mediator...technical skillz not required. Most admins admit freely that they don't have technical skills yet its exclusively admins that have access to the restricted pages (with the exception of the Template editors now having some ability). That is a problem no matter how you look at it. Most of the technical admins have had the tools since 2006 when Misplaced Pages was apparently doing things horribly wrong and it was easier to become an admin. ] (]) 00:48, 9 December 2013 (UTC)
:::But you don't need to be an admin, or even logged in in order to edit either of those pages. Nor do you need templating skills, I'm sure I've updated those table before now. That isn't to say we don't need more admins and especially technical ones, of course we do. But backlogs of actions that don't require use of the tools are not evidence for that. '']]<span style="color:#CC5500">Chequers''</span> 01:35, 9 December 2013 (UTC)
::::True but updating the "admin" numbers is an inherently administrative task that should and is generally done by admins and bureaucrats. If they aren't doing it correctly that only validates my assertions that we need more technical admins. Another perfect example is the protected templates. Prior to the new right all people had to do is do the change in the sandbox and notify an admin to implement. Easy enough right. But yet when the template editor right was created dozens of fixes were done by technical editors, most of which have applied to and been denied admin rights. Some of these changes were fixes to problems that have been on the template for a long time, a couple for over a year. Its the same thing here. Many editors won't touch it if it looks administrative and they don't have the tools. They may not make a fuss about that like I do, but the end result is the same. The communities failure to trust its longterm contributors is costing the project from improving. Some agree with me on that and some don't but the actions reflected by creating userights for Rollbacker, template editor and file mover all prove that the community '''will''' help if they are allowed too. ] (]) 01:47, 9 December 2013 (UTC)
*Hi folks, Sorry if I came across as grousing - I did the "GrumpBoing" thing as an attempt at injecting humour into what was meant as a polite reminder, but that doesn't always work in this text-only medium. And Andrevan, you're right that nobody ever speaks up when it's done correctly - I should know, cos it's often me who does it ;-) I'm happy to fix it up from time to time, but come on guys, not every time! -- ] (]) 10:11, 9 December 2013 (UTC)
*:Reading , it's not only here that you're coming across a bit strong: "''Do it properly''", "''Why does nobody ever do this properly?!''" If you don't want to tidy up these lists, feel free not to do so. They aren't really that important, which is probably why they aren't a major focus of the closing bcrat's attention (certainly not to the extent of cross checking another list that may not be up to date anyway). If you do want to do this task, please do so with good grace. We're all volunteers here... <strong style="font-variant:small-caps">] ]</strong> 15:12, 13 December 2013 (UTC)
*::Aye, fair enough -- ] (]) 17:24, 13 December 2013 (UTC)
::::I'm fairly certain that my good friend ] would give us a functioning script to automate this utterly mundane task within 48 hours of being asked if he were around, more certain that a functioning script is the best approach to mitigate the occurrence of short closures, and most certain that Δ would be around if able. If only I would remember to stay in my place. Kumbaya my Kobayashi Maru—] (]) 19:13, 24 December 2013 (UTC)
:::::Unfortunately Arbcom et al ran ] from this site like so many others...] (]) 20:59, 24 December 2013 (UTC)
::::::{{U|KumiokoCleanStart}}, I know I wouldn't be the first to suggest that your incessant rhetoric about how broken our RfA system is, by virtue of the fact you haven't passed one yet, is becoming tiresome. I can't stop you from beating this drum over and over and over, but can you please possibly consider restricting it to discussions to which it is actually pertinent? Comments like the ones you've flooded this particular discussion with have become ever-present on this page and it's becoming impossible to have a rational discussion about anything without you derailing it into a conversation about how unfair it is that the community hasn't given you the mop yet. I'm sorry, I honestly don't mean to cause offence, but I don't think it helps either your cause or everyone else's productivity to make this point ad nauseam as you do. ]&nbsp;]⁄] 00:15, 25 December 2013 (UTC)
:::::::Believe it or not I am completely beyond caring if I get the tools. That does not change the fact that RFA is broken, backlogs continue to grow, Arbcom is straying farther off mandate, admins are becoming more abusive and increasing the gap between admins and editors and editors, particularly IP's are treated with contempt. Your right, several have told me to let it go, to move on and to just go away. But that won't fix the problems. BTW I am not the only one who sees these problems. Most of these have been admitted by many including Jimbo but '''all of them''' fail to do anything about it They all claim they are powerless to act. As I have stated elsewhere though I a going to stop commenting after the first of the year. Think of it like a resolution. Not because people don't believe there is a problem, not because they don't care what I have to say about it, but because at this point I honestly believe that no one cares enough about the project to fix it and that is going to be the projects undoing. I don't have any sympathy for those backlogs anymore because I and others want to help but we're not wanted. They want editors who will stay in their corner and not push the system or try to improve it. You can make edits but don't question the Adminarchy, that is unacceptable. ] (]) 01:08, 25 December 2013 (UTC)

Let's just file a bot for this and see what the people at ] do. This honestly seems like a routine, tedious, administrative, and technical task better left to an automated counter. ] (] &bull; ]) 02:13, 25 December 2013 (UTC)

== Edit summaries ==

To whomsoever it may concern - ''please'', when removing RfAs from this page, link to them in your edit summary. It is a massive pain in the butt to have to scrape through page history to get to a recently-closed RfA after seeing a closure notice in your watchlist. Thank you! — ] <span style="color:#900">•</span> ] 13:11, 13 December 2013 (UTC)
:Huh? They don't get removed from this page - this is the talk page and they get removed from the 'flip side' of this page....] (] '''·''' ]) 13:36, 13 December 2013 (UTC)
::Normally we can find them easily through the "Latest RfXs" box on both this page and the project page. But for some reason the recent RfA by JamesMoose aka BigPimpinBrah is not displayed there. Is it because of the mid-discussion change of username? --] (]) 15:07, 13 December 2013 (UTC)
:::That table is only of use if you catch it while the RfX you're interested in is still listed. It may not even have been added properly, as you mention; or the RfX you're interested in seeing may have been an anomalous one that got removed swiftly and so was never put in the table. A practice of invariably linking to RfXs in edit summaries would provide a fast route to any closed RfX from the page (yes Cas, the page - not here, its talk page)'s history. — ] <span style="color:#900">•</span> ] 15:47, 13 December 2013 (UTC)
::::Catching the outcome of a recently closed RfX is probably easier from the table than from the edit summaries, where you'd have to either be cruising the page's history or catch it go by in your watchlist, but of course as you say, it relies on the table being updated. I encourage closers (or lurkers) to update the table with all closed RfX requests, even the swiftly closed ones. ] (]) 16:45, 14 December 2013 (UTC)
::::: You can always check:<br>
::::::]
::::::]
::::: <font face="Rage Italic" size="4" color="#800080">]</font> <sup><font face="Times New Roman" color="#006400">] ]</font></sup> 17:43, 14 December 2013 (UTC)
::::::*<small>See above section. ] (]) 17:49, 14 December 2013 (UTC)</small>

== A perfect example of the RFA problem ==


== Notification of RfC: Voluntary RfA after resignation ==
The current RFA for ] is a perfect example of the inconsistency and failure of the RFA process. Although Acather96 is a good person they have zero need for the tools, no demonstrated technical capability to use them, no Featured content work and has just come back from a long break. The main reason they seem to be applying for the tools is because they are getting bored with regular editing. This RFA seems to be a landslide support but yet all the failures of this candidate have derailed dozens RFA's, many in the last few months. A few examples, this month ] failed because they didn't have enough experience at AFD, XFD or activity in the last couple years, all apply to the current candidate; several have been derailed since this summer for lacking content building experience including ] where several supporters of the current RFA opposed; etc, etc. A couple even state openly they don't meet "all or some of their criteria". It seems to appear that pure luck is what passes an RFA these days rather than a demonstrated need and capability to use the tools and a fair amount of hypocrisy is present on the case of the voters opposing other candidates and then supporting this one for the very same reasons. ] (]) 22:50, 25 December 2013 (UTC)
::I think it is not unreasonable for an editor to apply to be an admin even if they have "zero need for the tools". They might have had their fill of regular editing and want to do a new job that will be useful to the encyclopedia. ] (]) 23:00, 25 December 2013 (UTC).
:::I could agree with that if the editor had some demonstrated experience in admin areas, and I should clarify that the current RFA is only one example of a larger problem and I am not targeted that editor specifically. When editors support one candidate as they are but then oppose others for reasons that the currently supported candidate clearly doesn't have, it proves that the current process isn't working. ] (]) 23:06, 25 December 2013 (UTC)
::::Some people support or oppose based purely on their 'gut feelings' of a candidate, or the candidate's personability. I think most Wikipedians' intuitions have been spot on. -- ]] 00:56, 26 December 2013 (UTC)
:::::That may be true but I still don't think this user has demonstrated a need for the tools or the technical ability to use them. It looks to me like another of those editors who will get the tools and not use them. Its unfortunate that these days the only ones who can pass are the ones who don't get involved in admin areas prior to getting the tools. That is not how the process should work. ] (]) 16:24, 27 December 2013 (UTC)
::::::Kumioko, if you've got a point to make, head across the road to the RfA in question and !vote. I don't think it's particularly fair to begin what is essentially a bashing thread against a candidate whose RfA is currently running. And this from an editor who has consistently criticised the hostile atmosphere surrounding RfA. ]&nbsp;]⁄] 17:26, 27 December 2013 (UTC)
:::::::You might want to take another look Basalisk because I did vote oppose. I also stated clearly that this isnt about this individual. Its in reference to the fact that several of the people who have supported this candidate opposed others for the very shortcomings this editor has stated or less. It gives the impression (and not too subtlely I might add) that getting the tools is less about what you know and more about staying below the radar until you get them. I would also clarify that I told the individual on their talk page it wasn't peronsal towards them and I waited until the RFA was essentially locked into a win before i started the thread. Now I know that you don't care about reforming RFA and just want me to go away, andI plan to do that in about 3 days, soo drop you droll about how this is only about my not getting access to the tools, its not and never has been. That's just PR from editors who don't like me getting the better of you. How about you step up and do something to make this process better since I am doing so badly at it. Also I honestly don't think anyone else really wants this process to change, after all it worked well enough to get them access to the tools so to say it isn't working would also be to say they didn't get the tools fairly right. I mean its not like we dont have enough adminsn to do all the tasks, we certainly don't have any backlogs of admin tasks and we didn't have to create 3 new roles over the years (rollback filemover and Template editor) to compensate for the lack of admins. Nope, I am just dreaming all of that. So please, please put your time where your mouth is and help improve this process. ] (]) 17:32, 27 December 2013 (UTC)
::::::::Well what I'm implying is that your !vote is sufficient, there isn't any need for yet another barrage on the talk page to follow it up. Telling someone "it's not personal" doesn't make any difference to how personal a criticism feels. If you go up to someone and say "you're a fucking asshole, nothing personal" it doesn't magically become impersonal. I just think the last thing someone needs when he's running the gauntlet of RfA is to be made the thinly-veiled subject of a critical piece on the talk page. Boring garden-variety straw man at the end there too, accusing me of being "against RfA reform" on the basis that I'm against the language you use to address it - "you're against x so you're clearly also against y". And please don't tell us yet again that you're leaving. I'd like you to stay, if you're going to leave so be it, but '''please''' stop ''saying'' you're going to leave if you're not ]&nbsp;]⁄] 17:46, 27 December 2013 (UTC)
:::::::::I would have liked to stay too but I am of no use to this project. I can't participate in the areas want to participate in so there isn't any point in staying. The editing environment has become toxic and the site has become a joke to most of the word outside its editors for a variety of reasons. Even longtime supporters and funding providers are cutting ties. I used to have a lot of passion for the project and pride in being an editor here and more and more I am embarrassed to tell people I edit Misplaced Pages, the encyclopedia very few can edit and those that do are severely restricted. ] (]) 17:51, 27 December 2013 (UTC)
::::::::::I'm finding that the nature of running an RfA at this particular time coincides with abnormal editing routines, i.e. I'm personally unlikely to be scheduling in the amount of research I'd normally expect to undertake. The same may be the case for others. <span style="white-space:nowrap;">-- ]</span> (] · ]) 18:28, 27 December 2013 (UTC)
:::::::::::Yes, I'm guilty of having done less research this time than I normally would. It would be surprising if we're the only two. Maybe there should be a moratorium on launching RfAs between, say, 14 December and 28 December. If in future years an RfA is launched when it will run over the festive season, I may just ABF and oppose on principle ;) --] (]) 18:39, 27 December 2013 (UTC)
::::::::::::I personally find it disappointing and annoying that the ones who get the tools are the ones who really don't need them and show no signs of using them. Those that do meddle in admin areas are shot down because the mentality is they have shown they could do the tasks without the tools. Or they have participated in those areas long enough to make some enemies. Its meaningless to me any more I have taken the hint, that's why I only comment in discussions now. Soon enough not even that. But if I were other editors like Wikid and Cyberpower who routinely do admin stuff and keep getting told no only to hand the tools out to others who have no demonstrated need or knowledge of the tools I would feel pretty insulted. Too many admin tasks rely on non admins helping out and the admins forget that. ] (]) 22:02, 28 December 2013 (UTC)
:::::::::::{{ping|Trevj}} Surely that isn't cheating, is it? Maybe the running of that RfA was just a coincidence and not a previously planned delay in launching a RfA. ] (]) 18:58, 29 December 2013 (UTC)
::::::::::::No, I wasn't suggesting cheating... just that it could've perhaps been more thoughtfully timed. Of course, there are no rules regarding the timing, and candidates need to consider their own availability to promptly answer questions. <span style="white-space:nowrap;">-- ]</span> (] · ]) 07:35, 10 January 2014 (UTC)
:::::::::::::There were more than 80 participants, and though it ended over Christmas the busiest time in most RFAs is the first couple of days which were clearly not in the holiday season. As this was the only RFA running from the 21st to the 24th I would consider that it had more scrutiny than many of our current admins had in their RFAs. However as this is not the first time that the holiday issue has come up, perhaps those for whom it is an issue could list the days that should be disregarded when calculating the length of RFAs and propose an RFC to extend all RFAs from 7 days to "7 days ignoring Diwali, Good Friday, New Years Day, Christmas Day and April the 1st". I'm not sure if I'd agree with you, but I've no objection to people trying to change policy via RFC, whilst I do find it distasteful to see people try to change policy by objecting to people who follow it. '']]<span style="color:#CC5500">Chequers''</span> 09:14, 10 January 2014 (UTC)
:I don't think that you necessarily need to have FAs, or have participated in AfDs and XfDs or whatnot to be an admin. Some admins just get the tools for a single purpose (for example, ] got admin tools solely so they can edit protected templates). Other admins just apply for adminship so they can have bundled user rights, not necessarily so that they can do admin tasks. Besides, the admins who don't use the tools now may use them later. Just because these admins have no need for the tools ''now'' does not mean that they will not use them at all, ever. Who knows, Acather96 may end up making thousands of page protections, page deletions, blocks, pagemoves, etc. ] (]) 18:54, 29 December 2013 (UTC)
::Rereading ] and especially his answers to q1 and q2 there are some obvious differences between his RFA and certain ones that failed. His q1 answer illustrated a use of the tools for which he was qualified - no surprise that he already has ] and his q2 answer demonstrated that he has content creation under his belt. There are some editors who want to see FAs, but the consensus at RFA seems to be that the content creation test is that you need to have demonstrated the ability to add content cited to reliable sources. I've seen RFAs that failed for several common reasons, but Acather96 avoided all of them, not because of lack of scrutiny but because he was a qualified candidate who avoided certain pitfalls. '']]<span style="color:#CC5500">Chequers''</span> 21:04, 9 January 2014 (UTC)


There is an RfC on seeking tools via a voluntary RfA after resignation at {{slink|Misplaced Pages:Village pump (policy)|RfC: Voluntary RfA after resignation}}. ] (]/]) 21:18, 15 December 2024 (UTC)
::: Having voted on almost all RfAs over the past few years and closely studied dozens of older ones, I notice that trends in voting appear to come and go in waves. The past year or so appears to have placed rather more emphasis on participation in GA and FA. While solid content contribution and ideally some immaculate creations beyond stubs is essential to have demonstrated that those who wish to police pages should know how to produce them, a correct and useful participation in admin related areas is just as important and possibly even more so. These are also the areas where voters should do their own research rather than piling on with ''support'' or ''oppose'' votes 'as per' other participants who may well have got their voting rationales quite wrong. ] (]) 04:13, 10 January 2014 (UTC)
::::I'd agree that fashions in the question section come and go, but the content creation threshold seems to have been fairly stable for some years. FAs and GAs are of course an autopass for the content creation test, but the threshold for support is much lower, and going back to Kumioko's three examples at the start of this thread, neither of the two who failed had demonstrated an ability to add reliably sourced information to the Wiki, whilst the candidate who succeeded had passed that test. We do sometimes get opposes for lack of an FA, but I'm not aware of any RFA ever where that alone has sufficed to fail a candidate. We also have a consistent test re need for the tools, here I'm sometimes on the losing side as I hold the view that if we can persuade a qualified member of the community to carry the mop they will perforce find themselves using those extra buttons, and perhaps more cautiously than some. However I wouldn't nominate a candidate unless they could credibly convince the community with their Q1 answer, and if a candidate's answer to Q1 fails to make a sufficient case to pass their RFA I may not even bother assessing them sufficiently to !vote. '']]<span style="color:#CC5500">Chequers''</span> 09:38, 10 January 2014 (UTC)
:The robust success of Acather96's RfA only serves to remind how completely bogus ] is. — ] <span style="color:#900">•</span> ] 13:20, 10 January 2014 (UTC)
::It also shows that if you don't make waves, go with the system and keep your head down you'll get the tools, but if you try and make this project better you stand no chance. That's not the environment most people want to participate in and a key reason why I left. The only reason I am commenting now is because someone sent me an email and asked me to comment because my name was mentioned. The arguments that WereSpielChequers presents that the examples I gave would not make good admins are completely false and only reinforce the current attitude that technical editors have no respect here. Not everyone is going to make FAs (especially since the process heavily favors British speech over American) but because for many of us that's not what they are interested in. Likewise, many don't want to code templates and do stats work. But that's no reason to hold them back and tell them they can be trusted with the ability to block. That argument is a complete fallacy and fundamental problem why the Misplaced Pages editing environment has turned into such a disgrace and an embarrassment. For all of the comments and bullshit being written on this page about how you all want to change this process not one editor on this page except me has any interests in making Misplaced Pages a better place, just business as usual because that what allows you to maintain control. You all should be ashamed! The lack of trust in the editors in this community is disgraceful. ] (]) 14:26, 10 January 2014 (UTC)
:::{{tq|"... not one editor on this page except me has any interests in making Misplaced Pages a better place, just business as usual ..."}}{{cn|date=January 2014}} doesn't make this place better either! <span style="white-space:nowrap;">-- ]</span> (] · ]) 14:53, 10 January 2014 (UTC)
IMO one piece of the answer remains obvious. Decide on qualities useful for admin and structure the RFA process to nudge it towards more discussion / evaluation regarding those points. That would make the criteria far less random/wrong. <b><font color ="#0000cc">''North8000''</font></b> (]) 14:20, 10 January 2014 (UTC)


== writer == == Odd patterns ==


The currently open RfA (]) has unanimous support votes (201/0/0 as of last check). I can observe that such unanimous supported RfAs are often for indviduals who have an ''exceptional'' track in copyright matters, if I remember correctly, since this area tends to be understaffed when it comes to admin capacity, as is the case with the subject of the RfA. Furthermore, for some reason, co nominations tend to be successful and self nominations tend to be unsuccessful (through means of withdrawal, ] e.g ], or ] e.g. ]). These are a few patterns that I could find at RfAs, but I do not see a reason for the latter (co noms better than self noms). ] (]) 20:34, 22 December 2024 (UTC)
Eamon Kelly was born in Dublin in 1963 <small><span class="autosigned">—&nbsp;Preceding ] comment added by ] (] • ]) 12:42, 7 January 2014 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
:All ill consider RfAs - i.e., someone ignoring all the guidance - are always self nominees. That alone would create a bias towards self nominations being less successful. The other reason is, perhaps, that !voters can't be bothered to review the track record of most candidates so for self noms will either tend to not !vote at all, or if they do !vote oppose, but will happily trust nominators and support. But without surveying !voters, who can say for sure. ] (]) 21:47, 22 December 2024 (UTC)
:I think you want ]. --] ] 12:46, 7 January 2014 (UTC)
::I'd say that when the person is qualified and happens to self-nom, they tend to pass. Some relatively recent examples include me, Spicy, and 0xDeadbeef. ] ] 06:20, 23 December 2024 (UTC)
:Why, self-noms are "prima facie evidence of power hunger", of course! /j ] (]) 11:09, 23 December 2024 (UTC)
:Let me put it differently: If a respected user nominated someone for RfA and that RfA ended as NOTNOW, it means that something went seriously wrong, most likely the nominator did not make proper research. Most nominators do, or at least attempt to do proper research, this is why NOTNOW RfAs tend to be self-nom. ] (]) 11:17, 23 December 2024 (UTC)
:Nominators also serve as coaches. They often tell the candidates if and when they should run or not run, and provide other very useful advice during the process, helping to avoid common missteps. A respected nominator can also provide a boost in supports, due to folks trusting the nominator. –] <small>(])</small> 17:37, 23 December 2024 (UTC)

Latest revision as of 15:04, 25 December 2024

    This is not the page to nominate yourself or another editor to be an administrator. To do so, please follow these instructions.
    Advice, administrator elections (AdE), requests for adminship (RfA), bureaucratship (RfB), and past request archives
    Administrators Shortcut
    Bureaucrats
    AdE/RfX participants
    History & statistics
    Useful pages
    Requests for adminship and bureaucratship update
    No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)
    Current time is 04:51, 26 December 2024 (UTC). — Purge this page
    Recent RfA, RfBs, and admin elections (update)
    Candidate Type Result Date of close Tally
    S O N %
    Sennecaster RfA Successful 25 Dec 2024 230 0 0 100
    Hog Farm RfA Successful 22 Dec 2024 179 14 12 93
    Graham87 RRfA Withdrawn by candidate 20 Nov 2024 119 145 11 45
    Worm That Turned RfA Successful 18 Nov 2024 275 5 9 98
    Voorts RfA Successful 8 Nov 2024 156 15 4 91


    Archives
    Most recent
    261, 262, 263, 264, 265, 266, 267, 268, 269, 270

    This page has archives. Sections older than 31 days may be automatically archived by Lowercase sigmabot III when more than 2 sections are present.

    Notification of RfC: Voluntary RfA after resignation

    There is an RfC on seeking tools via a voluntary RfA after resignation at Misplaced Pages:Village pump (policy) § RfC: Voluntary RfA after resignation. voorts (talk/contributions) 21:18, 15 December 2024 (UTC)

    Odd patterns

    The currently open RfA (Misplaced Pages:Requests for adminship/Sennecaster) has unanimous support votes (201/0/0 as of last check). I can observe that such unanimous supported RfAs are often for indviduals who have an exceptional track in copyright matters, if I remember correctly, since this area tends to be understaffed when it comes to admin capacity, as is the case with the subject of the RfA. Furthermore, for some reason, co nominations tend to be successful and self nominations tend to be unsuccessful (through means of withdrawal, WP:NOTNOW e.g wp:Requests for adminship/ToadetteEdit, or wp:SNOW e.g. wp:Requests for adminship/Numberguy6). These are a few patterns that I could find at RfAs, but I do not see a reason for the latter (co noms better than self noms). ToadetteEdit (talk) 20:34, 22 December 2024 (UTC)

    All ill consider RfAs - i.e., someone ignoring all the guidance - are always self nominees. That alone would create a bias towards self nominations being less successful. The other reason is, perhaps, that !voters can't be bothered to review the track record of most candidates so for self noms will either tend to not !vote at all, or if they do !vote oppose, but will happily trust nominators and support. But without surveying !voters, who can say for sure. MarcGarver (talk) 21:47, 22 December 2024 (UTC)
    I'd say that when the person is qualified and happens to self-nom, they tend to pass. Some relatively recent examples include me, Spicy, and 0xDeadbeef. Clovermoss🍀 (talk) 06:20, 23 December 2024 (UTC)
    Why, self-noms are "prima facie evidence of power hunger", of course! /j GreenLipstickLesbian (talk) 11:09, 23 December 2024 (UTC)
    Let me put it differently: If a respected user nominated someone for RfA and that RfA ended as NOTNOW, it means that something went seriously wrong, most likely the nominator did not make proper research. Most nominators do, or at least attempt to do proper research, this is why NOTNOW RfAs tend to be self-nom. Ymblanter (talk) 11:17, 23 December 2024 (UTC)
    Nominators also serve as coaches. They often tell the candidates if and when they should run or not run, and provide other very useful advice during the process, helping to avoid common missteps. A respected nominator can also provide a boost in supports, due to folks trusting the nominator. –Novem Linguae (talk) 17:37, 23 December 2024 (UTC)