Make sure we agree on requirements. Give design review, help plan implementations and decide how to split up long-term maintenance.
Streamline how we share edit quality thresholds, to tune the human-language classes like "very likely damaging" for each model.
Create UIs for parts of the pipeline that should be easy to use, for example an admin interface to create and manage Wiki Labels campaigns.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T172743 [Epic] Coordinate ORES UI features between Scoring and Collab teams | |||
| Resolved | Ladsgroup | T167910 [Discuss] Make ORES Review Tool preferences more prominent | |||
| Resolved | kostajh | T164331 Define a process for adding ORES filters to new wikis when ORES is enabled on those wikis | |||
| Resolved | Catrope | T167908 Summarize what it will take to separate UI and infrastructure for ORES Extension | |||
| Open | None | T172338 Hide ORES review letter from the change list legend. | |||
| Open | None | T172339 Componentization-lite of Extension:ORES UI and API | |||
| Open | None | T182600 Document that the edit review UI can be disabled separately from the extension | |||
| Open | None | T102335 [Spec] Implement admin actions for wikilabels |