It should include peak flow and rolling average.
This is for one wiki at a time.
This is an action item from the 2025-03-06 ML & Editing eng. checkin.
It should include peak flow and rolling average.
This is for one wiki at a time.
This is an action item from the 2025-03-06 ML & Editing eng. checkin.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T265163 Create a system to encode best practices into editing experiences | |||
| Open | None | T365300 Introduce Edit Checks that encourage behavior aligned with Manual of Style consensus | |||
| Open | None | T365301 Tone Check: Prompt people to revise promotional language | |||
| Open | None | T416406 [MILESTONE] Offer Tone Check as default-on feature (all wikis) | |||
| Resolved | Esanders | T413026 [MILESTONE] Offer Tone Check as default-on feature at partner wikis | |||
| Open | ppelberg | T392954 [FY25-26] WE 1.1: Increase constructive edits | |||
| Resolved | MNeisler | T387918 [MILESTONE] Run an A/B test to evaluate impact of Tone Check | |||
| Resolved | dchan | T388266 Make a fermi estimation of eventual request rate |
This happened and was conveyed to the ML team. Details could be provided by someone who has them, I'm sure.
@dchan: could you please update the task description with the estimate you made and shared with the ML Team?
Final estimate was a peak load of 2.6 requests per second, and a mean load of 0.7 requests per second, if Edit Check were running on all Wikipedias for users who've completed <100 edits.