Description
Some of the maintenance templates in the "copy edit" category are not easy for newcomers and don't fit into what many people view as copy editing (basic spelling and grammar improvements). We should create a new "Hard" task type to fit some of the more difficult maintenance templates tasks.
Related community discussion.
Open questions:
- What should this new Hard type of task be called? Text cleanup / Encyclopedic Tone Copy editing / ????
- Should these tasks include more specialized onboarding & links to the relevant NPOV article, etc.
Acceptance Criteria
TBD
Completion checklist
Functionality
- The patches have been code reviewed and merged
- The task passes its acceptance criteria
Engineering
- There are existing and passing unit/integration tests
- Tests for every involved patch should pass
- Coverage for every involved project should have improved or stayed the same
Design & QA
- If the task is UX/Design related: it must be reviewed and approved by the UX/Design team
- Must be reviewed and approved by Quality Assurance.
Documentation
- Related and updated documentation done where necessary
- Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc)
- Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on Extension:GrowthExperiments or Extension:GrowthExperiments/Technical documentation pages.