Sample Page

Hello Javert2113,

Backlog

The October drive reduced the backlog from 9,700 to an amazing 0! Congratulations to WaddlesJP13 who led with 2084 points. See this page for further details. The queue is steadily rising again and is approaching 2,000. It would be great if <2,000 were the “new normal”. Please continue to help out even if it’s only for a few or even one patrol a day.

2022 Awards

Onel5969 won the 2022 cup for 28,302 article reviews last year – that’s an average of nearly 80/day. There was one Gold Award (5000+ reviews), 11 Silver (2000+), 28 Iron (360+) and 39 more for the 100+ barnstar. Rosguill led again for the 4th year by clearing 49,294 redirects. For the full details see the Awards page and the Hall of Fame. Congratulations everyone!

Minimum deletion time: The previous WP:NPP guideline was to wait 15 minutes before tagging for deletion (including draftification and WP:BLAR). Due to complaints, a consensus decided to raise the time to 1 hour. To illustrate this, very new pages in the feed are now highlighted in red. (As always, this is not applicable to attack pages, copyvios, vandalism, etc.)

New draftify script: In response to feedback from AFC, the The Move to Draft script now provides a choice of set messages that also link the creator to a new, friendly explanation page. The script also warns reviewers if the creator is probably still developing the article. The former script is no longer maintained. Please edit your edit your common.js or vector.js file from User:Evad37/MoveToDraft.js to User:MPGuy2824/MoveToDraft.js

Redirects: Some of our redirect reviewers have reduced their activity and the backlog is up to 9,000+ (two months deep). If you are interested in this distinctly different task and need any help, see this guide, this checklist, and spend some time at WP:RFD.

Discussions with the WMF The PageTriage open letter signed by 444 users is bearing fruit. The Growth Team has assigned some software engineers to work on PageTriage, the software that powers the NewPagesFeed and the Page Curation toolbar. WMF has submitted dozens of patches in the last few weeks to modernize PageTriage’s code, which will make it easier to write patches in the future. This work is helpful but is not very visible to the end user. For patches visible to the end user, volunteers such as Novem Linguae and MPGuy2824 have been writing patches for bug reports and feature requests. The Growth Team also had a video conference with the NPP coordinators to discuss revamping the landing pages that new users see.

Hello Javert2113,

Backlog

Redirect drive: In response to an unusually high redirect backlog, we held a redirect backlog drive in May. The drive completed with 23851 reviews done in total, bringing the redirect backlog to 0 (momentarily). Congratulations to Hey man im josh who led with a staggering 4316 points, followed by Meena and Greyzxq with 2868 and 2546 points respectively. See this page for more details. The redirect queue is steadily rising again and is steadily approaching 4,000. Please continue to help out, even if it’s only for a few or even one review a day.

Redirect autopatrol: All administrators without autopatrol have now been added to the redirect autopatrol list. If you see any users who consistently create significant amounts of good quality redirects, consider requesting redirect autopatrol for them here.

WMF work on PageTriage: The WMF Moderator Tools team, consisting of Sam, Jason and Susana, and also some patches from Jon, has been hard at work updating PageTriage. They are focusing their efforts on modernising the extension’s code rather than on bug fixes or new features, though some user-facing work will be prioritised. This will help make sure that this extension is not deprecated, and is easier to work on in the future. In the next month or so, we will have an opt-in beta test where new page patrollers can help test the rewrite of Special:NewPagesFeed, to help find bugs. We will post more details at WT:NPPR when we are ready for beta testers.

Articles for Creation (AFC): All new page reviewers are now automatically approved for Articles for Creation draft reviewing (you do not need to apply at WT:AFCP like was required previously). To install the AFC helper script, visit Special:Preferences, visit the Gadgets tab, tick “Yet Another AFC Helper Script”, then click “Save”. To find drafts to review, visit Special:NewPagesFeed, and at the top left, tick “Articles for Creation”. To review a draft, visit a submitted draft, click on the “More” menu, then click “Review (AFCH)”. You can also comment on and submit drafts that are unsubmitted using the script.

You can review the AFC workflow at WP:AFCR. It is up to you if you also want to mark your AFC accepts as NPP reviewed (this is allowed but optional, depends if you would like a second set of eyes on your accept). Don’t forget that draftspace is optional, so moves of drafts to mainspace (even if they are not ready) should not be reverted, except possibly if there is conflict of interest.

Pro tip: Did you know that visual artists such as painters have their own SNG? The most common part of this “creative professionals” criteria that applies to artists is WP:ARTIST 4b (solo exhibition, not group exhibition, at a major museum) or 4d (being represented within the permanent collections of two museums).

• The May 2026 administrator elections are set to proceed.
• We plan to use the following schedule:
  • April 29–May 5: Candidate sign-up
  • May 8–May 12: Discussion phase
  • May 13–May 19: SecurePoll voting phase
• If you have any questions, concerns, or thoughts before we get started, please ask at Wikipedia talk:Administrator elections.

The administrator elections process has officially started! Interested editors are encouraged to self-nominate or arrange to be nominated by reviewing the instructions at Wikipedia:Administrator elections/May 2026/Candidates.

Here is the schedule:

• April 29 – May 5: Call for candidates
• May 8–12: Discussion phase
• May 13–19: SecurePoll voting phase

Please note the following:

• The requirements to run are identical to RFA—a prospective candidate must be extended confirmed.
• Prospective candidates are advised to become familiar with the community’s expectations of administrators, which are much higher than the minimum requirement of having extended confirmed status. This includes reviewing successful and unsuccessful RFAs, reading the essay Wikipedia:Advice for admin elections candidates, and possibly requesting an optional poll on their chances of passing.
• The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
• The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
• Administrator elections are also a valid means of regaining adminship for de-sysopped editors.

Ask any questions about the process at the talk page. Later, a user talk message will be sent to official candidates with additional information about the process.

If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.

The discussion phase of the May 2026 administrator elections is officially open. As a reminder, the schedule of the election is:

• May 8–12: Discussion phase (we are here)
• May 13–19: SecurePoll voting phase
• Scrutineering phase

We are currently in the discussion phase. The candidate subpages are open to questions and comments from everyone, in the same style as a request for adminship. You may discuss the candidates at Wikipedia:Administrator elections/May 2026/Discussion phase.

On 13 May, we will start the voting phase. The candidate subpages will close to public questions and discussion, and everyone will have a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for.

Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.

The voting phase of the May 2026 administrator elections has started and will continue until 19 May 2026 at 23:59 UTC. You can participate in the voting phase at Wikipedia:Administrator elections/May 2026/Voting phase.

As a reminder, the schedule of the election is:

• May 13–19: SecurePoll voting phase (we are here)
• Scrutineering phase

In the voting phase, the candidate subpages close to public questions and discussion, and everyone who qualifies to vote has a week to use the SecurePoll software to vote, which uses a secret ballot. You can see who voted, but not who they voted for. Please note that the vote totals cannot be made public until after voting has ended and as such, it will not be possible for you to see an individual candidate’s vote total during the election. The suffrage requirements are similar to those at RFA.

Once voting concludes, we will begin the scrutineering phase, which will last for a few days, perhaps longer. Once everything is certified, the results will be posted on the results page (this is a good page to watchlist), and transcluded to the main election page. In order to be granted adminship, a non-recall candidate must have received at least 70.0% support, calculated as Support / (Support + Oppose), and a minimum of 20 support votes. Recall candidates must achieve 55.0% support. Because this is a vote and not a consensus, there are no bureaucrat discussions (“crat chats”).

Any questions or issues can be asked on the election talk page. Thank you for your participation. Happy electing.