Page MenuHomePhabricator

Add an image: experiment (desktop)
Closed, ResolvedPublic

Description

Corresponding task from mobile: T294737: Add an image: experiment


When we deployed "add an image" to mobile, it was deployed with a controlled experiment only amongst mobile users. When we deploy the desktop version, we want to add the desktop users to the experiment.

  • For the mobile experiment, we had five groups, depending on whether a user created their account on desktop or mobile. See below for reference.
    • Mobile A: these users created their account on mobile. They get "add an image" on as the only default task. (40% of mobile account creations). This is the only group that will have access to "add an image" at all. Some of these users may subsequently visit their homepage on desktop. See this task about how we will prevent them from using "add an image" on desktop: T295000: Add an image: prevent desktop usage
    • Mobile B: these users created their account on mobile. They have the default suggested edits experience without "add an image" in their difficulty filters at all. Their experience would include copyedit and "add a link" as their default tasks. (40% of mobile account creations)
    • Mobile C: these users created their account on mobile. They don't get the Growth features at all and are our usual control group. (20% of mobile account creations)
    • Desktop B: these users created their account on desktop. They have the default suggested edits experience without "add an image" in their difficulty filters at all. Their experience would include copyedit and "add a link" as their default tasks. (80% of desktop account creations)
    • Desktop C: these users created their account on desktop. They don't get the Growth features at all and are our usual control group. (20% of desktop account creations)
  • Once we have the desktop version, experiment assignment will be simpler because we won't have to assign based on the platform where the user created their account. It should be like this:
    • A: these users get "add an image" on as the only default task. (40% of account creations). This is the only group that will have access to "add an image" at all.
    • B: these have the default suggested edits experience without "add an image" in their difficulty filters at all. Their experience would include copyedit and "add a link" as their default tasks. (40% of account creations)
    • C: these users don't get the Growth features at all and are our usual control group. (20% of account creations)

Event Timeline

Change 752657 had a related patch set uploaded (by Kosta Harlan; author: Kosta Harlan):

[operations/mediawiki-config@master] GrowthExperiments: Start add image experiment for desktop users

https://gerrit.wikimedia.org/r/752657

Change 752657 merged by jenkins-bot:

[operations/mediawiki-config@master] GrowthExperiments: Start add image experiment for desktop users

https://gerrit.wikimedia.org/r/752657

Mentioned in SAL (#wikimedia-operations) [2022-01-27T19:27:56Z] <tgr@deploy1002> Synchronized wmf-config/InitialiseSettings.php: Config: [[gerrit:752657|GrowthExperiments: Start add image experiment for desktop users (T298122)]] (duration: 00m 51s)

Change 757792 had a related patch set uploaded (by Gergő Tisza; author: Gergő Tisza):

[operations/mediawiki-config@master] GrowthExperiments: Disable mobile quality gate

https://gerrit.wikimedia.org/r/757792

Change 757792 merged by jenkins-bot:

[operations/mediawiki-config@master] GrowthExperiments: Disable mobile quality gate

https://gerrit.wikimedia.org/r/757792

Mentioned in SAL (#wikimedia-operations) [2022-01-28T09:23:37Z] <hashar@deploy1002> Synchronized wmf-config/CommonSettings.php: GrowthExperiments: Disable mobile quality gate - T298122 T300336 (duration: 00m 50s)

Urbanecm_WMF changed the task status from Open to In Progress.Jan 31 2022, 11:33 AM
kostajh changed the task status from In Progress to Open.Feb 7 2022, 9:16 AM
kostajh moved this task from Code Review to QA on the Growth-Team (Sprint 0 (Growth Team)) board.

I believe this task can be resolved, @Etonkovidova.