Jump to content

Wikipedia:Bureaucrats' noticeboard

Page semi-protected
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Bibliomaniac15 (talk | contribs) at 01:43, 7 May 2020 (Desysop for SQL: done). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

    To contact bureaucrats to alert them of an urgent issue, please post below.
    For sensitive matters, you may contact an individual bureaucrat directly by e-mail.
    You may use this tool to locate recently active bureaucrats.

    The Bureaucrats' noticeboard is a place where items related to the Bureaucrats can be discussed and coordinated. Any user is welcome to leave a message or join the discussion here. Please start a new section for each topic.

    This is not a forum for grievances. It is a specific noticeboard addressing Bureaucrat-related issues. If you want to know more about an action by a particular bureaucrat, you should first raise the matter with them on their talk page. Please stay on topic, remain civil, and remember to assume good faith. Take extraneous comments or threads to relevant talk pages.

    If you are here to report that an RFA or an RFB is "overdue" or "expired", please wait at least 12 hours from the scheduled end time before making a post here about it. There are a fair number of active bureaucrats; and an eye is being kept on the time remaining on these discussions. Thank you for your patience.

    To request that your administrator status be removed, initiate a new section below.

    Crat tasks
    RfAs 0
    RfBs 0
    Overdue RfBs 0
    Overdue RfAs 0
    BRFAs 14
    Approved BRFAs 0
    Requests for adminship and bureaucratship update
    No current discussions. Recent RfAs, recent RfBs: (successful, unsuccessful)
    It is 16:37:26 on December 3, 2024, according to the server's time and date.


    Why are we doing this

    So I read the rfc (and voiced my opposition), but the more I think about this, the more I am trying to discern the rationale(s). What is the "preventative, not punitive" reason for this?

    Concern about the account being hacked? Now that much of renames went global, pretty much anything a bureaucrat can technically do, is presumably reversible.

    Concern that the person is "out-of-touch"? Well, as we well know from the "adminship activity standards", editing does not prove that at all. And further, one stays "in touch" by reading, not by editing, so the editing standards really are not indicative of much.

    Concern that there are not enough hats to go around, in this virtual environment?

    Are we just doing this as a sort of Recentism, or some other unnamed bias against editors we have not personally interacted with? (See also Wikipedia:Systemic_bias.)

    Is it perhaps an act of "control", to stem a personal fear that some bureaucrat may "swoop in" and close a discussion in a way we might not like? I'm aware that some see low editing activity as "bad", simply because they feel that they cannot fully bring "pressure" to bear to semipassively "coerce" others into doing what they want, with the implication of harassment/wikistalking and/or various types of disruption to a user's talk page, or articles edited by the user, or discussions they propose or participate in, since, as they are a less active editor, they potentially provide less options to bring to bear. (And yes, this is a real concern of closers and others, with "extra" tools. More than once I've heard a closer say they merely "counted votes", rather than attempting to discern consensus, out of fear of reprisals.)

    Or is this simply an "I want x"/"I don't want x"?

    I've seen a lot of RFCs in my time, for many stated (and implied) reasons, such as the above.

    I ask this sincerely. I think we should take a moment, and assess our motivation here.

    I would like to think I am fairly open-minded, and am open to civilly discussing divergent points of view. And I am a firm believer in the "Wiki-way".

    So what am I missing here? - jc37 20:50, 29 April 2020 (UTC)[reply]

    some other unnamed bias against editors we have not personally interacted with? I think that is somewhat correct, but would phrase it in a more positive tone. Crats, like other advanced permissions, are granted by a community based on trust. In an online community, like any other community, trust is developed through the creation of emotional bonds between individuals. One of the great problems of wikis like ours is that meatball:CommunityMayNotScale; there are so many people in our community that it is impossible for us to interact with everyone, and so our trust needs to operate on something other than our interpersonal connections between people. We come to rely on reputation. Often this reputation is a proxy for the strength, number, and quality of emotional ties one has within the community. As someone spends more time away from a community, their social bonds weaken: those they did know also leave, and new people they don't know join. As this process continues, eventually the member who left is forgotten by the collective because of the demographic changes inherent to a community, and with it their reputation. Wikipedia is interesting in that we have a superordinate goal of building an encyclopedia, so we have an alternate (and in fact, prefered) way to build reputation: working. When someone with permissions representing community trust leaves for a long time and then comes back, the community has a hard time continuing to trust them because the only proxies we have for trust no longer exist; their social and sweat-of-the-brow reputations are gone or diminished. The Crat permission (like others) serves to meatball:RewardReputation and encourage engagement with the community, so when that reputation is lost for whatever reason, the community tries to rectify the situation by removing the symbol of trust. The RfC, and inactivity standards in general, are reflections of the community attempting to decide what level of reputation is necessary to speak for meatball:TheCollective.
    That's not to say it's a benign move. As you and Cecropia point out, cutting ties with an absent community member is painful for that member and often for the community as well. In the short term, it may feel like inactivity policies meatball:PunishReputation and serve as a mark of Cain on the participant should they wish to return. I don't think we've had someone return after such a hiatus and then attempt another RfX, so I don't think this is something we know. The problem is that, even if it doesn't punish reputation, it does dissuade reputation making it less appealing for a community member to return. That's a cost, but many people think it is an acceptable cost given that someone has already de facto left the community. People move on in their lives, and the community should be able to move on too. Having a tool by which the community and an absent member can part ways is a net positive. Wug·a·po·des 21:37, 29 April 2020 (UTC)[reply]
    I love this analysis and I love meatballwiki. Killiondude (talk) 22:00, 29 April 2020 (UTC)[reply]
    Thank you, Wugapodes, for your thoughtful - (I'm intending Shakespeare-like usage meaning thought-filled) - comments.
    I too enjoy reading Meatball Wiki (I link to it on my user page : )
    That said, I am pondering your comments, and find I am caught between conflicting assertions with regards to your comments on reputation.
    If I am reading you correctly, you first suggest that trust may equate to reputation. And then suggest that, due to scale, editors may feel that the best way to illustrate reputation, is by "working", by which, I presume you mean, amassing edits/building a review-able edit history.
    But then you suggest that lack of engagement/interaction with others causes a decline of someone's reputation.
    Doesn't this seem like a contradiction in terms?
    And that aside, why are we presuming an editor's amassed edits have a shelf life? This is a wiki, and each person's edits are still there to see, for now and always. Are we to presume that time=distrust? I'm not sure why that should be. The same edits are there, which caused us as a community to support their RFB, so, why would we stop AGF of an editor with no evidence to do so?
    And while we're on the subject of reputation, one of the values that the community has oft-stated to look for in a bureaucrat is (to try to put it succinctly) an almost quiescent, level-headed nature. And discovering wiki editing habits of less-than-high-activity would seem to me to not be surprising in such a person.
    So all that said, if you are suggesting that the reasons you stated, are the reasons for the rfc, I can believe your assertion, but that as a rationale just doesn't sound appropriate as a (set of) criteria for establishing trust. It almost sounds like a rationale for why we are building distrust. And I'm not sure that that is what we as collegiate encyclopedia builders should be doing.
    So I guess I reiterate: What am I missing? - jc37 23:50, 29 April 2020 (UTC)[reply]
    I had guessed you would appreciate them! I wasn't around during the heyday of wikis, and I wish meta had more of meatball-like community (maybe it does and I'm just missing it). I think my post was less a reason why we ought to have inactivity requirements and more a theory on why discussions on inactivity criteria seem to be a recurring theme. You're right to criticize it, and I think your points make sense. Dweller asked a (presumably rhetorical) question in his opposition: "Why do we so often chase people away from the project instead of concentrating on making people feel welcome?" I think it's something we need to grapple with, and I said elsewhere that maybe inactivity requirements are an c2:AntiPattern. The problem is we rarely have counter proposals. How do we get inactive crats back, or at the very least, convince them to say goodbye before leaving? Same with admins, or really any other editor. I don't know.
    Your points about reputation are all interesting to think about. One point I really like is The same edits are there, which caused us as a community to support their RFB, so, why would we stop AGF of an editor with no evidence to do so? I think it's that social dynamics just don't work like that. In the abstract, I agree that the edits should stand for themselves, but I think the community aspect of the encyclopedia leads to dynamics that undercut that ideal. Maybe Wikipedia has become more meta:Metapedian over time?
    But to your point about reputation and contradiction, I think of it more like a leaky bucket. As long as the hose is on, you'll fill it, but if you leave the hose off for too long, all the water leaks out. But I think we need more than a two-value logic system; the empty bucket isn't distrust, but simply neutrality. We could also fill the bucket with sewer run-off and people would distrust the person carrying around a bucket full of sewage. That bucket also leaks, and if the person stops trying to fill it with sewage, eventually they'll also be at neutral, and can eventually fill it with water and be welcomed back into the community similar to how we handle vandalism and unblocks and such. That doesn't really answer your question, and I think I also conflated a diachronic analysis and a synchronic analysis which might be why it's a little confusing. This is more musings than a solid argument for why we should do things a certain way. I think you're raising interesting questions, and I appreciate that you're pressing the community to think about them. Wug·a·po·des 00:48, 30 April 2020 (UTC)[reply]
    Wugapodes put it much better than I could have but I will add in terms of the honoring of past work, I would strongly support SilkTork's proposal to give former crats a usergroup that recognized this fact. In this way should they return to the project (and I hope they do since I believe among the best places to find "new" editors are people who edited here in the past) they can get respect owed to them for their past service while building the reputation and doing the work Wugapodes described. Best, Barkeep49 (talk) 22:24, 29 April 2020 (UTC)[reply]
    I do appreciate the sentiment, but if we get technical, we're all Wikipedians here. Aren't we all "emeritus" after being "auto-confirmed"? I don't know if we should be so focused on editcount-itis or the "when" of the timestamps of an edit. Are we really telling editors: "Thanks, but what have you done for me lately." ? - jc37 23:50, 29 April 2020 (UTC)[reply]
    I agree. User groups are (ideally) assigned based on whether assigning this user group to a certain user will be beneficial to the project in that this user can now help out more. There is a reason why the symbols for admins and crats are a mop and a wrench respectively. They denote that these are technical, often thankless, jobs that are restricted merely because we cannot trust everyone to use them correctly. They are not achievements that should be put on display for the sake of having them (an idea that Wikipedia:Hat collecting describes pretty well). A "former crat" usergroup would only serve a single purpose: To give these users a hat to proudly present on their userpage (or wherever else). Because "respect" is not something that comes with having a certain hat (or multiple hats). There are plenty of "non-hatted" users I respect greatly just like I assume there are plenty of users who do not respect me just because I have certain hats. Regards SoWhy 05:54, 30 April 2020 (UTC)[reply]

    As a point of order, why is this discussion happening here rather than at the actual RfC, where such meta discussions would typically occur? ~ Amory (utc) 23:59, 29 April 2020 (UTC)[reply]

    Speaking merely for myself, it's here for several reasons, including that I think it's actually beyond the scope of the rfc, and could potentially derail it or at the very least muddy the waters there. AFAICT, I believe that what I'm asking about, is more sort of "self-reflective", and a bit broader in topic than that at the rfc. And besides that, WP:BN is, AFAIK, the appropriate place to discuss such "meta" matters of this topic. - jc37 00:15, 30 April 2020 (UTC)[reply]
    Especially now that the other threads are achived, this thread has been robbed of context to the point of barely being comprehensible. I think it should be moved to the RfC's talk page. Ben · Salvidrim!  04:43, 30 April 2020 (UTC)[reply]
    When Cecropia started a section similar to this it became unpleasant rather quickly. I could see this one going a similar route had it been posted there. Wug·a·po·des 00:53, 30 April 2020 (UTC)[reply]

    To respond to a minor point above made by Wugapodes, we have in fact had users who have had a successful RFA after lengthy inactivity. I recall Opabinia regalis after her second RFA; the List of resysopped users also brings up Abecedare; his RFA was in the same month as Opabinia regalis's, as it happens. I can't find any failed RFA's after lengthy inactivity, at least by checking the relevant list. Graham87 04:16, 30 April 2020 (UTC)[reply]

    • The OP states most crat actions are reversible. However, a re-sysop is not, unless a messy abcom case in started. That is essentially the sole reason why I supported the RfC. I do like the "emeritus" idea. Rgrds. --Bison X (talk) 05:04, 30 April 2020 (UTC)[reply]

    I do believe there is a concern regarding an absentee editor's familiarity with current norms on Wikipedia, but you are correct that this involves reading rather than editing. I think there are many editors who like to feel that decisions affecting them are made by people who have some skin in the game, so to speak: some current investment of time and effort that provides motivation to safeguard Wikipedia and its community. To a first approximation, this gets translated into "makes edits on Wikipedia". Beyond that, some editors have the philosophy that advanced permissions are granted to users so they can act as proxies to implement community consensus, and thus if they are not actively fulfilling this role, the permissions aren't needed and the community should reclaim them. (For purposes of this discussion, I am ignoring the security principle of least privileges; based on past discussions, it's an important consideration to some but not to a lot of others.) Because of the self-selection bias in any Wikipedia discussion, I believe these views have greater prominence in these discussions than they might with a more representative sampling of the community. isaacl (talk) 08:08, 1 May 2020 (UTC)[reply]

    The problem with the "skin in the game" argument is that it implies that those who have put in vast amounts of time into this project, but have been off wiki in recent years, don't have "skin in the game". Of course they do. The need to refresh and update one's knowledge of the wiki, the risk of long dormant accounts becoming compromised, and the risk of deteriorating faculties are real issues and less contentious to discuss. We can differ on how long one can leave a project before skills atrophy and values change, and on whether RFA should be a test of character and judgment - things that deteriorate little with age until dementia sets in, or a test of policy knowledge, which obviously fades more quickly with disuse. As a real world example, a couple of years ago I acquired a car for the first time in over a decade. My driving licence was fine, I passed my test when I was 19 and it will need renewing when I'm 70. But my no claims bonus had gone and has had to be rebuilt. The reason why we keep rehashing this debate is that the bit of the community that cares about this is divided between those who echo those two perspectives, we lack the rigorous evidence base that insurance companies use to calculate no claims bonuses, and we differ between those who see our pool of inactive and former admins as deadweight, or as part of the same community as us and including some of the people who will be keeping this place going for decades after I and other greybeards here have kicked the bucket. ϢereSpielChequers 12:31, 1 May 2020 (UTC)[reply]
    For better or worse, ongoing engagement in the form of participation on the site is one of the few measures available to try to estimate if someone remains committed to English Wikipedia's current set of policies, guidelines, and norms. Trust in a small community is easier to establish, when everyone knows each other. Once this is no longer possible, people look for concrete measures to try to evaluate trust. Although I appreciate that some editors feel quite upset at the difference between the difficulty in obtaining advanced privileges versus what has to be done to retain them, personally I think many of them overestimate the degree to which the community at large shares these feelings. isaacl (talk) 16:25, 1 May 2020 (UTC)[reply]
    Ongoing engagement is certainly a measure of commitment, and one that gets overvalued by people who mentally compare wikipedia to a work environment. Remembering that wikipedia is a volunteer environment, and one less than twenty years old, the challenge facing us is how do we keep the door open to former regulars when divorce, redundancy, retirement or other vicissitudes of life put them into a situation where they have the time to resume an old hobby. There is a lesser issue of doing this in a way that screens out compromised accounts and the like. Part of the problem is how one defines the community, if you think of it as just the currently active, you are liable to come to a different conclusion than if you think it also includes those who will return in future decades, or who might if we don't create excessive barriers against them. ϢereSpielChequers 19:10, 1 May 2020 (UTC)[reply]
    While I think it is a good idea to make it easy to return to the English Wikipedia community, I don't think this means it is necessary for editors to retain their advanced permissions while they are away. I think an initial increase in engagement is useful for the editor to re-establish or make new connections with others, in order to re-integrate with the community. For me, this isn't due to parallels with a work environment per se, but rather any gathering place where a community interacts and discusses matters of common interest, thereby building up a sense of camaraderie. isaacl (talk) 19:51, 1 May 2020 (UTC)[reply]
    WSC, I'm strongly in favor of making it easy for old volunteers to return to the fold. We should find ways to encourage them to do so. We should develop documentation to make it easy for them to figure out what's changed (because much will not have changed leaving their skills and expertise ready to go). But I can think of at least one concrete example in a volunteer organization I served where a former board member who'd been away for years wanted to re-engage with the organization. There were lots of ways that the organization worked to do just that. But, as a board member at the time, we didn't put them right back on the board. A little while later we did, but until then we took advantage of that skill and expertise by working with them in other ways and giving them other leadership opportunities. I'd love for an old crat to return and start closing difficult RfCs. Or help BAG, or weigh-in on whatever areas they had skills with before. But they can do all that without being a crat (at least right away). Best, Barkeep49 (talk) 01:42, 2 May 2020 (UTC)[reply]
    Hi Barkeep, we aren't as far apart as you think. I'm thinking in terms of a day with renewed activity for each year of absence before resuming userights as the sort of direction that I would like to see the community move in. Of course trustee is a role with limited hats - more comparable to Arbcom than adminship or crats. ϢereSpielChequers 11:04, 2 May 2020 (UTC)[reply]

    The following inactive administrators are being desysoped due to inactivity. Thank you for your service.

    1. Ronhjones (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
    2. RonBot (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
    3. Anna Frodesiak (talk · contribs · blocks · protections · deletions · page moves · rights · RfA)
    xaosflux Talk 01:18, 1 May 2020 (UTC)[reply]
    Sad on all counts. Especially sad for Anna, given the circumstances, but I’ll say I admire her convictions even if they’re not my own. Hopefully one day things will change and she’ll be back. TonyBallioni (talk) 01:31, 1 May 2020 (UTC)[reply]
    +1. Barkeep49 (talk) 02:02, 1 May 2020 (UTC)[reply]
    Woof, this is a rough one. ~ Amory (utc) 10:13, 1 May 2020 (UTC)[reply]
    I have some incredibly grim news that will make this section even rougher ... Ronhjones passed away on the day he made his last edit, as confirmed by a friend of his I contacted on Facebook, who confirmed that the Wikipedian and their friend were the same person. I can't find any online obituaries but there's his Facebook profile and this edit of his ... tying these together are LinkedIn and this Researchgate link. I'm trying to contact his family.
    I hope this isn't out of line .. I wouldn't normally dig this far but I had a funny feeling when I encountered this situation. I'll update the former admins pages; I might do the other procedures later if somebody else hasn't gotten to them by the time I get there. Graham87 12:06, 1 May 2020 (UTC)[reply]
    Thank you for the update Graham87 - I took care of the things for the bot account. — xaosflux Talk 13:14, 1 May 2020 (UTC)[reply]
    Thank you, Graham. ~ Amory (utc) 01:25, 2 May 2020 (UTC)[reply]
    What a loss. I hope his family knows that we on Wikipedia continue to miss him even now. Best, Barkeep49 (talk) 01:44, 2 May 2020 (UTC)[reply]
    @Barkeep49: Yes, see my message on the talk page. Graham87 11:51, 2 May 2020 (UTC)[reply]
    I have some even sadder news that I can now share publicly: Ron and his wife Sue died together in a house fire, as noted in their obituary from the London Inland Waterways Association newsletter. The friend of theirs who confirmed his passing also told me this info, but I didn't want to say it here without confirming that it was publicly available or I had permission. Graham87 16:22, 2 May 2020 (UTC)[reply]
    That is very sad, indeed. Useight (talk) 17:39, 2 May 2020 (UTC)[reply]
    I'm saddened at their deaths and the manner in which they died but thank you for confirming what happened and the lengths you took to do so, Graham87. Acalamari 18:01, 2 May 2020 (UTC)[reply]
    I too am extremely saddened not only by their deaths but too in the manner in which they died in, May they both rest in peace ❤️, Thank you Graham for your efforts here. –Davey2010Talk 18:32, 2 May 2020 (UTC)[reply]
    Oof...that's horrible. Rest in peace. :( Reaper Eternal (talk) 19:19, 2 May 2020 (UTC)[reply]

    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.


    Epbr123 (talk · contribs · logs)

    I somehow found an inactive admin. The criteria for desysop is 1 year of no edits OR logged actions. Last edit was 30 days ago, and last logged action was 5 years ago (actually 8 years ago). Leaving it here to bureaucrats for a potential desysop on July 1, 2020. {{replyto}} Can I Log In's (talk) page 00:21, 4 May 2020 (UTC)[reply]

    It’s an exclusive or. Not an inclusive or. TonyBallioni (talk) 00:25, 4 May 2020 (UTC)[reply]
    I'm interpreting it as "an admin is considered active if they make 1 edit AND action within 1 year". Is that not what it is? {{replyto}} Can I Log In's (talk) page 00:32, 4 May 2020 (UTC)[reply]
    No. TonyBallioni (talk) 00:33, 4 May 2020 (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.

    Desysop for SQL

    Hi 'crats. I need to take some time away from the project (a month to a few months). As a security precaution, please remove my sysop flag. I have a similar request at SRP[1] for my CU flag. SQLQuery me! 01:31, 7 May 2020 (UTC)[reply]

     Done Best wishes for your Wikibreak. bibliomaniac15 01:43, 7 May 2020 (UTC)[reply]