Jump to content

Wikinews:Requests for permissions/Archive 11

From Wikinews, the free news source you can write!



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

NOMINATING COMMENT HERE -- NOMINATOR'S SIGNATURE WITH TIMESTAMP

Stats

Questions and comments

@Muluka Ahmed: I think this nomination may have been made in error. The position of bureaucrat is a fairly powerful one, and not one that will be granted to members of the Wikinews community without significant trust and experience. If you're interested in contributing to Wikinews, please do check out Wikinews:Writing an article and Wikinews:Style guide! --LivelyRatification (talk) 23:43, 16 May 2022 (UTC)reply

Votes


The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.


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

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)reply

Stats

Questions and comments

Votes


  • No clear consensus - after ten months of voting, the balance appears to be four in favour of removal and three against. Although the policy is for these votes to take place, there has to be clear consensus before removal can take place. [24Cr][talk] 20:27, 27 May 2024 (UTC)reply

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.





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

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)reply

I am withdrawing this request. Any Administrator: Take action. Close this as withdrawn.--Bddpaux (talk) 19:27, 3 June 2024 (UTC)reply

Stats

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)reply
I have, yes. We really need 2 active and involved here.--Bddpaux (talk) 20:35, 23 April 2024 (UTC)reply

Votes

I have withdrawn my vote because the requester has announced a long-term break from the project.[2] I think this request should be closed as it is no longer supported by the requester given their stated, long-term break. Michael.C.Wright (Talk/Published) 13:52, 3 June 2024 (UTC)reply
  • 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)reply
    Regarding the issues pointed out here; I am not sure what to think. I need to think about this for a while. EPIC (talk) 01:39, 1 June 2024 (UTC)reply
  • 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)reply
  • Strong oppose The fact that you don't know what consensus is, and launch personal attacks and are not civil, and fail to comply with don't assume is getting me close to requesting removal of some of your current tools. If I'm that far, yeah I'm definetly not supporting you get more. We don't need checkuser being abused for personal arguements. See User talk:Cromium for more details.Me Da Wikipedian (talk) 23:06, 31 May 2024 (UTC)reply
  • Oppose... reluctantly – A post at my user talk page (begging to support the nomination) and subsequent replies (no.1,no.2), which clearly reveals emotional response, make me wonder whether to trust Paul with the CU tools. I appreciate his frustrations about current policies, like the RFP policy. However, alternatively, he should've raised the concerns at the policy talk page before self-nomination. Furthermore, begging for support reeks desperation, IMO. There are no current local rules against canvassing, but begging for a vote is a lot to ask. Also, hostility toward stewards, especially from "oppose" "support" votes, due to their perceived inexperience with Wikinews sites smells like an attempt to maintain the project's autonomy. I appreciate those wanting to save this project, but giving him the CU tools merely to improve or save the project is hardly a reason to support the nomination. Sorry. George Ho (talk) 12:02, 31 May 2024 (UTC); corrected, 20:54, 31 May 2024 (UTC)reply
You are way out of line using the word "begging" and I don't appreciate it one single bit. I am engaged in news work and try to move that forward here. You show up here, flog about re: various permissions (who has them and who doesn't) and then quack crap of this nature. You can oppose and that is fine. Consensus matters around this place - but you'd better check yourself using the word "begging" whenever it comes to me. I hope to help and build up this place, (maybe to return it to some remnant of its former glory days)and little more. My desire for CU is only built around that end.--Bddpaux (talk) 13:26, 31 May 2024 (UTC)reply
Sorry @Bddpaux:, I think George has a point here. Your actions did seem like closer to "begging" than what's normal. I'm not opposing you; I think you would do good as a CU, but you need to be a bit more patient. Leaderboard (talk) 16:25, 31 May 2024 (UTC)reply
I guess my initial thoughts could be wrong about being asked to favor the nomination after reading this. I really do honestly wanna support the nomination when Paul asked, but the replies and frustrations amid the nomination pushed me toward the opposite. George Ho (talk) 12:10, 31 May 2024 (UTC)reply
This and that and that at someone's unsuccessful reviewer nomination now reaffrim my opposition to this CU nomination: assuming there was a "consensus" (when such assumption was challenged), (sarcastically?) trying to close this as "successful", and saying that the person not becoming a reviewer is the last thing Paul needs. Furthermore, I can't help wonder how Paul would treat someone accused of sockpuppeteering and other anonymous editors. --George Ho (talk) 18:19, 31 May 2024 (UTC)reply
@George Ho:, wasn't the first two diffs before Cromium challenged the consensus? Leaderboard (talk) 19:05, 31 May 2024 (UTC)reply
According to the history log, the diffs must've been. George Ho (talk) 19:11, 31 May 2024 (UTC)reply
  • Strongly oppose - I have tried to be supportive but this user has made a mess of a request for reviewer by failing to realise there was no consensus, granting the permission but not closing the discussion. When criticised, this user resorted to describing others as "quacking and barking”, which I assume means that he thinks they are animals. After I tried to find a solution, I concluded there was no consensus after several weeks and closed the discussion. This user has responded by leaving an angry message on my talk page], blaming me for the mess he made. For years, we have put up with his incompetence and rudeness. He has no respect for anyone that disagrees with him. He has no regard for any guidelines or policies, often describing them in disparaging terms. The warning bell was when I read that until recently, he had no idea what a Checkuser does. I have lost all confidence in his ability to handle any challenging tasks such as carrying out checks of IPs. [24Cr][talk] 18:42, 31 May 2024 (UTC)reply


