Page MenuHomePhabricator

[DRAFT] Implement bucketing for Edit Check (references) A/B test
Open, MediumPublic

Description

This task is about implementing the changes necessary to ensure people are being bucketed in the Edit Check A/B test (T342930) as expected.

Bucketing requirements

  • Bucketing should include both registered and unregistered users
  • Everyone who is accessing a desktop or mobile main namespace page (NS:0) at any of the participating wikis, logged in and logged out, should have a 50% chance of being included/bucketed into the A/B test's control or test group
  • Bucketing should be done on a per-Wikipedia basis. 50% of people within a given wiki should be placed within the control group; 50% should be bucketed in the test group
  • People should remain in the same group for the duration of the test.
  • Testing should be done across all desktop skins where available

Instrumentation-Related Requirements

  • Within the A/B test, we are able to distinguish all events logged for the control group and the test group.
  • An anonymous_user_token is applied to these events so we can track distinct unregistered users in addition to distinct registered users.
  • We are able to track if/when someone in the test group adjusts any of the edit check-related preferences (if available)

Participating wikis
Defined in T345298 (still being finalized)

Open questions

  • 1. Will there be a third test group that is shown Edit Check with the Reference Reliability experience T276857 will implement?
  • 2. How might we ensure that the people who are included in the A/B test are the same people for whom volunteers have made Edit Check available by way of community configuration
    • Note: if who Edit Check is available to is NOT consistent across projects, we will not be able to draw cross-wiki conclusions.

Done

  • A patch has been deployed that meets what's described requirements sections above
NOTE: QA will happen in T352122

Event Timeline

I'm currently working on updating the task description with proposed bucketing requirements:

Some open questions:

  • Do we want to run an A/B test or a multivariate test?
  • Will there be a preference where a user at one of the participating wikis can opt-in or opt-out of the Edit Check references feature?
  • Will this be available on different desktop skins?
  • Do we want to limit to newcomers and Junior Contributors?
MNeisler triaged this task as Medium priority.Sep 19 2023, 7:56 PM
MNeisler edited projects, added Product-Analytics (Kanban); removed Product-Analytics.
MNeisler moved this task from Next 2 weeks to Doing on the Product-Analytics (Kanban) board.

Documenting the answers @MNeisler and I converged offline today...

I'm currently working on updating the task description with proposed bucketing requirements:

Some open questions:

For now, we're going to plan to run a test with two groups: a control group and a test group.

By the time we prioritize implementing the test bucketing this task is specifying, Edit Check will be available for an initial population of newcomers (T331947) and we should know whether there is a secondary implementation of Edit Check we'd value evaluating through an A/B/C-style multivariate test.

  • Will there be a preference where a user at one of the participating wikis can opt-in or opt-out of the Edit Check references feature?

At present, no.

  • Will this be available on different desktop skins?

See T324355.

  • Do we want to limit to newcomers and Junior Contributors?

Per T345298#9185256, ideally, "yes." Although, we'll know for certain once we identify the partner wikis participating in the A/B test and the Edit Check configurations they're consent to as part of participating in the test.