Texas Surge in RFA promotions—a sign of lasting change?: A close look at the history of approving administrators on English Wikipedia, and a roundup of news← Back to ContentsView Latest Issue17 January 2017
Discuss this story
A belated congrats to the editors of the Signpost for its 12th anniversary. We couldn't do without it. Erik Zachte (talk) 12:56, 17 January 2017 (UTC)[reply]
I think part of the problem is that RfA is essentially a political process, and selecting people for positions of public trust is always stressful and fraught with difficulties in balancing kindness with the need to publicly evaluate candidates. Go Phightins! and I had discussed the possibility of referencing an article like the following in the article, but didn't get around to it: People are so stressed by this election that the American Psychological Association has coping tips That's not to say that we don't have additional, unique considerations that compound the issue...but it's worthwhile to keep in mind that it's a challenging area for any community with formal positions. -Pete Forsyth (talk) 00:01, 18 January 2017 (UTC) (Editor)[reply]
Why are RFAs crucial to the health of wikipedia
I am not an ADMIN as opposed to most of those who have been interviewed for this story. However, I try to participate in all RFAs because I am very concerned about Bad Apple ADMINs. I define Bad Apple types as editors who have a chilling affect on those who cross paths with them to the point of losing potential good editors. I realize that many wannabe ADMINs don't want to go through a gruelling process to get the "mop". However I believe those unwilling to stand up to scrutiny, should not be ADMINs on wikipedia. Wikipedia is a vast world with no Separation of powers which, unfortunately, invites people with agendas to gain the tools that allow them to get rid of other editors with whom they disagree. Ottawahitech (talk) 18:32, 17 January 2017 (UTC)please ping me[reply]
Betteridge's law of headlines. (((The Quixotic Potato))) (talk) 20:04, 30 January 2017 (UTC)[reply]