Thank you @ACraze and @Theofpa for your suggestions.

The unanswered question I have is whether it is possible to migrate these models out of ORES without retraining them from scratch. I hope so, but I need to dig into how KFServing standalone works before I could say for certain.

I have pushed a PR for this task here where I was able to replace preq with the api-testing REST client within 11 out of 13 tests.

Thanks for the great work! I have had a look at the document and made a couple of suggestions too.

With @daniel's guidance, I pushed a patch for this task here. Below are the steps I followed to test this patch that was added to MW 1.35;

@calbon, I created this PR that added 2020 trwiki data configurations to editquality.

@ACraze, I added the "badwords" and "informals" lists to this page:

I consulted @daniel who confirmed that the WikiCommons API uses the MediaWiki API as this documentation suggests.

@Halfak please see the PR here: https://github.com/wikimedia/editquality/pull/227

@Halfak I followed these instructions and took the following steps;

Thank you for the explanation @Halfak. I have managed to reproduce this issue and fixed the bug.

I tried to reproduce this issue by creating a new edit and tried to undo it here: https://en.wikipedia.beta.wmflabs.org/w/index.php?title=Foobar&action=edit&undoafter=418935&undo=438261

Thank you @ACraze and @Halfak for the suggestions. I ended up supplying both the parsed and unparsed text to the frontend and then loaded the 'unparsed' text in the text area field when the user clicks 'Edit'.

@ACraze, I have added documentation for the Jade secondary integration in Recent Changes Filters, Special:Diff, Undo and Rollback pages.

@ACraze, I have been able to promote a second label without the error and the jade_diff_label db table got updated successfully. Thank you for fixing this bug. I have +2'd.

The initial goal was to use AJAX ( either MediaWiki's or jQuery's ) but turns out the Jade API client was able to asynchronously return updated Jade entity data after every Jade action. So we leveraged this to update Jade elements asynchronously and stopped Jade page reloads on secondary integration pages which results into better UX for patrollers.

I ended up using these two hooks to render edit comments in Jade.

Also, this and this show that Wikidata is using the PageHistoryLineEnding MediaWiki hook to further customize edit comments.

Based on this and this, Wikidata is using the FormatAutocomments MediaWiki hook to render localized strings for edit comments.

I have pushed a patchset that solves this problem. Now as required, User A is not able to create and endorse a new proposal if they've already endorsed a proposal in the same facet.

I have pushed a patchset for this issue. Turns out User A was able to delete an endorsement created by User A but was not able to delete an endorsement created by User B. Now User A is able to delete an endorsement created by User B.

PS: I've pushed a patchset for this task here: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/587544

@Aklapper: Hi, in order to see a bubble notification appear in MediaWiki please navigate to Special:Preferences, make a change, and then save. It will appear in the right upper section of your page.

@Isaac I'm pleased to hear that the AfricaNLP Workshop will still go on despite the COVID-19 situation.

@Halfak, yes this is done for now.

Thanks @ACraze, I am going to implement it for for all the other api modules too.

@Halfak I have ended up using the MW bubble notification to give users feedback/confirmation that their action was successful.

@ACraze, thank you for the great work. I have reviewed and +2'd.

For now, I have removed the "edit source" link from Jade pages.

I have added autosize and maxRows to label notes

I have moved the "alternatives V" button up above the alternative labels using the preferredProposal / nonPreferredProposals strategy - similar to @ACraze's proposal but using a single ProposalListWidget instead of two separate ones.

Thanks @ACraze, the update LGTM. I've +2'd.

@ACraze I've reviewed your patchset and the README looks good. Just wanted to confirm though, is composer test and grunt run in the MediaWiki root or Jade root?

I've added English pronoun count features to drafttopic. PR: https://github.com/wikimedia/drafttopic/pull/43

@Halfak I used FastText to generate 50 and 100 cell vector models. Please find them on stat1007 under:

Worked on fetching WikiProject templates. PR : https://github.com/halfak/wikitax/pull/3