Where to surface AI in Wikimedia Projects
Type of activity
Currently, ORES is available in production and article recommendations is right around the corner. Where should we be taking advantage of these predictions?
1. The problem
There are new useful AI services, but the predictions/rankings are not yet consistently surfaced through our UIs. Where should they be surfaced? What should we prioritize?
For example, ORES has 4 models:
- reverted Should this edit be reverted?
- goodfaith Was this edit saved in good-faith?
- damaging Did this edit cause damage?
- wp10 What's the quality level of this article?
Where should these predictions be surfaced?
2. Expected outcome
Develop a list of products and features that could take advantage of available AIs.
3. Current status of the discussion
While initially intended to be interpreted broadly, ORES and general predictions became the focus of discussion. It seems that the Recommendation-API isn't quite ready for this type of discussion. @Quiddity brought up the proposal to do the obvious with ORES wp10 (article quality) models -- surface it on article pages. @jmatazzoni is interested in discussion surfacing the ORES edit quality models in his team's Edit Review Improvements project. @EBernhardson talked about pulling the wp10 models into ranking search results (and @Sumit signaled interest in collaborating). @Tgr talked about extending where the edit quality models of ORES are surfaced (e.g. diff pages) and discussed T132901, a specific project about using ORES scores to trigger flagged revisions. @Cenarium is already working on some patches to implement the ORES-based (as well as other scoring mechanisms) auto-flagging of edits. @ZhouZ, @Niharika, @Capt_Swing, @Fjalapeno, @dr0ptp4kt, and @Glorian_Yapinus signalled interest in the topic by awarding this task a token.
Preferred group size
Any - whoever is interested in getting AI in our products
Any supplies that you would need to run the session
A/V equipment for presenting an ether pad for discussion