In T232237#5578104, @Jdlrobson wrote:

Check out https://m.mediawiki.org/wiki/Reading/Web/Chores for all our boards. I think https://grafana.wikimedia.org/d/000000205/mobile-2g should have all the information you need.

In T234046#5561330, @ppelberg wrote:

Below are notes from the conversation @MNeisler and I had this morning...
4. Retention
Decided

• For purpose of calculating baseline metrics, we will look at retention across all experience levels; the goal of the project. Although, our goal for this project is to increase retention of junior contributors.
• We are defining activity as any edit to a talk page

Actions

• @ppelberg + @MNeisler: What do we define a "cool down period" as?

Update

• Engineering QA for T232237#5548323 is just awaiting confirmation from the Web team that the patch doesn't slow down page load times
• Product Analytics QA for T232237#5548323 is in progress: T235104#5573854

In T232237#5576474, @matmarex wrote:

Seems to work as expected, as far as I can tell, the 'init' event gets logged immediately, before the editor loads.

! In T232237#5576479, @matmarex wrote:

Oh, and I just saw that it also looks good on the Analytics side: T235104#5573854

In T235104#5573854, @Mayakp.wiki wrote:

Checked the distribution using Neil/Megan's initial code, for data starting from 10/10 (date when fix was applied). The buckets seem to be balancing now. The data is being collected 50-50 in both buckets.

bucket	attempts	attempts%	users	users %
default-source	176,263	49.96%	133,092	50.17%
default-visual	176,540	50.04%	132,212	49.83%

Some other "Selection Criteria" to consider as inspired by Communication networks do not explain the growth or survival of early-stage peer production projects:

In T233470#5516971, @gerritbot wrote:

Change 526235 had a related patch set uploaded (by Bartosz Dziewoński; owner: Bartosz Dziewoński):
[mediawiki/extensions/VisualEditor@master] MobileArticleTarget: Limit iOS fixed toolbar workarounds to iOS 12 only
https://gerrit.wikimedia.org/r/526235

In T234410#5566813, @Aklapper wrote:

@ppelberg: Could you please clarify / fix the "FY2020" which does not exist? Thanks!

Updated the task description. Made the following change to the retention metric

In T234046#5561761, @MNeisler wrote:

1. Junior contributors
Notes

• If we're not able to look at contributions on a per project basis, that would mean a contributor who has 200 edits to Commons and 2 edits to Wikipedia, would not be considered a junior contributor to wikipedia

Actions

• @MNeisler: is it possible to differentiate contributions by project?

Yes. I double-checked this and confirmed that while the event user revision count field does track a user's edits across all projects, we can add filters to differentiate contributions by the project. Based on this, I think we can keep the definition as "Contributors who have made <100 cumulative contributions to Wikipedia"

In T234561#5557709, @ppelberg wrote:

Documenting next steps from @iamjessklein's and my meeting today:
PP:

• Refine user stories
• Refine feature hypotheses and methods of measurement
• Refine specs (slides 34 + 53)
• Consider adding project and yearly metrics to front of deck

In T221728#5471778, @Neil_P._Quinn_WMF wrote:

I just consolidated our different experiment plans into the task description here.

In T221728#5471720, @ppelberg wrote:

Something else to note, @Neil_P._Quinn_WMF raised the question below, which our work on this task depends on having the answer to:

• Confirm: Do we have data on the pre-Edit Card state of VE to compare the post-Edit Cards v3 state of mobile VE to?
  • @Neil_P._Quinn_WMF, this comment leads me to think that "Yes, we do." but leaving to you to confirm: T221254#5376056

We have detailed data on linking and citations starting on 13 July (I just added this to the description). However, I could not figure out the deployment dates for the various versions, so I'm not sure if that's before our first Edit Cards deployment. @Esanders, @DLynch, could you help filling in the table of deployment dates in the description?

Below are notes from the conversation @MNeisler and I had this morning...

@Mayakp.wiki, this patch (see below) should be ready for QA as soon as tomorrow.

• Engineering QA for T232237#5548323 is completed
• Product Analytics QA for T232237#5548323 is completed. See task: T235104

In T234277#5545434, @ppelberg wrote:

Next steps
I think the only things we're waiting on now before the test can officially "restart" is for this patch (T232237#5535452) to be:

1. Merged. See: T232237#5545272
2. QA'd. Which – in addition to making sure contributors are being bucketed properly – should include a test of what, if any , impact it has on how long it takes an article, in read mode, to load. See: T232237#5536319

@Esanders, how'd you arrive at not providing contributors any feedback [1] about their attempted paste?

@MNeisler, copying over a few thoughts from conversations we've had before...

• "5. Productive contributions to article pages": any edits to Wikipedia articles that are not reverted.
  • Is ORES goodfaith a better predictor of "productive contributions" than non-reverted edits?

Documenting next steps from @iamjessklein's and my meeting today:

In T213120#5554032, @matmarex wrote:

I think this is a new problem. We fixed this back in April, and it has only regressed recently. It'll be more convenient to investigate in a new task, so I filed one: T234868

In T232237#5545272, @matmarex wrote:

Engineering. (Note that it's still not merged, Krinkle had some concerns on the patch, and I just updated it.)

I am drafting this spec in our Talk Pages/Planning document. Everyone should have access to comment on this document.

Adding some additional questions/thoughts to the ones posted in T234046#5539981:

In T213120#5095449, @Ryasmeen wrote:

ok, this time it's real. Still seeing this on bn.wiki. Here is the video capture:

ScreenRecording_04-08-2019 13-24-59.mp41 MBDownload

In T232790#5544653, @DLynch wrote:

Everything Rummana saw looks correct, it's just a confusion about what the event name is. For the VisualEditorFeatureUse events it's two-part, there's a feature and action component, with the name being written here as [feature].[action].
e.g. this console log shows the mwSave.checkbox-wpWatchthis event:

Got it. Thank you for demonstrating this and for updating the task description accordingly, David.

Next steps

Thank you, Megan. A couple quick comments in-line, below...

This comment pulls together the questions that emerged on this ticket, in various meetings and most recently, our discussion around what our next steps should be around the VE as default A/B test that took place in this task: T234277.

Great work, @matmarex. Documenting a question that came up during today's planning meeting...

I think we should re-run the test with no modifications to the design of the test, save for any changes @MNeisler deems to be necessary as a result of answering the "Resulting questions" below.

@matmarex do you know who is best suited to QA this patch? QA? Engineering? Product Analytics? cc @JTannerWMF @marcella

Our objectives and key results for this project have been defined as follows:

Updating the task description to include our current definitions.