Wikipedia:Requests for adminship/HickoryOughtShirt?4

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
The following discussion is preserved as an archive of a successful request for adminship. Please do not modify it.


Final (182/19/9); Closed as successful by Primefac (talk) at 01:37, 1 May 2019 (UTC)


HickoryOughtShirt?4 (talk · contribs) – HickoryOughtShirt?4 is one of those rare combinations - a user who is comfortable with both writing content and fighting vandalism. As a Canadian, their specialist subject is, as you might expect, ice hockey, and they've made significant contributions in this area, including the good article Quinn Hughes and numerous Did you know? nominations hitting the main page. But look elsewhere, and you'll see them making numerous intelligent reports at the anti vandalism noticeboard; easily enough to determine (along with their track record of content) they know exactly what's vandalism and what isn't.

I first discovered HickoryOughtShirt?4 was interested in adminship about six months ago, around the time they got the New page reviewer right. At the time, they were concerned about the perpetual backlog at AIV and really thought they ought to be able to do something about it, but equally they were concerned that they needed to work more on content and get a bit more experience in debates. I'm pleased to see they've done exactly what I hoped, and I can now see several editors thinking it really is time they had a go at asking for the old mop and bucket. Ritchie333 (talk) (cont) 23:32, 23 April 2019 (UTC)

Co-nom by TonyBallioni

I am pleased to present HickoryOughtShirt?4 for consideration for adminship. HickoryOughtShirt?4 registered in November 2017, and is one of those users who in a short time, was able to fully grasp why we are here as a project. They do their absolute best to make Wikipedia better, and while they make mistakes like everyone else, they are fully willing to discuss them with anyone who asks and are one of the single most pleasant users I have met on any Wikimedia project. When I first approached them about adminship in October, their first response was to say they didn't think they were ready and that they wanted to become more familiar with other areas of Wikipedia first. Having been active in the RfA area for a while, I can tell you that a good sign of a candidate and someone who will serve the community properly is someone who knows their own limitations and is willing to take a step back to assess whether it is right for them to do something. HickoryOughtShirt?4 gets this, and it is one of the most important traits in any administrator.

As some of you may know, I am generally skeptical of a vandalism focus in admin candidates: we often get editors who miss the forest for the trees in this area, but HickoryOughtShirt?4 is not one of them. You can tell by their actions that they fully understand that the purpose of Wikipedia is to build an encyclopedia, and view any administrative or backend role in the light of furthering that goal. I think HickoryOughtShirt?4 has what it takes to be one of the best administrators that we have, and I am trilled to support them in this RfA. I hope you all will join me. TonyBallioni (talk) 00:23, 24 April 2019 (UTC)

Candidate, please indicate acceptance of the nomination here: I accept this nomination. HickoryOughtShirt?4 (talk) 01:07, 24 April 2019 (UTC)
I also want to specify I have never edited for pay. HickoryOughtShirt?4 (talk) 01:29, 24 April 2019 (UTC)

Questions for the candidate

Dear candidate, thank you for offering to serve Wikipedia as an administrator. Please answer these questions to provide guidance for participants:

1. What administrative work do you intend to take part in?
A: The administrative work I intend to take part in would be in Administrator intervention against vandalism (AiV) and Request for Page Protection (RPP). I am an active Recent Changes Patroller and my main area of focus on Wikipedia have, and will remain, revolved around vandalism. In my experience, there is a continual backlog at AiV and RPP which I intend to help reduce. In many instances, one can wait hours for a page protection request and many have taken to posting to ANI to alert admins. My main editing area of focus is typically sports related, which is constantly experiencing vandalism (see the ridiculousness at Wesley Johnson (basketball) in March 2018 or NFL Honors (where I seemed to be the only editor fighting vandalism in January 2019) for example) and few admins are really focused in this area. I have stayed up many hours fighting vandalism as I waited for an admin to respond to my request for protection. Being given the tool to block and protect would be very helpful.
2. What are your best contributions to Wikipedia, and why?
A: I would have to say my best contributions to Wikipedia is my article creations (of which I have 67). Of these 67, I have 6 (at the moment) DYKs (2 are coming up) and 1 GA for Quinn Hughes. Despite these DYKs and GA, I am particularly proud of the collaborative work I have done with Flibirigit on List of members of the IIHF Hall of Fame. Starting from a list of redlinks, we collaborated together over a few months to fix these links (of which there were 28) and nominated several for DYK (such as Philippe Lacarrière). Besides working in my own article space, I also help out in New Page Reviewer (NPR). This also relates to my vandalism work, as one can see through my Speedy Deletion log. However, NPR has a similar problem to AiV and RPP which is a lack of involvement. If given the tools, I also intend to help with Speedy Deletion reviewing and continue with New Page Patrol.
3. Have you been in any conflicts over editing in the past or have other users caused you stress? How have you dealt with it and how will you deal with it in the future?
A: Of course, naturally, I have encountered conflict and disagreed with editors, especially in contentious areas. I have helped form, and will always go with, consensus and try to focus on the edits, not the editor. For example, as you can see here I was under the impression we are not supposed to use first names after the lede, so I reverted an editor on Elsa G. Vilmundardóttir. They came to my talk page and explained how I was mistaken due to Icelandic tradition (which I was unfamiliar with). I thanked them for explaining it to me, self reverted, and it taught me to move cautiously in areas I'm not familiar with. Due to my adherence to conflict resolution, I have not been taken to ANI/ArbCom etc. over problematic editing. This is also because I know when to walk away from the conflict. However, I consider all disputes I have been involved with to be in the past and prefer to move on from them.

You may ask optional questions below. There is a limit of two questions per editor. Multi-part questions disguised as one question, with the intention of evading the limit, are disallowed. Follow-up questions relevant to questions you have already asked are allowed.

Additional question from SkyGazer 512
4. First of all, thank you for being willing to run for adminship! I've seen you around a lot (I'm watching your talk page, fyi :)) and you seem to be a clueful, kind editor who does an excellent job creating content, tagging pages for deletion, and fighting vandalism. Because you mentioned that RfPP would be one of the primary areas you would use your mop in, I looked into your contributions to that page. As I understand it, extended-confirmed protection should only be used when multiple autoconfirmed users have recently and persistently vandalized a page and semi-protection has proved to be ineffective (aside from "special cases", like the whole Arab-Israeli conflict thing); in most cases of simple vandalism or BLP vios on an article, semi-protection should be used instead. After taking a look at your edits to RfPP, I noticed that in your last 20 reports, you requested ECP for over half of them. After taking a closer look, I saw that out of your last 20 reports suggesting ECP, 19 of them received only semi-protection or no protection at all; only one of the pages actually got extended-confirmed protection for any duration. I took an even closer look at two random pages of that sample: I noticed that Jake Gardiner had zero disruptive edits from any autoconfirmed user in all of 2019 and only one disruptive registered user edit since February (who was not autoconfirmed, so ECP would have been no different than semi for them). Benoît Bastien had zero disruptive edits from any confirmed user in its whole existence. Would you maybe care to share why you suggested ECP for all these pages instead of semi, and whether you would have ECP'd them yourself if you were an admin? Do note that I am leaning towards supporting, because I believe that adminship is no big deal and all that, and you clearly have a need for the tools. Much thanks, --SkyGazer 512 My talk page 02:53, 24 April 2019 (UTC)
A: Hi SkyGazer 512 and thanks for your question. That is a very good, thoughtful, and thorough question which I can appreciate. To begin, I am extra cautious around BLPs (as one should be). In my experience with vandalism, I've seen several autoconfirmed users go unnoticed/be sleeping before vandalising after protection is added (take this or this COI edit from an 11 year dormant account for example). You are right that I should be more cautious when it comes to requesting protection, especially to avoid WP:BEANS, but in my experience this an all too common occurrence (especially if the BLP is in the news). As an admin, I would have to carefully assess each situation as each one is different. I hope this helps. HickoryOughtShirt?4 (talk) 03:09, 24 April 2019 (UTC)
Followup: @Ferret: thank you for your comment. I will reiterate that I should be more cautious when it comes to requesting protection, but still agree that in my experience this is an all too common occurrence. As an admin, I will, of course, follow Wikipedia policy that ECP should not be used preemptively. HickoryOughtShirt?4 (talk) 03:34, 24 April 2019 (UTC)
Additional question from Reyk
5. In your opinion, what is the most important policy on Wikipedia and why?
A: You know, that's a hard one. I understand the importance of all of our policies and I think everyone would have mixed replies based on their circumstances. People who don't see the inner workings of Wikipedia (our readers) don't see the benefit they get from policies like WP:BLP, WP:NPOV and WP:V. Without any of these policies, I don't think this encyclopedia works. Those who just use Wikipedia for reading get the benefit of these policies without seeing them in action but that doesn't make them less important. Similarly, for those editing Wikipedia on the inside, policies like WP:CIVIL and Wikipedia:Consensus are important in the continual production of Wikipedia content. I can't say principles like WP:AGF aren't important, but this is not the only policy/principle that helps Wikipedia run its course and be successful. In my experience, WP:AGF, WP:CIVIL, WP:BLP, WP:NPOV, Wikipedia:Consensus, and WP:V have all played important roles in my everyday life on this website, but to others who work in different areas, this may not be the case. Without WP:V, there is no determining that our neutrally worded content on a biography of living people is correct, which defeats the purpose of the encyclopedia. The same can be said vice versa for the others. All of our policies tend to work in conjuncture with each other. I am sorry for this roundabout answer but trying to determine which is most important seems a bit like trying to find a needle in a haystack. HickoryOughtShirt?4 (talk) 05:49, 24 April 2019 (UTC)
Additional question from Andrew D.
6. Your account name is quite intriguing. In trying to puzzle it out, I learnt that hickory is a type of fabric that might be used for a tough shirt and I suppose that sports shirts have numbers on. But I reckon I'm still missing bits like the meaning of the question mark. Please explain.
A: Hahah, I can promise you it is nothing at all what you are thinking about. Back in high school, every student was given a unique password as their school login. This was mine. I chose to use it because of its anonymity. HickoryOughtShirt?4 (talk) 08:04, 24 April 2019 (UTC)
Additional question from GiantSnowman
7. Please can you explain why you felt you needed to clarify that you have never undertaken paid editing?
A: That was advice given to me by my nominators but I think that it is always a good thing to make note of. I am an active participant at Wikipedia:Conflict of interest/Noticeboard and Recent Changes Patrol so I tend to encounter a lot of COI editors. I fully understand the policies I would need to undertake if I ever became involved in such a circumstance myself. HickoryOughtShirt?4 (talk) 08:17, 24 April 2019 (UTC)
Additional questions from GeneralizationsAreBad
8. Again, thank you for deciding to throw your hat into the ring. When, if ever, is it acceptable to block an IP or account when it has not received talkpage warnings?
A: Well besides the obvious reasons of sock puppetry, if they were engaged in racist and anti-Semitic edits, posting threats, spamming, or clearly just here to vandalize especially with a troubling name. I would never block without warning except in extreme cases. Basically, if they were conducting actions that could lead to immediate harm of the encyclopedia and its users (such as threatening or repeatedly showing hateful content), I would block without warning. However I do want to stress that users should be warned before being blocked in most circumstances. HickoryOughtShirt?4 (talk) 14:49, 24 April 2019 (UTC)
9. What is your opinion on {{school block}}s for IPs?
A: I would generally be conservative and evaluate each instance case-by-case, doing what I feel is best for the encyclopedia in that specific case.HickoryOughtShirt?4 (talk) 21:12, 24 April 2019 (UTC)
Additional question from Andrew D.
BA309 A319-131 G-EUPJ 04-02-2019.jpg
10. It's said that you're active at WP:UAA so I looked through your recent contributions. These indicate that you typically use Twinkle to log entries there but that you don't discuss the issue with the user first, as recommended by the instructions. For example, one recent case was User:CoastalMountainSpotter. You reported them as a promotional user but their account name and upload (right) indicate that they are a plane spotter. Please explain. Andrew D. (talk) 12:40, 24 April 2019 (UTC)
A: Hi Andrew D. I want to clarify something. The instructions say borderline cases should be discussed with the users and to not discuss and report at the same time. This case was clearly a user who wanted to promote their Instagram. Their username matched their promotional (now deleted) edits (as the admins on their page also acknowledge). However, in retrospect, that was a mistake and I probably shouldn't have reported. I will resolve to do better next time. I also agree with the admins on their talk page to move forward to manage the situation.HickoryOughtShirt?4 (talk) 15:06, 24 April 2019 (UTC)
Additional questions from RhinosF1
11. You didn't join that long ago, What would be your advice to someone starting out?
A: I would suggest starting slow and picking an area that interests you. As well as not to be afraid to ask questions. Without the positive interactions and support I got from admins and experienced users, I don't think I would have lasted long.
12. You seem to have picked up how Wikipedia works very well, What convinced you to get stuck in so quick?
A: As something I have learnt throughout my time here, WP:BITE is important. While I began editing Wikipedia because I enjoyed my topic of interest, the courtious way I was introduced to the community was very important in convincing me to stay. HickoryOughtShirt?4 (talk) 15:36, 24 April 2019 (UTC)
Additional question from Dolotta
13. What area or areas of the English Wikipedia do you find yourself to be the weakest?
A: A weakness I can identify on English Wikipedia is that I do not have a technological background. I can handle basic coding knowledge but I am out of my depth regarding bots and script creation. Therefore, I don't plan on running any bots or applying for a BRFA. HickoryOughtShirt?4 (talk) 21:03, 24 April 2019 (UTC)
Additional question from SteveStrummer
14. You're a vandalism fighter and I like that. But how deep should an administrator get in these waters? It's great to revert childish scribble and random deletions, but what about the more insidious vandalism of deliberate wrong information? I don't mean "fake news", but false information that's added by IPs to sabotage Wikipedia. This is more common than it may seem: I've encountered numerous instances where names, dates, and other hard facts were quietly changed by IPs for no apparent reason other than vandalism. I've even seen an IP return after days to make the same kind of change. My question to you is: Do you think it's an admin responsibility to watch for and vet unsourced IP edits, or is it something for the editors?
A: My answer would be that we all should be responsible for keeping Wikipedia accurate. While some editors randomly change articles for disruptive reasons (such as the Cause of death vandal or the Dog and rapper vandal), sometimes people make good faith but wrong edits continuously; the best thing to do is make sure everything is sourced, ideally to something that's easy to verify. Then, if a random IP makes a change contradicting that, you can simply say "the source doesn't say that". If the problem is chronic, semi-protection may be needed (such as with Wikipedia:Long-term abuse/Catcreekcitycouncil). In all cases, AGF is best. While administrators might have different tools, in order to keep Wikipedia running, everyone should do their fair share of vetting edits and checking accuracy. This shouldn't be a job for a few people but a goal for the website. HickoryOughtShirt?4 (talk) 21:03, 24 April 2019 (UTC)
Additional question from SteveStrummer
15. Since you say you don't have a technology background and won't be using bots, how would you fight vandalism differently from the standard Twinkle user?
A: As an admin, I can view hidden content (such as accounts that trigger specific filters) that I cannot see now. Since I can see the hidden content, it will make it easier for me to find vandals and socks. For example, if I could have seen that previous versions of Mohamad Tiregar had been deleted due to G5, I could have blocked that user instead of wasting time engaging in a discussion with a sock. As an admin, I can also evaluate G4 instances as well. Another way I can fight vandalism is through CSD. Right now all I can do is tag articles and wait. As an admin, I can delete articles at CSD to help prevent a backlog, though of course not ones I tag myself. As has already been brought up, I can also help clear the backlog at AIV and RFPP. I hope this helps. HickoryOughtShirt?4 (talk) 05:25, 25 April 2019 (UTC)
Additional question from Feminist
16. In what situations would you apply pending changes protection to a page?
A:I would use pending changes protection on articles with a low rate of editing, typically from autoconfirmed users, and the occasional bad edits by IPs and new users. It must be manageable enough to be dealt with one at a time. If too much influx of vandalism is coming in, such as four or more instances of vandalism from non-autoconfirmed users per day, I would semi-protect. A good example I can think of is Phil Kessel who was given pending changes protection in 2013 that lasted until 2018. Semi protection was occasionally added in 2015 when the vandalism got too much for pending changes to handle. This would be a good example of when pending changes protection should be used. HickoryOughtShirt?4 (talk) 05:44, 25 April 2019 (UTC)
Additional question from PaleCloudedWhite
17. Your earliest edits seem quite unlike the ones I made as a newbie, which is not necessarily significant, but I'm wondering if you edited Wikipedia before you opened this account?
A: I previously edited as an IP for about a month before creating an account. HickoryOughtShirt?4 (talk) 20:51, 25 April 2019 (UTC)
Additional question from Deryck C.
18. Thanks for offering to help in the protection and block areas. Following up on your answer to the pending changes question, how do you draw the lines between applying semi-protection, extended confirmed protection, and full protection?
A: Semi Protection should be used to stop vandalism from new or anonymous editors. Before applying it, I would make sure to look in the history and see whether it is one new or anonymous editor who is causing the problem (because blocking that one editor might solve the problem without any need for protection). I would apply extended confirmed protection (ECP) in few cases as semi protection is usually all that's needed. I would apply ECP in the rare case where vandalism continues despite semi-protection. An example of an instance where ECP would be used is Wikipedia:User pages, where there was disruptive editing by multiple autoconfirmed users. I understand that ECP is rarely used and would be very cautious about applying it. Full protection is used in a different way than ECP is; it is usually used to stop edit wars. This would be a helpful alternative to blocking users. An example I can think of is Alligator gar which was recently given Full Protection to stop an edit war and make sure no one had the upper hand in an editing conflict. HickoryOughtShirt?4 (talk) 20:00, 26 April 2019 (UTC)
Additional question from EggRoll97
19. How would you plan to evaluate requests for permissions as an administrator, assuming it is the first permission the person is requesting?
A: I would look in the person's edit history and make sure they had a need for such permissions as well as passed the criteria for such permission. I would also evaluate their request to make sure they fully understood what they were asking for. As an example, I applied for Autopatrolled after I qualified because I knew (and listed in my request) that myself and Flibirigit would be making a lot of articles together and would cause a large backlog at NPP. I was given the permission based on the quality of my articles, there were no significant problems or tags, and the proven need for such permission. HickoryOughtShirt?4 (talk) 20:00, 26 April 2019 (UTC)
Additional question from Fastily
20. When are cool-down blocks acceptable and could you please give an example of how you would deploy one?
A: Blocks that are given with the sole purpose of giving a user time to cool down aren't allowed, however, if the user is being disruptive they can be blocked to prevent further harm to the encyclopedia. For example, if a user breaks 3RR, threatens other users, or harasses them, then a block for disruption can occur. This is because blocks should not be punitive but preventative. If blocking a user who has committed the above actions will prevent further harm to the encyclopedia, then the block would be doing its purpose. I would also only deploy such a block if I wasn't WP:INVOLVED as well. However, in saying this, communication is very important to this encyclopedia. If you go in with guns-a-blazing, then the user will likely reciprocate your tone and constructive conversation cannot happen. I find successful results happen most when I personally approach users and discuss problems assertively but with an understanding of the context. Sometimes dropping a user a line acknowledging their side but letting them know it was over the top can achieve better results than a block.HickoryOughtShirt?4 (talk) 17:44, 27 April 2019 (UTC)
Additional question from PaleCloudedWhite
21. If, as an admin, you were contacted on your talk page by Editor Nice, a non-admin editor with whom you had socialised off-wiki, and they requested that you make a single intervention in a content dispute involving Editor Nice, Editor Might-Be-Nice and Editor Might-Be-Nasty, specifically they requested that you revdel a spiky comment made by Editor Might-Be-Nasty toward Editor Might-Be-Nice, what would be your course of action?
A: It depends on what the content is. "Spiky comment" could vary from borderline uncivil to personal attacks. WP:REVDEL is used only under certain specific, limited circumstances (such as if personal, identifiable information was revealed (which I would also request oversight) or it is grossly insulting, degrading, or offensive). However, if the "Spiky comment" does qualify, it doesn't matter who asks for it. I might guide Editor Nice to the IRC email instead of a public talk page as well, especially if the content should not be in the public record. HickoryOughtShirt?4 (talk) 20:48, 27 April 2019 (UTC)
Additional question from Pudeo
22. Do you plan on participating at AN/I and AE or just anti-vandalism? If you plan so, what kind of a role do you see for yourself? --Pudeo (talk) 08:47, 27 April 2019 (UTC)
A: I think anti-vandalism work can be covered in multiple ways. I see myself being more active at WP:BLPN and WP:COIN (where I already am active) than WP:AE or WP:ANI (unless vandalism happens there, as it often does). I don't often participate at ANI and have yet to ever at AE so if I ever did have to comment, I would do so cautiously. I would investigate claims of offences and take action if necessary. HickoryOughtShirt?4 (talk) 20:48, 27 April 2019 (UTC)
Additional question from Interstellarity
23. An important quality of editors is that they have the competence to work with other editors to make the encyclopedia better. How would you deal with editors that lack the competence necessary to contribute?
A: I would look at Wikipedia:Competence is acquired rather than Wikipedia:Competence is required first. In my experience on Wikipedia, I have dealt with many editors who are ESL, on the spectrum etc. and understand that people learn at different rates. Wikipedia indeed has a learning curve so I would approach any situation doubting someone's competency with absolute caution and AGF. If someone's lack of competency has become disruptive (such as ignoring consensus and refuses to communicate, violating WP:BLP, etc), than a block could occur, although that would be a last resort. As stated earlier, I think personal communication can go a long way to settling disputes. For example, if someone is ESL I might ask another editor who is more fluent in the language to help. I understand that not only is blocking always a last resort but usually questioning someone's competency can be uncivil. HickoryOughtShirt?4 (talk) 04:09, 29 April 2019 (UTC)