The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.


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

Request withdrawn. Ternera (talk) 16:51, 26 December 2025 (UTC)reply

Hello! I would like to nominate myself for the role of sysop on English Wikinews. I am an experienced contributor, particularly on Bengali Wikinews, where I have made over 1,000 edits. In addition, I am also active as an editor on English Wikinews. I am genuinely enthusiastic about contributing to this project and would be honored to take on more responsibility. I hope the community will consider giving me the opportunity to serve as a sysop. Md Mobashir Hossain (talk) 12:14, 10 May 2025 (UTC)reply

Stats

Questions and comments

  1. Comment or Vote here.
  2. Ask question for clarify.

Votes



The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.


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

Closed as successful. Gryllida 08:18, 23 November 2025 (UTC)reply

(When I went to nominate Koavf for adminship, I opened my mouth and couldn't close it for two minutes. The form loaded on my smartphone and wouldn't let me type my nomination request. I believe the candidate possesses a talent to get things going properly; if it is needed to burn some javascript or networking issues with fire, I have confidence that Koavf is able to do so.) From my point of view, Koavf has shown a reasonable understanding of the project policies, technicalities and is an excellent communicator. I trust that Koavf is willing and capable of supporting the project from administrative side, both for page content administering, taking protected requests, and other tasks. May the force be with you, Koavf. --Gryllida 21:49, 3 September 2025 (UTC)reply

Stats

Questions and comments

  • Comment I accept the nomination and I am happy to help the community however I can. I have advanced user rights on several WMF wikis, am a generally trusted contributor for over 20 years, and have written a handful of front-page pieces here, including some with original reporting. I would look to fight vandalism, maintain the infrastructure, and be of service for requests. As G mentioned, I also have some competence at CSS/JavaScript/Lua/MediaWiki, so I can sometimes help with those issues. Thanks. —Justin (koavf)TCM 21:55, 3 September 2025 (UTC)reply
    Question: Will you try to write some news articles? Thank you. @Koavf BigKrow (talk) 00:32, 4 September 2025 (UTC)reply
    I reckon, but I imagine that it will only be a few here and there, which is similar to how I have written in the past. Being an admin will encourage me to generally be more active on the site and I do actually have two interviews recorded that I have yet to publish, so I have some original reporting in the chamber. —Justin (koavf)TCM 01:44, 4 September 2025 (UTC)reply

Votes



The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.


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

TUFKAAP (talk · contribs) — removal

This user's last edit was on 28 Aug 2023, as per WN:PeP their administrator rights should be removed now. -- Tanbiruzzaman (talk) 16:07, 12 November 2025 (UTC)reply

Stats

Questions and comments

Sysop right removed. This request may be closed. --Gryllida 20:22, 5 January 2026 (UTC)reply

Votes


The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.


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

ShakataGaNai (talk · contribs) — removal

This user's last edit was on 25 Aug 2023, as per WN:PeP their administrator rights should be removed now. -- Tanbiruzzaman (talk) 16:04, 12 November 2025 (UTC)reply

Stats

Questions and comments

@Gryllida: feel free to remove ShakataGaNai's reviewer and administrator privileges together. There is consensus to remove them. Codename Noreste (talk) 22:19, 16 February 2026 (UTC)reply
Done; this request may be archived now. Gryllida 23:48, 16 February 2026 (UTC)reply

Votes


The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.



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

Non-bureaucrat closure as not promoted. See requests[4], [5]. Request moot given pending closure of the project.

Self nominating due to issues with BigKrow, Lofi Gurl impersonator accounts and related discussions at wN:AAA. I think previous checkuser is Acagastya who was away for a few weeks. This is a self nomination. Gryllida (talk) 21:37, 20 April 2025 (UTC)reply

Stats

Questions and comments

