In T307605#7939828, @Sneha wrote:

This was another option explored to match the style with how we show namespaces on commons. But as you can see (as indicated by the pink line) the alignment looks disorganized which negatively impacts scanning of information. Hence we should go with the option mentioned in the description.

@Seddon

Note that as per T283865, we'll only be notifying users of suggestions with a confidence score of >=80%.

In T306884#7927739, @Sneha wrote:

If we close this then could we capture snippet length investigation as a separate task in backlog so it is not lost?

In T293878#7920273, @Cparle wrote:

Update on this ticket - looking at the data I'm not sure that what we've gathered is capturing the effect of the synonyms patch, and I think we might need to curate it more carefully.

Probably ought to pause further work on this ticket until we have a chance to consider this more closely

Hi @cchen! JarBot just completed a run of his bot in arz.wp. Can you run the same analysis there?

Noting that as a result of T296507 we'll have to make sure to run the script in smaller batches.

Closing based on the above; we'll make sure to run the script in smaller batches. Thanks.

Closing since all subtasks are complete.

It does, thanks! I think that then @SWakiyama needs to make a call based on the information gathered for this ticket which confidence level to use in T292147 (AC #3). I'll follow up with her offline and will close this ticket.

Noting that development can begin, but nothing should be merged until we've had the chance to get feedback from the communities (in progress).

Noting that development can begin, but nothing should be merged until we've had the chance to get feedback from the communities (in progress).

Noting that development can begin, but nothing should be merged until we've had the chance to get feedback from the communities (in progress).

Noting that development can begin, but nothing should be merged until we've had the chance to get feedback from the communities (in progress).

Blocked by T307560

Resolving because we determined this isn't the best way forward. From @Sneha in Slack: