Should T89970 be considered a blocker for this?

Is it something that Product and Strategy depend on existing to do the work? ;)

In T93394#1136223, @Whatamidoing-WMF wrote:

Should T89970 be considered a blocker for this?

I originally created the task with a more limited scope in mind (i.e. only what Oliver, Tilman and I would be doing) but I have no objections to expanding the scope to cover all research-type support for VE from multiple teams. I actually think it would make a lot of sense. We just need to add the appropriate projects and tweak the description.

I don't know. That's why I'm asking.

Being able to get quick, big-picture feedback from actual users, and especially being able to compare that feedback based on which editing environment is being used (and other things, like the user's experience level) is a good way to support the rollout with research and analysis. But it's not the only possible way.

That sounds like qualitative rather than quantitative work - which is valuable but...Guillaume, is this the sort of thing you'll be working on?

In T93394#1136267, @Ironholds wrote:

That sounds like qualitative rather than quantitative work - which is valuable but...Guillaume, is this the sort of thing you'll be working on?

Not as far as I currently know :)

Does list-making fall into this scope? See T96323 for the latest copy on behalf of TemplateData.

Probably, but I'll note that the database doesn't actually know templatedata exists, so I'll be damned if I know how to indicate if it's present or not :/.

Isn't it in the page_props table?

Yep; you're right!

Now to handle joining page, templatelinks and page_props. Argh.