I have the following questions:

  1. The documented process for requesting permissions was not followed fully for this request. Can you explain your understanding of the correct process, what went wrong in this case, and how you would ensure procedural accuracy when handling CheckUser actions?
  2. There have been past disputes regarding page protection during a discussion you were involved in[6], as well as concerns about policy-compliance during reviewing activity. How do you reflect on those incidents now, and what steps would you take as a CheckUser to ensure strict adherence to CU policy and avoidance of conflicts of interest?
  3. In one case, you removed talk-page access from a blocked user during what others considered a constructive discussion.[7] How do you approach decisions about restricting TPA, and how would you balance preventing disruption with allowing space for block clarification or appeals in future cases, especially in light of this advice from you?
  4. CheckUser duties sometimes require timely response to sockpuppetry or abuse reports. Given past concerns about availability and responsiveness, what level of availability would you commit to if granted CU rights, and how do you believe the community should evaluate whether local CU coverage is even needed versus relying solely on global Stewards?

Thank you in advance for your answers. Michael.C.Wright (Talk/Reviewer) 18:44, 5 January 2026 (UTC)reply

Hi @Michael.C.Wright
1a. I am not aware of substantial procedure error about this request.
1b. A CU action would arise from a request on-wiki. Policies for handling it are documented. Ideally a connection with an existing CU, including possibly that from another wiki, could help for questions if needed; as the CU here is away. As far as I know overuse of CU can result in serious issues and its use should be limited as much as possible, i.e. only when really required. In such a transparent wiki logs are available to see what action was done.
2a. I have not had a conflict of interest issue here in the past that was handled incorrectly.
2b. Already discussed at my talk page. TLDR; best to ask me about a specific published article before 24 hour window closed and I will be happy to work on a solution immediately and then on notes what was missed. Second best is to annoy me with this at time of archival. Both of those should happen at article talk page in the first instance, with added new section at my talk page to link me to a discussion. If this process is not documented then should be. Process to query my reviews is now documented at my user page. --21:00, 16 February 2026 (UTC)
2b.i. This could be displayed at a published page just to post a new section at article talk as some news sites have a "error found? Select it and Press alt+enter" feature.
3a. Unlike Wikipedia in Wikinews there is a lower tolerance to meta discussions. They take away valuable time for working on news. This has been the case for a while and is well documented.
3b. I consider that TPA revocation acceptable as of my position today. The user was not being constructive and it was dragging other users into the discussion. I believe one item could be done better there, that is, a note pointing to a email to admins. This user could use that to query to get unblocked eithout entertaining whole wiki. Some wikis have a way to email to admins only via a mailing list. This function is probably either not setup here or is out of date, as I am not on it.
3c. "This advice from you" link leads to a paragraph that is consistent with what I wrote above I believe.
4. Recently I am available every day (though not every day active on wiki) and have a bunch of social media contacts on my user page which can be buzzed if a request is time sensitive. I will have breaks from time to time. They are posted on my user page and during these breaks I remain online, even if not fully replying until the break ends except for urgent issues, in these social media and email. Gryllida 20:26, 16 February 2026 (UTC)reply
Thank you for your responses. I’ve numbered my comments to correspond with yours for clarity.
I have not yet reached a final view on this nomination. The following points are intended to assess readiness for the role and, separately, to consider whether there may be a broader structural issue for the project. Given our past disagreements, I have focused on policy and observable conduct rather than interpretation.
1a. CheckUser is a sensitive role that requires close attention to procedure. Your self-nomination was created in April but was not properly transcluded for eight months; it was later added to the voting page by HKLionel, and a SiteNotice update was requested only recently by Codename Noreste. Under Wikinews:Never assume, intent is not the issue. The fact remains that required procedural steps were not completed for an extended period. CU depends on precise and timely adherence to process.
2a. Wikinews:Protection policy states, “Do not protect a page you are involved in a dispute over.” During our dispute regarding Wikinews:Plagiarism, you moved the page to User:Brian McNeil/Wikinews:Plagiarism and applied full protection. Separately, you declined to follow WN:REV while proposing changes to it; the related RfC was initiated only after concerns were raised. REV is central to our identity as a journalism project. In both instances, established policy was not followed while you were directly involved in the matter. For a role entrusted with nonpublic data and advanced permissions, that is directly relevant.
3b & 3c. You have stated that users may ignore others who are “being a fool.” In the case of Me Da Wikipedian, talk page access was revoked immediately after they asked when they could again participate. Revoking TPA is a significant restriction, as it removes the user’s ability to seek clarification regarding their block. CU requires careful judgment and proportional use of authority.
4. Wikinews is a volunteer project, and no one is obligated to contribute time. However, CU requires dependable responsiveness. Your recent administrative activity appears intermittent in areas such as WN:AAA and counter-vandalism. Of the twenty most recent admin action requests, you participated in one, and you did not engage in the discussion titled “Check User.” For this role, demonstrated responsiveness to requests is especially important.
More broadly, the CU policy requires “at least 25 users’ approval,” and it is unclear whether we currently have 25 active, eligible voters. One existing CU is semi-retired, and the other has limited recent activity. If the threshold is not realistically attainable, that structural issue should be addressed independently of any nomination. In that context, the community may wish to consider whether relying on global CheckUsers is the more workable arrangement for now.
@Acagastya and @Cromium, with appreciation for your service, would you be open to discussing whether retaining local CU flags remains necessary while this broader question is evaluated?Michael.C.Wright (Talk/Reviewer) 02:22, 18 February 2026 (UTC)reply
1. I saw that and did not consider it urgent at that time. On the scale of eternity it takes to get 25 participants to comment in this section, a few weeks delay with transclusion does not cause major issue. I do believe however that requests for permission should be hanged into SiteNotice as a key item, when you have time. I did note your comment for my future reference.
2A.1. I considered that page was necessary to be kept for historical reasons. As you may know, Brian McNeil was project leader previously and then was deceased. I consider it harmless to keep a copy in their user space if desired. If you had issue with it, I can move it to my user space.
2A.2. I do not agree about 'declined to follow WN:REV while proposing changes to it'. I provided my argument previously that interpretation of WN:REV that I have got is consistent with past practices and context. I do believe that one has to rely on context and on existing practices as well as on the text of the policy. I do not consider the position 'RFC was created only after issues were raised' accurate in that case. I consider that RFC was opened because I wanted to get confirmation from other reviewers about their existing practices and thoughts about these given contexts. Unfortunately with reviewers being away this is hard to get that task done. I continue to have the position that practicing a policy does not merely rely on what is written but also on the context and the existing practices and comments from other users.
2A.2.1. I do not believe that would be an issue with usage of CheckUser if I were approved here; as noted earlier, if in doubt I would be able to query whoever group EPIC referenced on-wiki recently who could do CU for here while CUs are missing - that group is active, experienced, and having access to such a group is something I do not have here as a reviewer as when everyone else is away I have to make my own judgment call.
2A.3. I think I did not wish to discuss the issue of compliance with WN:REV until and unless it applied to a specific ongoing article. I do not wish to comment on this any further until a question about a particular and current article was brought up.
2A.4. Separately, I opened a request to comment on User:Gryllida/ATPG which is an article talk page guideline (maybe partly should be renamed to just talk page guideline not only article talk) where I proposed that (to put it strongly) meta discussions are a capital offence and work should be towards publishing a particular story report item.
3. Decision was made to revoke TPA of that user because it was dragging other users into that discussion. That is a 'meta' aspect that was making a net negative impact on news related work. I already stated that earlier.
4. Ok, I can work out how to increase my responsiveness on weekend. Currently it is close to nil.
Hope this is helpful. Gryllida 00:54, 24 February 2026 (UTC)reply
Just as a procedural note, stewards generally do not perform checks on wikis with local checkusers, except in emergencies or if local policies explicitly state so (though to my knowledge, only enwikibooks and enwikivoyage allow stewards to perform non-emergency checks). As for whether this wiki should have local CUs or not I'm not in a position to determine, but I do want to note that there have been multiple instances on this wiki where stewards have been hindered from "doing their job" and performing local checks since this wiki had checkusers, and that several requests have been forwarded to us throughout the years since local checkusers have not been active to process requests in a timely manner (which we've had to decline for the reasons mentioned above). That being said, should this wiki not regain local CUs the stewards will happily continue to process requests in our capacity. EPIC (talk) 17:29, 24 February 2026 (UTC)reply
Well, apart from weekend, I am here 16 hours a day. About weekend, I have setup mobile phone notification. Notification says "Wikinews page [name] has been changed by [nick]" which should be sufficient, if it mentions AAA or CU page, something is on fire. Gryllida 19:14, 24 February 2026 (UTC)reply
  • Comment. The checkuser permissions of Acagastya and Cromium have now been removed. Since there must be at least two checkusers, this nomination cannot succeed without a second nomination, even if 25 supports is reached (or relaxed), unless one or other of the former checkusers returns. DrKay (talk) 14:17, 1 March 2026 (UTC)reply
  • Wikinews:Requests for permissions/Bureaucrat/Ternera was recently closed with no consensus after less than three months and only three votes. This request has been open for nearly a year and has not reached the required 25 approvals. Should it now be closed as unsuccessful?
At present, CheckUser support is provided by several stewards, offering broader and likely faster coverage than two local CheckUsers would.
Since 2017, only four requests have been made at Wikinews:Requests for CheckUser, and one was later deemed unnecessary—after receiving timely and useful advice from a steward.
Given the limited demand and existing steward support, would it be more productive for the community to focus on improving the rate of article development, publication, and archival?Michael.C.Wright (Talk/Reviewer) 23:21, 15 March 2026 (UTC)reply

Votes


The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.