Wikipedia

Wikipedia:Requests for adminship/Creffett

< Wikipedia:Requests for adminship

The following discussion is preserved as an archive of a successful request for adminship. Please do not modify it.

Creffett

Final (137/31/3); Closed as successful by Maxim(talk) at 13:01, 17 May 2020 (UTC) [reply]

Nomination

Creffett (talk · contribs) – Insightful, hardworking, kind, and dedicated to the project, Creffett is someone whose work has stood out to me many a time. Across his over 32,000 edits, Creffett has been a distinct positive force in the project. Aside from his writing (such as Willa Brown, a Good Article on the first African American woman pilot licensed in the U.S.), Creffett’s experience is concentrated in the thankless areas of countering spam and COI editing. Through his work in these areas, Creffett has developed a strong understanding of the letter and spirit of our policies and norms. Creffett has a highly compelling need for the tools, and his temperament and good judgment will make him a terrific addition to the admin corps.

Creffett’s need for the tools is quite clear. Some of the areas where Creffett has contributed include UAA (where he is an absolutely prolific contributor), COIN, and NPP. As someone who responds to revdel/oversight requests, I can attest that Creffett regularly submits many requests arising from his spam/COI work, and in my view as a CheckUser, Creffett’s contributions at SPI have been quite strong.

Just as importantly as his contribution history, Creffett’s judgment and temperament are exactly what I look for in an administrator. Creffett has shown that he’s someone who thinks before he speaks, and communicates well in stressful situations, stepping back when he needs to, which I deeply admire. He’s enjoyable to work with, has a collaborative spirit, and treats everyone – from our most experienced editors to the many COI editors on Wikipedia – with empathy and respect. These are the qualities that I think will make Creffett an excellent administrator. Kevin (aka L235 · t · c) 22:09, 9 May 2020 (UTC)[reply]

Removed my error in my description of Willa Brown at Alanscottwalker's request. Kevin (aka L235 · t · c) 17:58, 10 May 2020 (UTC)[reply]

Co-nomination

I am delighted to nominate creffett for adminship. I was not the first to notice his fitness for the mop; as it turned out, I joined a crowd of people urging him to go for it. Kevin has wonderfully summarized his attributes, so I will just note a few things that impressed me about creffett. His input at important admin areas like AIV, UAA, COIN, and RFPP is huge (1,700 referrals to UAA alone) and always right on target. His insight and understanding of Wikipedia policy, expressed at areas like AN and ANI, made me wonder why he was not already an admin. Looking further, I found his massive and highly accurate CSD log, which assured me that he has a good understanding of what is required for an article here. Creffett has been doing valuable work for the 'pedia; it's time we gave him the tools to do even more. -- MelanieN (talk) 00:48, 10 May 2020 (UTC)[reply]

Co-nomination

Creffett has been on my radar for a while now as a potential administrator. He is a prolific vandal- and spam-fighter, and spends a substantial part of his time patrolling for conflict-of-interest editing, promotional articles, and spam. Creffett increasingly finds himself asking admins for help, either by tagging articles for speedy deletion, reporting promotional usernames so they can be blocked, or asking for copyright violations to be hidden from the history. I have responded to many of Creffett's revdel and oversight requests, and have consistently found his judgment to be solid and his requests to be well-grounded in policy.

Giving Creffett access to the administrator toolset will allow him to increase his efforts to control paid and promotional editing, an ever-increasing problem on this project. Access to deleted revisions alone will drastically increase his efficiency at NPP and COIN, and being able to take care of speedy deletions and spam blocks himself will decrease the CSD and UAA backlogs considerably.

Perhaps most importantly, Creffett has the temperament I expect in an administrator. Fighting spam and promotional editing is not just a numbers game – it's an exercise in patience and persistence. Explaining to people over and over again that Wikipedia isn't a place for advocacy or self-promotion is exhausting, and Creffett has shown that he has what it takes not to get discouraged but to remain civil, respectful, and empathetic in every encounter.

I believe that Creffett will make a great administrator, and that he has proven himself worthy of the community's trust. I am thrilled to be part of the team to present him to you, and humbly ask for your support. – bradv🍁 01:13, 10 May 2020 (UTC)[reply]

Candidate, please indicate acceptance of the nomination here: I accept, and would like to thank my nominators for their kind words and their support. I have never edited for pay, and the list of my alternative accounts can be found at User:Creffett#Account_disclosures. creffett (talk) 11:59, 10 May 2020 (UTC)[reply]

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: Most of my current work is chasing COI, spam, and promotion, so I intend to start in the corresponding admin areas - patrolling UAA, handling U5 and G11 speedy deletion requests, and providing an admin presence at COIN. I also am thinking of helping handle unblock requests for username and promotional blocks, though I'll ease into that one since it's not something I could get much experience with as a user. I'll probably also try helping out at RFPP - I've requested protection a few times and it seems like an area that can always use another patroller. Over time, I'm sure I'll lend a hand in other places, but this is where I plan to start.
2. What are your best contributions to Wikipedia, and why?
A: I think my best contributions are in the areas I work in the most - keeping spam and promotion off of Wikipedia. It's not exactly glamorous work, but I think that keeping Wikipedia neutral and spam-free are important tasks. Outside of that, I'm especially proud of getting Willa Brown to Good Article status - I read a short profile about her, thought that she was a really interesting person, saw that our article on her was lacking, and with the help of Atsme and GA reviewer CaroleHenson made a bunch of improvements to the article and got it both to GA status and to a DYK entry on the main page. Writing isn't my strongest area, so getting her article to GA felt really good, and it gave me a newfound appreciation for the work involved in content creation (and for those editors who primarily work in that space).
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: I've absolutely been in conflicts over editing and have been stressed out by other editors - usually disagreements in policy areas, but sometimes article content disputes as well. Also, occasionally an editor will disagree with me tagging their article for deletion or suspecting them of COI, and sometimes they express that disagreement rudely or just refuse to listen. Of course that stresses me out, and I expect to face more of the same if I were to be an administrator.
As for how I deal with conflicts (this is how I do it now, and I don't expect it to change): first, I remind myself that there are very few things on Wikipedia that have to be changed right away (there are exceptions, of course, like BLP violations or anything that requires contacting the WMF). In other words, if I take a break so I don't edit while stressed or angry, I'm not hurting anybody. If I can't respond politely, I'll do something off of Wikipedia, like take the dog for a nice long walk. I'll then look at the discussion with fresh eyes and ask myself whether I might not have expressed myself clearly, or misread someone's argument, or am honest-to-goodness wrong (and if I'm wrong - admit it and apologize!). If we seem to have exhausted discussion and it would be appropriate, I'll bring it up somewhere for neutral eyes - maybe request a 3O or raise it on an appropriate noticeboard. And sometimes, I recognize that arguing is going nowhere and wasting time, and in that case I'll just step away from the argument - even if I'm sure I'm right, endless arguing isn't worth it.

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 Lee Vilenski
4. I notice (outside of your GA which has just shy of 50 edits) the most you have contributed to a single article is 10 times. Why do you think it is important for admins to have experience in content creation? Best Wishes, Lee Vilenski (talk • contribs) 12:11, 10 May 2020 (UTC)[reply]
A: I believe that admins should have enough experience in article space that they can a) appreciate the work involved in writing good articles (and, for that matter, Good Articles) and b) get a practical understanding of the policies and guidelines in article space, but I don't think that it's necessary for admins to be prolific content creators. creffett (talk) 13:41, 10 May 2020 (UTC)[reply]
Actually, Lee Vilenski (and Anarchyte, since you asked a sort of follow-up below), I'd like to expand this answer a little more, I think I got nervous (first freeform question in the RfA and all) and rushed my answer and so I don't think I really communicated my thoughts well. Would you mind if I added some more to this answer later today after I've had time to reflect on this? creffett (talk) 16:28, 10 May 2020 (UTC)[reply]
No problem. Best Wishes, Lee Vilenski (talk • contribs) 17:05, 10 May 2020 (UTC)[reply]
Sure. Cheers, Anarchyte (talk • work) 17:38, 10 May 2020 (UTC)[reply]
All right, let's try this again (and thank you both for giving me another chance). I am of the opinion that every administrator needs to have a solid understanding of "content" - what is good, what is bad, what is against policy, and so on, as well as a reasonable familiarity with the policies regarding "content" (for example, our BLP policies). However, I do not believe that content creation is the only path to that understanding. For why understanding of content is important, consider the the three main technical privileges in the admin toolset - content comes up a lot in their usage:
  • Blocking frequently relates to content (POV-pushing, vandalism, spam, BLP violations, and so on). Even those blocks which aren't directly content-related can often be traced back to content (personal attacks against editors who disagree, edit warring)
  • Protection is done because of ongoing content problems (going back to the previous examples: repeated BLP violations and large-scale edit-warring are all solid examples of reasons to protect an article).
  • Deletion (particularly my usual area, speedy deletion) is done because the content does not belong on an encyclopedia, either because it meets a speedy deletion criterion, a PROD expired, or consensus at AfD was that the article doesn't belong here. This also applies to revdel, which is the same but at a smaller level.
