Wikipedia talk:Administrators

Page contents not supported in other languages.
Source: Wikipedia, the free encyclopedia.

This is an old revision of this page, as edited by Fish and karate (talk | contribs) at 13:26, 3 March 2018 (→‎RFC: Slight tweak to lengthy inactivity policy: closing RFC). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

WikiProject iconWikipedia Help NA‑class Top‑importance
WikiProject iconThis page is within the scope of the Wikipedia Help Project, a collaborative effort to improve Wikipedia's help documentation for readers and contributors. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks. To browse help related resources see the Help Menu or Help Directory. Or ask for help on your talk page and a volunteer will visit you there.
NAThis page does not require a rating on the project's quality scale.
TopThis page has been rated as Top-importance on the project's importance scale.


Should one of the expectations of administrators be to have email enabled?

I'd like to see that as a requirement. Doug Weller talk 19:00, 24 January 2018 (UTC)[reply]

  • I agree. Totally. I suppose it would be OK to temporarily disable one's e-mail during a wikibreak, but otherwise, users should be able to e-mail all admins. Bishonen | talk 19:54, 24 January 2018 (UTC).[reply]
  • Best practice, yes, required? No. My email is enabled (and I don't think I ever had it disabled when I wasn't an admin), but there may be valid privacy and harassment reasons why an admin does not want email enabled. TonyBallioni (talk) 20:01, 24 January 2018 (UTC)[reply]
  • No, instead of getting the message that the admin's email is disabled, and knowing to move on to another admin / process / etc, you would end up with emails falling off into the void (either switching to a bs email address, or filtering mail from wikipedia most likely). I agree with Tony - it is a best practice. SQLQuery me! 20:49, 24 January 2018 (UTC)[reply]
  • I'm an admin. My email is enabled, and that is only for the situation where I forget my password (it has happened). If anybody else emails me, I usually ignore the email, so it does fall off into the void in a sense. My reason is that I believe in openness, so I discuss Wikipedia matters on-wiki, the only exception being at organised meetups such as m:Meetup/Oxford/57. --Redrose64 🌹 (talk) 23:30, 24 January 2018 (UTC)[reply]
    I agree with this.--Ymblanter (talk) 08:12, 25 January 2018 (UTC)[reply]
  • Yes, this should be a requirement per the general sense of
    WP:ADMINACCT which requires that admins be contactable. Some issues might be sensitive, such as BLP enforcement, and so open discussion on talk pages might be considered inappropriate. There then needs to be a private communication channel and email seems to be the standard alternative. Andrew D. (talk) 08:34, 25 January 2018 (UTC)[reply
    ]
  • Yes. -- Euryalus (talk) 09:07, 25 January 2018 (UTC)[reply]
  • Yes, a requirement. The question of where one replies (per RedRose64 above) is actually distinct to the question asked. All admins should have email enabled in the spirit of making oneself openly communicable, particularly so as not to deter editors from sending private info. Or indeed, editors who just do not want to be seen asking a certain question  :) However, per RedRose— with whom I agree—this does not automatically mean one is entitled to a reply, and the choice to do so, or to otherwise reply publicly, is very much still reserved to the admin. >SerialNumber54129...speculates 09:48, 25 January 2018 (UTC)[reply]
    Actually, administrators are not really authorised to deal with private info, and I was always uncomfortable when I was sent pieces of private information. I would say if issues can not be discussed onwiki, they should be sent to
    WP:OVERSIGHT if needed.--Ymblanter (talk) 10:11, 25 January 2018 (UTC)[reply
    ]
    But there is not a single quality called privacy, and a thing that is not oversightable may still be private. I'd like to think that admins were willing to save editors' good faith embarrassment if they had the ability to. >SerialNumber54129...speculates 11:03, 25 January 2018 (UTC)[reply]
  • I wonder whether it's plausible to assume that everyone can have a secure email address. I also think that since the community has no effective means to monitor email usage (all what we can do is to ask a checkuser if user X sent an email at date Y, or take Z's word at face value without firm proof), there is more potential for abuse there than with an user talk page. Jo-Jo Eumerus (talk, contributions) 10:24, 25 January 2018 (UTC)[reply]
  • Best practice, yes - requirement, no. If admins don't want to be bothered by users outside the time they have allotted to working here, they should be able to choose so. There is no requirement at RFA that says admins have to be available outside Wikipedia. What's next, requiring admins to be active on IRC? As Ymblanter points out, there are already processes to handle certain matters, like OTRS and OS and we should encourage people to send privacy-relevant requests there instead of some random admin who might not even be active at that time. Regards SoWhy 10:35, 25 January 2018 (UTC)[reply]
    Just to clarify, that's nothing in the proposal that says anything about doing unpaid overtime, or out of hours work. If an admin is daft enough, though, to use a main email a/c, rather than a single use, generic <[email protected]> than that is, absolutely and irreparably, their lookout. >SerialNumber54129...speculates 11:03, 25 January 2018 (UTC)[reply]
    It's all unpaid overtime... ~ Amory (utc) 12:54, 25 January 2018 (UTC)[reply]
    No, if an admin doesn't want to deal with wikimatters off wikipedia they should be able to have this separation. There are plenty of admins who are fine with this and very few matters can't be dealt with on talk pages. For cases where users are prevented from sending emails or blocked from their talk, there is usually a reason and UTRS exists. (my email is on but I ignore most emails or reply on wiki)
    Spartaz Humbug! 12:40, 25 January 2018 (UTC)[reply
    ]
  • No. Recommended best practice perhaps, but not a requirement. If an admin only wants to be contacted on-wiki, that should be their right. Users shouldn't be contacting admins about urgent or private matters anyway, we have official emails for those things. Ivanvector (Talk/Edits) 12:46, 25 January 2018 (UTC)[reply]
  • No, administrators should not be required to have email enabled. To some extent, it would go against Wikimedia's privacy policy ("If you do create an account, you do not need to give us your name or email address"). It's a voluntary service; and to add to this, for those administrators who, of their own choice, have emails enabled, there is no (and there should be no) further requirement that they need to answer via emails to received emails. Lourdes 12:48, 25 January 2018 (UTC)[reply]
  • What SoWhy said. Best practice, and to be encouraged, but not required. We should encourage as much to be on-Wiki as possible, and email certainly encourages the spreading of personal information. There's no guarantee that email would be more responsive anyway — plenty of folks have non-personal emails for privacy reasons, and as someone recently more active, it's easy to miss emails for months/years. ~ Amory (utc) 12:54, 25 January 2018 (UTC)[reply]
  • Of course not, best practice maybe, but certainly not required. I have mine enabled but as someone above mentioned, that is mostly for password reasons. There is pretty much nothing as an individual admin that I would deal with through email that cannot be done on a talk page. Anything that needs privacy can go to OTRS etc. -DJSasso (talk) 13:11, 25 January 2018 (UTC)[reply]
  • As Tony says above, best practice, yes, requirement, no. There are privacy-respecting venues that can be used for material that can't go on talk. --SarekOfVulcan (talk) 13:56, 25 January 2018 (UTC)[reply]
  • No. All the good arguments have been taken already, so I'll just throw my weight behind Lourdes, SoWhy, Tony and others. Best practice, but not a requirement. We are volunteers, after all... *goes off to check Wikipedia email inbox for the eighth time today... 14:01, 25 January 2018 (UTC) — Preceding unsigned comment added by Yunshui (talkcontribs)
    • Just because all the good arguments are already gone that's no reason to hide your name from us as well Regards SoWhy 14:44, 25 January 2018 (UTC)[reply]
  • No. Echoing most of the others, it's a good idea, especially for password recovery - but requiring it "to be enabled", no. I would not expect them to be 'required' to actually read it even if it were enabled. Should this conversation result in a "yes", I think it should be "required" that anyone wanting to email an admin under a communications expectation also be required to contact them publicly (by leaving a talk page message such as {{
    ygm}}) as email delivery (and echo notifications) can be unreliable. — xaosflux Talk 14:24, 25 January 2018 (UTC)[reply
    ]
  • Interestingly enough, I note that, unless I am missing something
    WP:ADMIN mentions communication, only in "failure to communicate" (are we uncommunicative about communication?). So perhaps all these ways of communicating about admin-type things should be added in a section, 'Communication with Admins'. Perhaps I am reading more into this but given Doug started this, is this prompted by an admin-to-admin communication issue? If so the communication section I suggest should address that, too. (I also, think, that if an admin is the type that regularly ignores e-mails, as many people are, it's really better if it's shut off, or they make that rather clear, somehow). Alanscottwalker (talk) 14:52, 25 January 2018 (UTC)[reply
    ]
  • Agree with it as a best practice but not a hard requirement. If private information that can’t be shared on-wiki is involved, users should be contacting the
    talk) 16:44, 25 January 2018 (UTC)[reply
    ]
  • It should not be a requirement. No admin needs to be "on call" when off-wiki. There's nothing I can do that one of the admins on
    WP:AN couldn't handle. I personally have it enabled, but if anyone has been sending me e-mails I have definitely missed them.--Aervanath (talk) 14:12, 26 January 2018 (UTC)[reply
    ]
  • Comment I just noticed the standard AE block template in Twinkle (which I'm thinking most admins use) has this text: "You may also appeal directly to me (by email), before or instead of appealing on your talk page." The template itself has an option to turn that wording off but that's not the default nor can it be adjusted through Twinkle. There's no time limit on when an appeal can be initiated so admins using this specific block template should be aware that there is an expectation they'll be reachable by email. --NeilN talk to me 05:26, 30 January 2018 (UTC)[reply]
  • Some things are best handled by email, most things are best handled on wiki. My email is enabled, I get a trickle of email, almost all perfectly OK. But I'm a bloke. I can understand some of our female admins not enabling email. More generally are we addressing a problem here or being bureaucratic for the sake of it? Do we have regular backlogs anywhere that involves emailing admins? ϢereSpielChequers 18:12, 30 January 2018 (UTC)[reply]
  • I have email enabled, and I've gotten exactly zero of them since I became an admin last September. Don't know if there's a pressing need for email to be enabled. ansh666 18:58, 30 January 2018 (UTC)[reply]
  • Not sure I would force admin to enable email, but would strongly request it. There are plenty of times when an editor or another admin need to contact an admin privately (
    WP:HARASS, etc) and best practice is for it to be enabled. Dennis Brown - 14:19, 5 February 2018 (UTC)[reply
    ]

RFC: Slight tweak to lengthy inactivity policy

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


In the case of admins who have not actively used their tools for a prolonged period, should they still be granted two years to simply ask for them back if they are removed for inactivity?

talk) 22:59, 4 February 2018 (UTC)[reply
]

  • No This occured to me when looking over Wikipedia:Inactive administrators/2017. There are numerous admins there who went totally inactive in 2016 after not taking any administrative action for a prolonged period prior to that: In nine cases, there was no tool use for between five and ten years, five cases where the user had not used their tools in over ten years, and one very extreme case of an admin who got the tools in 2004, never used them even one time, and hadn’t actually spoken to another user on any sort of talk page in 12 years.
