Hey,

This is the 18th weekly update from revision scoring team that we have sent to this mailing list.

*Communications:*

- Aaron presented on how user-feedback has been helping us address some sneaky biases in ORES' models. [1, 2, 3]

*New development:*

- We included 'autoreview' and 'patroller' groups in Turkish wiki models to get a fitness boost. [4]

- We added some basic uwsgi metrics to grafana[5] and added a response timing metric from Change Propagation so that we can track any performance issues. [6]

*Maintenance and robustness:*

- We increased the number of workers per node in production for a 66% increase in total capacity for ORES[7]

- We updated all of our edit quality models with the new version of revscoring [8] and sent an email out to wikitech-l and ai-l about the implications for tool developers. [9]

- We decided not to make specialized models for ORES in beta labs. [10] Instead, we'll use the production models so that issues with them will be caught in beta.

1. https://phabricator.wikimedia.org/T143275 -- Present on user-feedback stories at Research Showcase 2. https://www.youtube.com/watch?v=rsFmqYxtt9w#t=29m00s -- Video of ORES user-feedback talk 3. https://www.mediawiki.org/wiki/File:Deploying_and_maintaining_AI_in_a_socio-... 4. https://phabricator.wikimedia.org/T140474 -- Include specific user groups in the trwiki edit quality model 5. https://phabricator.wikimedia.org/T143081 -- Add uwsgi-related metrics to grafana 6. https://phabricator.wikimedia.org/T143568 -- Add median, 75% and 95% response time to ORES dashboard 7. https://phabricator.wikimedia.org/T143105 -- Increase celery workers to 40 per scb node 8. https://phabricator.wikimedia.org/T143125 -- Update editquality models with new version of revscoring 9. https://lists.wikimedia.org/pipermail/ai/2016-August/000068.html -- "[AI] New models coming to ORES & notes" 10. https://phabricator.wikimedia.org/T141980 -- Should we make a model for ores in beta?

Sincerely, Aaron from the Revision Scoring team