Page MenuHomePhabricator

Organize tasks related to the overhaul of CheckUser
Open, MediumPublic

Description

A good number of tasks that have to do with the overhaul of CheckUser are currently not connected with T237039: [Epic] CheckUser 2.0: Preliminary check on Phabricator. I think it would be nice to connect them (as subtasks, duplicates, etc.) Here are some example:

@Niharika has been doing a great job in sorting out these tasks, so I am assigning it to her. We basically need someone to go through all tasks on the CheckUser board and clean them up.

Event Timeline

Huji created this task.Nov 6 2019, 12:33 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptNov 6 2019, 12:33 AM
AronManning added a subscriber: AronManning.EditedNov 6 2019, 6:27 AM

Root: T139810 RFC: Overhaul the CheckUser extension
Hub/parent tasks with many subtasks:

  • T132892: CheckUser UI revamp
  • T237039: [Epic] CheckUser 2.0: Preliminary check

I've added children:

T139810 RFC: Overhaul the CheckUser extension

  • T237039: [Epic] CheckUser 2.0: Preliminary check
    • T236981: Create a new Special page in CheckUser for the redesigned version
  • T132892: CheckUser UI revamp
    • T234980: Implement an option to highlight non-standard user-agent strings in CheckUser.

The task graph of the root T139810 exploded... it's possible that's not what you want.

AronManning added a comment.EditedNov 6 2019, 7:55 AM

I suggest the following tree to separate tasks expected to be done in 2019 (T132892: CheckUser UI revamp are tasks from 2016)

T139810: RFC: Overhaul the CheckUser extension (also from 2016)

  • T236225: [Epic] CheckUser 2.0 Improvements
    • T237034: CheckUser 2.0: Input form
    • T237039: [Epic] CheckUser 2.0: Preliminary check (7 subtasks)
    • T237593: CheckUser 2.0: Compare
      • T174553: Create a mechanism that allows fetching geolocation and subnet data for IP addresses
      • T175587: Add a user-agent parser to CheckUser
    • T237595: [Epic] CheckUser 2.0: Timeline
      • T234980: Implement an option to highlight non-standard user-agent strings in CheckUser
    • T94735: Rewrite Special:CheckUser using server side templates

Orphans - unsure:

  • T61677: FlaggedRevs reviews are not visible in CheckUser
  • T54849: Checkuser option "get users" should should point out when user password is changed
  • T21796: Checkuser watchlist feature
  • T177793: Make links to non-existent accounts visually distinctive in CheckUser
  • T122296: Allow checking by last 64 bits of an IPv6 address

Old/stale:

  • T26411: List recent User-Agents for a user or IP (2012)
  • T26232: check new accounts only (2012)
  • T54849: Checkuser option "get users" should should point out when user password is changed (2014)
  • T26231: check account creations only (2014)
  • T146837: Add ability to search by user agent from CheckUser interface

@Niharika: I'm not making this tree yet, so you can review it. It would be best if you would author the "Tnew" tasks.

Niharika triaged this task as Medium priority.Nov 6 2019, 7:14 PM

@Huji @AronManning This is helpful, thank you! I will go through these and create/merge tasks as appropriate. It's also a good way to know who all I can ping for input. I was initially unsure if it is fine for me to take ownership of organizing the CheckUser tasks but sounds like that's fine. :)

Niharika added a comment.EditedNov 7 2019, 12:37 AM

@AronManning For the improvements we are working on, the epic task I created is T236225: [Epic] CheckUser 2.0 Improvements . My apologies that task was accidentally private earlier. I'll add that one as a subtask of T139810: RFC: Overhaul the CheckUser extension and then add the ones we will be working on as subtasks of T236225. I'll be merging similar tasks into the ones I create or repurpose them as appropriate.

AronManning added a comment.EditedNov 7 2019, 6:58 AM

@Niharika that's perfect. I've re-parented the leftover tasks in the tree above. Only the subtasks of T132892 (CheckUser UI revamp), the Orphans and the Old/stale tasks remain to be reviewed and anything I might have missed in the backlog. There were a few tasks that weren't obvious, so I'll run through the list once more and maybe you might be aware of a task I wasn't.