The hard question: Can we just disable it/remove it? It sounds like there is no long term maintenance plan anyway?

Other hard question: Why is the last known good version before it was made into it's own extension? Weren't there tests done when it was split out of MF?

@greg All the test runs were done before it was moved and unfortunately we didn't catch the problem afterwards (partially since it involves communication between wikis and is hard to test).

@phuedx We may either have to just leave it off for now or only run it for logged in users (for a longer time).

@greg:

Can we just disable it/remove it? It sounds like there is no long term maintenance plan anyway?

The Read{er,ing} team are meeting to discuss this on Wednesday, 13th. I'll be sure to update this ticket after the meeting.

Why is the last known good version before it was made into it's own extension? Weren't there tests done when it was split out of MF?

WikiGrok is hard to end-to-end test and not enough of those tests were done after the split. That said, we should have put more effort into making it easier to test.

In T98142#1275774, @phuedx wrote:

The Read{er,ing} team are meeting to discuss this on Wednesday, 13th. I'll be sure to update this ticket after the meeting.

Update? :)

This hasn't been announced on the mailing list yet, but we're planning on turning off WikiGrok until we're ready to pick up work on it again.

Does "turn off" mean undeploy? Unsure if T97979: (5) Add UserMerge support to WikiGrok needs to be worked on or not...

@Legoktm recently helped us out of a hole that we'd dug ourselves into about anons, CentralAuth tokens, and POSTing data cross-wiki. So we're, somewhat sheepishly, going to request that the WikiGrok UI is disabled in the config rather than underployed.

We'll need to get T97979 scheduled for the next sprint as we'd obviously like to keep the data that we've accumulated thus far up to date.

So we're, somewhat sheepishly, going to request that the WikiGrok UI is disabled

-> Updated Title + description.

Btw.: It should be enough to remove all wikis from wmgUseWikiGrok except test wikis and wikidatawiki and remove cleanup all UI related config vars, too:

wmgWikiGrokUIEnable
wmgWikiGrokUIEnableForAnons
wmgWikiGrokUIEnableOnAllDevices
wmgWikiGrokUIEnableInSidebar

(@Legoktm asked me to add this here :))

Change 212017 had a related patch set uploaded (by Florianschmidtwelzow):
Disable WikiGrok in WMF production

https://gerrit.wikimedia.org/r/212017

Why would it stay enabled on Wikidata?

I'm not sure if its needed to hold the already collected data or if it would be save to uninstall it there too. To be clear: the extension wouldn't have any visible feature.

@Florian: We shouldn't drop the tables when we disable the feature. Could you update your patch to include 'wikidatawiki' => false where appropriate?

Change 212017 merged by jenkins-bot:
Disable WikiGrok in WMF production

https://gerrit.wikimedia.org/r/212017