Change Details

In September, we will deploy "add an image" to these four Wikipedias: Greek WIkipedia el Polish Wikipedia pl Chinese Wikipedia zh Indonesian Wikipedia id This is the engineering task, the associated CRS communication task is T301601. The feature should be available on both desktop and mobile. For newcomers who get the Growth features, half should have 'add an image' as their default task type. **Acceptance Criteria** Given I'm a newcomer on el, pl, zh, id Wikipedia, When I visit the newcomer homepage, Then there is a 50% chance that I will see 'add an image' as my default task type. ----- #### 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 [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.

In September, we will deploy "add an image" to these four Wikipedias: Greek WIkipedia el Polish Wikipedia pl Chinese Wikipedia zh Indonesian Wikipedia id Romanian Wikipedia ro This is the engineering task, the associated CRS communication task is T301601. The feature should be available on both desktop and mobile. For newcomers who get the Growth features, half should have 'add an image' as their default task type. **Acceptance Criteria** Given I'm a newcomer on el, pl, zh, id Wikipedia, When I visit the newcomer homepage, Then there is a 50% chance that I will see 'add an image' as my default task type. ----- #### 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 [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.

In September, we will deploy "add an image" to these four Wikipedias: Greek WIkipedia el Polish Wikipedia pl Chinese Wikipedia zh Indonesian Wikipedia id Romanian Wikipedia ro This is the engineering task, the associated CRS communication task is T301601. The feature should be available on both desktop and mobile. For newcomers who get the Growth features, half should have 'add an image' as their default task type. **Acceptance Criteria** Given I'm a newcomer on el, pl, zh, id Wikipedia, When I visit the newcomer homepage, Then there is a 50% chance that I will see 'add an image' as my default task type. ----- #### 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 [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.