Wikinews:Requests for permissions

Shortcut:
WN:RFP
WN:PERM

RFP Archives By date 2004  |  2005 2006  |  2007 2008  |  2009 2010  |  2011 2012-20 2021 By type Administrator Bureaucrat CheckUser Oversight Removal

Requests and votes Accreditation ARBCOM AWB Bots Functionaries Reviewer

Requests for permissions (RFP) is the process by which the Wikinews community decides which users can have access to the administrator, bureaucrat, checkuser, and oversight permissions.

• Users can submit their own requests (self-nomination), or
• Other users can nominate a candidate.

I	Please read the policy before making a request for permissions. See also the global permissions policy. Previous requests have been archived, and contain some common questions, comments, and objections made during the process.
II	Create your request for permission: Add your username in the box in the relevant section below and click the button. Complete the questions on the resulting page and save it. Transclude your request page at the foot of the relevant section by adding the title of your request page, enclosed by curly brackets e.g.: {{Wikinews:Requests for permissions/Administrator/YourUsername}} Then inform the Wikinews community of your request.
III	Questions You may be asked questions by other users so they can review your request. Please try to provide full answers.
IV	Community decision The request must remain open for at least one or two weeks (depending on the permission sought). A bureaucrat will close the request and will also grant the appropriate flag, if the minimum criteria have been met. For CheckUser or Oversight, the bureaucrat will request the flag at Meta. Closed requests are moved to the Archives.

CheckUser and Oversight

To add a nomination for CheckUser

Bddpaux

Nominating myself. One of ours is 100% in-the-wind and the other is about 98% in the same category. We need at least one CU active and checked in, although I am heavily focused on Reviewing and developing Reviewers (primarily) at the moment.--Bddpaux (talk) 19:55, 22 April 2024 (UTC)

Stats

• Links for Bddpaux: Bddpaux (talk · contribs · deleted · count · logs · block log · review log · lu)

Questions and comments

• I guess you've brushed up on the technical knowledge needed? (I ask since you asked Acagastya last month what CUs' duties are.) Also Acagastya is still fairly responsive to CU-related inquiries, not that having another CU would hurt. Heavy Water (talk) 03:18, 23 April 2024 (UTC)

I have, yes. We really need 2 active and involved here.--Bddpaux (talk) 20:35, 23 April 2024 (UTC)

Votes

• Support Very active, long-time editor here with advanced user permissions and who has already publicly declared his identity. No issues on other wikis. —Justin (koavf)❤T☮C☺M☯ 20:02, 23 April 2024 (UTC)
• Support We could definitely use another CU. I don't see anything that would cause me any issues in supporting this request. A.S. Thawley (talk) (calendar) 18:41, 24 April 2024 (UTC)
• Strong Support very nice well deserved user BigKrow (talk) 22:52, 24 April 2024 (UTC)
• Support I have recently had the need to request CU and unfortunately, neither local CU has responded. And our need for Checkusers will only increase once Temporary Accounts is rolled out. So I see this as both a short- and long-term solution for us. I also agree with Justin's comment above. Michael.C.Wright (^Talk/_Published) 23:56, 24 April 2024 (UTC)
• Support, I am not entirely convinced that this wiki should have local CUs. It's really too inactive and underserved with admin support to justify having them, and I think this can be taken over by stewards sooner or later, who are quicker to handle CU requests most of the time. However, this wiki does get quite a bit of abuse to the level where I think it does somewhat justify having local CheckUsers, and if there is someone relatively active who wants to help out, then that's positive. EPIC (talk) 08:45, 2 May 2024 (UTC)
• Strong Support Very active and experienced editor, already advanced permissions, we need another CU, disclosed identity, etc. Also, this user makes up more than 20% of this entire wikis editing, and is the main reason it hasn't totally fallen apart. Well deserved.Me Da Wikipedian (talk) 23:51, 14 May 2024 (UTC)

To add a nomination for Oversight

Removal

• {{Remove}} means "support removal of permission".
• {{Keep}} means "keep permission".

TUFKAAP

Inactive for at least two years since 16 July 2021 (last edit). No recorded log since March 2021. Twice notified about inactivity; no response yet. Per WN:PEP, should be de-sysopped. --George Ho (talk) 19:00, 15 July 2023 (UTC)

Stats

• Links for TUFKAAP: TUFKAAP (talk · contribs · deleted · count · logs · block log · review log · lu)

Questions and comments

• Comment: For what it's worth, they've continued to edit at enwiki as recently as this morning. Heavy Water (talk) 19:15, 15 July 2023 (UTC)

  Unsure how this counts. But thanks for the reminder, so I sent a message there. George Ho (talk) 21:21, 15 July 2023 (UTC)

• Comment: Yes, I've been away from Wikinews for a long while, I'm just busy in real life. Wikinews isn't like Wikipedia, since most articles are written mostly by one person with minor edits made by others. At least, that's it's always been to me. Wikipedia currently fits my workflow better in my busy life. I should note I was contacted by someone from the Foundation recently about the Wikinews Facebook account and trying to regain access to it because currently it is posting semi-NSFW videos using the Stories feature. Granted, I never had access and I think the person who had access was Brian McNeil, who as we know is sadly no longer with us. I will abide by whatever this RfP proposes, however, I don't think I should be de-sysopped for what it's worth. --Patrick M (TUFKAAP) (talk) 16:28, 28 August 2023 (UTC)
• Comment I will take action on this before May 15th. Please leave up for now.--Bddpaux (talk) 19:45, 22 April 2024 (UTC)

Votes

• Desysop Thanks for what you've done, but it seems like you've moved on. No prejudice against reapplying if/when life makes you available for service here. —Justin (koavf)❤T☮C☺M☯ 01:55, 16 July 2023 (UTC)
• Keep: PeP is both something the community can choose to apply, with discretion and common sense, and a measure to prevent compromised admin accounts or admins unaware of now-significantly changed policy, not a punitive one for simple inactivity. It shouldn't be taken as "better revoke any permissions as soon as the letter of these requirements is met." TUFKAAP is active elsewhere, so the security argument is moot; and I'm aware of no significant changes in customs regarding the use of admin tools in the past two years. Additionally, I think what SVTCobra said at Special:Diff/4730161 about having a shortage of admins makes sense. I'd add, for context about what was meant by "[ceasing] to be familiar with current practice": When drafting PeP and pushing for it to become a policy in 2012, Pi zero and Brianmc specifically expressed a desire to utilize it to revoke the permissions of those who either became reviewers very early on (i.e., about mid-2008 through 2009), when the standards for publishing were much lower, or left for the fork and were aware of Wikinews standards, but openly stated they had a complete lack of care about such, and even which site they were on. Heavy Water (talk) 19:32, 20 July 2023 (UTC)

  This is your general view about PeP, right? I don't see how this view helps us trust this admin to use the tools any longer. To clarify, why must your reluctance to enforce PeP and (supposed) shortage of admins be one of reasons to support this person as an admin? George Ho (talk) 17:29, 22 July 2023 (UTC)

  This is my view on enforcing PeP on TUFKAAP, and it's in line with my general view on enforcing PeP when the problems, listed above, that motivated the creation of PeP aren't present, especially at a time like this. As for the rest of your comment: WTF? I don't comprehend at all. Much of my vote was dedicated to explaining why those reasons make me inclined to oppose desysopping. I think one of the things you're saying is "you are reluctant to enforce PeP, but that should not matter, as it is policy." If it was like the review policy, you'd be right, but I go back to the first sentence of my vote, where I said PeP is "something the community can choose to apply, with discretion and common sense." Heavy Water (talk) 17:46, 22 July 2023 (UTC)

  I now recall you said practically the same thing to SVTCobra when he objected to your suggestion Gopher65 be desysopped, George. Heavy Water (talk) 19:54, 22 July 2023 (UTC)

  As you said, you have your reasons to oppose desysopping this person. Are they the same reasons to support this person as an admin? If so, I'd be flabbergasted, but whatever if the direction of the community heading toward your way. I have plenty of reason to oppose this person as an admin any longer, but if my reasons aren't enough for you, then... *sigh* George Ho (talk) 20:42, 22 July 2023 (UTC)

  Opposing desysopping is equivalent to supporting the admin remaining an admin, so yeah, they're the same reasons. Heavy Water (talk) 20:49, 22 July 2023 (UTC)

  Okay, what are your views about this admin besides PeP? George Ho (talk) 21:26, 22 July 2023 (UTC)

  I think they served well. I mean, I've never interacted with them, so I wouldn't really know, but. Heavy Water (talk) 21:29, 22 July 2023 (UTC)

  I've not interacted much with this person either, and I honestly can't say much about this person's hard work. However, the past is the past. No reason to hold on the past too long in the present, is there? George Ho (talk) 21:35, 22 July 2023 (UTC)

