Page MenuHomePhabricator

Support generation of reports based on arbitrary lists of pages
Open, HighPublic

Description

Currently, Reports bot output is based on WikiProjects, as defined in the project index database. This is fine for existing WikiProjects, but increases the burden on our users who want to have short-term collaborations and don't want to invest effort in creating WikiProject assessment categories. There should be an ability to define an arbitrary list of articles, whether in wikiproject.json or somewhere else, and then have reports (such as new discussions) based on that.

This will especially be useful for the Women in Red project, the scope of which is "biographies about women". They could in theory embark on a massive talk page tagging campaign, but why should they have to when they can just say "anything in Category:Women and subcategories" (or something like that) is in scope.

Event Timeline

Harej created this task.Oct 26 2015, 10:32 PM
Harej assigned this task to XZise.
Harej raised the priority of this task from to Medium.
Harej updated the task description. (Show Details)
Harej added a project: WikiProject-X.
Harej added subscribers: Aklapper, Harej.
Harej added a comment.Jan 8 2016, 5:49 AM

The planned extension T123028 is planning on doing this by defining WikiProjects in terms of categories/pages included/excluded. It will be a separate decision whether to implement this in Python or to just wait for the extension to be deployed and then just rely on the data provided by the extension.

Harej edited projects, added Reports-bot; removed WikiProject-X.Apr 14 2016, 1:45 AM
Harej moved this task from Backlog to Bugs/Improvements on the Reports-bot board.Apr 26 2016, 3:36 AM
Harej reassigned this task from XZise to Earwig.Jun 9 2016, 8:33 PM
Harej added a subscriber: XZise.
Harej raised the priority of this task from Medium to High.Jun 9 2016, 8:35 PM
Aklapper removed Earwig as the assignee of this task.Jun 19 2020, 4:18 PM
Aklapper added a subscriber: Earwig.

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)