And yet, in all of these cases current policy grants them two additional years in which all they need do is ask, and they will get their tools back. Re-granting the tools is the purview of the bureaucrats, who aren’t given much leeway to bend the rules, so if one or more of these admins were to ask for their tools back anytime in the next two years, they would be compelled to do so. This just can’t be the right way of doing this.
I would therefore propose that any admin who has not used their tools in five years and is subsequently desysopped for total inactivity would no longer be able to simply ask for them back, and would need to pass a new RFA to regain the tools and that wording to this effect be added to the administrative policy at Wikipedia:Administrators#Lengthy inactivity.
The point of granting advanced permissions is not to reward users, but to give them what they need to help maintain the encyclopedia. If they aren’t doing that, they aren’t actually admins, and
talk) 23:12, 31 December 2017 (UTC)[reply
]
You do know we already have activity requirements and have for some years now? This is just a minor tweak to the existing requirements, if you are opposed to the very idea that we have any standards that is a seperate discussion.
talk) 20:49, 6 February 2018 (UTC)[reply
]
Oppose both the proposed requirement tweak and the existing requirements, although only the former is relevant to this particular discussion. Κσυπ Cyp   06:56, 7 February 2018 (UTC)[reply]
  • Oppose, change goes into a wrong and unhelpful direction. The proposal makes it harder for people who have been admins to become admins again. What we need is to make it easier for people who have never been admins to become admins. How does your proposal help? —Kusma (t·c) 21:01, 6 February 2018 (UTC)[reply]
  • I'm fine with the proposal. If you haven't logged an action in five years, and haven't touched the project in two one, then I don't see a compelling reason to assume that you have a current and nuanced understanding of policy. No comment on admins with barely a ghost of activity opposing what is an exceptionally lenient increase in our inactivity policy. GMGtalk 07:39, 7 February 2018 (UTC)[reply]
    Clarifying question related to this: someone brought up five years, but I don't see it on the policy page anymore. Could someone give a clear policy proposal here? From what it looks like, this will change the activity requirement to an edit or log action in the last year or else permanent removal. But I don't have any experience with how this policy was made or how it is applied, so I would appreciate some clarification. -- Ajraddatz (talk) 07:50, 7 February 2018 (UTC)[reply]
    Full disclosure, I'm running on caffeine, calories and nothing resembling sleep. It does look like there are two ways I see to read the proposal actually, depending on how you interpret the word "subsequently". Either five years of no logged actions the last of which had no edits at all, or five years of no logged actions followed by a sixth year of no edits at all. GMGtalk 08:01, 7 February 2018 (UTC)[reply]
  • Support. If an admin is not active for 5 years, they clearly aren't being an admin and should not be able to simply request the tools after being desysopped for inactivity. A lot changes in 5 years of inactivity, enough that they should have to go through RfA again. However, I do think the comments about admins who use the tools in a way that doesn't get logged as activity make a valid point about how admin tool inactivity should be considered. timawesomenesstalk⟩ 06:10, 9 February 2018 (UTC)[reply]
  • No, assuming however, that we find a way to account for non-logged actions. If someone hasn't been an admin for one year, I think they're likely out of step with the community; the current policy allows for a good bit longer than that. Maybe we should be spending our time on fixing RFA instead, but I don't see how this can hurt, and I do see ways it can help. Vanamonde (talk) 12:14, 13 February 2018 (UTC)[reply]
  • Not as worded A couple of years ago, Arb made it clear that closing an WP:AE discussion is indeed an admin action (subject to wheel warring policy if reverted) yet it is not logged. I don't think closing an AFD as "keep" creates a log entry, although policy clearly prefers admin close AFDs (although doesn't require the bit). Many admin actions do not generate log entries, so this is fairly unworkable. Dennis Brown - 13:49, 13 February 2018 (UTC)[reply]
  • Comment All of the discussion about logged vs non-logged admin actions does not really seem on point to me. We are not talking about an automated process that simply looks at logs and spits out a binary decision we are discussing guidance to give to human beings whose judgement on the suitability of an editor for the admin bit we already trust. Not having performed a logged admin action simply is a trigger ie a necessary but not sufficient condition. If there are no logged actions then it is necessary to look and see if the admin is doing other adminy stuff before making a final decision.

    Why not just say "In the case of admins who have not actively used their tools for a prolonged period, and have not otherwise performed administrative actions" and proceed from there? The purpose, as I understand it, is to give the Bureaucrats a bit of leeway that they do not otherwise have to deal with inactive admins. As to identifying other 'adminy' actions, just ask the editor in question, if they can not point to something they do not need the tools back. Jbh Talk 18:45, 13 February 2018 (UTC)[reply]

    As I said above, we simply can't know if someone has used their tools recently or not. Viewing deleted revisions leaves no trace at all; editing through protection would be painfully difficult to spot (afaik there aren't automated tools for this yet). And since we're talking about inactive editors - being desysopped for inactivity requires one year of total inactivity, at least as far as we can tell, given what I noted before - we can't simply ask them. ansh666 19:57, 13 February 2018 (UTC)[reply]
    (edit conflict) Ummm... The question asked by this RfC is "...should they still be granted two years to simply ask for them back if they are removed for inactivity?" They have already been desysoped and they are asking for them back so it is possible to ask them questions as well.

    If the question is whether to desysop and how to determine activity many of the situations brought up can be handled by a bit of searching - ie closes etc. There are not so many of these that spending an hour or so looking into each is much of a burden. In the hypothetical case of an admin who has been so inactive as to be examined for whether they should be desysopped and it is impossible to get in touch with them then they should have the tools removed. When they come back they can be asked what it is they are doing that left no trace. If they have been doing admin stuff within whatever window it is that we require then give them the tools back, if not do not.

    If they are not editing and can not be asked the question then they do not need the tools because... they are not editing. It seems to me that this, like most changes on Wikipedia, is being made much harder than it need be by placing too much emphasis on edge cases. The final decisions in this are being made by highly trusted users who can figure the edge cases out. What they need from the community is a set of instructions to guide them in making those decisions in line with community wishes/expectations. Jbh Talk 20:53, 13 February 2018 (UTC)[reply]

    Wow, I feel really dumb now. Of course we'd be able to ask them, this would only come up when they're asking for the bit back. Sorry about that. In any case, the focus on edge cases here, specifically, is because bureaucrats have historically not been welcomed by the community to use IAR and such as freely as everyone else, so considering edge cases is important. ansh666 22:57, 13 February 2018 (UTC)[reply]
  • No. I agree with
    Beeblebrox's proposal: for any admin who has not used their tools in five years and is subsequently desysopped for total inactivity, bureaucrats should usually not regrant the tools upon request.. Perfect. Let's leave a little room for 'crat discretion. Bishonen | talk 20:49, 13 February 2018 (UTC).[reply
    ]
  • No. The admin bit is a tool to assist with maintenance, not elevation to the Wikipedia Peerage. If someone hasn't used the admin tools for a protracted period, then we can't trust that they still understand current policy and (importantly) custom and practice, and they should have to go through RFA again. If anything, I'd support making the inactivity rules even stricter. ‑ 
    Iridescent 20:55, 13 February 2018 (UTC)[reply
    ]