• Remove Seeing that the admin in question has been inactive for years, is active on the English Wikipedia, has been pinged there, and still doesn't care enough to engage here. Pecopteris (talk) 06:40, 20 August 2023 (UTC)

  "Doesn't care"? Why do you infer bad faith? TUFKAAP may well be too preoccupied in real life to respond here. But I find it highly unlikely someone with eighteen years' work on this project "doesn't care" about a request to desysop them. (To clarify, I'm not asking you to AGF — we have a guideline of never assuming good faith or bad, but drawing reasoned conclusions.) Heavy Water (talk) 17:20, 20 August 2023 (UTC)

• Keep, due to lack of sysop on this project. Lemonaka (talk) 05:05, 2 December 2023 (UTC)

  Is that the sufficient reason to preserve this inactive admin's tools? George Ho (talk) 12:10, 14 December 2023 (UTC)

  Generally, such reasons can be sufficient once the community agrees to that. On the other hand, I do not recognize any Wikimedia projects with such agreements. MathXplore (talk) 02:08, 26 February 2024 (UTC)

  Remove, but waiting for stewards regular check. Lemonaka (talk) 00:20, 23 January 2024 (UTC)

  (Note) According to m:Admin_activity_review#Please_note and Wikinews:Permission_expiry_policy#Introduction, local policy (Wikinews:Permission_expiry_policy) will be prioritized. Therefore, there will be no stewards regular check until our admins go to m:Steward_requests/Permissions#Removal_of_access (Wikinews:Requests_for_permissions/Policy#Requests_for_removal_of_permissions). Please let me know if I'm wrong. MathXplore (talk) 02:06, 26 February 2024 (UTC)

• Keep I am satisfied by the response of the user above. --Bedivere (talk) 02:36, 26 February 2024 (UTC)

  (Note) According to Wikinews:Requests_for_permissions/Policy#Requests_for_removal_of_permissions, no anonymous IP or new accounts will be allowed to vote. MathXplore (talk) 01:57, 26 February 2024 (UTC)

  Hi. I want to note it was me who voted actually. Have removed the IP. It's true I don't have any other edits right now but that might change, so I don't mind if you don't take this vote into the count. --Bedivere (talk) 02:36, 26 February 2024 (UTC)

  Thank you for the vote corrections. According to Wikinews:Requests_for_permissions/Policy#Requests_for_removal_of_permissions, our bureaucrats will count the votes. MathXplore (talk) 02:41, 26 February 2024 (UTC)

• Keep: I don't see inactivity alone as a reason to desysop when we already have a dearth of active admins. Leaving advanced privileges intact leaves the possibility they could come back and immediately lend a hand with maintenance tasks. Having said that, it would be great if @TUFKAAP could use their famous block hammer at WN:AAA. They may not want to write articles and that's fine. There are plenty of pages to be deleted^{(a specific need here)}, vandals to be blocked, etc. ツ Michael.C.Wright (^Talk/_Published) 00:27, 15 May 2024 (UTC)