Discussed QA process with DL, PP, RY on 02-18 And met with Rummana to walk thru the events on 02-19 this week.
Rummana will be doing one round of testing on Beta Cluster prior to production release to see if events are firing correctly. QC template for recording the events is available here and also posted in the description of the task.

Presented updates in today's meeting..

Presented the Data QA Process to Editing team on 02-18-2020 and it was well received. Requested for feedback by end of next week.

Reviewed the changes. Confirming that everything discussed with @DLynch for v1.0 has been made as expected.
We are tracking the required changes to EditAttemptstep using this section of the Instrumentation spec document.

Tentative steps decided in 1:1 with @ppelberg today -
V1.1 ---> V2.0 instrumentation: document features needing instrumentation as well as process for instrumenting those on T244498 for Maya to review; once reviewed, we will incorporate into Instrumentation spec
Step 1: document features, ordered by priority of release + metrics associated with each one
Step 2: ask maya to review features + metrics to determine, what – if any – additional instrumentation is needed
Step 3: create tickets for new instrumentation
Step 4 : document new instrumentation needs in instrumentation spec

Decided in 1:1 today:
@ppelberg to update description, add more info on why do we need this? , By when do we need this? , As much detail about what is asked, etc.

Thanks @matmarex , I have opened T244939 to QA this after Feb 20.

Currently under 'Next Up' since this task is coming up within the next 2 weeks.

Discussed with Olga and she mentioned that it would be good to have these stats now, since they are in talks with different teams for the Desktop Improvement Project.
I am planning to look into it this week.

Brainstormed with the Product Analytics team during sharing meeting and sent the following ideas to Olga for further discussion :

In T243467#5867062, @DLynch wrote:

But Maya and I have spoken about it, and we know what needs to happen.

Met with @DLynch over the last week to discuss, (focussing only on the current release V1.0) which events need to be instrumented and which schema they will live. We have come to the conclusion that for the features being implemented as a part of Replying V1.0, we will not need a new schema and everything we need can be tracked using EditAttemptStep.
T243363 is not a blocker for V1.0

Met with @DLynch over the last week to discuss, (focussing only on the current release V1.0) which events need to be instrumented and which schema they will live. We have come to the conclusion that for the features being implemented as a part of Replying V1.0, we will not need a new schema and everything we need can be tracked using EditAttemptStep.
T243363 is not a blocker for V1.0

Thanks @nshahquinn-wmf for digging it out ! :)

Will get this done only by Q4. moving to backlog.

Confirmed from Peter that T243641 will be completed in Q3. So this QA ticket will be coming up this quarter but not immediately. Moving back to Q3 bucket on the PA-workboard.

Successfully presented Wikistats2, Turnilo, and all other data resources at the Data Party workshop.

Met with David and Peter and to understand how the EditAttemptStep schema can be used for Replying Talk pages.
Will discuss next week during All Hands or after, regarding the new talk page schema.

Thanks @Nettrom !
@Abit and @Ramsey-WMF , can you please review and let me know if you have any further questions ?

In T231952#5803922, @Mayakp.wiki wrote:

In T231952#5783773, @Ramsey-WMF wrote:

Please also let me know by when do you want the updated numbers.

I'll leave that to Amanda (who is unfortunately out sick today) since she has more a schedule need than I do.

Confirmed with Amanda in today's review meeting that this is needed by end of January. Created subtask T242816 for this.

Discussed with Connie about outline and slide deck

@nettrom_WMF : created pull request for metrics with December 2019 numbers that we reviewed on 01/22. Can you please merge it with the master branch ? Thanks !

These are metrics affected INDIRECTLY due to features being added as a part of DIP.
Refer to following documents to think more about this:

• Sequencing (DIP)
• Desktop improvements update for Maya (this is an unchanged copy of the original slide deck)

Discussed with Olga in 1:1 today :

• High priority i.e. Important but not urgent
• Test started running in Oct 2019
• Analysis for this task may be similar to another test that was run by the Web team: T209720 - Determine impact of sitemaps on search traffic to Indonesian, Portuguese, Punjabi, Dutch, and Korean Wikipedias
  • Query & scripts: https://github.com/wikimedia-research/SEO-Experiment-Sitemaps

This looks great. Thanks Peter! will discuss further in our meeting with Jason/Mikhail today.

It would be helpful to have a table of the metrics and the status of each--I can't for the life of me remember what we need the dumps for.

Met with Peter and David over this week to finalize project kpi, replying kpi, impact kpi as well as Workflow Engagement metrics. Also discussed workflow events and scenarios that we will need to track.
Topics discussed in 01/17 meeting between DL-PP-MK:

• What talk page and replying-related events would we like to track?
• In what schema should these events be logged?
  • DL: seeming more and more like a new schema is necessary; contexts are sufficiently different; dashboarding would become tricky if metrics for talk pages and articles were collapsed into one schema
• Current talk pages tracking
  • Assume things we are tracking on articles we are tracking on talk pages EXCEPT for VE-related metrics (all happens in Schema:EditAttemptStep - Meta)
  • Mostly this is just EditAttemptStep. People using NWE will also be submitting VisualEditorFeatureUse for any wikitext tools they use.
• Talk pages/Replying/Instrumentation spec
  • Workflow completion timing
    • Complicated, but potentially not impossible to create a 1:1 comparison between replying workflow and full page b/c full page workflow could – in the case of contributors using classic wikitext editor – involve a contributor visiting 3 distinct pages. Then becomes difficult to work out when exactly the session started
    • Also: more thought needs to be put to when exactly the workflow starts in both experience (full page and new replying workflow)

In T231952#5783773, @Ramsey-WMF wrote:

Please also let me know by when do you want the updated numbers.

I'll leave that to Amanda (who is unfortunately out sick today) since she has more a schedule need than I do.

Fundamentally it's the same effort for both approaches, but If we redo it with December alone, the queries will take much lesser time 🙂 but I understand that including it would help in giving you a better picture of 2019.

Hey @Ramsey-WMF , December 2019 data is available in the database now.
Would you like us to redo all the existing analysis and publish it with the new numbers (which will include Dec numbers) Or would you like to only see the December numbers alone for all the analysis ?

Update on parent ticket: Test is currently running
T235101#5782877

Moving to 'Needs Review' since this task is completed and needs a final check from @Abit and @Ramsey-WMF before getting closed.

Confirmed that this issue impacted desktop and not phone, hence it will not have a big impact to 'VE as default' project.
Provided analysis on this Github notebook.

Checked the data in serversideaccountcreation table of event_sanitized db and verified that post the update to the Whitelist on 11/20, usernames have been saving as expected and none of the usernames are null.

In T231952#5755782, @Abit wrote:

Thanks @Mayakp.wiki ! I will look at these before the break. Do you want
me to create the two new tickets?

Discussed with Kate and Max Binder about shipping this around: