@Aklapper - it seems I don't have the permissions to edit this task. Is there a way to check what is causing that?

We need to decide whether to send multiple events per page or follow an approach similar to https://meta.wikimedia.org/wiki/Schema:MobileWikiAppPageScroll

Is this correct? I thought we'd decided to send one event per page.

Discussed in standup and noted that the next way forward might be to create a draft of the schema in parallel to this task.

^ If creating a draft schema helps the investigator to think about the implementation, then they should feel free to create one!

number of sections opened/closed per page (we could potentially use the section usage schema: https://meta.wikimedia.org/wiki/Schema:MobileWebSectionUsage)

Note, we should also consider the fact that Special:MobileOptions allows users to expand all sections by default, a state which will impact instrumentation.

Since there is no "points 0" on this task it means we haven't talked about it. We did an async estimation and estimations are all over the place.

@jan: 8, @pmiazga: 8, @Stephen: 5, @Jdlrobson: 13, @nray: needs analysis:banana:

Let's talk about this today and work out how to make this clearer.

In T199157#4501787, @Jdlrobson wrote:

Since there is no "points 0" on this task it means we haven't talked about it. We did an async estimation and estimations are all over the place.

@jan: 8, @pmiazga: 8, @Stephen: 5, @Jdlrobson: 13, @nray: needs analysis:banana:

Let's talk about this today and work out how to make this clearer.

I'm a bit confused. Why are we pointing this? In grooming we decided it was a spike (so hours, not points) and gave a rough estimate for 8 hours. I'm not arguing against looking at it again, just confused as to the process here.

We tried to point the '''hours'''. We (devs+tilman) then chatted about the task in the grooming meeting and decided this was not ready to be worked on. A precursor has been added to the task which we believe is important before agreeing to a timebox and taking on this spike.

For clarity: we have been adding 0 points to the field of a spike task as a signal that we have talked about the task, agreed on the hours and said it is ready to be worked on.

For clarity: we have been adding 0 points to the field of a spike task as a signal that we have talked about the task, agreed on the hours and said it is ready to be worked on.

Got it! I think I was missing this part - did we decide on doing this at some point? Have I been missing it all along? (i.e. I haven't done this to any of the tasks I've added hours to - doesn't adding hours show that we have discussed it as a team as well?)

Got it! I think I was missing this part - did we decide on doing this at some point? H

It's a new thing that's been happening given we were getting confused about whether spikes had been discussed or not. While adding hours is one way, we've historically created tasks where one-two person has suggested/decided upon hours and these hours have changed and it's hard to distinguish. I've documented this here:
https://www.mediawiki.org/wiki/Reading/Web/Team/Story_estimation#Spikes_(0)
Comments are probably the most useful signal here (the where, the who, the what, the why) and I'll commit to doing better at that when updating points/hours in future.

A few questions (no urgency right now)

number of sections opened/closed per page

@Tbayer I made a few edits to https://meta.m.wikimedia.org/wiki/Schema:MobileWebSectionUsage to update it with current code.

With it, if we were to send multiple events per page we would be able to count scrollIntoView events and close events and I think answer this question using the code we used before.

total number of pixels scrolled up and down per page

It feels like https://meta.m.wikimedia.org/wiki/Schema:ReadingDepth tells us how long a user spends on the page (visible time and total time spent on page). Would the plan be to add pageHeight,scrollFluxDown,scrollFluxUp,percentageViewed (or something along those lines) to that schema?

I think this is the tricky one we would want to investigate in this spike. Specifically how those fields get calculated.