I would too, even with this little tweak the rules are still incredibly lenient. When I was drafting this I had some ideas that were significantly stricter than this, but thought it would be best to start with something small and achievable.
talk) 22:03, 13 February 2018 (UTC)[reply
]
  • No One small step towards making sure people with the admin bit are familiar with current community practices and norms. --NeilN talk to me 22:15, 13 February 2018 (UTC)[reply]
  • No, by which I mean yes, let's make the change Beeblebrox is suggesting. While non-logged admin actions (reviewing deleted content, responding to emailing queries, etc.) can be helpful, requiring a single logged action every few years is nowhere close to an unreasonably burdensome requirement. 28bytes (talk) 01:18, 14 February 2018 (UTC)[reply]
  • Comment We talk about giving Crats some wiggle room for "discretion" but that is kind of against the grain for a Crat. Crats are supposed to act in a way that is clearly and obviously documented, making high level actions that are non-controversial. Most Crats like clear lines drawn in the sand. The last thing a Crat wants is to be dragged to WP:AN to explain why they put the admin bit to someone when the rules were fuzzy. Whatever we do, if anything, it should a hard and fast rule that leaves little to debate. Dennis Brown - 01:33, 14 February 2018 (UTC)[reply]
  • No however this hardly goes far enough IMO. For example look at this batch of "admins" - they have ZERO logged actions in 5 years or more (including ANY action, not just sysop actions - even a Thanks would avoid this list).
