Page MenuHomeMiraheze
Create Task
Maniphest T7358

Enable wgCheckUserEnableSpecialInvestigate
Closed, ResolvedPublic
Actions

Description

New in 1.36, needs Stew help to test

Related Objects
Search...

Event Timeline

RhinosF1 triaged this task as Normal priority.May 24 2021, 22:44
RhinosF1 created this task.
Herald added a project: Universal Omega. · View Herald TranscriptMay 24 2021, 22:44
RhinosF1 updated the task description. (Show Details)May 24 2021, 22:45
Unknown Object (User) moved this task from Backlog to Short Term on the MediaWiki (SRE) board.May 25 2021, 04:59
Unknown Object (User) moved this task from Unsorted to Short Term on the Universal Omega board.
RhinosF1 claimed this task.May 25 2021, 15:04
Restricted Repository Identity mentioned this in R9:172fee78433d: LS: enable wgCheckUserEnableSpecialInvestigate.May 25 2021, 15:10
Restricted Repository Identity mentioned this in R9:c2593a8ef925: LS: enable wgCheckUserEnableSpecialInvestigate (#3923).May 25 2021, 15:40
John subscribed.May 25 2021, 18:21

needs Stew help to test

Stewards shouldn’t be asked to use community empowered tools for routine testing. It puts Stewards in a liability position which places sole responsibility on themselves as testing is not authorised part of Steward, CheckUser policy or privacy policy.

RhinosF1 closed this task as Resolved.May 25 2021, 18:27
In T7358#146748, @John wrote:

needs Stew help to test

Stewards shouldn’t be asked to use community empowered tools for routine testing. It puts Stewards in a liability position which places sole responsibility on themselves as testing is not authorised part of Steward, CheckUser policy or privacy policy.

This has already been done. It did find an issue but we can do it as SRE next time.

John added a comment.May 25 2021, 18:38
In T7358#146756, @RhinosF1 wrote:
In T7358#146748, @John wrote:

needs Stew help to test

Stewards shouldn’t be asked to use community empowered tools for routine testing. It puts Stewards in a liability position which places sole responsibility on themselves as testing is not authorised part of Steward, CheckUser policy or privacy policy.

This has already been done. It did find an issue but we can do it as SRE next time.

So, no recognition that it’s wrong, an apology for making such a request but rather a ‘well it did what we wanted so’? Not the first time I’ve raised this, extremely unimpressed.

RhinosF1 added a comment.May 25 2021, 18:40

I apologise for any issues this caused. I asked Doug to help because he would have naturally had access to the tools anyway and we're extremely busy at the moment and stretched.

Unknown Object (User) added a comment.May 25 2021, 19:31
In T7358#146765, @RhinosF1 wrote:

I apologise for any issues this caused. I asked Doug to help because he would have naturally had access to the tools anyway and we're extremely busy at the moment and stretched.

RhinosF1, with all respect here. We shouldn't ask Stewards for help with testing (as I've also recently learned) but even if we are stretched, we must manage, we can ask community assistance if people will volunteer to help 1.36 work such as testing, but we shouldn't ask Stewards to help with testing in their Steward capacity, making them reliable for any issues with CheckUser usage.

Restricted Repository Identity mentioned this in R9:ce4ac0726e98: Update config for 1.36 (#3824).Jun 12 2021, 19:45