Please keep discussion constructive and civil. If you are unfamiliar with the nominee, please thoroughly review their contributions before commenting.

  1. Support as co-nom. TonyBallioni (talk) 01:15, 24 April 2019 (UTC)
  2. Support No major problems, net positive. SemiHypercube 01:24, 24 April 2019 (UTC)
  3. ’Bout time.💵Money💵emoji💵💸 01:28, 24 April 2019 (UTC)
  4. Enthusiastic Support I rarely jump into newly posted RfAs but am making an exception here. Numerous interactions with this editor leave no doubt about their qualifications for the bit. Good luck! -Ad Orientem (talk) 01:29, 24 April 2019 (UTC)
  5. Support: I run into Hickory frequently, and I don't think I've ever had cause to doubt their reports and assessments. I also happened upon a big fat article they wrote the other day; I didn't know Hickory did that too. So yeah, I support. Drmies (talk) 01:31, 24 April 2019 (UTC)
  6. Support This individual is an asset to this website. I am happy to lend my support. Capt. Milokan (talk) 01:41, 24 April 2019 (UTC)
  7. Support I’m glad to see this nomination. I have been aware of HickoryOughtShirt?4 for some time as a person who contributes helpfully all over the ‘pedia. Their experience meets all my criteria, and more importantly they seem to consistently show the type of temperament we look for in an administrator: calm, courteous, patient, and always focused on Wikipedia policy. I feel sure they will be an asset to the admin corps. -- MelanieN (talk) 01:42, 24 April 2019 (UTC)
  8. Good luck. ~ Abelmoschus Esculentus (alt) (talk to me) 01:48, 24 April 2019 (UTC)
  9. Support Hickory is a pretty dedicated vandalism fighter and it is always nice to have more help at AIV. I do hope they will try to not stay up too late and over-exhaust themselves in editing Wikipedia. – XYZt (talk  |  contribs) – 01:53, 24 April 2019 (UTC)
  10. Support Per Richie and the glimpses I have seen of this editor and theri work. I expect some opposition over shortness of tenure but I dont care Thanks,L3X1 ◊distænt write◊ 01:55, 24 April 2019 (UTC)
  11. Support. Consistent contributor with a good attitude in dealing with other editors. Many positives in background support (counter-vandalism, NPR etc). Loopy30 (talk) 01:56, 24 April 2019 (UTC)
  12. Support, solid work on the mundane with sound judgement and patience. Really, just for mopping up the ankle nonsense at Wesley Johnson (basketball) alone. Kuru (talk) 01:59, 24 April 2019 (UTC)
  13. Support, an asset to the project. Hughesdarren (talk) 02:18, 24 April 2019 (UTC)
  14. Support because why the hell not? CoolSkittle (talk) 02:25, 24 April 2019 (UTC)
  15. Support. This is the first time I hear about this editor, but now that I look into Hickory's work the candidate is clearly a strong net positive deserving of adminship. Biblio (talk) 02:30, 24 April 2019 (UTC)
  16. Support as a fellow Canadian, but his edits and contributions seem solid. Two thumbs up from me. QueerFilmNerdtalk 02:32, 24 April 2019 (UTC)
  17. Support, even though he's a Leafs fan. He'll be an asset. schetm (talk) 02:47, 24 April 2019 (UTC)
  18. Support, adminship is not a big deal. Anybody can perform most of the admin actions. ~SS49~ {talk} 03:12, 24 April 2019 (UTC)
  19. Support Specialist at hockey player articles. Generates content. Looks good to me. Also sorry about your team tonight Samir 03:30, 24 April 2019 (UTC)
  20. Support likely net positive. Cas Liber (talk · contribs) 04:10, 24 April 2019 (UTC)
  21. Support with enthusiasm. Diligent, conscientious, good judgment, helpful, good demeanor and positive interactions with others. Works on content as well as in other areas. I have interacted with Hickory on several occasions. Has established trustworthiness. Definitely a net positive. Donner60 (talk) 04:21, 24 April 2019 (UTC)
  22. Absolutely. Though I do wish I understood the username. — 🦊 04:52, 24 April 2019 (UTC)
  23. Support it will be good to have an admin focused on working in these areas. Mccapra (talk) 05:04, 24 April 2019 (UTC)
    Support - I see no problems with this RfA. — Preceding unsigned comment added by AurumPower (talkcontribs) 05:42, 24 April 2019 (UTC)
    !Vote of obviously someone's sock indented. -- Amanda (aka DQ) 09:23, 24 April 2019 (UTC)
  24. Support per above. Solid, respected editor. – Broccoli & Coffee (Oh hai) 06:04, 24 April 2019 (UTC)
  25. Strong support - The candidate both contributes content and is an experienced editor. Reaper Eternal (talk) 06:15, 24 April 2019 (UTC)
  26. Support - I don't often vote at RFA's, but Hickory is a user I see often at AIV and UAA and I think they would be valuable addition for administrating those. Agent00x (talk) 06:44, 24 April 2019 (UTC)
  27. Support - Can't see any reason not to. Deb (talk) 07:12, 24 April 2019 (UTC)
  28. Support as nominator Ritchie333 (talk) (cont) 07:34, 24 April 2019 (UTC)
  29. Support wholeheartedly. I often see them at UAA and they would be immensely helpful there, and I believe in other areas. 331dot (talk) 07:58, 24 April 2019 (UTC)
  30. Support- good answer to my question, decent AfD work, good article content creation. I really see no downsides. Reyk YO! 08:04, 24 April 2019 (UTC)
  31. Support - Thanks for volunteering! Vermont (talk) 09:53, 24 April 2019 (UTC)
  32. Support- Great answers to all the questions :)—NØ 10:18, 24 April 2019 (UTC)
  33. Support. The nomination is convincing and the candidate has adequate experience. Deryck C. 11:21, 24 April 2019 (UTC)
    Withdrawing support (for now) - concerns about misunderstanding of protection policy below seems significant. Deryck C. 13:14, 26 April 2019 (UTC)
    Restoring support after reading the candidate's replies to questions over the last few days. The candidate had misunderstood WP:ECP's purpose, but the support from Kashmiri, Ajraddatz, Tryptofish, and Wugapodes swayed me to come back to the supporters' camp. Deryck C. 12:00, 29 April 2019 (UTC)
  34. Support Gog the Mild (talk) 12:20, 24 April 2019 (UTC)
  35. Support - I haven't yet looked in detail but if Ritchie333 and TonyBallioni are vouching for the candidate, admins I respect and trust, then that's a powerful argument. Per nom! Per nom! Also, the user has good solid content creation and the oppose/neutrals so far don't look like show-stoppers. Cheers.  — Amakuru (talk) 13:26, 24 April 2019 (UTC)
  36. Support good candidate. Jianhui67 TC 14:19, 24 April 2019 (UTC)
  37. Support – I don't see any problems. PCN02WPS (talk | contribs) 14:26, 24 April 2019 (UTC)
  38. Support. Well beyond any reasonable minimal criteria, also pleasant and thoughtful in their discussions. Ifnord (talk) 15:10, 24 April 2019 (UTC)
  39. Support The RfPP mistakes are reasonable in an editor's learning curve. Trustworthy and will learn. Lourdes 15:19, 24 April 2019 (UTC)
  40. Support Looks goods and will be a net-positive to the project. « Gonzo fan2007 (talk) @ 15:32, 24 April 2019 (UTC)
  41. Support The issues raised WRT question 4 are valid, but I don't think it's a big enough deal to make me oppose an experienced and otherwise excellent contributor. Hickory has noted the concerns, and promised to be more cautious with ECP in future - I'm happy to take that at face value and support. GirthSummit (blether) 15:50, 24 April 2019 (UTC)
  42. Support. A dedicated vandalism fighter. --Miaow 16:52, 24 April 2019 (UTC)
  43. Support. My interactions with this editor lead me to trust them. They have the interests of the encyclopedia at heart. Undoubtedly they will make mistakes, but show that they will learn and improve. Will be glad to have you as an admin!Jacona (talk) 16:53, 24 April 2019 (UTC)
  44. Support. Thank you for stepping forward and wanting to take on more responsibility. -- Tavix (talk) 16:53, 24 April 2019 (UTC)
  45. Support. As Ritchie333 has nominated this Wikipedian, I trust his judgement. SethWhales talk 17:15, 24 April 2019 (UTC)
  46. Support A quality contributor in multiple areas. The project could use more admins who have personal experience starting out as an editor in today's Wikipedia. Bakazaka (talk) 17:19, 24 April 2019 (UTC)
  47. Support I'd thought of asking them about RFA myself as they make a ton of valid reports at UAA. I'm not finding the opposes that compelling, admins don't have to be perfect, or have 500,000 edits, just a decent understanding of when to use the tools and I'm confident that is the case here. Beeblebrox (talk) 17:27, 24 April 2019 (UTC)
  48. I'm not wildly keen on people who request adminship on the basis of vandalfighting, as historically we've had a longstanding problem of people who take RFA as a license to play WikiCop, cause a bunch of problems, and prove very difficult to rein in. However, I'm not really seeing that kind of issue here. HOS appears to be someone who's willing to admit they don't know everything and to listen to other people, which is something we could do with more of. I don't find any of the opposes remotely concerning in this particular case. ‑ Iridescent 17:35, 24 April 2019 (UTC)
  49. Support though I've had limited interactions with this user, they've all been positive. Good admin temperament and vouching from respected members of community. Enwebb (talk) 17:38, 24 April 2019 (UTC)
  50. Support number of edits is fine, but tenure length is bleeding edge for me, albeit on the right side of bleeding edge. Does not strike me as a hat collector. I have seen him around and been positively impressed. Could do better regarding semi-vs-ECP, but I think the candidate will take it on board. Regarding conflict resolution, not every admin frequents our most contentious areas, nor do they need to, to be a net positive for the project. I don't get any sense that the project will be harmed if candidate accesses the tools, and I see many areas that will be improved. 78.26 (spin me / revolutions) 17:43, 24 April 2019 (UTC)
  51. I've seen HOS?4 around at AIV/RfPP/UAA a bunch, they always make good reports and they make a lot of reports; it'd definitely be a net gain having them on the janitor team. Autopatrolled user with a fine CSD log suggests good understanding of inclusion and content policies. I think the concerns about over-requesting ECP are valid, but it is a very recent shift. Per XTools, HOS has made roughly 411 RfPP requests since the beginning of 2018; 36 (~9%) were for ECP, and all but five of those were made in the past three months. I'd like to know from HickoryOughtShirt?4 what, if anything, prompted the change, but I'm not too concerned about it after this. Were it a longer ongoing issue maybe, but the many editors (correctly) telling HOS that it's not appropriate should be sufficient to set HOS straight. Answers to some questions could be a better, in particular to question 9, but they're approaching milquetoast, not alarum; indeed, some indicate that HOS should occasionally be more confident in their actions. Concerns over tenure are not warranted here, user has a more-than-sufficient track record on which to measure their judgment. ~ Amory (utc) 18:01, 24 April 2019 (UTC)
    Also, I support more sysops with annoying characters in their username, on the off-chance that any malicious attacker/compromise script gets borked by not appropriate sanitizing its inputs. (I'm half-joking, but which half I'm not sure!) ~ Amory (utc) 18:05, 24 April 2019 (UTC)
    ❤️.....❤️ 04:24, 25 April 2019 (UTC)
  52. Support. In just a few years, this editor was able to accomplish what others with much more tenure have failed to do. HickoryOughtShirt?4 is passionate and has a purpose. I support nominees who have a clue and want to take on more responsibilities. MX () 18:08, 24 April 2019 (UTC)
  53. Support. We don't need perfection in admin candidates; we need competence in one or more admin areas, a willingness to learn, and the ability to communicate constructively. I'm seeing all of those things, and that's enough for me. Vanamonde (Talk) 18:12, 24 April 2019 (UTC)
  54. Strong support. ~Swarm~ {sting} 18:20, 24 April 2019 (UTC)
    Support Without a doubt! I fought vandalism with this user for quite a long time. INeedSupport :3 18:37, 24 April 2019 (UTC)
    Moved to Neutral INeedSupport :3 16:57, 25 April 2019 (UTC)
  55. Support, precisely what Vanamonde93 said just above. -- zzuuzz (talk) 18:49, 24 April 2019 (UTC)
  56. Support This user has been a huge help in fighting vandalism. I often try to report users at AIV only to find that this user has beaten me to the punch! I've long admired this user's diligence, patience, civility, and fairness. Giving them the admin tools will be a huge net positive for the project. Aoi (青い) (talk) 19:00, 24 April 2019 (UTC)
  57. Support with enthusiasm. - Julietdeltalima (talk) 20:04, 24 April 2019 (UTC)
  58. Support, I see the candidate quite a lot requesting protection at RFPP, and their requests are typically sufficiently justified.--Ymblanter (talk) 20:38, 24 April 2019 (UTC)
  59. Support I've seen them around doing a lot of vandal-fighting. I think they can be trusted with the mop.-- 5 albert square (talk) 21:02, 24 April 2019 (UTC)
  60. Has more than enough experience and exhibits sounds judgement, with no indications that they'd abuse or flagrantly misuse the tools. Most admins go their entire careers here without any major confrontations or disputes, so I'm not convinced by the opposes demanding to see combat scars before they'd reconsider. I'll grant that concerns about the candidate's trigger-happiness do have merit; there are a handful of overzealous RFPP and UAA reports to be found, if one digs deep enough (per Andrew D., "CoastalMountainSpotter" was a bad report and a bad block). That said, the vast majority are within policy and collectively helping to keep the project clean. Like I always say, adminship is not a "perfect editor" award. – Juliancolton | Talk 21:06, 24 April 2019 (UTC)
  61. Support per Vanamonde93. Tenure is a bit short for me, but that's certainly not a deal-breaker. GABgab 21:33, 24 April 2019 (UTC)
  62. Support Although I haven't crossed paths with the candidate yet, their noms are trustworthy and answers to the questions are good. Suitable temperament for adminship and a willingness to learn from mistakes (which we all make) enable me to overlook the opposes. Definite net positive. Miniapolis 21:43, 24 April 2019 (UTC)
  63. Support – Like Aoi, I have often tried to revert vandalism / report vandals to AIV only to find that HickoryOughtShirt?4 was faster Face-smile.svg. I find them to be clueful and have no reason to believe they will abuse the mop. –FlyingAce✈hello 21:53, 24 April 2019 (UTC)
  64. Support HickoryOughtShirt?4 is a competent editor who will make good use of the tools. Also, I think 18 months and 50,000+ edits is enough to meet basic tenure requirements. Spirit of Eagle (talk) 23:01, 24 April 2019 (UTC)
  65. Support I've seen this user actively cleaning up vandalism and being an active recent changes patroller. Although I don't know how much information he may or may not know regarding this project, I am inclined to support them to become an admin. As others have mentioned, since the user is considered fairly new I have my faith that he is a quick learner in admin-ship and undoubtedly will be an asset as an admin. --Wikiemirati (talk) 01:08, 25 April 2019 (UTC)
  66. Support I met the candidate at an edit-a-thon, found them impressively helpful and remember thinking: "You're going to make a good admin some day". Vexations (talk) 01:38, 25 April 2019 (UTC)
  67. Support Competent and hard-working vandal fighter. -- Scott Burley (talk) 03:04, 25 April 2019 (UTC)
  68. Support no reason to think that this user would abuse the tools --rogerd (talk) 03:13, 25 April 2019 (UTC)
  69. I don't see anything to suggest that this editor would abuse the tools. SQLQuery me! 03:45, 25 April 2019 (UTC)
  70. Support. Seems like a fine candidate. OhanaUnitedTalk page 03:50, 25 April 2019 (UTC)
  71. Support 18mo is long enough for me, vandal fighting supported by AIV stats, and what Vanamonde said. Levivich 05:30, 25 April 2019 (UTC)
  72. Support - meets my criteria. Clearly a net positive. A decade of tenure or religious participation at the drama boards should not be a prerequisite for adminship in my opinion. EclipseDude (Chase Totality) 06:03, 25 April 2019 (UTC)
  73. Weak Support candidate has a nice mix of content contributions and anti vandalism work. There have been a couple of comments in the Oppose section about tenure, but the candidate has been active since late 2017, about 18 months, easily long enough for a first run at RFA. Weak because of the Extended confirmed issue raised in Q4, support because of their assurance of learning from that criticism in their answer to Q4. Having read some of their articles created I would also bring the candidate's attention to their use of the word "currently". ϢereSpielChequers 07:18, 25 April 2019 (UTC)
  74. Support personally I'd like to see more content creation and development to GA at least, but what I've seen of HickoryOughtShirt?4 has been positive, and I'm minded to support, provided they take on board the ECP vs. semi feedback. Peacemaker67 (click to talk to me) 07:25, 25 April 2019 (UTC)
  75. HickoryOughtShirt?4 hasn't been here all that long, but he's got enough experience and will help with backlogs. NinjaRobotPirate (talk) 07:38, 25 April 2019 (UTC)
  76. Cautious support. As their response to Q4 show, the nominee still needs to learn more about page protection policies (and perhaps many more rules). However, in all honesty, this is not something that can't be done over an evening or two. For now, I don't see any signals that the candidate cannot be trusted. I also keep in mind that desysopping always exists as an option. So, for now, my cautious support. — kashmīrī TALK 07:42, 25 April 2019 (UTC)
  77. Support I don't see an issue with the months of experience. HickoryOughtShirt?4 has demonstrated good content creation, sufficient understanding of our policies and a commitment to fight vandalism. I see no indication whatsoever that the user may abuse or misuse the tools, so I thank him for his commitment to undertake this new responsibility and I am happy to support his nomination. --Crystallizedcarbon (talk) 07:58, 25 April 2019 (UTC)
  78. Support, meets my RFA criteria. Tenure is a stupid reason to oppose a perfectly good candidate. Like some of the other supporters above, I'm happy to see the response to constructive criticism about which levels of protection to use and when IffyChat -- 10:24, 25 April 2019 (UTC)
  79. Support I like the answer to Q5, which is a common enough question founded on the weird premise that someone might like, for instance, WP:RS over WP:NPA. I mean, a thoughtful editor might have observations on which policies have had unintended consequences in the 15+ years of enwiki's existence, but that's not what the question is asking for. Anyway, the candidate answered it thoughtfully, as they did with Q6 and Q7 which shouldn't have appeared in this RfA either. I'll also note the weirdness of opposers who apparently want RfA candidates, who edit for free like everyone else, to get into bunfights they have no appetite for as evidenced by comments like "These days admins must have experience in handling any and all kinds of contention." Sigh. Let's just have a better RfA for whoever the next candidate is. Airbornemihir (talk) 10:27, 25 April 2019 (UTC)
  80. Support. Shows the WP acumen to use tools (both content and non-admin rights), the enthusiam for WP to be impactful with the tools (we need that), and demonstrates the temperment to resolve and learn from the inevitable mistakes that comes with getting any new WP rights. Britishfinance (talk) 11:04, 25 April 2019 (UTC)
  81. Support Seems to be a good candidate, users I trust support so I'll join in. Abzeronow (talk) 14:55, 25 April 2019 (UTC)
  82. I assume that you've taken into account comments made by other users regarding inappropriate RFPP requests. feminist (talk) 15:45, 25 April 2019 (UTC)
  83. Support Vandal-fighting experience and content contributor. 18 months and 50k+ edits is plenty of experience to establish a track record. Candidate is reacting well to concerns about some of his answers, and I'm confident he'll continue to do so. Thanks for stepping up. MarginalCost (talk) 15:50, 25 April 2019 (UTC)
  84. Support as a net positive. I'm not convinced by any of the opposing rationale. --Laser brain (talk) 16:18, 25 April 2019 (UTC)
  85. Support Net positive. Nova Crystallis (Talk) 16:30, 25 April 2019 (UTC)
  86. Support Although Q4 was slightly troubling, they are an all round good editor and I see no reason why they are not suited to the mop. I would suggest that the editor considers it (like they have done in their answer), however, this isn't a big deal and we are all human (so mistakes can be made). Dreamy Jazz 🎷 talk to me | my contributions 16:34, 25 April 2019 (UTC)
  87. Weak Support - The tenure and the answer to Q4 are both a concern for me however I have to agree with Vanamonde there is no perfect candidate and as long as they don't delete the main page then I don't see why they shouldn't generally be granted the tools. –Davey2010Talk 18:40, 25 April 2019 (UTC)
  88. Support - seldom have I seen an editor who has developed as complete and nuanced understanding of Wikipedia as fast as Hickory has. He will not delete the mainpage. John from Idegon (talk) 18:49, 25 April 2019 (UTC)
    I like that for a quick and simple guide to RFA voting. Will the candidate delete the main page if given the tools? (y/n)FlyingAce✈hello 22:43, 25 April 2019 (UTC)
  89. Support I don’t see why not. Nothing wrong with having experience in a smaller number of areas, and experience will always continue to be gained. Aiken D 18:59, 25 April 2019 (UTC)
  90. Support per nom. DrewieStewie (talk) 21:15, 25 April 2019 (UTC)
  91. Support - civilized, pleasant, clued-up editor with good skills and excellent commitment. DBaK (talk) 21:48, 25 April 2019 (UTC)
  92. Support Their length of tenure did give me pause but they have enough of a track record for me to trust them with the tools. Pawnkingthree (talk) 21:54, 25 April 2019 (UTC)
  93. Support Clearly a capable all-rounder. We need people like him. Moriori (talk) 22:17, 25 April 2019 (UTC)
  94. Hickory has earned my support, Kevin (aka L235 · t · c) 23:19, 25 April 2019 (UTC)
  95. Will make a fine addition. El_C 23:47, 25 April 2019 (UTC)
  96. Heck Yea Thegooduser Life Begins With a Smile :) 🍁 00:28, 26 April 2019 (UTC)
  97. Support Can certainly be trusted; I've come across his edits in numerous areas in the past and he has thanked me for numerous edits, and I his. JACKINTHEBOXTALK 00:32, 26 April 2019 (UTC)
  98. Support - Although tenure and some of the answers gave me pause, there is nothing concerning enough to put me in the oppose camp and the candidate seems open to feedback. No reason not to trust them with the tools. -- Dane talk 00:40, 26 April 2019 (UTC)
  99. Support - Fine candidate. Looks like a mistake was made in the answer to the protection question, but that's fine. So long as the candidate can learn, they will do fine with access to a few extra buttons. -- Ajraddatz (talk) 01:16, 26 April 2019 (UTC)
  100. Support per nom and per questionable opposes. —pythoncoder (talk | contribs) 02:27, 26 April 2019 (UTC)
  101. Support - Competent user who can be trusted to make good use of the admin tools. utcursch | talk 02:38, 26 April 2019 (UTC)
  102. Innisfree987 (talk) 03:38, 26 April 2019 (UTC)
  103. Support. After a very thorough, exhaustive investigation of this user's editing history I've come to the conclusion that he's Canadian and can do no wrong. ;) -- œ 03:56, 26 April 2019 (UTC)
  104. Support per OlEnglish. Also, Hickory has done good work at NPP, which I hope continues. – bradv🍁 04:20, 26 April 2019 (UTC)
  105. Support Per œ.... Here's to another member of the Canadian Cabal. You fellas editors up north (don't want to leave out the rest & best!) are spectacular. But honestly, any green-ness from the candidate ought to wear off in no time.  Spintendo  04:27, 26 April 2019 (UTC)
  106. Support Per others--BoothSift 05:00, 26 April 2019 (UTC)
  107. Support. I'm not looking for millions of edits or decades of tenure, just someone who has been here long enough and done enough to show they know how things work and will use the admin tools well. HickoryOughtShirt?4 passes that test easily, and I don't find any of the opposes remotely convincing. Boing! said Zebedee (talk) 05:12, 26 April 2019 (UTC)
  108. Support Seems to be helpful and a net positive to the project, at least from the editor's history. Swordman97 talk to me 06:37, 26 April 2019 (UTC)
  109. Support. No Problems with the candidate, good luck! - JJBullet (Talk) 10:35, 26 April 2019 (UTC)
  110. Support good candidate. Tolly4bolly 11:39, 26 April 2019 (UTC)
  111. Support Despite the concerns raised in the oppose !votes, I think Hickory has CLUE, will be accountable for their actions, and will ultimately be a net positive as an administrator. ceranthor 13:42, 26 April 2019 (UTC)
  112. Support Knows the policies and wants to do good work. Not at all concerned about being over-eager, as some of the opposition is. Psu256 (talk) 14:33, 26 April 2019 (UTC)
  113. Support: I agree that he is diligent, helpful and has good judgment. Will make a trusted Admin. - Ret.Prof (talk) 14:39, 26 April 2019 (UTC)
  114. Why not? Zingarese talk · contribs`
  115. Support: I like his answers to most of the questions, even the weird ones like #14. As per usual some of the opposers have ridiculous demands like multiple GAs or an FA--demands that penalize admin applicants who might be a little shaky with English, or applicants who might be autistic and unable or disinterested in writing GAs. Adminship is a trust position and I trust this experienced, non-problematic user. And in areas where Hickory might not be as strong, I trust him to tread carefully and cross his Ts and dot his Is. Cyphoidbomb (talk) 15:41, 26 April 2019 (UTC)
  116. Support None of the concerns raised below, nor a review of HickoryOughtShirt?4's edits, convince me that they will abuse or be incapable of using the admin toolset. Unlike brightline RfA criteria that some editors have with regard to number of edits, articles created etc., I like to see an editor who is competent, clueful, is able to express themselves clearly, and who is willing to spend some of their volunteer time here helping out with the various janitorial tasks that pile up. HickoryOughtShirt?4 is all of these.-- Jezebel's Ponyobons mots 15:56, 26 April 2019 (UTC)
  117. Support I am always given pause when there is a candidate who has been active for a shorter time than my three years. However, the specific answers the candidate gave in response to many of the questions has won me over. -- Dolotta (talk) 16:44, 26 April 2019 (UTC)
  118. Support. When one of the concerns is over possibly too-short tenure, I look to see what problems, if any, have occurred due to lack of experience. Here, the one issue that has come out is the one over extended-confirmed protection. I'm satisfied that this does not reflect some sort of underlying flaw in judgment and that the candidate gets it now and understands how to handle it in the future. Other than that, the other criticisms strike me as a typical assortment of oppose views held by individual editors, but not as indicating any serious pattern. I don't think I've crossed paths with the candidate, but I'm seeing someone with content creation experience and articulate answers to questions. And I respect the noms and some other editors who have vouched for the candidate's qualifications. So, taking that together, I'm seeing enough experience, and a clear net positive. --Tryptofish (talk) 17:18, 26 April 2019 (UTC)
  119. Support Meets my RfA criteria. Furthermore, also my implicit vote towards bringing down the bar for adminship (the point of contention here somehow being 18 months of experience). --qedk (t c) 18:31, 26 April 2019 (UTC)
  120. Support Sounds like a good candidate for admin Rollidan (talk) 19:11, 26 April 2019 (UTC)
  121. Support. Fully qualified candidate. I disagree with the concerns about length of tenure. Some of the other concerns are more substantial, but I am confident the candidate will take the feedback he's received here into account going forward. Newyorkbrad (talk) 20:01, 26 April 2019 (UTC)
  122. Support - Good editing/writing skills, confortable fighting vandalism, experience. Spyder212 (talk) 21:23, 26 April 2019 (UTC)
  123. Support - Conscientious. S0091 (talk) 23:12, 26 April 2019 (UTC)
  124. Support (Moved from "Neutral") My earlier hesitation to support was based upon the response to Q4 and wanting to see evidence that they'd properly apply page protection policy. After reading comments by NewYorkBrad above as well as SoWhy and Amory below, I don't think that argument holds much water. I may not have evidence from RFPP, but I do have evidence from their cluefullness and competence that they will look into and correctly apply page protection policy going forward. I don't believe the editor will misuse the tools. Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 00:39, 27 April 2019 (UTC)
  125. Support Hickory thanked Tristan for reverted vandalism on Mel Brooks and Cody Zeller. Hickory would be proud using admin tools, and doing great as well. Carl Tristan Orense 01:53, 27 April 2019 (UTC)
  126. Support A net positive editor. I created a 15 minute stub on Virginia Overton a few weeks back, which became a DYK in no time thanks to this editor's efforts. Those are the kind of of dedicated editors we should keep and recognize. ThatMontrealIP (talk) 05:04, 27 April 2019 (UTC)
  127. Support good all-round editor. Overdue to be honest. Gizza (t)(c) 05:08, 27 April 2019 (UTC)
  128. Support I find it very hard to understand how anyone can oppose a candidate who wrote a Good article about a 19 year old Jewish hockey player born in Orlando, Florida who played for the University of Michigan before signing with the NHL Vancouver Canucks, and scored a goal in his first professional game. More seriously, one concern seems to be that the editor is too new. I became an adminstrator eight years after starting to edit, so I might be expected to sympathize with this argument. I don't. This editor has been here long enough for reasonable people to see that their sincere goal is to do their best to improve this encyclopedia. Some oppose because the nominee is interested in fighting vandalism. Hey, I am not a dedicated vandalism fighter but revert it and block vandals quite regularly when vandalism pops up on my watch list. Kudos to vandalism fighters who comply with our policies and guidelines. Yes, perhaps they have been a bit too assertive in requesting ECP, but requesting is not granting, and the discussion here shows a willingness to learn when concerns are expressed, and a cautious attitude going forward. Those are the traits of a good administrator. I have read all of the opposes so far, and see nothing that convinces me that it would be a mistake to approve this RfA. Cullen328 Let's discuss it 05:22, 27 April 2019 (UTC)
  129. Support - clearly qualified candidate. Tazerdadog (talk) 06:48, 27 April 2019 (UTC)
  130. Support: not a jerk, has a clue. Nomination statements from Ritchie333 and TonyBallioni are compelling and the basic stats look good. I'm not concerned with the objections raised on the grounds of length of tenure or protection requests. Everyone makes a bum request or a duff call every now and again. I don't see a pervasive pattern of repeated poor requests or calls and I have no reason to believe Hickory will abuse the tools. SITH (talk) 12:40, 27 April 2019 (UTC)
  131. Support Not concerned with protection and deletion policy concerns expressed by the opposers. The tool is more about trust than understanding each intricate part of each policy. Tony & Ritchie make a good trust argument.--v/r - TP 16:28, 27 April 2019 (UTC)
  132. Support I've wavered on this one over the last few days but end up finding myself here. His tenure is a non-issue, and I don't think he would misuse the tools intentionally, which is what this boils down to. My only word of advise would be to not think that you need to be present in multiple areas of adminship at once while you are still finding your footing. Nihlus 16:50, 27 April 2019 (UTC)
  133. Support The best admins are those who know their limits and heed them (I know my worst times have been when I've not done that), and the discussion gives solid evidence that Unique Password As School Login understands and will heed limits. "Too new" opposition is rubbish; HickoryOughtShirt has been here for almost a year and a half! That's far longer than needed (and lots of good admins were promoted with much less time); this isn't a seventeen-week or seventeen-day editing period, but seventeen-month. Nyttend (talk) 20:55, 27 April 2019 (UTC)
  134. Support Good luck.--Mona.N (talk) 23:57, 27 April 2019 (UTC)
  135. Support – Appears to have reasonably good judgment, and is sufficiently experienced. Paul Erik (talk)(contribs) 00:17, 28 April 2019 (UTC)
  136. Support Q4 gave me a pause, but I found the candidate's answers to later questions to be satisfactory. Despite their short tenure, I'm confident that HickoryOughtShirt?4 will exercise caution when performing admin actions and read up on the relevant policies -FASTILY 00:32, 28 April 2019 (UTC)
  137. Support: More than a sufficient number of edits and amount of time. Shows good judgement and good temper. Not a big deal.  SchreiberBike | ⌨  00:38, 28 April 2019 (UTC)
  138. Support – A year and a half of activity and plenty of experience in a variety of different areas. I don't expect a certain number of GAs or FAs, nor do I need an editor to have several years under their belt before supporting their RfA. I just expect a reasonable amount of experience and the right temperament for the job, and I think Hickory has both. Kurtis (talk) 02:46, 28 April 2019 (UTC)
  139. Support can be trusted with the tools, has demonstrated good judgement, adminship is meant to be WP:NOBIGDEAL so a tenure of 18 months is more than enough to show commitment to the project. --DannyS712 (talk) 06:22, 28 April 2019 (UTC)
  140. Support, precious --Gerda Arendt (talk) 07:21, 28 April 2019 (UTC)
  141. Support already have 30K mainspace edits(60%) and a prolific vandal fighter. There are other factors as well in support but I am not repeating what others have already stated. Only 32 AfD votes IMHO is less to properly judge, I would have liked to see more AfD participation. I am sure you have read the oppose votes and would incorporate those suggestions so that those concerns do not arise. Overall I feel you are ready for the admin bits. Good luck. --DBigXray 07:57, 28 April 2019 (UTC)
  142. Support - active, dutiful, and has a clue. Stormy clouds (talk) 11:11, 28 April 2019 (UTC)
  143. Support net positive.Pharaoh of the Wizards (talk) 12:05, 28 April 2019 (UTC)
  144. Support - solid if not spectacular addition to the ranks of those who wield the Mop-and-Bucket. --Orange Mike | Talk 12:22, 28 April 2019 (UTC)
  145. Support - As per co-nominator. Sincerely, Masum Reza 14:37, 28 April 2019 (UTC)
  146. Support ticks all my boxes. FitIndia Talk 17:02, 28 April 2019 (UTC)
  147. Weak Support the edit/tenure aspect is absolutely fine. They look like they're fine on the AIV side. The weak is because of the extended-confirm bit discussed so much below. I felt they were able to learn, and having had the issue so thoroughly pointed out, I felt they would be an overall benefit to the mop. Nosebagbear (talk) 18:27, 28 April 2019 (UTC)
  148. Support Seems capable and has some good answers to the questions. Not concerned about tenure, especially based on this record. Best of luck! Lord Roem ~ (talk) 20:21, 28 April 2019 (UTC)
  149. Support Any interactions that I've had with them have been positive and seeing their interactions with other editors give me no concern about temperament. Answers to questions and editing record reveal enough to me to trust with the mop. Deadman137 (talk) 21:20, 28 April 2019 (UTC)
  150. Support. Review of noticeboards and your talk archives finds conduct well within bounds of expected behavior. Competence in areas of editing work focus. Concerns of "too soon, not enough experience" in the oppose and neutral sections are unpersuasive; the RfA bar was lowered so that editors like you would run sooner rather than later. Go Blue Jackets! nice save!wbm1058 (talk) 21:25, 28 April 2019 (UTC)
  151. Support Consistent contributor with a good attitude in dealing with other editors. Many positives in background support (counter-vandalism, NPR etc). Support, solid work on the mundane with sound judgement and patience. Has good judgment, and is sufficiently experienced. Lubbad85 () 23:10, 28 April 2019 (UTC)
  152. Utterly unconvinced by the opposes. This is admin, not CU/OS/crat/ArbCom so 18 months is fine for me. As far as extendedconfirmed protection, I'm not even sure that 50% of admins know about it given that it came out within the last few years. --Rschen7754 22:34, 28 April 2019 (UTC)
  153. Support - while the user is relatively new compared to other RfA applications, I've seen what they've done and they seem ready and able to handle the role. Kirbanzo (userpage - talk - contribs) 01:23, 29 April 2019 (UTC)
  154. Support I'm not able to oppose on the basis of tenure - I became an admin 16 months after my first edit, and have yet to delete the main page in the almost 12 years since then. I see no reasons for concern. Acroterion (talk) 01:28, 29 April 2019 (UTC)
    @Acroterion: - so many opportunities missed! Nosebagbear (talk)
  155. Support - All the best to you. Your mop is going to need several rinsings before you know it. Neovu79 (talk) 03:26, 29 April 2019 (UTC)
  156. Support. Strong anti-vandalism work. — Newslinger talk 06:05, 29 April 2019 (UTC)
  157. Support. No objections. --Gereon K. (talk) 10:30, 29 April 2019 (UTC)
  158. Support as good counter-vandalism work, will be a good addition as an admin. Rubbish computer (Talk: Contribs) 17:26, 29 April 2019 (UTC)
  159. Support Why not? Double sharp (talk) 17:47, 29 April 2019 (UTC)
  160. Support Seen HickoryOughtShirt's good work as an anti-vandalism patroller, has a good attitude, seems reasonably experienced, answers to the above questions don't raise red flags for me. Looking forward to having another admin working AIV. creffett (talk) 18:58, 29 April 2019 (UTC)
  161. Support, looks solid on a check of edits. The oppose reasons I see are unconvincing. 18 months of solid experience is in no way too soon, and while some of the ECP requests were erroneous, the candidate has shown willingness to learn from those mistakes. If we expect candidates to never have made an error, we'll never have any at all. Seraphimblade Talk to me 19:43, 29 April 2019 (UTC)
  162. Support - trustworthy editor and vandal fighter. PhilKnight (talk) 19:57, 29 April 2019 (UTC)
  163. Support Clueful and dedicated editor with good temperament. As some of the opposers have noted, the candidate has made some good-faith errors at RFPP, and there are (inevitably) admin-areas they haven't delved into. But given the qualities on display, I don't doubt that HOS?4 will take this feedback into account, be cautious when wading into new areas, and wield the tools responsibly. Abecedare (talk) 22:40, 29 April 2019 (UTC)
  164. Support Strong answers: no objections. --Balabinrm (talk) 23:13, 29 April 2019 (UTC)
  165. Support He probably was not here long, but is fully qualified to be one. Interstellarity (talk) 23:16, 29 April 2019 (UTC)
  166. Support (edit conflict) - No objections! Class455 (talk|stand clear of the doors!) 23:18, 29 April 2019 (UTC)
  167. Stephen 23:49, 29 April 2019 (UTC)
  168. Support Of course. Shellwood (talk) 01:03, 30 April 2019 (UTC)
  169. Support I have never come across the candidate previously, but on an examination of their history I find nothing egregious. Solid, consistent work. For me, the tenure is a bit on the short side, but that said, some people are very quick to pick up the essentials of Wikipedia editing and policies, and certainly meets my criteria. A brilliant answer to Q23. Some opposes may be legitimate but on the whole are unconvincing. Kudpung กุดผึ้ง (talk) 01:07, 30 April 2019 (UTC)
  170. Support As an RFPP regular, I do remember being mildly annoyed at a few instances where the candidate requested ECP when there appeared to be no need for it. However, I've found their contributions to be overwhelmingly positive, and I believe they'll make a capable, careful, and considerate admin. Airplaneman 02:16, 30 April 2019 (UTC)
  171. Support Net positive. Kpgjhpjm 03:11, 30 April 2019 (UTC)
  172. Support and good luck. Sro23 (talk) 03:46, 30 April 2019 (UTC)
  173. Support. Competent enough to know their own limits, which is what really matters. As to comments on short tenure, well this is just sad, and IMO justifies taking the occasional risk on some "new blood", not that I think HOS?4 is a particularly strong risk. Suffusion of Yellow (talk) 05:43, 30 April 2019 (UTC)
  174. Support Their talk page archives reveal how they have listened and developed rapidly as a competent editor in a relatively short period of time (impressive in itself), and they've clearly made significant contributions in the field of anti-vandalism. It seems unreasonable to expect any successful RfA candidate to instantly become "the best admin ever", and I do sometimes wonder whether some new admins feel they receive enough support or guidance from the longer-established janitors in their early days here with the mop. Nothing in HOS's history or comments suggests they aren't open to listening and improving on feedback, and a new admin that can do that is far better than one who cannot. Nick Moyes (talk) 09:03, 30 April 2019 (UTC)
  175. Cautious support My impression is that a fair chunk of the candidate's edits are vandalism reversions, and I suspect that their experience of conflict resolution is limited, however they seem to have an amenable disposition and concern to follow policy, which should serve them well in this area. I would have preferred their answer to my question 21 to have explicitly recognised that real care should be taken by an admin when they are introduced to a conflict via a friend, as this can so easily result in a skewed assessment, however the wording of the question probably had limitations, and the candidate did recognise that their approach would depend on the content of the dispute. Overall, my impression is that things probably won't go horribly wrong if they just learn as they go along. PaleCloudedWhite (talk) 09:45, 30 April 2019 (UTC)
  176. Support good luck and don’t F it up! NJA (t/c) 12:14, 30 April 2019 (UTC)
  177. Support on review. No issues here and meets my criteria. ZettaComposer (talk) 12:21, 30 April 2019 (UTC)
  178. Support. Hickory is a helpful and humble user. He is always willing to assists others, willing to admit if an error is made, and to learn from his mistakes. I am confident he will be an asset to Wikipedia as an admin. Flibirigit (talk) 15:58, 30 April 2019 (UTC)
  179. support Seen 'm around. does not need GA's or FA's to be an admin. Has sufficient experience in admin related areas. Net positive. DlohCierekim 18:16, 30 April 2019 (UTC)
  180. Support Definitely qualified for the mop. EggRoll97 (talk) 20:02, 30 April 2019 (UTC)
  181. Support. Experienced, and even better I like their demeanour. Will make a good admin. AGK ■ 20:36, 30 April 2019 (UTC)
  182. The answer to Question 4 is perfectly fine. Benoît Bastien is a wikipedia horror story: a little-watched BLP. Worse still, it's a football referee, who could easily be a vandalism target from time to time. The problem with these shit "articles" is that the vandalism can just sit there unnoticed especially if it doesn't trigger one of the bot filter machine things or whatever they're called. Protecting it for a few hours in response to one instance of vandalism is stupid. Better to delete the article or, failing that, exercise our moral duty to its subject by preventing new or unregistered users from touching it until they've implicitly earnt trust by racking up the required tenure and number of edits. Anyone who disagrees is an idiot. And where the hell has the auto-sign button in the editing box gone? --Mkativerata (talk) 20:45, 30 April 2019 (UTC)
  1. Oppose - Editor for the past year and a half, wanted the tools six months ago? right after they'd received NPR? That alone gives me pause. Being given the tool to block and protect would be very helpful - Mmm... blocking is a tool of last resort. It should not be the first thing in your "arsenal". Moreover, I took a look at your RfPPs in light of Skygazer's question. You requested ECP for Jake Gardiner today. The article has been edited disruptively by some IPs. The same is true of Nikita Kucherov, Andrei Svechnikov, Nazem Kadri and Benoît Bastien where you've requested ECP over the past week or so. You appear to regularly ask for ECP to combat disruptive IPs, this is not what ECP is for. Pressingly though, your other main tool request is to enact page protection. I don't think you have the knowledge to be trusted with that tool. In the case of Enes Kanter, which I skipped over in the above list, well at least one of the editors is AC. Of course, naturally, I have encountered conflict and disagreed with editors, especially in contentious areas - Perfect, except the example of conflict you give is to a page with less than 50 edits total and isn't really a conflict. That's unconvincing. If that's the best example of conflict resolution you have, then you don't have any experience dealing with conflict. If it's not, then why bring it up? And it's from six months ago to boot. In sum, I don't think this user is ready to use the tools they are requesting. Mr rnddude (talk) 03:41, 24 April 2019 (UTC)
    On the first point, I was the person who approached them 6 months ago to urge them to think about RfA down the line and pinged Ritchie333 about it to make him aware. If you read the full conversation, you’ll see I preemptively gave them NPR, and that they are one of the single most humble and authentic users on the project, who actually was not trying to set a campaign up for RfA, but was approached being told after 11 months that they had the potential to be a good admin in the future.
    Speaking as one of the more conservative people when it comes to reviewing RfPP, I can get why the question was asked/the concern. At the same time, something that I’ve come to realize over time is that sports bios in particular tend to attract a lot of disruption around specific sporting events, and that you do get woodwork autoconfirmed accounts coming out to vandalize, etc. it’s not an excuse for pre-emotive protection, but I certainly get why sports editors are frustrated with it and read the response as explaining the past actions rather than being indicative of future performance, especially as they already have explained that they have no intent of protecting preemptively. People are allowed to be frustrated with policy based on experience. What matters is the commitment to follow consensus and policy, even if frustrated. I see nothing in any of their actions or responses that suggests they would do otherwise. TonyBallioni (talk) 03:53, 24 April 2019 (UTC)
    TonyBallioni - Thank you for the clarification regarding the first point. That changes my perception from what appeared to me to be hat collection. On the second point, read the response as explaining the past actions just doesn't gel with what I'm seeing. This isn't an issue that I'd dug up from months ago, it was from an hour before the RfA was initiated. The initial answer that Hickory gave to Q4 was carefully worded so as to not rule out them violating the policy on consideration. It took a follow-up to firm up that they'd abide by policy. Mr rnddude (talk) 17:39, 26 April 2019 (UTC)
  2. Oppose per the Rnd dude analysis. The answer to Q4 is indeed troubling: Wants to work in RFPP but pre-emptively ECP's pages against IP users? No thanks; there's enough of that kind of thing already, and promising to follow policy after becoming an admin isn't worth much when one has failed to do so before. More nuance is clearly required; not an insurmountable problem, I assume. ——SerialNumber54129 07:04, 24 April 2019 (UTC)
  3. Oppose per Chope. Lugnuts Fire Walk with Me 09:29, 24 April 2019 (UTC)
    @Lugnuts: I'm not sure I understand what you're trying to say here. Are you saying this candidate hasn't been sufficiently scrutinized without saying what specific problem you have? Or that there is a procedural irregularity with the nomination? Or that you have some generic opposition to RfA in general? Just trying to understand, thanks. MarginalCost (talk) 14:47, 24 April 2019 (UTC)
    @Lugnuts, whatever the rest of his career Chope is famous for one thing and one thing only, and that's his attempt to prevent upskirting being made illegal. Are you sure this is the signal you want to be sending? ‑ Iridescent 15:47, 26 April 2019 (UTC)
  4. Oppose per Rnd dude. The requests for page protections were plainly bad. More importantly, I want to see more examples of his being in conflict and how he wades across them. The one mentioned does not remotely seem to be a conflict and that I don't support the linked method of gaining the tools, I choose to oppose. I also wish to emphasize that I have no personal qualms against his editorial behavior, till date and remain willing to shift camps, shall my concern be satisfied. WBGconverse 13:48, 24 April 2019 (UTC)
    Since it’s been commented on twice, the use of the new user in Q3 is likely my fault. We were discussing the nom and I said the example could even be something small as what people care about is seeing the interactions with others. When they mentioned that example, I thought it was great as they’d mainly be interacting with new users, and it showed how they’re always willing to discuss things, even with new users, which is often ignored in RfA. Not trying to badger, but I think it’s worth pointing out when my advice is the cause of concerns. TonyBallioni (talk) 13:57, 24 April 2019 (UTC)
    Behavior with new users is worth a point, emphasizing upon but to quote Guy:-...Spend one or maybe two years never disagreeing with anyone on anything..... but never ever on anything where there is the slightest chance that there will anything other than overwhelming agreement with you......
    I don't believe that Hickory is running for RFA with such a grand scale of pre-planned staging but the concerns are valid, (at-least to me). When you protect an article in the wrong version and it's legacy maintainer screams at you, you need to have served in the trenches to understand his perspective and to resolve that, in a competent and least-drama manner. WBGconverse 14:07, 24 April 2019 (UTC)
    Also, as to Tony's comment:- and you'll see them making numerous intelligent reports at the anti vandalism noticeboard, I note that after about a month of the RFA-chat with Tony, he resigned from AIV-reporting and his last edit over there was on 27 November. (Assuming SQL's stats are correct.) There's virtually nil AfD participation, prior to this year. A single PROD, all along. CSD-log is enabled from January, 2019 and is quite-restricted to user-space and/or R8 et al; though that's understandable post-ACTRIAL. The page-curation log documents reviews of sure-shot stuff, mostly about basketball/ice-hockey team sessions and surnames. The more I look, the more I believe that he is the best-fit for Guy's supposedly hypothetical way to mop and I seek for the passage of about a year. WBGconverse 15:25, 24 April 2019 (UTC)
    @Winged Blades of Godric: SQL's stats are incorrect. According to xtools, they've made 745 edits to AIV this year alone. Suffusion of Yellow (talk) 18:09, 24 April 2019 (UTC)
  5. Oppose for now. Not enough experience in contentious areas. These days admins must have experience in handling any and all kinds of contention. I was also surprised to see favourite policies did not include WP:RS which is fundamental to writing articles. Littleolive oil (talk) 14:55, 24 April 2019 (UTC)
  6. Regretful oppose - a good and enthusiastic editor, but too new for me to be comfortable handing out the tools. Sorry. GiantSnowman 15:10, 24 April 2019 (UTC)
  7. Oppose. With all due respect for the work so far, I have no problems with that at all, but I'd like to see a little more staying power before handing out a mop. I'd be happy to support in another year or so. In short: WP:NOTQUITEYET. Yintan  19:54, 24 April 2019 (UTC)
  8. Oppose - I have to agree with Mr rnddude. I don't think Hickory will be responsible with the tools. Foxnpichu (talk) 20:24, 24 April 2019 (UTC)
    Additional note. One of the general comments down below mentioned how it appears the candidate has only voted in one RfA in the past. Wouldn't it be a good idea if they had more experience in RfA? Foxnpichu (talk) 15:13, 25 April 2019 (UTC)
    Not sure if this is a trick question... but nope, admins don't need to worry about RfA beyond their own candidacy. — 🦊 07:12, 27 April 2019 (UTC)
    Being involved in RfA voting and discussions to me sounds like experience that's relevant to becoming a bureaucrat, not an admin. Gizza (t)(c) 09:06, 27 April 2019 (UTC)
    Well, too each their own, I suppose. Foxnpichu (talk) 13:26, 27 April 2019 (UTC)
    I think there's a valid argument that having good things to say at RfA or having a good sense of what makes a good RfA would be meaningful should that person go to RfA themselves; certainly, a history of unhelpful participation at RfA would be counterproductive. That is, RfA participation can be good or bad, but lack of RfA participation is neither. Saying this at RfA is one helluva selection bias, though. ~ Amory (utc) 14:50, 28 April 2019 (UTC)
  9. Weak oppose: the ECP requests concern me, as RFPP is a place where admins use discretion about what sort of protection to apply. It's already incredibly hard for new editors to start out on Wikipedia and we don't need to put up more barriers. ECP is a sledgehammer used to crack a nut and in my opinion, it is absolutely insane to apply in any non-Arbcom instance (semi and PC are much, much better). The answer to question #4 just isn't firm enough to make me confident that the candidate won't go over the top with protections. I don't see any civility issues with the candidate, which I think is far and away the most important trait in an admin, so that's why my oppose is weak. I do like their response to question #10, as admitting mistakes and changing your behaviour, rather than digging further, is important. I'd like to vehemently disagree with editors saying that 18 months is not enough experience, and point out that some of the questions posed to the candidate (#5, #7, #12) are ridiculous. Bilorv (he/him) (talk) 23:04, 24 April 2019 (UTC)
    I'm sorry you don't understand the point of question 5. All the candidates that I have asked it have understood its relevance, and nobody's ever described it as ridiculous before. Reyk YO! 09:03, 25 April 2019 (UTC)
    It’s certainly more relevant than ″what does your username mean” which it appears we must now have at every RfA. Pawnkingthree (talk) 11:18, 25 April 2019 (UTC)
    I agree that extended confirmed protection should normally be used on articles and pages in response to Arbitration Committee remedies and enforcement, but there are times that the use of ECP outside of Arbitration enforcement is necessary and where I applied it to an article on different occasions (though they aren't very common). One example was during one of my usual recent changes patrols a few months back. A BLP had reportedly just died, and I saw a huge wave of anonymous, new, and autoconfirmed users adding details and information about the person's death without citing any kind of source or reference at all. On top of this, it was occurring at an enormously high enough rate where ECP was absolutely necessary to put a stop to the BLP violations and get everyone to start citing references. It even got worse after that; I then saw a wave of extended confirmed users (including some users with over 100K edits and years of experience) doing the exact same thing - adding content to a BLP without citing any kind of reference or source. I eventually had to fully protect the article until users started responding to the talk page discussion I started that warned everyone that they were violating Wikipedia's BLP policy with the unsourced edits they were trying to add. In situations like this one, ECP was a logical and appropriate protection level to apply to the article (it was of course removed after sources started finally coming in). I've also temporarily applied it in instances where edit warring and clear 3RR violations were occurring between autoconfirmed users and at an out-of-control rate, but where those involved were not extended confirmed accounts. In this case, I didn't want to restrict everyone from editing the article if only those that were involved could be stopped and then kindly nudged toward the article's talk page to resolve the matter. I see it as a protection level that should be very carefully considered (just like all other protection levels) and applied only when the right situations call for its use (again, just like all other levels of page protection). ~Oshwah~(talk) (contribs) 01:14, 30 April 2019 (UTC)
  10. Oppose for now, but might support in the future. They joined just few years ago and I'm concerned about their lack of experience. I think it is just a bit too soon. Whatever happens, I wish them all the best.Tamsier (talk) 09:47, 25 April 2019 (UTC)
  11. Oppose. (Moved from "Neutral".) After giving this some more thought, and reading other editors' comments, I'm in this camp. Almost everything I'm seeing regarding the nominee's work that supports them getting the administrative rights is in regards to WP:AIV and WP:UAA. For an administrative candidate, I would have at least expected some work in other admin-related areas such as WP:RFPP, performing non-admin closes on any of the WP:XFD forums, drama prevention at WP:ANI, WP:SPI ... just anything else in addition to WP:AIV. In other words, I feel as though the nominee is too green in regards to their knowledge of places where administrators tend to be needed, with the exceptions of WP:AIV and WP:UAA. So, I oppose on the basis of not enough experience working in additional forums on Wikipedia where administrators are needed. Too much risk of human error for me to be comfortable with supporting at this time. Steel1943 (talk) 18:33, 25 April 2019 (UTC)
    Also, the nominee fails my minimum RfA criteria. Steel1943 (talk) 19:26, 25 April 2019 (UTC)
    Steel: Just curious, any reason why you left "autopatrolled" off the list? (BTW I would have failed your criteria.) -- MelanieN (talk) 20:10, 25 April 2019 (UTC)
    @MelanieN: Oh snap, I did, and I know what happened: I must have thought it said "autoconfirmed" when I first read it. Well, time to update that list (and may have to up the minimum number by one; I left it at that number for reasons I hope to have time to further explain one day.) Steel1943 (talk) 20:25, 25 April 2019 (UTC)
    Not to bludgeon but just to point out: In addition to their 2,144 edits at AIV and 964 at UAA, Hickory has 555 edits at RFPP and 78 at ANI. [1] -- MelanieN (talk) 19:21, 25 April 2019 (UTC)
    @MelanieN: Fair enough, I'll strike out the bit I said about WP:RFPP. I'm not going to strike out the WP:ANI part (yet) though since I'm unaware what the content of their WP:ANI edits consist of. (But, on a related note, this RfA motivated me to finally create a start for my own RfA criteria, and this candidate fails it.) Steel1943 (talk) 19:26, 25 April 2019 (UTC)
    Having few edits at ANI should be a good thing! ANI is bad. Honestly, 78 is higher than I'd like! ~ Amory (utc) 21:21, 25 April 2019 (UTC)
  12. Oppose. I think candidates, particularly relatively new members, who say their primary goal is anti-vandalism should be scrutinized very closely: It's rather like a police cadet whose primary goal is to make arrests. I was very disappointed by HOS's lack of enthusiasm for the detective work I described in my Q14. I see a far greater danger to WP in data saboteurs (not to mention hoaxers, publicists, plagiarists, and others) than garden variety vandalism. The Q15 response was also disappointing: I was hoping for some distinct areas of concentration, not just helping with simple tasks like G4 and G5 Speedy Deletions. I also don't approve of the answers to Q9 (call me crazy but I think school blocks are always wrong) and Q4 which speaks to the usefulness at RfPP. Lastly I see very few Support votes that say more than "Net gain, good chap, why not?" and that is inappropriate for a lifetime appointment. SteveStrummer (talk) 22:30, 25 April 2019 (UTC)
    SteveStrummer, to be fair, Q15 is very high on my list of “silliest RfA questions ever asked” and I don’t think the candidate should have even answered it. I jokingly call adminship “advanced twinkle” because from a practical standpoint, that’s all it is. TonyBallioni (talk) 23:19, 25 April 2019 (UTC)
    TonyBallioni I bet you get a lot of laughs with that joke. I simply wanted to know what the candidate would focus on beyond reverting. SteveStrummer (talk) 23:44, 25 April 2019 (UTC)
    What more would you be looking for? HOS could've said merely "I can block and delete instead of reporting, and can block and delete that which others have nominated" and it would have been wholly helpful. G4 and G5 were given as examples relevant to recent areas of work, but every user blocked and every page deleted is one another sysop doesn't have to spend time reviewing. ~ Amory (utc) 02:52, 26 April 2019 (UTC)
    call me crazy but I think school blocks are always wrong You must not be aware of the massive amount of silly, childish vandalism that comes from school IP addresses, a significant portion of which is prevented by school blocks. Granted, some of them are heavy-handed, but to say that they're all wrong? —DoRD (talk)​ 16:45, 26 April 2019 (UTC)
  13. Oppose. Per admin criteria. The candidate is partway there, with one GA, and with additional time and another GA (or one FA) I could support. GregJackP Boomer! 00:03, 26 April 2019 (UTC)
  14. Oppose I really would like to support a person who has impressive stats - but 90% of his AfD !votes were "delete" and almost all are within the past six months (about 97%). Of his 67 total articles created, 85% are within just the past six months - and are heavily "parallel construction" articles about second-tier hockey players done in rapid-fire order. Six months activity may be enough for an admin, but I fear the close parallel construction of his BLPs done almost on a cookie-cutter basis do not impress me all that much. And I am not, therefore. agreeing or disagreeing with any other arguments made above. Collect (talk) 13:39, 26 April 2019 (UTC)
  15. Oppose Too soon. Banks Irk (talk) 16:19, 26 April 2019 (UTC)
  16. Oppose Not enough experience for me. Maybe later. Intothatdarkness 17:08, 26 April 2019 (UTC)
  17. Oppose, based on review. Kierzek (talk) 19:53, 26 April 2019 (UTC)
    @Kierzek: care to share the results of this "review"? Surely you must have found something concerning to have opposed over. What was it? ~Swarm~ {sting} 20:49, 26 April 2019 (UTC)
  18. Oppose, per Collect, the lack of understanding of extended-confirmed protection, little evidence of work in deletion yet wishing to work at CSD (see Q15), and generally poor/bland answers to many of the questions, especially main questions 1 & 3, and optional questions 5, 8, 13, 16 & 19 (and pending the answer to Fastily's question 20). Generally I think this editor is well meaning but I have yet to see evidence that they would make a good administrator. Espresso Addict (talk) 01:08, 27 April 2019 (UTC)
    "little evidence of work in deletion yet wishing to work at CSD". Looking at User:HickoryOughtShirt?4/CSD log, I see they have nominated about 238 pages for speedy deletion in 2019 so far. Of those, I spotted 7 (ie: 2.9%) that did not immediately result in deletion, and on further investigation, as far as I can tell none were because another admin or editor explicitly declined the speedy tag. Ritchie333 (talk) (cont) 11:41, 29 April 2019 (UTC)
  19. Oppose A good candidate for 2 years from now. With admin status still bundling heavy duty disciplinary matters with the mop, this is a "not yet" situation for someone who is so new. . North8000 (talk) 03:23, 30 April 2019 (UTC)
  1. Too new Borderline fails my criteria but I'm not decided, yet. Since the 'crats won't count my vote I guess it doesn't matter. Chris Troutman (talk) 01:30, 24 April 2019 (UTC)
  2. Neutral Tentatively, but hoping to be persuaded. The answer given for Q4 is somewhat concerning, as I feel the answer suggests the candidate did not pause to read the protection policy before forming a response. I really suggest they go reread WP:ECP and perhaps amend the answer with a follow up. -- ferret (talk) 03:16, 24 April 2019 (UTC)
    I'm going to remain here, essentially in complete agreement with Teratix's neutral comments. If this was in danger of failing, I'd probably shift to support, but want to underscore the concerns about WP:PROT and jumping the gun on higher than required protections. -- ferret (talk) 14:01, 30 April 2019 (UTC)
  3. The RFPP concerns give me pause because the first thing you learn there is that you shouldn't request protection preemptively. Additionally, as Mr rnddude pointed out, rushing to block someone isn't the first port of call either. Suggests a degree of over-eagerness, but I hope future questions can persuade me to support. Anarchyte (talk | work) 07:38, 24 April 2019 (UTC)
  4. Neutral - They're a bit too soon a bit too soon for me but they seem to be doing pretty well. Others have expressed some concerns that given the areas they want to work in are concerning but I can't see anything concerning enough to oppose although I'm not convinced enough to support. Maybe try again in 9 months to a year. See my RfA Criteria for what I've based it on. RhinosF1(chat)(status)(contribs) 15:41, 24 April 2019 (UTC)
    It is strange that you would link to WP:TOOSOON, since that essay is totally about notability of article subjects, and makes no reference to RfA.--rogerd (talk) 16:29, 25 April 2019 (UTC)
    @Rogerd: Somehow I completely missed this was aimed at me but  fixed RhinosF1(chat)(status)(contribs) 21:21, 26 April 2019 (UTC)
    Neutral, leaning oppose. (Moved to "Oppose"). I really feel like it's WP:TOOSOON WP:NOTNOW, and surprisingly to me, given that I tend to be everywhere on Wikipedia, I've never heard of this editor. (Seriously, I originally thought this RFA was for an alternative account of Shirt58.) May be sitting this one out, but I don't see myself hovering to the "Support" column. Steel1943 (talk) 04:35, 25 April 2019 (UTC)
    It is strange that you would link to WP:TOOSOON, since that essay is totally about notability of article subjects, and makes no reference to RfA.--rogerd (talk) 17:28, 25 April 2019 (UTC)
    @Rogerd: Almost everyone does that at some point when commenting on RFA when they mean to link WP:NOTNOW. Corrected. Steel1943 (talk) 18:22, 25 April 2019 (UTC)
    @Steel1943: Not to be argumentative, but "almost everyone"??? I have been an admin for 13 years and I have never seen it. Let's see "most" would mean more than 50% of users who participate in the RfA process, and "almost everyone" would be more than 85%, wouldn't it?? --rogerd (talk) 16:05, 26 April 2019 (UTC)
    To add to the confusion, you probably meant WP:NOTQUITEYET, for intermediate users who are just a bit too inexperienced. WP:NOTNOW is the "sysop is not for n00bs" essay. And of course there is an essay about this distinction, WP:NOTNOTNOW. —pythoncoder (talk | contribs) 02:25, 26 April 2019 (UTC)
    Neutral (Moved to "Support") Response to Q4 makes me wary because technical restriction on editing should be a last resort to prevent abuse. The preemptive requests for ECP worry me because of that, but the user seems to have enough clue that I take them at their word that they'll do better going forward. However like SerialNumber54129 I'd want to see some indication of that before saying I fully trust them with the tools. I'll think about it over the coming days but I think I'm firmly neutral. Wugapodes [thɑk] [ˈkan.ˌʧɹɪbz] 06:23, 25 April 2019 (UTC)
  5. Neutral I originally voted support in this request. However, now when I think about it (with the influence of the general comment section), I think having only 1.5 years of experience is not quite enough just yet. Having around 2-3 years of experience would be best for the user. I worried that with just 1.5 years of experience, the user would cause some questionable actions. This happens to me sometimes, even though I have around 1.5 years of experience. Also, I would realize that I have more things to learn after other users told me about things I was obvious too. Although I definitely think that this user has a lot more experience than me, I feared that the user would do things like I did earlier. I do feel remorseful that I have to change my vote from support to neutral, but I thought it's important that I have to be earnest. INeedSupport :3 16:57, 25 April 2019 (UTC)
    A more appropriate homage to The Importance of Being Earnest would be to create two accounts, one taking on the role of well-respected admin Jack Worthing, the other taking on the more forthright and less civil content creator Ernest .... "Gwendolen, it is a terrible thing for an admin to find out suddenly that all his life he has been speaking nothing but Wikipedia policy. Can you forgive me?" Ritchie333 (talk) (cont) 17:58, 25 April 2019 (UTC)
    "When one is a sysop one amuses other people. It is excessively boring." Or maybe "This RfA candidate is quite perfect." "Oh! I hope they are not that. It would leave no room for developments, and I expect them to develop in many directions." ~ Amory (utc) 21:25, 25 April 2019 (UTC)
    Neutral Tough one. Mostly per answer to Q4. Normally this wouldn't be a concern, but since the candidate has expressed interest in RfPP work, I can't support in good conscious. -FASTILY 08:02, 26 April 2019 (UTC) Moved to support -FASTILY 00:32, 28 April 2019 (UTC)
  6. Neutral comes across as WP:NOTQUITEYET, but not strong enough for me to outright oppose. Polyamorph (talk) 18:58, 27 April 2019 (UTC)
  7. Neutral. If there was a suitable admin recall (or not so much an admin recall, but an admin-renew-licence, or even an admin learner licence, step up to provisional license before gaining full licence, like driving licenses I'd support, but some answers to questions give me pause for thought. Sounds a bit too trigger happy, like an 18 year old traffic cop. Subsequent responses and saying I'll do better and learn from this are fine, but not yet convinced they actually will, just as I'm unsure some learner drivers would if they didn't have to sit the next level licence. But I won't oppose, on basis that Admin should be no big deal and AGF and if they are genuine as the sound they might nake a half decent admin. Consider this a vote for admin reform, and it should be easy along these lines. ClubOranjeT 07:21, 29 April 2019 (UTC)
  8. Neutral Honestly, HOS4 seems to have demonstrated a good use of the tools in their hand so far, and I would support this RfA. But like many others have pointed out, it seems to be a case of WP:TOOSOON. I don't want to oppose this request because I have no grounds to oppose it but my skepticism asks me to remain neutral. --Rsrikanth05 (talk) 19:04, 29 April 2019 (UTC)
  9. I have been teetering from oppose to support to neutral for the last week. Overall I have had nothing but a positive experience with Hickory, having encountered their content creation and anti-vandalism work, both excellent. Their tenure, while on the lower side, doesn't concern me. The misunderstanding of ECP displayed is my main problem, especially as Hickory explicitly mentioned they were to work at RPP. The issues are recent and not isolated (19 out of the last 20 requests for ECP receiving semi or none), and they failed to adequately address their mistakes in their initial answer to the question. However, I don't wish to oppose because Hickory has an exemplary attitude to learning from their mistakes (otherwise they would not have gone from new user to successful RfA in 18 months), they will be more than adequately reminded to abide by protection policy by the responses to this RfA, their enhanced ability to perform other anti-vandalism work would amount to a net positive, and adminship is no big deal. So I am remaining neutral. – Teratix 12:29, 30 April 2019 (UTC)
General comments
Take the general comments about RfA elsewhere, they are not relevant to this RfA. -- Amanda (aka DQ) 09:00, 24 April 2019 (UTC)
The following discussion has been closed. Please do not modify it.
  • It's pointless voting: the 'crats will change the guidelines at will to make a mockery of the system anyway. - SchroCat (talk) 08:13, 24 April 2019 (UTC)
    Oh stop whining. We know you weren't happy, the matter is over. --Redrose64 🌹 (talk) 08:17, 24 April 2019 (UTC)
  • Making a valid comment is not "whining", so pop it up your smoke and pipe it, will you. While it's fecking obvious that the matter of the last RfA is over, the overall system is not "over", and is still open to the same underhand machinations as to the last one. Please don't try to poke me further - it's not big or clever. - SchroCat (talk) 08:27, 24 April 2019 (UTC)
  • No, it is whining - please feel free to do it elsewhere and leave this RFA alone. GiantSnowman 08:29, 24 April 2019 (UTC)
  • Goodness me: two admins unable to stomach valid criticism in a fractured system. Please feel free to ignore the comment, do something useful somewhere else (I don't know - do something most admins can't do: write a decent article or something) and don't try poking me. - SchroCat (talk) 08:33, 24 April 2019 (UTC)
  • @GiantSnowman: Since this RfC, candidates are required to disclose if they have edited for pay. Best, Kevin (aka L235 · t · c) 09:58, 24 April 2019 (UTC)
    • (edit conflict)@GiantSnowman Per policy, this is required (Candidates are also required to disclose whether they have ever edited for pay) and is usually done in the acceptance to preempt a question asking the same. (And, full disclosure, I nudged the nom to nudge the candidate) ~ Amory (utc) 10:00, 24 April 2019 (UTC)
    • @Amorymeltzer and L235: thanks for confirming! GiantSnowman 10:05, 24 April 2019 (UTC)

  • Seeing this theme of "here only 18 months" makes me a bit sad. That seems like more than sufficient of a tenure to become a sysop. Heck 12 good months (and yes I mean good not great or does nothing but edit Wikipedia 24/7/365) should be more than sufficient in terms of background. Of course not everyone is ready after 12 months or 18 months or 120 months but that readiness (or not) seems to have less to do with the length of tenure than other factors. Best, Barkeep49 (talk) 15:46, 24 April 2019 (UTC)
    • I agree that people’s expectation of admin tenure is getting kind of ridiculous. “Only” 18 months’ tenure is now considered “too new”? Or a recent RfA where a candidate was dinged for having “only” 25,000 edits? It used to be that a year of solid, quality editing and 10,000 to 15,000 edits was considered sufficient for RfA, and IMO that is still a good baseline. In this case, Hickory has over 50,000 edits - more than many long-established admins, and way more than most successful RfA candidates. Can we please evaluate someone like this on the basis of their history and their contributions and their temperament, rather than raising the bar higher and higher on tenure? -- MelanieN (talk) 16:27, 24 April 2019 (UTC)
      • Please be aware that the prevalent qualifications have risen since each of you joined. This isn't 2007 and we don't run RfAs that way, anymore. You can disagree with popular expectations if you like but Wikipedia has changed. We have many more rules across a considerable number of fora and niche communities. The project reaches more broadly than it used to. Chris Troutman (talk) 17:34, 24 April 2019 (UTC)
          • @Chris troutman: Please be aware that the prevalent qualifications have risen since each of you joined. This isn't 2007 and we don't run RfAs that way, anymore. Please don’t assume. I became an admin in 2015; RfA had high standards then, and still does, and should. As I said, a minimum tenure, minimum number of edits, and experience in various admin areas are all expected now. For a long time the minimum tenure was a year; I don’t think there is any real justification for the recent escalation that says even a year-and-a-half is too short. What is the requirement now? Two years? Five? Based on what? -- MelanieN (talk) 19:47, 24 April 2019 (UTC)
        • Even in 2007, no candidate could reasonably be expected to know all the rules. Shouldn't the baseline be (in any "era") that the candidate has demonstrated sufficient clue in their previous interactions and edits that one can expect them to be able to follow and enforce even those rules they are not yet familiar with? Regards SoWhy 17:50, 24 April 2019 (UTC)
          • This. It's why looking for particular metrics frequently isn't helpful, whether here or at WP:PERM, but looking for a track record that shows a user is clueful is. Maybe 8,000 edits in a year could do that, and maybe 80,000 in eight couldn't; not all edits are the same. If you get people who have a good sense of what they know and what they don't know, and how to proceed, if at all, in the latter cases, you're better off than with someone who looks great on paper but won't handle a new scenario well. To make an analogy to statistics, it's better to have a model that is reasonably good on past data and works well going forward than one that works 100% historically but is overfit and doesn't work well in the future. ~ Amory (utc) 18:15, 24 April 2019 (UTC)
            • To put things into perspective, edit count and tenure is a stickly precedent to entertain, at any time. For example, GoldenRing made an administrator with a long tenure but relatively less edits to show for it, on the other hand, BU Rob13 did probably the opposite and both of them are adminstrators in good standing now (former is an AC clerk and the latter, a member). It's always apples and oranges, that's my entire point. --qedk (t c) 19:01, 24 April 2019 (UTC)

  • I have frequently found it useful to examine a candidates own !votes at previous RFAs. In trying to do so today, I find the tool isn't working for me. Is it working for anyone else? Is anyone aware of another method of obtaining these, or perhaps of the contributions this candidate has made at previous RfAs? Vanamonde (Talk) 20:18, 24 April 2019 (UTC)

  • I have to wonder, what is the generally accepted amount of experience it takes in order to gain the adminship rights? Is one and a half years of experience enough? This user joined in November 2017. I joined in June 2017, yet I don't think I'm as experienced as HickoryOughtShirt?4. As of April 24, the user is very likely to gain the right, which probably makes the user one of the fastest ever to gain it. INeedSupport :3 21:29, 24 April 2019 (UTC)
  • I'm not sure there is a "generally accepted amount of experience". It varies by editor, and several editors have an "RFA standards" page, but in only applies to their own criteria. At the beginning of the project, a couple months and a thousand edits was sufficient, but how could have been otherwise? About 5 years ago I would have said the general consensus is 1 year and 10,000 edits. Now I'd say 18 months and 20,000 edits. I think for almost everyone context matters. For instance, I'd much rather see 3 years and 15,000 edits than 9 months and 50,000 edits. The type of edits also matter. I just made a hash of a move attempt of a portal and subpages, which resulted in more than 800 "edits." I'm also working on a new article for Lanor Records, for which I have precisely two edits to account for over the last week. Guess which one involved far more time and effort? 78.26 (spin me / revolutions) 21:49, 24 April 2019 (UTC)
    • I still think a year and 10,000 is the brightline for most people. You’ll some opposes over it, but by that point it’s not enough to sink an RfA if there are no other issues. TonyBallioni (talk) 13:03, 25 April 2019 (UTC)
  • Edit Conflict @INeedSupport I very much doubt that this candidate is in the running to be one of the 100 admins with shortest tenure when they passed RFA, let alone the least tenure of any new admin ever. 18 months is relatively short for recent years, but not the shortest of the modern era. In the 2003-2008 era when the vast majority of admins were appointed the expected minimum tenure steadily grew from a few weeks, to several months until stabilising at about a year close to a decade ago. A year seems like a long time, but there was a theory that it pretty much guaranteed that a new admin wasn't one of certain problem users returning. I don't know why anyone would think that more than 12 months was necessary, let alone 18 months. ϢereSpielChequers 13:42, 25 April 2019 (UTC)
In 2007, having a tenure of one year meant you were here for one sixth of Wikipedia's existence. In 2019, a tenure of one year translates only into 1/18th of Wikipedia's total existence. Hence, some might (subconsciously) require longer tenure now than in the "good old days"™ because the same absolute length no longer corresponds with a significant relative length. So I can somewhat understand that some people don't feel like one year nowadays is the same as it was when Wikipedia was comparatively young. I mean when I ran for admin, Wikipe-tan was barely in elementary school, now she is old enough to vote. Face-wink.svg Regards SoWhy 13:52, 25 April 2019 (UTC)
Hi SoWhy, I get that subconsciously there is a tendency for some to get pickier over time. Though from the voting at this and a recent RFA for a candidate with much less tenure it is clear that consensus is not with those who see a need for more than a year's tenure. What I don't understand is what such opposes are trying to prevent. We already require more tenure and edits than almost anyone is prepared to check, and our problem admins for the last few years have not been new ones, but longer serving ones who have drifted away from community norms. ϢereSpielChequers 11:37, 26 April 2019 (UTC)

  • Do the bureaucrats have authority to set minimum edit counts and years of experience standards to become an administrator regardless of the vote tally? Eschoryii (talk) 06:53, 28 April 2019 (UTC)
The above adminship discussion is preserved as an archive of the discussion. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the talk page of either this nomination or the nominated user). No further edits should be made to this page.