Page MenuHomePhabricator

Enable patrollers to choose recipient of reviewed message
Open, Needs TriagePublic

Description

User story: As a new page patroller, I want to select who receives my review message, so that I can be sure it is sent to the user who actually wrote the content I'm reviewing.

Screenshot 2023-02-03 at 12.25.15.png (430×854 px, 72 KB)

When marking an article as reviewed, patrollers can additionally send a message to the article creator. PageTriage selects the article creator as the recipient of that message, but sometimes doesn't select the correct editor. This is especially common when a page was a redirect and has been turned into a full article by another user - the user who created the redirect is sometimes (or always?) selected as the message recipient, but the patroller wants to message the user who wrote the article content they're reviewing.

One simple solution to this problem would be for PageTriage to still make a best guess at who the target should be, but provide that user in a drop-down box containing all editors of the page. The patroller could then select the correct target if the original one was incorrect.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Samwalton9-WMF renamed this task from Enable patrollers to choose recipient of reviewed message functionality to Enable patrollers to choose recipient of reviewed message.Feb 3 2023, 1:01 PM

There is some logic to get the list of contributors (sorted by number of edits), in the wikiLove section of the toolbar module. This can be reused. It will also be useful for T124396: Allow moving to draftspace and tagging accordingly (keywords: draft, draftify, draftification)

Ah, yes, overlapping at least. One question I have is whether such a solution (finding the article creator when a redirect has been removed) is foolproof enough that patrollers will be able to trust it. What happens if editor A un-redirects, B redirects, and C undoes the redirect? A should receive the notice but presumably we'd pick the most recent un-redirect in case of historical (un-)redirects.

My suggestion here was to make a best guess but ultimately still allow the user to choose in case the software got it wrong - perhaps there's room for both tasks.

The AFC Helper Script does something similar to this. Here's a screenshot.

image.png (581×1 px, 74 KB)