big list
user_name user_editcount user_registration Last edit Last log
Sebastiankessel 4569 20050607221548 20170126191418 20090129213910
Knowledge Seeker 10201 20041122073705 20170301023720 20100505205338
RG2 13292 20050828070336 20170303064209 20111130043959
Yannismarou 20253 20060102151546 20170309153458 20120131222718
Chochopk 24485 20050117093317 20170330061951 20110709043351
Bratsche 5479 20030104000341 20170416034406 20080930033108
Scott Burley 3312 20040503062516 20170517231623 20120826044153
Moink 5432 20031202000434 20170520101957 20120606101704
David.Monniaux 17000 20030913115900 20170605134217 20111203144756
Thatcher 28280 20060208173441 20170615220941 20121107052744
KF 23685 20020225155115 20170727110704 20120520025610
Arcadian 163049 20040913134723 20170806092412 20120424100541
Where 7156 20051225023642 20170809160526 20110810012028
Daniel Quinlan 4700 20021207042559 20170829234211 20100711203841
G.A.S 15690 20060905182406 20170907103632 20121120043339
Fang Aili 24548 20050809133756 20170913184534 20120317174753
Babajobu 7998 20050128142308 20170918042415 20111028021547
Jrdioko 4460 20040313220527 20171006204133 20090125183223
Morven 18617 20030217073253 20171030015717 20090310163226
Davidruben 18989 20040907001819 20171107231910 20110410231547
Butseriouslyfolks 16737 20070104201720 20171124013346 20111011054725
K1Bond007 25913 20030805032410 20171224050135 20100819063220
Graft 3473 20020714112549 20171230235415 20090513002809
Ilyanep 6908 20030507214927 20171231201943 20111126083352
Brian 4151 20050709085306 20180101012825 20120201004455
Tcncv 17720 20080315041627 20180102042812 20120807235435
Harro5
14593 20050314051629 20180102082102 20120608070545
Viajero 11388 20030104002332 20180124153812 20081012070805
Dwheeler 2800 20020805092806 20180125162605 20050812155306
Peruvianllama 13508 20040326191110 20180207045641 20130111043559
  • I generally expect admins to actually use their mops to help maintain the project, and these editors seemed to have lost the key to the mop closet. — xaosflux Talk 02:17, 14 February 2018 (UTC)[reply]
