Stewards need a global Check User tool for an anti spamming or an anti vandalism.
|Open||None||T139810 RFC: Overhaul the CheckUser extension|
|Open||None||T212779 Implement Global CheckUser|
|Resolved||Rxy||T212781 Strategy for how to change the "cu_changes" DB schema|
|Resolved||Rxy||T213668 Split a method between logic and output|
|Declined||Rxy||T214820 Enable CheckUser for beta cluster|
|Open||None||T281560 Global Checkuser|
How we do handling this?
if above extension is only considered for miraheze and only hosted in github, I'll still use "GlobalCheckUser" and requesting for create wmf gerrit repository that name as "GlobalCheckUser" .
As said above,
I'd like to requesting a new repository and publish an extension that name as "GlobalCheckUser" written by me soon.
That extension is work in CentralAuth unified wikis.
However currently "GlobalCheckUser" is conflicting naming with https://github.com/examknow/GlobalCheckUser.
for this, if I continuing still use "GlobalCheckUser" for my extension, extensions are conflicting name and may caused confusing to users. also API module names, Special page names...