Page MenuHomePhabricator

New pages feed/ page curation Wishlist changes
Open, Needs TriagePublic


This task is on the planning agenda of the Collaboration-Team-Triage Before claiming, check the status of this task w/ one of the team members here.

Proposed in Community-Wishlist-Survey-2016. Received 38 support votes, and ranked #35 out of 265 proposals. View full proposal with discussion and votes here.


(essential cross-Wiki application, core software extension). en.Wiki receives around 850 or more new pages every 24 hours directly published in mainspace. Currently there is a backlog of around 14,000 unreviewed new pages of which up to half are not suitable for publication. Page Curation is is the only firewall against undesirable new pages. These days, most of these are cleverly contrived corporate spam (by rings of multiple accounts -w:Orangemoody) or non notable autobiographies, while some are in fact from good faith first-time creators who need a simple nudge on the right track to avoid their work being deleted.

Who would benefit

  • The encyclopedia from being better policed and kept free of spam, hoaxes, and attack pages.
  • Good faith new users who have created pages that are not ready for immediate publication.
  • The improvements listed below would attract more users of the right calibre to the task of reviewing new pages and using the New Pages Feed and the Curation Toolbar.

Proposed solution

Develop and implement the following requested short list of improvements, many of which were intended, but 'forgotten' during initial development. We were recently asked by the WMF for a shortlist from the list of 20 or so requested updates. Thee details are not exhaustive but this update to the New Page Review tools should be addressed as one project/one request. Most of the template texts have already been written along with details of the required functions. WMF implementaion is required.

Curation toolbar

  1. Tool for moving pages to draft and notify creator
  2. Notify creator whenever an article is patrolled but tagged for maintenance
  3. Tool for declining a CSD placed by another reviewer, and for notifying patroller of wrongly applied tags
  4. Removing the 250 character limit for messages to creator (done in T157056: Remove the 250 character limit from messages sent through the Page Curation Tool)
  5. Add the accept and decline features of the AfC Helper Script templates so that submitted drafts can also be reviewed by either New Page reviewers or AfC reviewers from the New Pages Feed.
  6. Add the CSD criteria that are listed in Twinkle but not in Page Curation (already listed at Phabricator but apparently closed as 'Resolved' because no one understood what was wanted. This is also one of the reasons why people won't use Page Curation. (this is apparently T150628: Update PageTriage speedy deletion tag list to match Twinkle's, if there is a misunderstanding, comment there)

New Pages Feed

  1. Change the green 'patroll' blob to other icons for all pages that have been CSD?PROD/BLPPROD/AfD so that patrolling admins know what's going on. There should also be an indication of the type of deletion nomination (rather than a generic trash can).
  2. Auto refresh. The feed should auto refresh every 5 seconds like the other one does. This is the other main reason why so many patrollers won't move over to Page Curation. Anyone opening the New Pages Feed finds that up to 60% of all pages, especially the low hanging fruit, have already been tagged - sometimes incorrectly.
  3. Inform with an icon if a page has previously been deleted.
  4. Pages that have been tagged for maintenance issues (but not for deletion) and are otherwise just acceptable for inclusion, should be shown not with the green 'checked' icon, but with an orange blob that contains a capital T (for 'Tagged'). It should be obvious that this would enable admins who are patrolling the quality of the patrollers themselves rather than new pages, can immediately revert any tags that have been inappropriately or erroneously applied, and replace them with correct ones or use the 'unreview button' which should then send the 'unreviewed' message automatically to the patroler, using a dropdown list of canned reasons.
  5. Display in the Feed entry, in red alongside the 'no citations' alert, a 'Naked URL' alert. This should enable a patroler to send a canned message to to the creator on the lines of: Thank you for creating X. I notice you left naked URLs in the references section. Please consider returning to the article and addressing this and any other tagged issues. For more information about correctly formatting sources and external links, please see WP:CITE.

Technical details

Time, expertise and skills required

  • e.g. 2-3 weeks, advanced contributor, javascript, css, etc

Suitable for

  • e.g. Hackathon, GSOC, Outreachy, etc.



Related links

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
This task was proposed in the Community-Wishlist-Survey-2016 and in its current state needs owner. Wikimedia is participating in Google Summer of Code 2017 and Outreachy Round 14. To the subscribers -- would this task or a portion of it be a good fit for either of these programs? If so, would you be willing to help mentor this project? Remember, each outreach project requires a minimum of one primary mentor, and co-mentor.

As explained on-wiki, this task mashes numerous separate issues into a single one and hence will likely never get completely fixed. (I personally consider this task invalid.)
If this was something to work on in an Outreach program, the scope needs to be drastically reduced and clarified.

jmatazzoni renamed this task from New pages feed/ page curation to New pages feed/ page curation Wishlist changes.Feb 28 2017, 6:59 PM

If this was something to work on in an Outreach program, the scope needs to be drastically reduced and clarified.

@srishakatux I agree the task should either be closed, or at least made an Epic with meaningful self-contained subtasks. It has far too many unrelated items and is not actionable as is.

Can you please clarify what you mean by 'I agree the task should either be closed, or at least made an Epic with meaningful self-contained subtasks. It has far too many unrelated items and is not actionable as is.' and how this statement can apply to one of the major and most sensitive of all Wkipedia operations?

@Kudpung: This statement can apply to any task because it is about formal requirements and not about the task content covering "one of the major and most sensitive operations".

Task creation guidelines ask to include only one problem per report. The task description here lists 11 separate problems (items). Each item should be a task on its own, which would make separate items actionable. Currently this task is not actionable and rather an Epic.