I don’t uderstand why someone who never uses the tools at all would care whether they had them or not, there’s really no reason I can see other than wanting the status, which is funny since actual working admins don’t exactly live in a world of unending respect and universal love where everything is puppies and rainbows.
talk) 06:02, 14 February 2018 (UTC)[reply
]
Yeah, I deliberately aimed low with this proposal, it’s still exceedingly lenient and won’t affect anyone who still makes one edit per year, logged actions or no. Somewhere between this and the proposal you mention lies a good balance that the community will support this is a baby step in that direction.
talk) 20:45, 18 February 2018 (UTC)[reply
]
I mean... I understand where the argument is getting at, but I have personally seen multiple times when returning admins needed fairly basic policy explained to them, of the type that any RfA candidate would be expected to understand before they're handed extra buttons (at times even asked and answered at the Teahouse of all places, although I'd be hard pressed to find the diffs), and this starts to at some point, codify very different sets of expectations from the community. I would also point out... again... that half a decade away from the project is a pretty exceptionally long time. Even as someone who considers themselves fairly inactive, you don't even approach the type of standard being proposed here. This wouldn't catch most "sometimes-inactive" admins; it would catch patently absent ones.
There is also IMO a larger matter of eroding the notion of the admin corps being its own landed aristocracy, which I, and I'm sure many others, see as an overall positive direction to go in. I expect this peerage is the main reason why RfA has continuously inched closer to a beatification process, rather than a net-positive/negative evaluation, because it's seen by many as, if a mistake, a nearly irrevocable one that must necessarily degrade into a spectacular catastrophe in order to undo.
I would argue that the whole thing on average is corrosive of community confidence in the corps overall, and leads to a less effective cohort, filled with some fairly unqualified candidates, and less overall qualified active ones because of the effect it has on recruitment. GMGtalk 15:42, 22 February 2018 (UTC)[reply]
Exactly this. I am not concerned with the account security or policy forgetfulness issues. I just don't see how adminship can be "not a big deal" but also a lifetime appointment. I don't advocate for a very high activity standard, because that would make it more of a big deal than no activity standard at all. But I think that some easy processes to remove adminship from people who no longer need the buttons is a step in the right direction. And I support this proposal, because it actually enforces that standard, rather than removing the tools but not the status as the current policy does. I would also like to see the policy changed to prevent admins from continually turning in the bit and then getting it back when they come back from vacation, but that's another debate I suppose. -- Ajraddatz (talk) 18:28, 22 February 2018 (UTC)[reply]
@Ajraddatz: guess it depends on the length of the vacation, the ones that literally make 1 edit a year (often removing the required warning notice) and go away for a year are the ones keeping up the "lifetime" standards. Notably, this discussion will not have any impact on them. — xaosflux Talk 18:53, 22 February 2018 (UTC)[reply]
  • No / Support. Though I think I would prefer it to fix the 5 year interval as running between the last admin action and the request to regain the tools, which doesn't quite seem to be the proposal (I find it a touch unclear on that). Johnbod (talk) 12:13, 22 February 2018 (UTC)[reply]
  • Meh. Seems like a solution looking for a problem. Stifle (talk) 17:28, 22 February 2018 (UTC)[reply]
  • No or Support proposal, whichever is more clear. If an admin hasn't made a logged action in the last year, chances are that they're busy. If an admin hasn't made a logged admin in the last five years, chances are that they're either using only the viewing-deleted-revisions function, or they really aren't on Wikipedia and need to get re-familiarized with the rules. If these users are in good standing, passing a re-RFA shouldn't be a problem. epicgenius (talk) 01:19, 23 February 2018 (UTC)[reply]
  • Oppose A very large percentage of admin actions don't actually generate a log entry, closing Afds, Tfds, etc. Closing request for moves or other Rfds etc etc. That being said there really shouldn't be activity requirements other than editing requirements to keep the bit. No admin should be forced to use their tools just for the sake of activity. -DJSasso (talk) 13:18, 23 February 2018 (UTC)[reply]
