Demo produced during hackathon is at https://github.com/TK-999/mediawiki-extensions-ContentReview

A few notes on how we can progress from here:

Reviews in the current prototype are atomic (1 click approve/reject). We should probably introduce In Review state as found in the original Wikia ContentReview extension, where the reviewer starts a review before approving or rejecting a revision. Then we can also tie any automatic review processes (linter, CI build) to the review start event.

(I hope the cookie is not misinterpreted, I just wanted to say Thank You for working on this!)

Going by the list of open farms with most sysops (https://wikiapiary.com/wiki/Farm:Farms ), I wonder if any of them (e.g. (Gamepedia, Referata, Uncyclomedia, Miraheze, Brickimedia) has a similar use case, i.e. wikis where the admins aren't necessarily trusted to be in good faith and where somebody would be interested in handling a central queue of JavaScript changes.

If I understand correctly, TK-999 is looking for at least one non-Wikimedia farm interested in trying his extension, so that he can ascertain its usefulness and be guided in its further development.

On Gamepedia we use a vetting process before giving people administrator level access and we actively engage with the administrators in our IRC/Slack channels. However, an extension like this would be useful once the number of wikis/admins grow past what is reasonable to handle. As for taking over accounts we have our own AuthenticationProvider and SessionProvider that more or less mitigates those possibilities.(I won't say it is impossible though!)

While I want to give TK-999's extension a try on our stack I know it will be blocked by our(Amazon's) legal acceptance process. GPL-3.0 licensed projects/extensions are unfortunately prohibited.

Side note: I see that MW 1.29 or higher is required. I just finished merging MW 1.29-rc0 into a Hydra testing branch yesterday. It could one to two months before it actually goes out to live servers so it would be a while before we could actually test it assuming I could get an exception granted for the GPL-3.0 licensing policy.