If an administrator is expected to be familiar with "content," how can a prospective administrator show it? Of course, there's content creation - if you have a stack of GAs and FAs under your belt, there is no question that you understand what is and is not good in an article. I believe, however, that there are alternative ways to show that you are familiar with content (and the relevant policies) without actually writing articles. In my case, I believe that my work in NPP and 3O shows my familiarity - the former by reviewing new articles in mainspace and handling them appropriately (approving, draftifying, or sending them to deletion, and in the case of approving sometimes tagging their issues or performing initial cleanup on them), and the latter by providing additional opinions in content disputes. I think that my speedy deletion record shows that I'm pretty good at identifying several kinds of bad content (particularly advertising and copyvios), though I'll be the first to admit that my A7 taggings aren't great (and that's why I don't plan to patrol the A7 queue). I can imagine several other ways one could establish themselves - off the top of my head, AFC and recent changes patrol would both be solid ways to establish oneself. Of course, these are all double-edged swords - somebody who consistently gives bad advice at 3O or keeps publishing low-quality drafts from AfC is going to clearly show that they do not understand "content".
I hope this does a better job of explaining my thoughts on the matter. Anarchyte, I'll wait to answer Q5 in case you'd like to change anything now that I've updated this answer. creffett (talk) 18:39, 10 May 2020 (UTC)[reply]
Thank you for clarifying, creffett. I've updated my questions below. Anarchyte (talk • work) 04:23, 11 May 2020 (UTC)[reply]
Additional questions from Anarchyte
5. You noted in question 4 that you don't plan on working with content-related speedy deletions, like A7. Is this because you feel you lack a proper understanding of this area, or just that you're not interested in it? Your CSD work is commendable, though I would like you to explain why you nominated the following articles:
Anarchyte (talk • work) 04:23, 11 May 2020 (UTC)[reply]
A: I wouldn't say "lack a proper understanding of this area," but I recognize that I have trouble with the "credible claim of significance," or at least that my idea of a CCS often is narrower than other editors'. In order:
  • Capital com: Yeah, okay, looking at it again I'll concede that the awards and "first contracts for difference brokerage on mobile" are credible claims. That was a bad tag on my part.
  • Kısmet Press: Actually, I stand by tagging that one. I still don't see a credible claim of significance, and while there are independent reviews of a couple books, WP:INHERITED suggests that publishing a possibly-notable book isn't itself notable, and I feel that "published a book which could potentially be notable" is not a sufficient claim of significance.
  • Vivion group: Also stand by that one being A7 (though I concede that I tagged without checking history - I've made that mistake a few times lately, as noted by SoWhy, and it's something I'm trying to be more conscious about). On its own, I don't think "a portfolio of 3 billion" is a credible claim of significance, it's the top line of a marketing brochure. Now, if it said "a portfolio of 3 billion, making it the largest real estate company in Luxembourg" (or something like that), that at least would be a claim of significance. creffett (talk) 12:49, 11 May 2020 (UTC)[reply]
    Follow-up, having thought this over some more and seen Galobtter's !oppose, I don't think I can stand behind the Vivion A7 either - I think the disconnect is that I don't have a reference point for what constitutes a "significant" portfolio, so I discounted it on the assumption that if the most notable thing was their portfolio then they probably wouldn't be notable. That was a bad assumption on my part, if there was a claim whose significance I was unsure of I should have performed a proper WP:BEFORE and nominated it for AfD if appropriate. Going forward, I think I will start taking that approach more and using A7 less. creffett (talk) 02:45, 12 May 2020 (UTC)[reply]
5A. (consider this my second question). Are you aware of WP:ATD? I ask because all but four of your AfD votes have advocated for deletion and you've only turned one article into a redirect when patrolling (note that I used mw-new-redirect as the tag to find this, so there may be more). As an admin, will you be open to seeking alternatives to deletion (if the option arises)? Anarchyte (talk • work) 04:23, 11 May 2020 (UTC)[reply]
A: Yes I am aware of ATD. During NPP I've done plenty of tagging/editing (when I think the page is sufficiently notable but has issues) or draftifying (when I think the page could potentially be notable but doesn't have the sources). As for redirecting, I think my lack of use there comes from two main factors. First, since the area I've done most of my work is COI/spam, a lot of the articles I tag for deletion there have no alternative to redirect to (since they're a new company "establishing their web presence" or something like that), so redirect only became a practical option in my toolkit when I started doing NPP. Second, it may sound a little strange, but I'm actually more comfortable tagging for deletion than boldly redirecting - deletion tagging at least has someone else reviewing, whereas a redirect unilaterally removes the article's content. Now that I think about it, I would totally be up for a "proposed redirect" (in the vein of PROD) process. Finally, I'd like to point out Wikipedia:Articles_for_deletion/Marrying_Irving (an AfD filed by my public-computer sock, so it might not have come up) - in my nomination I specifically suggested redirection as an outcome.
As for the second part: yes, I would absolutely be open to alternatives to deletion if the option comes up. Again, the biggest issue will probably be redirects, and that's just a matter of consciously making myself check for potential redirects until it becomes a habit. creffett (talk) 13:05, 11 May 2020 (UTC)[reply]
Additional question from usernamekiran
6. Hi. Unlike most commonly found time charts, your time chart says you almost never edit between 3AM to 11AM UTC. Without giving out personal details, could you explain why? —usernamekiran (talk) 21:05, 10 May 2020 (UTC)[reply]
A: That's my normal sleep schedule, and even if I'm having trouble sleeping I stay off of the computer during my sleep time. creffett (talk) 21:20, 10 May 2020 (UTC)[reply]
Yes, as pointed out by comments by Mz7, and QEDK in comments section; it is a sign of a healthy sleep schedule, unlike mine. I apologise for the question, with humour gone confusing. I published just half of the question with funny part left out. I also found your time chart very odd when I saw it. All because of one reason: I've been up since almost 30 hours, and a little sleep deprived. I apologise for my silliness again. I struck out the question. —usernamekiran (talk) 21:44, 10 May 2020 (UTC)[reply]
Additional questions from The4lines
7. Let’s say you find these usernames at WP:UAA. What do you do for each of them. Signed,The4lines |||| (You Asked?) (What I have Done.) 04:42, 11 May 2020 (UTC)[reply]
Poopbubbles3990
sdadfsgadgadjhm,hj,jh,jhlhjlkfjkghkfuhlkhjsS?!!!
12, 23 June 2009
PMiller
I love you too
A: I see you're a fellow CVU editor. In order:
  • Block, offensive username.
  • Block at the first hint of vandalism - keyboard mash usernames like that are almost always vandalism-only accounts.
  • Block, misleading username (usernames which mimic datestamps are explicitly mentioned in WP:MISLEADNAME)
  • Depends. If they are extensively editing an existing article about someone whose name is of the format "P. Miller," then impersonation block + request verification. Otherwise, editing using a real name is permitted, decline and say as much.
  • Not inherently disruptive (possibility of editors being uncomfortable, but it isn't sufficiently problematic to merit a block). Decline and suggest WP:RFCN.
creffett (talk) 13:33, 11 May 2020 (UTC)[reply]
7A. This is about WP:RPP. What would be your minimum Requirements to protect a page. (One for each protection level, PC, Semi, Full, etc.) Signed,The4lines |||| (You Asked?) (What I have Done.) 14:17, 11 May 2020 (UTC)[reply]
Not really a "7A" since it's not a follow-up to 7, but sure. It's not so much "minimum requirements" as "what's the situation at the page" - in the end, the purpose of protection is to prevent disruption, so it should only be applied when there is clearly an ongoing problem, and the protection should be at the lowest level and for the shortest time that will stop the problem. Here are the various levels of protection, and what I'd consider to be good cases for protection:
  • Semi-protection: ongoing vandalism by new or anonymous editors, either a large number at once or a number of incidents over consecutive days, assuming that the unconstructive edits by anonymous/new editors significantly outweigh the constructive edits by the same. If there are a lot of constructive edits, then I'd consider...
  • Pending changes: The main reason would be that article has a reasonable proportion of constructive anonymous/new edits (as mentioned above) and/or the disruptive editing is slow but over an extended period of time. As an alternative, I've requested it in the past for an article which is infrequently edited but is a spam magnet (as an example, I requested this on The Crickets, since while it was edited infrequently, a lot of anonymous/new edits were poorly-targeted spam about cricket (the sport)). I would not use PC for articles where we're having trouble with material that would need to be revdel'd or oversighted (e.g. serious BLP violations) since the additions would still need to be deleted even if they never showed up in the article.
  • EC: Not one I expect to work with much. Either there is problematic editing in ArbCom-authorized areas (and I'm currently not planning to work arbitration enforcement, so that should be rare), significant multi-party edit warring between autoconfirmed users, or cases where problematic editors have previously shown that they're willing to gain autoconfirmed before editing the article.
  • Full protection: Also rare and as temporary as possible, I'd only use it to shut down a clear edit war, with instructions to all participants to discuss the changes on the talk page.
  • Template protection: Not one I think I'll deal with much, but I would consider applying it on request for high-use templates.
  • Move protection: Pretty much any case of move-warring (move, move back, move again) would probably be enough for me to apply this.
  • Creation protection: After the third time a page is deleted, or if it had previously been salted elsewhere.
creffett (talk) 19:08, 11 May 2020 (UTC)[reply]
Additional questions from Robert McClenon
9. This question is about conflict of interest and in particular about paid editing. In cases where an editor states that they do not have a conflict of interest, but questions are raised, how do you think that administrators should balance the assumption of good faith against appearances, or against a duck test?
A: An excellent question, and I will say that this is probably my biggest weakness in this - since my main work is dealing with those areas, I recognize that it gets really easy to look at a good-faith brand-new editor and write them off with "well, they turned out a solid biographical article in their first few edits, they must be the subject or being paid to do this." I have made that mistake before, and I probably will make it again. Overall, I tend to lean more toward DUCK, but am willing to accept credible explanations. An example of a credible explanation (and one where I guessed wrong) can be found on WP:COIN at Special:Permalink/956090112#Cheri_L._Canon - it looked possibly promotional and I came into the discussion feeling very suspicious, but they had a fairly reasonable explanation. Alternatively, there are cases where someone supposedly "likes (random company) and saw they didn't have a Wiki page" or is "an independent journalist who wrote a piece about the company and saw how great they are" and proceed to turn out a perfectly-formatted page of PR speak. Those cases quack loudly enough for me that I wouldn't extend good faith. There have also been cases where I'm dead certain that someone is COI/UPE, their editing fits the pattern, I've given them a warning, but they deny it and I have no solid proof - in those cases I've brought the discussion to COIN so that other editors can weigh in.
On the whole, I don't think I have a definite answer to your question - balancing AGF with keeping COI/UPE off of Wikipedia is a difficult balance; it's a question of whether you'd prefer to have more false positives (a good-faith editor is driven away because of incorrect allegations of paid editing) or false negatives (paid editing and promo slips through). I prefer keeping the promo out, but pushing away good-faith editors is a high price to pay for neutrality. I will continue searching for that balance, but the best I can offer is that I will always listen to criticism - if someone tells me that I was too suspicious (or too not-suspicious, for that matter) when dealing with a suspected COI editor, I will stop, listen, and re-evaluate. creffett (talk) 15:07, 11 May 2020 (UTC)[reply]
10. What experience can you cite in the general area of dispute resolution?
A: My main dispute resolution work is that I (and my sockpuppet creffpublic) contribute from time to time at WP:3O. I think I have done a reasonable job there of giving neutral, third-party opinions on disputes, backed up by policy as much as possible. On a more one-on-one level, I often have people post on my talk page disagreeing with my speedy deletion nominations or tagging their work as COI/UPE; see, for example, User_talk:Creffett#Om_Records. For an example of a disagreement between me and another editor which started firm but turned into a teaching opportunity (not precisely dispute resolution, but my approach here was the same as for DR), see User_talk:Creffett#Pictures and Copyright - it started as me being very upset with someone uploading copyvio pictures as "own work" but I ended up getting the chance to help them figure out our copyright rules. Just as with 3O, it is my goal to always respond to those questions respectfully and backed by appropriate policies. creffett (talk) 15:07, 11 May 2020 (UTC)[reply]
Additional questions from Sir Joseph
11.Would you ever block an admin, when necessary, and would your process for doing so be the same process as blocking a non-admin? If not, what would you do differently?
A: Yes, I would block an admin if they were doing something blockworthy, and yes, it would be the same process as blocking a non-admin. As with any editor, I would try to discuss my concerns with them and/or bring it to the appropriate discussion forum and only block as a last resort. Of course, if they were doing something which needed to be stopped immediately and no time to talk, I would block first and then raise it at the administrators' noticeboard - as I referred to in Q3, I'm thinking of them repeatedly and quickly adding major BLP violations or anything I'd be expected to contact the WMF for; I also consider "appears to be compromised and actively causing disruption with admin powers" to be a valid reason for blocking an administrator, at which point I would block and immediately contact ArbCom and advise them of a possible WP:LEVEL1 desysop situation. Excluding those situations, however, I would prefer to raise the discussion at WP:AN (or at least contact another administrator for review), especially as a new administrator. creffett (talk) 20:34, 11 May 2020 (UTC)[reply]
Additional question from Mz7
12. Do you think you could share more about your approach to speedy deletion, especially some of the more nuanced criteria like A7 and G11?
A: Certainly. First, I'll admit that I used to be a lot looser in my interpretation of the CSD criteria, especially G11; that changed during the RHaworth ArbCom case - the full details can be seen at Wikipedia:Arbitration/Requests/Case/RHaworth#Statement_by_creffett (it's a back-and-forth with Thryduulf and Boing! said Zebedee, so you'll have to see their sections as well), but basically I was interpreting G11 by the intent of a page author rather than by the content of a page (for example, I considered someone writing about their company or themselves to be G11 material, regardless of the tone of the page). That was a mistake, and following that discussion I have become more strict in how I interpret CSD. I still will tag for G11 as soon as those pages cross the promotional line, but if a page is just a factual "this company exists" (and if it comes back clean from a copyvio check, as those pages are often lifted wholesale from the company website) I will tag it as COI if applicable and let the AfD process deal with it. Same applies to "up and coming young musical artist" pages (which usually translates as "autobiography from someone who thinks that they need a Wikipedia page because they released an album on SoundCloud"), of which I see a lot since I patrol the "possible autobiography" filter - in the past, I would have given it the G11 treatment; now, I will A7 if it's in mainspace (and there actually is no claim of significance), otherwise, just tag it as autobiography if necessary and leave it there. In terms of A7, I've also interpreted it more strictly as of late, but that was due to me not getting that "credible claim of significance" is not the same thing as "credible claim of notability."
Now, as for what qualifies for A7 and G11, even with a strict interpretation of either, I feel that there's a lot of room for interpretation. Consider G11, whose text reads in part: pages that are exclusively promotional and would need to be fundamentally rewritten to serve as encyclopaedia articles, rather than advertisements (emphasis orig). I would consider all of the following to be possible indicators of a promotional page if I saw it in NPP, but I'm sure someone could interpret things differently:
  • Article is significantly written in the second person ("WidgetCorp serves all of your FooWidget needs")
  • Most of the article is a list of the company's products/services (assuming that none are notable)
  • Excessive puffery, especially when unsourced ("WidgetCorp is a leading supplier of high-quality FooWidgets" - if there were a source for that statement)
  • Article is almost exclusively cited to the company website and/or press releases
  • If the article was clearly written by a COI editor (e.g. user WidgetCorpMedia created the page WidgetCorp, or user BobMcSmith wrote about FooBarLtd and the page lists the founder as "Bob McSmith"), I tend to extend less benefit of the doubt
  • Article generally looks like PR/marketing copy
The problem is that even those are vague, and even if an article meets one or more of those criteria it could look like it could be cleaned up without too much effort.
As for A7, I look for a credible claim of significance, but again, interpretation of CCS can vary between editors - for example, I'm not sure I would consider "winner of (non-notable magazine's non-notable award)" to be a claim of significance. I think I covered my recent issues with A7 in my answer to Q5, so I'd refer readers there for comments on recently contested A7s. Since I'm aware that I have trouble with A7, if I become an admin I would plan to keep tagging those instead of unilaterally deleting. For both A7 and G11, my bottom line is this: even though a lot of both is up to interpretation, I will always be able to point to the article and identify something specific (more general than "it looked promotional") that caused me to tag it as such.
I hope you don't mind, Mz7, but since we're on the topic of speedy deletion I'd also like to deviate a bit just to address the concerns raised about me incorrectly tagging articles with histories. Most of my experience with CSDs has been in handling drafts, userspace drafts/userpages, or brand new pages. Until I started doing NPP, I wasn't used to the possibility that I was working with an article expanded from redirect, and so I didn't consider the possibility that an article I was reviewing had much of a history. Likewise, I was usually the first to handle those pages, so it was very rare that there was a previously-declined CSD by a different user. I have made that mistake several times while working NPP, tagging an expanded redirect (or restoration of an AfD-created redirect) because I only considered what I was looking at and didn't stop to check the article's history since I assumed that any page coming up at NPP was new or almost new. That was incorrect on my part, and I am making a conscious effort to history before tagging for deletion until it becomes a habit. creffett (talk) 20:24, 11 May 2020 (UTC)[reply]
Additional question from Levivich
13. Would you be open to recall and if so, under what process?
A: First, I'd like to cite Girth Summit's excellent take on the matter from their RfA (see Wikipedia:Requests_for_adminship/Girth_Summit#Questions) - I completely agree with their first two paragraphs and would probably do the same as they suggested (resign the tools if someone I really respected told me that I was unfit to hold the mop or an RfC/AN report clearly showed that I had lost the community's trust). I also think that the role of administrator should be treated as a sort of stewardship role (lowercase s!) that the community has seen fit to trust the admin with. Thus, if I am an administrator and the community no longer trusts me to to execute that stewardship, then the community should have some way to revoke the tools, and so I will be open to recall.
As for the precise details, I spent some time before the RfA browsing the various recall policies of the administrators open to recall. Sparing you the whole story of my thoughts on the various choices I've seen, I think that I will adopt some variant of K6ka's criteria - it is simple, straightforward, minimizes the drama, and adheres to NOTBURO, but still has the concerned parties discuss the matter with me before recalling and it at least tries to keep the recall related to my administrative conduct. creffett (talk) 01:45, 12 May 2020 (UTC)[reply]
Additional question from Deryck Chan
14. Thank you for your continued participation in CSDs. Here is a hypothetical scenario (based on a real case) for you to consider. An editor created a redirect and a different editor tagged the redirect (using rcat templates) and added an incoming links in a related article. Sometime later, it was discovered that the creator of the redirect was a sockpuppet of a banned user. The editor(s) who tagged the redirect and added the incoming link remained in good standing throughout the timeframe in question. How will you decide whether to use WP:G5 to delete the redirect?
A: Based on the available information, I would probably not G5 it (or decline a G5 tag) for a couple reasons. First, G5 only applies if there have been no substantial edits, and I would consider an rcat to be a significant edit (given how small a redirect is), so I'd decline on those grounds. Second, since the other editor has used the redirect, that would suggest that the redirect is appropriate for the topic. Even if the other editor hadn't come along, I would consider leaving the redirect alone if I thought it was a plausible redirect that a different editor could have reasonably created. creffett (talk) 23:37, 12 May 2020 (UTC)[reply]


Discussion

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

Support
  1. Support Their work at COIN is very massive and commendable. Has a clue, not a jerk. —Nnadigoodluck🇳🇬 12:11, 10 May 2020 (UTC)[reply]
  2. Support I’ve seen the candidate around and been very impressed. They have a clear need for the tools and I trust their judgment. P-K3 (talk) 12:14, 10 May 2020 (UTC)[reply]
  3. Support per nom clear net positive and good work in COIN.Pharaoh of the Wizards (talk) 12:17, 10 May 2020 (UTC)[reply]
  4. Support Knowledgeable editor who has a clear need for the tools. Happy to support. -- LuK3 (Talk) 12:24, 10 May 2020 (UTC)[reply]
  5. Support Creffett has been prolific at janitorial work, has a clear use for the mop. Cabayi (talk) 12:25, 10 May 2020 (UTC)[reply]
  6. Support No reason to think they'd misuse the tools. FeydHuxtable (talk) 12:25, 10 May 2020 (UTC)[reply]
  7. A Very Obvious Support. ~~ CAPTAIN MEDUSAtalk 12:28, 10 May 2020 (UTC)[reply]
  8. Support - Can be trusted with the mop. - FitIndia Talk Commons 12:45, 10 May 2020 (UTC)[reply]
  9. Support - Seen the candidate around and have been impressed with their comments, No red flags here. Easy support. –Davey2010Talk 12:55, 10 May 2020 (UTC)[reply]
  10. Support. For what I've see creffett around it's obvious that they could use the toolkit. – Majavah (t/c) 13:01, 10 May 2020 (UTC)[reply]
  11. I can see some soft opposes on lack of content, but those should be outweighed by Creffett's reasonable attitude, work with copyright issues (several good G12s), and evidence that they can write. Pretty easy support. Moneytrees🌴Talk🌲Help out at CCI! 13:05, 10 May 2020 (UTC)[reply]
  12. Support. Excellent anti-spam work. Creffett's username reports and speedy deletion nominations are both consistently accurate. — Newslinger talk 13:10, 10 May 2020 (UTC)[reply]
  13. I have seen for myself a lot of the fine work mentioned in the nomination statements. Best, Barkeep49 (talk) 13:17, 10 May 2020 (UTC)[reply]
  14. Support. One of the reasons I was drawn to this user as a possible admin candidate was their questions on my talk page. He was always checking policy and making sure he was well informed. One of the great things about his editing is his willingness to grow and gain expertise and fresh perspectives (like he did at the RfC re: COIN). HickoryOughtShirt?4 (talk) 13:19, 10 May 2020 (UTC)[reply]
  15. Finally! Trusted, competent. ~ ToBeFree (talk) 13:29, 10 May 2020 (UTC)[reply]
  16. Support Clear net positive. Natureium (talk) 13:37, 10 May 2020 (UTC)[reply]
  17. Support Definitely. Creffett is very active, and their CSD tags and UAA reports are reliably solid, but more importantly they have exactly the right demeanor, always preferring to wind down tension rather than fan the flames. GirthSummit (blether) 13:59, 10 May 2020 (UTC)[reply]
    I'm seeing some comments below from people who are impressed by the stats, but who haven't interacted with creffett, so I'm feeling I should have been more fulsome in my support. Can I just add that I have interacted with creffett frequently, and have always been impressed both by their knowledge, and their willingness to share it in a friendly manner. GirthSummit (blether) 18:50, 10 May 2020 (UTC)[reply]
  18. Support Solid record, reliable reports, clear net positive. -- ferret (talk) 14:00, 10 May 2020 (UTC)[reply]
  19. Support. The candidate has a clear need for the tools (especially at UAA and deletion), and also a bit of article creation. He is also civil, one of the other qualities that we should look for in an admin candidate. epicgenius (talk) 14:28, 10 May 2020 (UTC)[reply]
  20. Support. MER-C 14:29, 10 May 2020 (UTC)[reply]
  21. Finally! Levivich [dubious – discuss] 14:40, 10 May 2020 (UTC)[reply]
  22. Support. Well able to use the tools (AfD noms and CSD log), good temperment, and has made content. Britishfinance (talk) 14:58, 10 May 2020 (UTC)[reply]
  23. Strong Support. (edit conflict) Clear net positive. Meets my RfA criteria. I have full trust in creffett that they will use the tools for the benefit of the community. I also think that creffett's work on in UAA and deletion is very useful, an example of many reasons why creffett is WP:HERE. Creffett is civil and willing to engage in discussion, even on matters which they have explained or talked about countless times such as the example bradv gave that Wikipedia isn't a place for advocacy or self-promotion. If I had heard that creffett was going for RfA, I would have jumped at the first chance to nominate or co-nominate. Dreamy Jazz talk to me | my contributions 15:04, 10 May 2020 (UTC)[reply]
  24. Support been waiting for this. --Puddleglum2.0(How's my driving?) 15:10, 10 May 2020 (UTC)[reply]
  25. Support as one of the nominators. – bradv🍁 15:25, 10 May 2020 (UTC)[reply]
  26. Support as co-nom. -- MelanieN (talk) 15:42, 10 May 2020 (UTC)[reply]
  27. Support enthusiastically as a nominator. Kevin (aka L235 · t · c) 15:47, 10 May 2020 (UTC)[reply]
  28. I thought about this for a while given the candidate's incredibly weak content creation outside of that one GA (for which the candidate has a mere 50 edits). However, admins are primarily backstage workers so I just barely end up in this column. Do beef up your content work, though, regardless of whether this passes (which it probably will). – John M Wolfson (talk • contribs) 16:10, 10 May 2020 (UTC)[reply]
  29. Support. ST47 (talk) 17:11, 10 May 2020 (UTC)[reply]
  30. Support. While most admins need to be content creators, we also need some prepared to work mainly in these important other areas. Mccapra (talk) 17:21, 10 May 2020 (UTC)[reply]
  31. Support. bibliomaniac15 17:30, 10 May 2020 (UTC)[reply]
  32. Support. I have only come across this editor recently, and I admit that the amount of content creation is not impressive, but I don't have any general concerns about their ability to do the job. Deb (talk) 17:37, 10 May 2020 (UTC)[reply]
  33. Support, clearly. Suffusion of Yellow (talk) 18:08, 10 May 2020 (UTC)[reply]
  34. Support I've yet to interact with the nominee, but it appears that they do valuable work at a high clip, and have a valid use case for the tools. The lack of content creation does not bother me, but the ritual devaluation of non-article work in RfAs by some editors certainly does. We need more people willing and able to do the background work that keeps the project running, not less. The Squirrel Conspiracy (talk) 18:34, 10 May 2020 (UTC)[reply]
  35. Support – Excellent candidate, no concerns. Kurtis (talk) 18:39, 10 May 2020 (UTC)[reply]
  36. I am very pleased to see this. I was one of a sizable group of editors who encouraged Creffett (often stylized as creffett) to go for RfA. He works in many of the same areas that I do in my admin work, so I see his name pop up fairly frequently. Having begun editing Wikipedia in March 2019, creffett's tenure on the project is admittedly shorter than most candidates we see nowadays, but since joining, he has become one of our most helpful editors, especially in the behind-the-scenes areas of the project where the administrative toolset is most needed. On a typical day, you might find creffett gnoming away, patrolling new pages, reverting vandalism, or flagging spam and other inappropriate content. On the content side, he improved the fascinating Willa Brown article from about C-Class to GA-Class. Although he is not the most prolific content creator, his experience with Willa Brown, as well as the behind-the-scenes administrative areas of the project, demonstrates his familiarity with adding well-researched content and our content and administrative policies.
    Finally, creffett is unfailingly level-headed—I've never seen him lose his temper, even when he disagrees with editors. For evidence of this, you can take a look at his user talk page, where he is frequently addressing questions from new editors with respectfulness and precision—as an administrator involved in deletion, this will be something he will continue to have to do. From my interactions and observations, I believe creffett is the kind of person willing to take a step back and listen to you, even when you think he's made a mistake. For these reasons, I believe that creffett will be an excellent addition to the administrator team, and I hope you will join me in supporting him. Mz7 (talk) 18:41, 10 May 2020 (UTC)[reply]
  37. Support. Creffet is level-headed, easy to work with, understands what the encyclopedia is supposed to be about, and will be an asset to the admin corps. – Athaenara ✉ 19:01, 10 May 2020 (UTC)[reply]
  38. Support - so there are two reasons why I might consider opposing Creffet: his content creation and his delete-heavy AfD participation. However. While his content creation is certainly fairly minimal (compared to most candidates), his GA certainly demonstrates he can sing the tune. Additionally, almost all his delete !votes are nominations - active NPP editors often have skewed figures. The pros are all given, multiple uses for the tools, reliable etc etc. Nosebagbear (talk) 19:07, 10 May 2020 (UTC)[reply]
  39. Strong candidate, strong nominations. El_C 19:43, 10 May 2020 (UTC)[reply]
  40. Support - Candidate has proven beneficial to the encyclopedia especially in behind-the-scenes administrative areas. Strong candidate. Daask (talk) 19:48, 10 May 2020 (UTC)[reply]
  41. Support -- Clearheaded, writes well, has a dog. Per noms, Mz7, and my own limited experience reading their sensible posts. -- SashiRolls 🌿 · 🍥 20:12, 10 May 2020 (UTC)[reply]
  42. Support Has a strong support from Dreamy Jazz (arguably all one needs) and MelanieN says he's good, so don't need more to be convinced really. Easy +1 from me. --qedk (t 愛 c) 21:16, 10 May 2020 (UTC)[reply]
  43. Support A regular in administrative areas already, why not? -- King of ♥ ♦ ♣ ♠ 21:35, 10 May 2020 (UTC)[reply]
  44. Support Definite net positive. Vermont (talk) 21:42, 10 May 2020 (UTC)[reply]
  45. Support Clearly a positive influence on the community and a great editor to give the mop to. EggRoll97 (talk) 22:19, 10 May 2020 (UTC)[reply]
  46. Support, anyone who can maintain such a pristine time card clearly has the self-discipline to be an admin. But don't look at mine. ♠PMC♠ (talk) 22:22, 10 May 2020 (UTC)[reply]
  47. Support No doubt. S0091 (talk) 22:33, 10 May 2020 (UTC)[reply]
  48. Support Clearly does indeed have a clue & would be a net positive. Celestina007 (talk) 23:00, 10 May 2020 (UTC)[reply]
  49. Support - I supported creffett when they requested access to the info-en queue (OTRS), and my support here is based on the same observation: creffett is a helpful fellow. The content creation concerns are fair, but the postives outweigh these concerns for me. --MrClog (talk) 23:10, 10 May 2020 (UTC)[reply]
  50. Support what appears a strong candidate with genuine need. — Insertcleverphrasehere (or here)(click me!) 23:41, 10 May 2020 (UTC)[reply]
  51. Stephen 00:41, 11 May 2020 (UTC)[reply]
  52. Support Why not? -FASTILY 00:42, 11 May 2020 (UTC)[reply]
    By the same logic: Why? Carrite (talk) 02:18, 11 May 2020 (UTC)[reply]
    The nominators have already explained why.-- P-K3 (talk) 19:17, 11 May 2020 (UTC)[reply]
  53. Not a jerk, has a clue. TonyBallioni (talk) 00:44, 11 May 2020 (UTC)[reply]
  54. Support Not gonna beat a broken drum here, so I'll just say that s/he meets all of my criteria, and per Mz7, Dreamy Jazz, and the noms.Squeeps10 Talk to meMy edits 00:51, 11 May 2020 (UTC)[reply]
  55. Support Guy has a clue and a sleep schedule. Nova Crystallis (Talk) 01:03, 11 May 2020 (UTC)[reply]
    Galobtter (pingó mió) 01:34, 11 May 2020 (UTC)[reply]
  56. Support ~SS49~ {talk} 02:14, 11 May 2020 (UTC)[reply]
  57. Support - Normally with only one year showing on the charts I would say "inadequate tenure," but the previous account (though lightly used) Geekboy72, was registered in 2005 and started Arizona Air National Guard in 2006. Activity is "administratorish" rather than that of a content person, but that is freely admitted and not really a big problem in my book. Clean block log for both accounts, no indication of assholery, no problems. Carrite (talk) 02:27, 11 May 2020 (UTC)[reply]
  58. Strong support - Ran into Creffett several weeks ago and saw them pursuing, with great zest, the most irksome linkspamers on our site. I've looked through his other contributions since then, and have been quite pleased with what there is to see. He's got a good head on his shoulders, is even-tempered, and hasn't shown any reason to worry he wouldn't be able to handle the tools. A resounding +1 from me. Welcome aboard! — Coffee // have a ☕️ // beans // 04:00, 11 May 2020 (UTC)[reply]
  59. Support- I don't know much about this candidate, but the three opposes are so ludicrous they need cancelling. Reyk YO! 06:43, 11 May 2020 (UTC)[reply]
  60. Support - absolutely, has a clue and the energy to properly execute what needs to be done. Atsme Talk 📧 11:17, 11 May 2020 (UTC)[reply]
  61. The candidate is averaging 500 edits per month in article space. Yes, it’s not content creation. It’s maintenance, per a spot check of their mainspace contributions. Not everyone has the skills to create articles from scratch. That doesn’t mean they don’t value content. Creffett is doing useful gnomish content-related work. Add in the positive temperament and I’m a yes. —valereee (talk) 11:43, 11 May 2020 (UTC)[reply]
  62. Support. Overall excellent work in a variety of areas. I see the concerns of SoWhy over some rushed or overzealous speedy deletion work, and would certainly encourage Creffett to rush it less - but the mistakes are relatively sparse and primarily technical errors, very few are wildly wrong. Clear net positive to grant admin tools. ~ mazca talk 12:24, 11 May 2020 (UTC)[reply]
  63. Strong Support without per noms and Mz7. Creffett is running roughly around where I did account age wise. Not to take away from other users who run, but it is also good to see "fresh"er eyes/candidates with competence, clue, and a need for the tools running. Best of luck! --TheSandDoctor Talk 13:03, 11 May 2020 (UTC)[reply]
  64. Support, Making errors, even several errors, does not make someone disqualified from being an admin. The fact that the candidate did look back and corrected some of the mistakes they made shows that they are well suited to the role. I think granting them the tools would be a net positive. Devonian Wombat (talk) 13:08, 11 May 2020 (UTC)[reply]
  65. Support per TheSandDoctor. ~riley (talk) 13:32, 11 May 2020 (UTC)[reply]
  66. Support, will be fine. Fish+Karate 14:51, 11 May 2020 (UTC)[reply]
  67. Support - no real concerns. GiantSnowman 15:22, 11 May 2020 (UTC)[reply]
  68. Support I feel that creffett has been ready for quite some time! GrammarDamner how are things? 15:24, 11 May 2020 (UTC)[reply]
  69. (edit conflict) Support - no problems that I can remember, doesn't matter if he's been on the project for <2 years. SemiHypercube 15:26, 11 May 2020 (UTC)[reply]
  70. Support will be a net-positive to the project. « Gonzo fan2007 (talk) @ 15:37, 11 May 2020 (UTC)[reply]
  71. Strong support excellent editor, well rounded and their WP:COIN work really seals the deal for me. Praxidicae (talk) 16:19, 11 May 2020 (UTC)[reply]
  72. Support Polite, knowledgeable, experienced, hard working, wrote a GA. And a software engineer ... but, hey, they can't be all good things! --GRuban (talk) 17:22, 11 May 2020 (UTC)[reply]
  73. Support I think that the concerns over a handful of questionable CSDs belie the fact that the standard we should be looking for in an admin is "net positive", not perfection. signed, Rosguill talk 17:45, 11 May 2020 (UTC)[reply]
  74. Support - candidate seems to be familiar with WP policies. Not a jerk, has a clue. While overzealous CSDing is very bad, I'm not convinced it is enough for me not to support. L293D (☎ • ✎) 18:04, 11 May 2020 (UTC)[reply]
  75. As El_C writes below, good candidates should be welcomed with enthusiasm! So this can be considered my enthusiastic support! P.I. Ellsworth  ed. put'r there 18:35, 11 May 2020 (UTC)[reply]
  76. Support - may need a bit more experience in CSD, but otherwise they're a great fit - they should get the hang of it quickly. Kirbanzo (userpage - talk - contribs) 18:46, 11 May 2020 (UTC)[reply]
  77. Obvious choice. — Wug·a·po·des​ 18:57, 11 May 2020 (UTC)[reply]
  78. Support - solid work so far, expecting great work in the future. ◢   Ganbaruby!   (Say hi!) 19:18, 11 May 2020 (UTC)[reply]
  79. Support - Even though the candidate messed with some of my edits recently, I still see them as a very worthy addition to the admin team after going through their contribution history. I !vote yes. BasicsOnly (talk) 19:20, 11 May 2020 (UTC)[reply]
  80. Support Has a clue, will be a great admin/sysop. Signed,The4lines |||| (You Asked?) (What I have Done.) 19:43, 11 May 2020 (UTC)[reply]
  81. Support I've seen them at various other places on this wiki, and they've always seemed like an intelligent and reasonable person. They will be a good admin ThePlatypusofDoom (talk) 19:51, 11 May 2020 (UTC)[reply]
  82. Support This candidate has convinced me of their suitability based on their work, their answers to the questions above, and the faith their highly respected nominators have placed in them. CThomas3 (talk) 20:52, 11 May 2020 (UTC)[reply]
  83. Support no reason to think this user would abuse the tools --rogerd (talk) 21:29, 11 May 2020 (UTC)[reply]
  84. Support 2 articles created? Hmmm... --Killarnee (T•1•2) 21:58, 11 May 2020 (UTC)[reply]
  85. Support. Long overdue. Guy (help!) 22:12, 11 May 2020 (UTC)[reply]
  86. Support I've seen the candidate around, and like what I've seen. Trustworthy noms, good answers to questions. Opposes are not a deal-breaker. Miniapolis 02:00, 12 May 2020 (UTC)[reply]
  87. Support level-headed, and has been very helpful at COIN. It is always good to have one more person hanging around there with the block/delete button.ThatMontrealIP (talk) 03:04, 12 May 2020 (UTC)[reply]
  88. The candidate's responses indicate resolve to take the opposing editors' concerns on board. serial # 04:38, 12 May 2020 (UTC)[reply]
    To contextualise Kudpung's oppose, while ten of our most trusted and experienced admins are opposing this candidate, err, forty four of their colleagues are supporting them. serial # 09:21, 17 May 2020 (UTC)[reply]
  89. Support The best thing I can say is that I thought creffet was already an admin. I've always been impressed by my interactions with them. I must note that the opposes gave me some pause, notably on the incorrect use of A7 and general carelessness with CSD. But creffet's answer to 12 puts any concerns I have to rest. I have no doubt that creffet will be much more careful with CSD in the future. CaptainEek Edits Ho Cap'n!⚓ 07:21, 12 May 2020 (UTC)[reply]
  90. Support. I don't recall the last time I have cited "per nom" in my statement of support, but it's very rare that such an excellent set of nominators come along to take the words out of my mouth (because usually I have a lot of words).. From the little I've interacted with Creffett, I've had no redflags, so I'm supporting per nom. –MJL ‐Talk‐☖ 10:27, 12 May 2020 (UTC)[reply]
  91. Support for meeting my minimums and no big deal. The oppose votes seem just nitpicking over one statistic or another, nothing behavioural to indicate they wouldn't be a net positive. Ifnord (talk) 12:40, 12 May 2020 (UTC)[reply]
  92. Support - no concerns. Jauerbackdude?/dude. 15:46, 12 May 2020 (UTC)[reply]
  93. Support - After reading this RfA, I'm confident that creffett will use the tools wisely, and will learn from any mistakes made in doing so. Happy to !vote support. Phuzion (talk) 16:23, 12 May 2020 (UTC)[reply]
  94. Support - The nomination statements are great and the opposes do not sway me. Seems like a great help to the project. Killiondude (talk) 17:48, 12 May 2020 (UTC)[reply]
  95. Support - creffett is a wonderful individual who does excellent work countering spam on this project. I trust they'll make use of the tools to keep doing that. Not a jerk, has a clue, fantastic sense of humour and humility in equal measure. -- a they/them | argue | contribs 20:47, 12 May 2020 (UTC)[reply]
  96. Support CLCStudent (talk) 20:58, 12 May 2020 (UTC)[reply]
  97. Support - Thoughtful answers to questions and lots of evidence of good work. --WMSR (talk) 21:28, 12 May 2020 (UTC)[reply]
  98. Support - good answers to questions, clear net positive. Iseult Δx parlez moi 21:53, 12 May 2020 (UTC)[reply]
  99. Support Based on positive interactions with the candidate around new pages reviewing speedy deletion tags; has my trust. SpencerT•C 00:35, 13 May 2020 (UTC)[reply]
  100. Support: As someone who almost exclusively contributes by adding content, the low proportion of mainspace edits doesn't bother me. More than 6,000 mainspace edits is really not such a small number, and anyways I would only really be concerned about that if it was bundled together with various signals that the candidate doesn't place a high value on adding content to the encyclopedia. I think the amended answer to Q1 covered that concern very successfully. - Astrophobe (talk) 02:17, 13 May 2020 (UTC)[reply]
    I mean Q4. I swear I can read. - Astrophobe (talk) 02:19, 13 May 2020 (UTC)[reply]
  101. Support - Excellent and collegial editor in my experience. The nomination makes a clear case exhibiting the need for the tools, and I am confident that they will exhibit enormous experience in the area of administration. Michepman (talk) 04:27, 13 May 2020 (UTC)[reply]
  102. Support - Trusted, friendly contributor. Has a long term history of vandalism fighting and demonstrates a strong understanding of policy. And while 25.6% of all edits are in mainspace, it is the second largest category where they have made edits. Aasim 07:20, 13 May 2020 (UTC)[reply]
  103. Support LGTM, can be trusted with a mop --DannyS712 (talk) 07:22, 13 May 2020 (UTC)[reply]
  104. Support Good demeanor and interactions. Answers and talk page comments give clear explanations and understanding of policy. Per noms, Mz7, GirthSummit, —valereee and Devonian Wombat, in particular. Clear net positive. Donner60 (talk) 07:33, 13 May 2020 (UTC)[reply]
  105. Support after review. No issues here. ZettaComposer (talk) 13:03, 13 May 2020 (UTC)[reply]
  106. Support No red flags in risk assessment. --Pudeo (talk) 16:29, 13 May 2020 (UTC)[reply]
  107. Support unequivocally! Yay, Creffett! - Julietdeltalima (talk) 17:36, 13 May 2020 (UTC)[reply]
  108. Support - Looks like will be a good admin 👍🏽 Obhf (talk) 22:00, 13 May 2020 (UTC)[reply]
  109. Support I thought you were an admin already... – Frood (talk) 02:10, 14 May 2020 (UTC)[reply]
  110. Weak Support. SoWhy and others' issues about creffet, while certainly important, aren't enough for me to oppose. However, should more information become available, I might reconsider this !vote. JavaHurricane 06:30, 14 May 2020 (UTC)[reply]
  111. Support I had to log in when I saw this. I've had a few positive Interactions with creffett and saw them around numerous other times. They seem to have the judgement, character and attitude I'd want to see in an admin Magisch talk to me 06:59, 14 May 2020 (UTC)[reply]
  112. Support — a strong counter-vandalism record which I hope they take into their adminship. Concerns from the opposes, particularly SoWhy's, are valid; however, in the bigger scheme of things not something I'd use to oppose a net positive candidate. Creffett I wish you all the very best! —MelbourneStar☆talk 08:30, 14 May 2020 (UTC)[reply]
  113. Support - I agree with Creffett views on the importance of content moderation. All of the reasonable oppositions are ones claiming that an admin should have experience in content creation, but I disagree. Moderation isn't as enjoyable as creation but without it nobody would trust anything on Wikipedia. - amitlevy49 —Preceding undated comment added 13:30, 14 May 2020‎ (UTC)[reply]
  114. Support -- I believe that an admin should be familiar enough with content creation in order to be able to use the appropriate tools - page protection; deletion; etc. - and Creffett has reached that bar for me. -- Dolotta (talk) 23:54, 14 May 2020 (UTC)[reply]
  115. Weak support. I'm slightly queasy about the candidate's low participation in content creation and high participation in deletion, though the answers to the questions show good understanding. Overall likely a net positive. Deryck C. 00:15, 15 May 2020 (UTC)[reply]
  116. Support Nick (talk) 12:32, 15 May 2020 (UTC)[reply]
  117. – Juliancolton | Talk 14:27, 15 May 2020 (UTC)[reply]
  118. Strong support. I have read through the opposes, and although I see where they are coming from, do not believe they rise to the level which should prevent Creffet, who has a need for the tools and I believe would be a net positive, from being an admin. --Mdaniels5757 (talk) 14:50, 15 May 2020 (UTC)[reply]
  119. Support, Great anti-vandalism and anti-spam work. I think having admin tools will help them to do more good work in that direction. ‐‐1997kB (talk) 15:09, 15 May 2020 (UTC)[reply]
  120. Support would like to see more content work in a candidate, but I'm sufficiently impressed by Creffett's aptitude in dealing with spam and coi issues. LEPRICAVARK (talk) 16:14, 15 May 2020 (UTC)[reply]
  121. Support. I'm minded to think you need a good balance among an administrative team of people who spend their time doing article creation and curation, but also those who really get a feel for what vandalism and abuse looks like. That team together balances the deletionist and non-deletionist arguments that are present throughout the community. It'd be concerning if every administrator had as little content experience as creffett does, but it's a good idea to have at least a few who focus like he does. I certainly can't fault his experience in his area - I've seen him around the AIV-type boards a fair few times, and he always seems to be doing good. Naypta ☺ | ✉ talk page | 18:02, 15 May 2020 (UTC)[reply]
  122. Support Great work combating spam, while showing the ability to learn and grow from criticism. I don't find the opposes convincing. Content creation should not be a requirement for admin privileges. buidhe 18:10, 15 May 2020 (UTC)[reply]
  123. Support - I would generally prefer that a candidate have a little bit of a longer tenure before applying for the tools, but this candidate otherwise seems very qualified and giving the tools would likely be a net positive. Aoi (青い) (talk) 18:42, 15 May 2020 (UTC)[reply]
  124. Support already an asset to the 'pedia and the mop and pail will increase that. MarnetteD|Talk 20:39, 15 May 2020 (UTC)[reply]
  125. Support good candidate. JohnThorne (talk) 21:36, 15 May 2020 (UTC)[reply]
  126. Support, as I am reasonably convinced that the candidate has learned the appropriate lessons from missteps of the past. BD2412 T 01:38, 16 May 2020 (UTC)[reply]
  127. Aye, good stuff. InedibleHulk (talk) 07:58, 16 May 2020 (UTC)[reply]
  128. Support A common criticism of RFA shines bright here: content creation is not well-aligned with use of admin tools, while relevant work in space such as NPP can be controversial. Creffett has done well fighting spam, conflicts of interest, and vandalism. Reywas92Talk 08:05, 16 May 2020 (UTC)[reply]
  129. Support The candidate has showed that he can use the tools responsibly. Past experiences has helped him to correct his previous mistakes. LSGH (talk) (contributions) 10:47, 16 May 2020 (UTC)[reply]
  130. Support The accuracy of their judgement is satisfactory. TheBirdsShedTears (talk) 11:57, 16 May 2020 (UTC)[reply]
    Support Appears to be competent. -- Dolotta (talk) 12:56, 16 May 2020 (UTC)[reply]
    Struck duplicate vote. --qedk (t 愛 c) 15:15, 16 May 2020 (UTC)[reply]
  131. Support: I too would prefer that the candidate have a little bit longer tenure before applying for the tools, but the candidate is clearly a net positive. - Ret.Prof (talk) 14:47, 16 May 2020 (UTC)[reply]
  132. Support - A qualified editor. Robert McClenon (talk) 14:58, 16 May 2020 (UTC)[reply]
  133. Support Has a clue, seems qualified enough to me. Curdle (talk) 16:43, 16 May 2020 (UTC)[reply]
  134. Support.--AhmadLX-(Wikiposta) 19:34, 16 May 2020 (UTC)[reply]
  135. Support; I had my suspicions regarding his speedy deletions, but his answer on Q12 is good enough for me. He seems to be passable everywhere else as well. Swordman97 talk to me 22:43, 16 May 2020 (UTC)[reply]
  136. Support. I honestly thought they were already an admin.--Jorm (talk) 03:55, 17 May 2020 (UTC)[reply]
  137. Support Trusted and well qualified. TheGeneralUser (talk) 11:49, 17 May 2020 (UTC)[reply]
Oppose
  1. Oppose The candidate only started two articles. The candidate !votes delete at AfD at a very high rate The candidate has only $25% of edits in the main space. Administrators should have experience in content creation: we are building an encyclopedia. Protecting content and content creators is best done by an administrator who has experience creating content. Lightburst (talk) 13:10, 10 May 2020 (UTC)[reply]
    @Lightburst:, purely with respect to the AfD !vote count, the large majority of his AfD participation is as a nominator (c 75%) - this is a common case for NPP-heavy editors, and naturally swings their count towards delete without that automatically indicating a deletionist. As a fairly staunch inclusionist myself, I'm not too concerned by his AfD stats. Nosebagbear (talk) 19:08, 10 May 2020 (UTC)[reply]
    Hi. I am not talking about your particular oppose vote, but about the rationale behind such votes. I totally agree that a candidate should have good experience with content creation. But article creation is not the only gauge for that. Adding substantial content to existing articles is also content creation (by the way, in my opinion, the candidate doesnt have that either). Regarding the AfD: CSDs, and AfD exist for a reason. I think of myself as an inclusionist but I have around 90% delete votes in almost 500 AFDs. When I see a spammy article, or promotion/advert I obviously vote delete, or take it to AfD/speedy. Those so called inclusionists who dont do that are simply bad editors. And if one is patrolling new pages, they are bound to come across problematic pages that need to be deleted. —usernamekiran (talk) 21:23, 10 May 2020 (UTC)[reply]
  2. Oppose I very rarely oppose, however the candidate has 16.7% of all edits (that's 5,407 edits) that have been instantly deleted, and as Lightburst says, only 6,824 (25.3%) are main page edits. So I oppose now, but my advice would be to produce some more new articles, and maybe have one Did you know, that would be good. SethWhales talk 13:30, 10 May 2020 (UTC)[reply]
    @Seth Whales: Respectfully, the user performs CSD tagging, which will naturally lead to lots of deleted edits and an imbalance of mainspace % versus user talk CSD notifications. -- ferret (talk) 13:45, 10 May 2020 (UTC)[reply]
    Also, I would note, creffett has one DYK for Willa Brown. Dreamy Jazz talk to me | my contributions 15:06, 10 May 2020 (UTC)[reply]
    I look forward to the day that no RFA voters vote based on stats, which never, ever accurately reflect anything meaningful. Levivich [dubious – discuss] 15:20, 10 May 2020 (UTC)[reply]
    User:Ferret is correct. I took a look at Creffett's deleted contributions. They have had 90 deleted contributions so far this month, and every one was a CSD or PROD request. Naturally, when the item gets deleted, the edit requesting it also gets deleted. -- MelanieN (talk) 15:48, 10 May 2020 (UTC)[reply]
    Ferret, Creffett — word salad! El_C 00:14, 11 May 2020 (UTC)[reply]
    Knew I was not the only one! ​--qedk (t 愛 c) 05:32, 11 May 2020 (UTC)[reply]
  3. Oppose not suited to be an admin. Sir Joseph (talk) 00:21, 11 May 2020 (UTC)[reply]
    I was told this was a business casual event. Natureium (talk) 01:26, 11 May 2020 (UTC)[reply]
    Wikipedia needs an upvote button. Squeeps10 Talk to meMy edits 03:52, 11 May 2020 (UTC)[reply]
  4. Oppose. Candidate wants to work in speedy deletion but they are making mistakes, even quite recently, that give me pause:
    I concede that the candidate does a lot of taggings and that these only represent a small share of those taggings (although I have not checked deleted taggings). However, these examples also demonstrate that the candidate is either far too hasty when tagging (and does not always catch their hastiness-related mistakes) or is not sufficiently familiar with the requirements of CSD. Both would be troubling in any candidate, but they are even more so in a candidate who explicitly wants to handle such requests. If the candidate approaches such requests as an admin as they do as an editor, i.e. without sufficiently checking the article and/or its history before deletion, we risk losing valuable encyclopedic content. There are enough editors who are quick to tag a vandalized article instead of restoring the previous revision that we have to rely on admins to do the necessary checks the taggers often don't. At this point, the candidate does not appear to be able to fill this role. Regards SoWhy 06:46, 11 May 2020 (UTC)[reply]
    Discussion moved to the talk page. qedk (t 愛 c) 13:07, 11 May 2020 (UTC)[reply]
  5. Oppose – Not enough experience editing articles. --- C&C (Coffeeandcrumbs) 07:35, 11 May 2020 (UTC)[reply]
  6. Oppose due to overzealous CSD concerns brought up by SoWhy. – filelakeshoe (t / c) 🐱 09:48, 11 May 2020 (UTC)[reply]
  7. Oppose per SoWhy. I did a quick spot check of the candidate's mainspace contributions, and the first thing I saw was edit-warring over an A7 tag on Capital com (which IMHO is probably notable as the sponsor of the major Spanish football club Valencia CF). [2] No thanks. Ritchie333 (talk) (cont) 11:19, 11 May 2020 (UTC)[reply]
    Discussion moved to the talk page. Primefac (talk) 16:53, 11 May 2020 (UTC)[reply]
  8. Oppose - You fail my criteria. Sorry. Foxnpichu (talk) 15:51, 11 May 2020 (UTC)[reply]
  9. Oppose Inadequate knowledge of deletion criteria, and generally careless work in this area. This area is one of the key functions of an admin, and mistakes here can cost us good contributors. DGG ( talk ) 20:30, 11 May 2020 (UTC)[reply]
  10. Oppose per SoWhy. The A7 of Vivion group particularly struck me. I understand some jadedness with the endless torrent of corp spam, but I don't think any reasonable interpretation of "significance" would label a company that owns 3 billion euros of real estate to be "insignificant" and subject to speedy deletion, and that the candidate continues to defend this speedy deletion nomination in Q5 is concerning. And the issues re G11 mentioned in Q12 show issues with interpreting policy (the plain language of G11 does not include "intent" in any way and while I appreciate that he acknowledges that his interpretation was a mistake, this still shows issues with understanding the deletion policy). Galobtter (pingó mió) 01:33, 12 May 2020 (UTC)[reply]
  11. Oppose per SoWhy. Some of those examples are very recent (less than two weeks old) and show a lack of understanding of the CSD policy. Anyone routinely working in CSD should be checking talk pages and page histories first, and should know instinctively that an article that has survived an AfD is ineligible for speedy. Self-reverting is admirable, but the necessity of it shows excess haste in tagging and that you're only checking the prerequisites after the fact. I get that "credible claim of significance" can be subjective, but composing music for a blue-linked film and another film by a blue-linked director easily passes the threshold even without considering the coverage in reliable sources (which aren't necessary for the claim to be credible). The last thing we need is an admin deleting articles and then checking afterwards that the prerequisites were met, if they check at all. There is very little oversight of speedy deletions, and we've had enough problems in the past with admins whose interpretation of the criteria has drifted from the community's. I certainly wouldn't rule out supporting in future, but I feel you need at least another few months' experience in applying policy without the tools. HJ Mitchell | Penny for your thoughts? 09:46, 13 May 2020 (UTC)[reply]
  12. Oppose - Unfortunately, I find myself here. I echo the concerns of SoWhy and Galobtter primarily, but it's really the initial answer to Q4 and the response to Q5 that influenced me. While I appreciate the followup to Q4, I still have concerns. For instance, an article shouldn't be deleted just because a PROD expired; the admin should check it one last time before deleting it. Additionally, the fact that an entire conversation took place under SoWhy's oppose regarding improper A7s and then the Vivion group Q5 still had to be modified concerns me. I've heard and can understand valereee's concerns about paid editing, but that's not a reason to delete (CSD-wise). The Q5 answer to Kısmet Press was also problematic. I was hoping they would comment on why they CSD'd an article 20 minutes after creation, not why they believe the A7 was valid (which at the time of tagging, I agree: there was no claim of significance). Many users, especially newer ones, create the page before adding the main content. This is also what happened here, whereby the article was created at 02:35, tagged at 02:42, and deleted by 02:45. An infobox was the only content. It's quite obvious this RfA will be successful but I hope creffett will keep all these concerns in mind going forward. Anarchyte (talk • work) 10:16, 13 May 2020 (UTC)[reply]
  13. Oppose per SoWhy, HJ Mitchell, et al. I'm concerned that Creffett would be too much of an eager beaver with the delete button. CJK09 (talk) 15:36, 13 May 2020 (UTC) Strong oppose. Per SoWhy, HJ Mitchell, etc, we've seen that Creffett is far too eager to delete content, bite newcomers, etc. Frighteningly, it appears that he doesn't understand the CSD criteria. A delete-happy editor with little to no content creation experience doing NPP while armed with the delete button is not a net positive for the encyclopedia. Further, I agree with SMcCandlish below about the role of admins. Wikipedia is already overly convoluted and process-driven. A thinkpiece on Slate a few years back accurately described us as a Kafkaesque bureaucracy. The last thing we need right now is an ever-expanding professional-managerial class that doesn't do content work, and spends the sum total of their time on Wikipedia managing and adjudicating those who do. On this particular front, what Spinningspark unearthed from Creffett's participation at 3O makes it absolutely crucial that Creffett not be granted the admin toolkit. Quoting widely known policies back at editors trying to come to a consensus, while refusing to give the actual third opinion they were looking for, shows a complete lack of understanding of the dispute resolution process. This is the most important task of an admin. Kashmiri summed it up nicely: we're here to build an encyclopedia, not to delete one. I'm not one to demand a laundry list of GA's, FA's, whatever. But when the candidate's lack of content work is combined with a trigger-happy approach to deletion and a gross misunderstanding of the process for resolving content disputes, it becomes absolutely clear that they should not be entrusted with the admin bit. CJK09 (talk) 23:42, 14 May 2020 (UTC)[reply]
    Strong oppose due to concerns about the candidate's approach to deletion as articulated by SoWhy, HJ Mitchell, et al, and due to concerns about the candidate's approach to the dispute resolution process as per Spinningspark. CJK09 (talk) 01:38, 15 May 2020 (UTC)[reply]
    I am disappointed with the disrespectful tone of this oppose vote, and I think it poorly reflects even the views of other oppose votes. What we have here is a candidate who has offered himself entirely in good faith—his request is not in the least "frightening" or "Kafkaesque". This is a candidate who, in the view of myself and dozens of editors who work in the same areas that the candidate does, does extremely helpful work for the areas of the project where administrative tools are most needed.
    I think those who have offered opinions in this section have raised a few valid points, but I reject the assessment that Creffett is a candidate with "little to no content creation experience" on the basis of the candidate's contributions to the Willa Brown article. It is true that the candidate is not a more prolific content creator as some RfA participants may wish to see in a candidate (and I would respectfully disagree with that view), but I think it is a mischaracterization of this candidate's contributions to say that he has hardly touched the mainspace at all.
    I also believe it is a misjudgment of the candidate's character to accuse him of not being here to build the encyclopedia, but rather to delete the encyclopedia. I appreciate that other editors in this section have offered legitimate advice to Creffett about his work in speedy deletion, but it is important to view his contributions in this area in context. On a typical day in Wikipedia, dozens of editors decide to misuse our encyclopedia to promote themselves, their clients, or their company—Creffett's work in combating these spammers from interfering with the legitimate work of our encyclopedia writers has, for the most part, been indispensable. Mz7 (talk) 01:11, 15 May 2020 (UTC)[reply]
    On reflection, you're right that I got carried away in writing up my rationale. I apologize to creffett for any implication of bad faith. Shortly I'm going to retract that oppose and rewrite it with a more succinct and more respectful rationale. However, I feel the need to respond to a few of you points.
    I did not call creffett or his request for adminship Kafkaesque. That was in reference to Wikipedia's mind-bogglingly byzantine bureaucratic structure. IMO it's a serious problem for editor retention, among other things. Wikipedia may claim not to be a bureaucracy, but that's a laughable claim. Anyway, that description was targeted squarely at Wikipedia's administrative structure, not the candidate.
    I strongly disagree on the front of content creation experience. Aside from Willa Brown there's not a single article that creffett has made more than ten edits to. That lack of content work combined with the candidate's approach to deletion tagging is a concerning combination for an admin, for reasons other opposers have explained much more eloquently than me. Combined with what Spinningspark found in creffett's 3O work, I'm very concerned about how he would approach content disputes and other content-related issues as a result of not having significant experience being part of such disputes. CJK09 (talk) 01:35, 15 May 2020 (UTC)[reply]
  14. Oppose, without prejudice to a later RfA. Mainly it's insufficient content work. We need great encyclopedia editors to become admins; we don't need the volunteer equivalent of a "professional class" of essentially admin-only users. I'm also opposing because of the long string of CSD problems. I might have let that slide in a candidate who proposed to spend their admin time doing completely different things, but this is someone who wants to focus on that. On the up side, I agree with supporters that the candidate has a good demeanor and is generally clueful and constructive. I would probably support after more content work (which needn't necessarily be all-new article creation or GA/FA, just a lot of mainspace contributions) and after a better CSD track record. PS: I agree with comments above that frequent nomination for deletion (speedily or otherwise) will result in a higher than average deleted-edits count, AfD delete vote record, and user-talk namespace edit count. So, none of those are concerns for me (and shouldn't be for anyone else).  — SMcCandlish ☏ ¢ 😼  19:32, 13 May 2020 (UTC)[reply]
  15. Oppose Insufficient content work. An admin who hasn't been in the trenches of content is ill-equipped to mediate among content contributors.--Wehwalt (talk) 08:19, 14 May 2020 (UTC)[reply]
  16. Oppose, reluctantly. The errors highlighted by SoWhy are typical of NPPers who think that admin work is all about keeping as much crap out in the shortest time possible. This is valuable work, but I think the candidate now needs time to show that they are capable of the more careful and considered approach required of admins. Perhaps try again in six months. I really hope that the candidate doesn't believe, as the answer to Q4 implies, that an expired prod is in itself a reason to delete. Many people oppose at RFAs for lack of article content; in Q4 the candidtate offers their work in NPP and 3O as a substitute. SoWhy has shown weaknesses in NPP so I took a look at 3O work. The first response I came across [3] frankly horrified me. If you don't feel you are able to give an opinion, you shouldn't answer the request, that's what the process is entirely about. Asking the disputants to name sources, and if necessary quote from them, will soon ferret out who has the sources on their side. After several sources are, in fact, referred to, the candidtate then ducks out again and recommends using a different dispute resolution process [4]. Sorry, that just doesn't do it for me. SpinningSpark 08:51, 14 May 2020 (UTC)[reply]
  17. Oppose, insufficient content work at this time AlasdairEdits (talk) 12:15, 14 May 2020 (UTC)[reply]
  18. Oppose per SMcC and Spinning Spark. Gog the Mild (talk) 15:42, 14 May 2020 (UTC)[reply]
  19. Oppose, reluctantly, per SoWhy. Having your article tagged for speedy deletion is an awful experience for a new, good-faith editor, but having an incorrectly-tagged page deleted can be much worse. And their response to Q12, which came after SoWhy's concerns, solidifies my opposition - it's too defensive, it doesn't show enough willingness to take criticism and learn from it. Guettarda (talk) 16:27, 14 May 2020 (UTC)[reply]
  20. Oppose Limited content creation.--Catlemur (talk) 22:08, 14 May 2020 (UTC)[reply]
  21. Oppose with regret. We are here to build an encyclopaedia, not to delete an encyclopaedia. — kashmīrī TALK 23:20, 14 May 2020 (UTC)[reply]
  22. not yet I think the concerns about speedy deletion tagging are real. I think the candidate has been moving in a direction more aligned with policy and they have certainly indicted an understanding of the problems. But the problems are recent and I'd like to see them improve in practice for a while before moving forward. Hobit (talk) 03:14, 15 May 2020 (UTC)[reply]
  23. Oppose per SoWhy and HJ Mitchell. I am open to support in a second Rfa perhaps as soon as later this year, but the concerns expressed by respected Wikipedians are convincing at this time. I thank the candidate for their work on the project, and urge careful consideration of the points raised here if given the mop in the next few days. Jusdafax (talk) 08:58, 15 May 2020 (UTC)[reply]
  24. Oppose: Concerns over deletion tagging and NPP work. Its a tough area NPP but sometimes too much at these things without enough content creation can be a problem. I haven't delved through all the things given here in depth, but I see the concerns from people who know what they are talking about.Djm-leighpark (talk) 10:28, 15 May 2020 (UTC)[reply]
  25. Ask again in 3-6 months please. With a great deal of respect for Creffett's dedication and positive demeanour, the noise about CSD is a bit too recent, and together with planned admin activities does raise concerns about an admin with potential spam/COI-searching tunnel vision. Much appreciated that he's become involved in content generation (GA last month) too. But all in, feels like letting things settle for a few more months is prudent, with the candidate being able to come back then and demonstrate their approach has mellowed. Martinp (talk) 11:08, 15 May 2020 (UTC)[reply]
  26. Oppose Some of our most trusted and experienced admins including HJ Mitchell, SoWhy, DGG, and Ritchie333 (I have read the talk page) to name but a few, have sufficiently outlined why adminship right now might not be a good idea. And I'm afraid In have to concur with them. Kudpung กุดผึ้ง (talk) 12:57, 15 May 2020 (UTC)[reply]
    Bizarre. serial # 13:02, 15 May 2020 (UTC)[reply]
  27. Oppose: I'm sorry, but I'm not sure that the candidate currently meets my criteria for the mop, especially regarding content creation. — Javert2113 (Siarad.|¤) 13:16, 15 May 2020 (UTC)[reply]
  28. Reluctant Oppose per SoWhy and DGG, et al. It takes good judgement to decide to delete non-encyclopedic content and this candidate doesn’t seem to possess that quite yet. Running off good content creators does a lot of harm, and wastes time. Gleeanon409 (talk) 11:59, 16 May 2020 (UTC)[reply]
  29. Oppose; understanding (and/or care in application) of deletion policy seems wanting. wjematherplease leave a message... 14:11, 16 May 2020 (UTC)[reply]
  30. Oppose per SoWhy and HJ Mitchell. Nihlus 15:32, 16 May 2020 (UTC)[reply]
  31. Support A clear benefit to the encyclopedia. Regarding the issue of the candidate's account's youth, I'm of the opinion that fresh voices should be welcome. userdude 22:54, 10 May 2020 (UTC)[reply]
    First account started in 2005, so not sure that "youth" with respect to accounts is a term I would use. Carrite (talk) 02:30, 11 May 2020 (UTC)[reply]
    Yes, but they only made 34 edits and didn't seem particularly involved with the project writ large. I'm not interested in the user's age so much as their (potentially) fresh views of the project. userdude 03:26, 11 May 2020 (UTC)[reply]
    With regret, changed to oppose per CJK09. userdude 21:53, 16 May 2020 (UTC)[reply]
Neutral
  1. The candidate started editing in March 2019. Thats 14 months. This is not about their competency, but I would like to see a candidate with a tenure of at least two or three years. —usernamekiran (talk) 21:28, 10 May 2020 (UTC)[reply]
    Two or three years? Everyone's entitled to their opinion, but seriously? ‑ Iridescent (who passed RFA 83–1, 14 months after registration but after four months of actual activity) 22:53, 10 May 2020 (UTC)
    I got mine in about a year and I feel like I was ready. Speaking from my experience, I don't think a wait of another year or two would have benefited me. I think that's the case here, also. More generally, it doesn't make sense to have more stringent RfA standards at the time when we need more admins than ever. Wikipedia has grown a lot since my RfA in 2005, but the admin corps has not grown proportionately with it. Anyone willing and able to help with backlogs and bottlenecks should be welcomed with enthusiasm. El_C 00:08, 11 May 2020 (UTC)[reply]
    Note the previous account, Geekboy72, started at WP in 2005. Serious activity has been happening only for about a year, but this is not someone who has just happened upon WP recently. Carrite (talk) 02:34, 11 May 2020 (UTC)[reply]
    Those were the old days. I would have supported the candidate back then. And yeah, three years seems a lot now. I would say 2 years. I am also aware oppose on this point would be harsh, and there is nothing else to oppose for. They are a good candidate. Thats why I came in neutral section. I went through the nominations/and 3 questions again, but I couldnt find mention of geekboy72. There was a mention in support #48. Could anyone tell more about it? Thanks. —usernamekiran (talk) 10:48, 11 May 2020 (UTC)[reply]
    I passed my RFA in 2018 at about the same account age, if I recall correctly. --TheSandDoctor Talk 13:09, 11 May 2020 (UTC)[reply]
    User:usernamekiran, in his acceptance he linked to his other accounts here. -- MelanieN (talk) 15:59, 11 May 2020 (UTC)[reply]
    Thanks MelanieN. I somehow didnt see it. After seeing their "sort of activity" in the past, I was not so sure about me being in support or neutral. But currently the oppose section has a few good rationales. But they are not enough for me to oppose, so I will remain in neutral section :) —usernamekiran (talk) 09:52, 16 May 2020 (UTC)[reply]
  2. the candidate seems a bit opinionated on policies. this isn't an oppose because ignore all rules exists. Clone commando sev (talk) 23:03, 10 May 2020 (UTC)[reply]
  3. I'm trying to sort out whether starting to edit in Wikipedia space around May 2019, just a year ago, is sufficient. ☆ Bri (talk) 19:20, 14 May 2020 (UTC)[reply]
General comments
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.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_adminship/Creffett&oldid=1221634973"