This argument is a red herring. It’s incredibly unlikely that someone would spend five years doing admin work on a regular basis yet never once see any situation where admin tools were called for. It just doesn’t add up.
talk) 04:42, 28 February 2018 (UTC)[reply
]
  • No (or Support proposal, whichever is more clear). We're talking about logged admin actions here - not things that are preferred to be done by admins but which any editor can do without the tools. Admins are elected at RfA on the fundamental premise that they claim to need the tools and will use them. Kudpung กุดผึ้ง (talk) 14:40, 24 February 2018 (UTC)[reply]
  • No/Support - As mentioned above, this stance is still exceptionally lenient. I mean seriously, this will only apply to admins who haven't logged a single edit in a year, and have not logged an admin function in five years. And to the people saying that "not all admin actions are logged": seriously? No admin is going around using the mop in a way that doesn't log a single action for five freaking years. Can you imagine a desysopped admin coming back 7 years after their last admin action, saying, "It's okay because I've been using the mop to look at deleted revisions". Not exactly a mitigating factor. Swarm 00:47, 26 February 2018 (UTC)[reply]
  • No/Support per Swarm. Double sharp (talk) 05:09, 27 February 2018 (UTC)[reply]
  • No/Support per Swarm and further the project is nearly 17 years and activity of several of them has declined over time .Pharaoh of the Wizards (talk) 08:34, 28 February 2018 (UTC)[reply]
  • No if they aren’t being used for so long, there’s no point in having them. Even with this proposed change, it’s still much too lenient for me. Part of me can appreciate what Slakr says above, and the fear of having to go through RFA is not unexpected from less active admins. But at the end of the day if you aren’t here, you don’t need extra privs. Aiken D 16:46, 28 February 2018 (UTC)[reply]
  • NO/Support: Oh give me a break. If you toodle over to the section of Wikipedia where they approve the use of scripts for approval/declining of draft articles, if you've been inactive for a couple of years, they turn you down and ask you to get familiar again with current WP standards before reapplying. WP changes all the time, and I really don't think any admin who takes a few years off has the current knowledge to be FIT for the mop. Nha Trang Allons! 19:31, 1 March 2018 (UTC)[reply]
  • No (i.e. support proposal)- This seems to me very sensible. Being an admin is a functionality, not an honorific. If it no longer serves any function, then the rights should be removed. Beyond My Ken (talk) 12:27, 2 March 2018 (UTC)[reply]
  • No (support). Really great to see this proposal getting traction in contrast to prior efforts to rein in the hangers-on.  — Scott talk 13:17, 2 March 2018 (UTC)[reply]
  • No yes, admins need to use their tools to remain familiar with the standards, and there are a few good analogies above. As for the minutiae as to what constitutes an admin action- well that's why we have bureaucrats. jcc (tea and biscuits) 23:40, 2 March 2018 (UTC)[reply]
  • No - Just no. Coffee // have a ☕️ // beans // 02:19, 3 March 2018 (UTC)[reply]

