Description

This task represents the work with implementing the instrumentation required to evaluate the impact of topic subscriptions (T280895) as well as peoples' adoption of (T280896), and engagement with (T280898), the feature.

Implementation Steps

1. @DLynch review the instrumentation spec and for each Event to be tracked comment whether we are tracking said event in the Currently being tracked (Yes/No) column: T277349
- See: T277349#7152757 + T277349#7152762
2. @MNeisler to propose naming conventions for events that require new instrumentation: T277349
3. @DLynch to review proposed naming conventions: T277349
4. @MNeisler to document new events/instrumentation that needs to be implemented: T286076
- Done in: T286076#7276011
5. Ping @LZaman/ @ppelberg once the schema questions are resolved so she can forward to legal.
6. @LZaman to consult with WMF Legal team: T288695
- Documentation should be forwarded to privacy@wikimedia.com; more details here: https://office.wikimedia.org/wiki/Legal .
@matmarex @DLynch Editing Engineers to implement new instrumentation: T286076
~~8. @Ryasmeen to verify new events are being emitted as expected: T286076~~
In progress --> 9. @MNeisler to verify new events are arriving in DB as expected: T286075

Status	Assigned	Task
Open	None	T276497 Scale DiscussionTools to all projects
Open	None	T251207 [Epic] Scale DiscussionTools to all Wikipedias
Resolved	ppelberg	T284489 Deploy topic subscriptions (desktop) as opt-out feature at all projects
Open	None	T233447 [OKR] Increase response rates
Resolved	ppelberg	T274833 [RELEASE TICKET] Enable topic subscriptions as opt-out at partner wikis
Resolved	ppelberg	T280896 Topic subscriptions: calculate adoption metrics
Resolved	ppelberg	T284848 Instrument topic subscriptions
Resolved	ppelberg	T277349 [SPIKE] Determine what – if any – new instrumentation is needed for notifications
Duplicate	MNeisler	T286075 QA: Verify talk_page_edit events are landing in DB as expected
Resolved	ppelberg	T286076 Implement topic subscription instrumentation
Resolved	• LZaman	T288695 [SPIKE] Conduct legal review of proposed instrumentation changes
Resolved	MNeisler	T296437 Reenable Schema:Echo

Event Timeline

ppelberg created this task.Jun 11 2021, 10:17 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 11 2021, 10:17 PM

ppelberg added parent tasks: T280896: Topic subscriptions: calculate adoption metrics, T280898: Topic subscriptions: calculate engagement metrics, T280895: Evaluate impact of notification interventions.Jun 11 2021, 10:18 PM

ppelberg added a subtask: T277349: [SPIKE] Determine what – if any – new instrumentation is needed for notifications.

ppelberg removed parent tasks: T280895: Evaluate impact of notification interventions, T280898: Topic subscriptions: calculate engagement metrics.

ppelberg renamed this task from Instrument manual topic subscriptions to Instrument topic subscriptions.Jun 11 2021, 10:20 PM

• LZaman updated the task description. (Show Details)Jun 14 2021, 7:46 PM

• LZaman updated the task description. (Show Details)

• LZaman added subscribers: DLynch, MNeisler.

• LZaman added subscribers: Ryasmeen, matmarex.

ppelberg updated the task description. (Show Details)Jun 15 2021, 12:14 AM

ppelberg updated the task description. (Show Details)Jun 15 2021, 12:18 AM

Progress update

1. @DLynch review the instrumentation spec and for each Event to be tracked comment whether we are tracking said event in the Currently being tracked (Yes/No) column: T277349
- @DLynch completed the above. See comments T277349#7152757 + T277349#7152762. Task description has been updated to reflect this progress.

Next up:

2. @MNeisler to propose naming conventions for events that require new instrumentation: T277349

ppelberg mentioned this in T277349: [SPIKE] Determine what – if any – new instrumentation is needed for notifications.Jun 30 2021, 10:06 PM

matmarex moved this task from Backlog to Triaged on the DiscussionTools board.Jul 1 2021, 2:56 PM

ppelberg mentioned this in T286075: QA: Verify talk_page_edit events are landing in DB as expected .Jul 2 2021, 5:40 PM

ppelberg updated the task description. (Show Details)

ppelberg updated the task description. (Show Details)Jul 2 2021, 5:44 PM

ppelberg updated the task description. (Show Details)

@LZaman I'm assigning this task over to you to track the progress on the steps listed in the task description.

@LZaman - Please see an update of current progress in T277349#7216918.

ppelberg updated the task description. (Show Details)Jul 19 2021, 11:34 PM

• LZaman updated the task description. (Show Details)Jul 21 2021, 4:25 PM

@MNeisler to propose naming conventions for events that require new instrumentation: T277349

With @MNeisler posting T277349#7227660, step "2." is now complete. Onwards to step 3.

The task description is updated to reflect the above.

ppelberg updated the task description. (Show Details)Jul 21 2021, 8:29 PM

ppelberg updated the task description. (Show Details)

• LZaman updated the task description. (Show Details)Jul 23 2021, 7:45 PM

ppelberg added a subtask: T280857: [SPIKE] Determine what – if any – changes are needed to access comment data.Jul 23 2021, 10:23 PM

@DLynch to review proposed naming conventions: T277349

Now that the outcomes of the conversations in T277349 are documented in the Topic Notifications/Instrumentation spec [i], "Step 3." is now completed...onwards to "Step 4."

i. See: T277349#7255866

ppelberg closed subtask T277349: [SPIKE] Determine what – if any – new instrumentation is needed for notifications as Resolved.Aug 3 2021, 8:01 PM

ppelberg updated the task description. (Show Details)

ppelberg updated the task description. (Show Details)Aug 11 2021, 8:31 PM

ppelberg updated the task description. (Show Details)Aug 11 2021, 11:33 PM

ppelberg updated the task description. (Show Details)Aug 28 2021, 1:31 AM