Background
WikimediaEvents, MobileFrontend and now WikimediaCustomizations make use of a OWNERS.md. The former 2 also have tests to enforce it. Going forward it would be good to share a central definition of what ownership looks like so any new extension (including WikimediaCustomizations) can make use of it.
User story
As a developer I want it to be easy to enforce ownership in my repo
Requirements
- An abstract class exists in core
- MobileFrontend uses the abstract class
- WikimediaCustomizations the abstract class
BDD
- For QA engineer to fill out
Test Steps
- For QA engineer to fill out
Design
- Add mockups and design requirements
Acceptance criteria
- Add acceptance criteria
Communication criteria - does this need an announcement or discussion?
- Add communication criteria
Rollback plan
- What is the rollback plan in production for this task if something goes wrong?
This task was created by Version 1.2.0 of the Web team task template using phabulous