Close requested

I think it’s pretty clear what the result is here, and have asked at

talk) 19:54, 2 March 2018 (UTC)[reply
]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Inactivity?

Should an admin with just two (non-admin) edits in the last year still keep the bit? (A once very-active editor whose edits over the last eight years haven't exceeded double figures.) Andy Dingley (talk) 01:08, 22 February 2018 (UTC)[reply]

Under current policy, yes. Attempts to raise it above 1 edit or log entry a year have failed in the past. TonyBallioni (talk) 01:12, 22 February 2018 (UTC)[reply]
So the absence of any admin actions isn't grounds then? That is surprising (although it's how I read the literal statement too). Andy Dingley (talk) 01:40, 22 February 2018 (UTC)[reply]
All an admin has to do is either have one edit or one logged action a year to keep the bit. The reason for this that has been explained to me was that the community adapted the activity policy primarily for account security concerns, not for reasons involving competence and familiarity with project norms. TonyBallioni (talk) 01:45, 22 February 2018 (UTC)[reply]
Not exactly. The original discussions leading to the introduction of the process featured all those elements strongly, but the account security argument was harder to dismiss. Failure in 2008, success in 2011. Johnbod (talk) 11:54, 22 February 2018 (UTC)[reply]
Sorites paradox ~ Amory (utc) 01:23, 22 February 2018 (UTC)[reply]

You can see in the above discussion that some users are disputing whether not using the tools at all for five years is sufficient reason to question someone’s fitness to be an admin. There is a segment of the community that seems to think “not all admin actions are logged” is a blanket argument against any sort of standards for admin activity. It’s ridiculous, but there are enough people who actually believe it to keep things more ro less the way they are.

talk) 02:10, 22 February 2018 (UTC)[reply
]

In the 2011 discussion I link to above I mentioned several admins who hadn't edited at all since 2002; there were still plenty of people against de-sysop. Johnbod (talk) 12:08, 22 February 2018 (UTC)[reply]
@Andy Dingley: see in the thread above "big list" there are admins with 0 logged actions in over 10 years. — xaosflux Talk 15:11, 22 February 2018 (UTC)[reply]