Making a comment instead of just editing the description (so people can more easily follow along):

A full copy of enwiki isn't possible for the test MVP instances (5) on WMF labs. We need a subset. Someone needs to define that subset for us. Please make it as small as possible but still meet the needs (which is just to test basic functionality).

@greg I'm not sure how to define a subset that is meaningful (or rather how to define a subset in a meaningful and understandable way) do you have a recommendation?

Can you take a look at the Proposed Tasks section of https://docs.google.com/a/wikimedia.org/document/d/1YKaCwhR_RW-iCe6zJvuST5NBVP01eE_seNyc-v7rvxs/edit#heading=h.2fxajlbxqbi1

and based on those tasks propose a subset that would make sense, or be usable, e.g. needs functioning search, categories, history, article content etc.

In T792#13628, @Jaredzimmerman-WMF wrote:

Can you take a look at the Proposed Tasks section of https://docs.google.com/a/wikimedia.org/document/d/1YKaCwhR_RW-iCe6zJvuST5NBVP01eE_seNyc-v7rvxs/edit#heading=h.2fxajlbxqbi1

As I'm not the researcher doing the testing, I'm going to have to request the UI/UX team do that part :) (I'm likely to miss some nuance that you're shooting for). My suggestion:

1. Determine which subset of those proposed tasks you absolutely need to test the two providers on the 1-5 instances ("test MVP")
2. Then, go through those tasks and determine what minimum of content you need to test them.

After that, we need to talk with someone from Ops to get that information exported and imported correctly.

For the full on "Production Testing" requirements we'll be able to do more.

@greg I guess there is no concept of a task being high priority for one team and lower for another.

@Jaredzimmerman-WMF Yeah, for now. But we could make this task (the tracking one) in a Design/UX project board and then put the appropriate sub-tasks in the appropriate workboards for other teams/projects (including Release-Engineering-Team ). Do you all have a project yet?

@greg Re: "subset" - are there any docs giving examples/details of what previous people/teams have used? Partially for the sake of this particular task, but also because I've long been curious as to what subset of content exists on test, test2, beta, etc. and what could potentially be requested at other test-instances.
I have no idea whether a "subset" implies 10, or 500, or 10,000 pages! Nor if there are obvious-in-hindsight pros/cons to selecting certain subsets. E.g. One of my first hypothetical suggestions (given what Jared asks for above), would be "Everything 2 degrees away from Arctic tern" (a recently Featured-class article) but that's probably in the 10,000 range (or more).

(I tried a bit of searching, and found nothing useful at wikitech or test/test2/beta, and way too many results at mw.o, so possibly it's already documented somewhere? Nothing at the obvious suspects, like [[mw:Beta cluster]] or [[mw:Test wikis]])
Thanks.

Maybe "UX-Testing-Environment" deserves a project on its on? Is this a short one-off shot, or an actual project?

@Qgil I don't know what scale something has to have to get a "project" ;) if it becomes a Q3 goal, probably.

This is more about semantics ;) than about sale. If it is a project, then it deserves a Phabricator project. If it's just a group of tasks belonging to something bigger, then not.

It is also probably a matter of timing. If this is just preliminary work to propose a project, then not yet, if you are certain that you will work on this and the only question is when and with how much resources, then yes.

We are defining the guidelines as we go. In case of doubt, I would create a project. They are cheap, and are better than having tasks in the pool of orphans (as these tasks are now).

If we're making a project it should be "State of the User" UX testing
environment is an aspect of that larger project.

Related tasks (precursors to this task):

• T108582
• T108531

This task is blocked until we get an engineering resource

In T792#1540485, @Capt_Swing wrote:

Related tasks (precursors to this task):

So should those be listed as blocking this task under "Blocked By" here, or are they "just" related?

@Aklapper not sure. This task/project has been significantly re-scoped post-reorg. I'll follow up with the team at our next backlog grooming session and update accordingly.