| 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) | |||
| Open | None | T413026 [MILESTONE] Offer Tone Check as default-on feature at partner wikis | |||
| Open | ppelberg | T392954 [FY25-26] WE 1.1: Increase constructive edits | |||
| Open | MNeisler | T387918 [MILESTONE] Run an A/B test to evaluate impact of Tone Check | |||
| Resolved | ppelberg | T394806 Tone Check: Conduct adversarial testing |
Event Timeline
Comment Actions
This work ended up taking on the form of two things:
- Adjusting the presentation of the Tone Check card so that it more clearly and accurately predicts that relative uncertainty of the feature
- Brainstorming with volunteers how we might mitigate some of the cases they helpfully identified. See: https://en.wikipedia.org/wiki/Wikipedia_talk:Edit_check/Tone_Check#Summary_of_discussions_so_far