Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T265163 Create a system to encode best practices into editing experiences | |||
Open | None | T360799 [EPIC] Empower developers to author new Edit Checks and Structured Tasks | |||
Open | None | T364507 Develop an SLO for Edit Check |
Event Timeline
Next steps
Per 13 November meeting with @VPuffetMichel and @RLazarus, next step is for me to review the content of https://wikitech.wikimedia.org/wiki/SLO/EditCheck and document any questions/edits/etc. I think are important to address before "signing off" on this agreement in my capacity as Editing Team product manager.
Notes to self:
- Ensure description of Edit Check is accurate exhaustive
- Confirm performance/availability targets align with expectations
For reference: https://wikitech.wikimedia.org/wiki/SLO/template_instructions.
Having published these changes to the SLO and confirming @RLazarus agrees with them, I think we can consider this iteration of the SLO complete from the perspective of product.
Per what Reuven and I discussed offline, we'll iterate on this SLO if/when Edit Check changes in ways that warrant us doing so. E.g. When Edit Check begins to depend on external services which we're planning to have happen via T379397.