This task involves the work of defining the requirements that will come to shape/define the controlled experiment of the mobile web section editing dead-end controlled experiment (T409112)
=== Open questions
- [ ] What (if any) requirements beyond those listed in the `=== Experiment requirements` need to be defined?
=== Experiment requirements
- The following //new// events will need to be added/instrumented:
-- All events to be added/instrumented are documented in the [[ https://docs.google.com/spreadsheets/d/1Y-D_7gTOQEBm97g0g7ZfixZpZ8ljYLESHbbAn1NsyVI/edit?gid=0#gid=0 | Instrumentation Spec ]]
-- Event name proposal for the new “Edit full page” button is documented in T410319#11402693
- The experiment will be run on the following wikis:
-- **All Wikipedias**
- Groups of people that will be included in the experiment:
-- This experiment analysis will focus on registered users with 100 or fewer cumulative edits and logged-out users.
-- The current recommended approach is to make everyone eligible for the experiment and then focus the analysis on logged-out users or registered users who have an edit count of 100 or fewer edits at **first exposure**.
- Bucketing logic/criteria:
-- Bucketing should include both registered and unregistered users at all Wikipedias. This will require the use of `edge-unique` as the [[ https://wikitech.wikimedia.org/wiki/Test_Kitchen/Conduct_an_experiment#Experiment_design:_identifier_type | identifier type ]]. Note: This means enrollment will be per-device.
-- All users, who are editing a **mobile main namespace page (NS:0)**, at any of the Wikipedias should have a 50% chance of being included/bucketed into the A/B test's control or treatment group.
-- The treatment group should have the new Mobile section editing button enabled when a user opens the section editor. The control group will not.
-- Each device should remain in the same test group for the duration of the test (and across sessions and pages). Note: If the cookie is cleared manually or automatically – by, for example, a privacy enhanced browser – the client is issued a new wmf-uniq cookie, and they may or may not end up enrolled or even assigned to the same group.
=== Done
- [ ] Answers to all "Open questions" are documented
- [ ] All `Experiment requirements` are defined and documented