@Tgr We plan to start this epic in October, but we should map out our timeline and deployment strategy soon.

From a technical point of view:

1. Is documentation up-to-date? https://wikitech.wikimedia.org/wiki/Add_Image#Enabling_image_recommendations_on_a_new_wiki
2. Should we create technical documentation for the section-level "add an image" task?
3. What is the general level of effort of releasing "add a link" to more wikis?
4. Should we consider releasing section-level "add an image" and article-level "add an image" together? (Will that help reduce the overhead of scaling both features to more wikis, or should we approach these releases separately?)
5. What level of manual testing do you think is needed at each wiki? In other words, do you think testing for each language version needs to be part of the engineering task, or QA cycle, or do you think CRS or Product also needs to test each language version before it is released?

FYI @Trizek-WMF - since we will coordinate on the community-side of this rollout.

In T322592#9057275, @KStoller-WMF wrote:

1. Is documentation up-to-date? https://wikitech.wikimedia.org/wiki/Add_Image#Enabling_image_recommendations_on_a_new_wiki

We are not doing A/B testing anymore, so I removed to corresponding bullet point. Other than that, I think it's still valid.

2. Should we create technical documentation for the section-level "add an image" task?

Added some notes at https://wikitech.wikimedia.org/wiki/Add_Image#Section-level_images but there isn't much difference.

3. What is the general level of effort of releasing "add a link" to more wikis?

Did you mean "add an image"? For that, we have to generate infobox lists, which isn't much work but it isn't as effortlessly scalable as community configuration, either - it takes a small dedicated effort for each new wiki. Other than that, we are just flipping a switch, I think. For section-level images, we don't care about infoboxes so doing those is very little effort.

(For "add a link", the main difference is that we have to wait for the maintenance script to generate tasks. We probably want to make sure there are enough tasks, for all three structured task types; that's a manual effort now but easy to automate / scale up, we already built the infrastructure for that.)

4. Should we consider releasing section-level "add an image" and article-level "add an image" together? (Will that help reduce the overhead of scaling both features to more wikis, or should we approach these releases separately?)

I don't think it makes much difference; doing them together is less work, but only marginally.

5. What level of manual testing do you think is needed at each wiki? In other words, do you think testing for each language version needs to be part of the engineering task, or QA cycle, or do you think CRS or Product also needs to test each language version before it is released?

I don't think testing on all 300 or so Wikipedias is a good use of our time. We should probably check the number of available task though - we can do that in batches, we built an API for that + I think we are also exporting the information to Grafana.

Thank you for answering all of my questions and updating documentation! 🏆

In T322592#9057453, @Tgr wrote:

3. What is the general level of effort of releasing "add a link" to more wikis?

Did you mean "add an image"? For that, we have to generate infobox lists, which isn't much work but it isn't as effortlessly scalable as community configuration, either - it takes a small dedicated effort for each new wiki. Other than that, we are just flipping a switch, I think. For section-level images, we don't care about infoboxes so doing those is very little effort.

(For "add a link", the main difference is that we have to wait for the maintenance script to generate tasks. We probably want to make sure there are enough tasks, for all three structured task types; that's a manual effort now but easy to automate / scale up, we already built the infrastructure for that.)

Yes, thanks for interpreting what I really meant to ask. I was indeed thinking about how the level of effort for scaling "add an image" compared to "add a link".

4. Should we consider releasing section-level "add an image" and article-level "add an image" together? (Will that help reduce the overhead of scaling both features to more wikis, or should we approach these releases separately?)

I don't think it makes much difference; doing them together is less work, but only marginally.

5. What level of manual testing do you think is needed at each wiki? In other words, do you think testing for each language version needs to be part of the engineering task, or QA cycle, or do you think CRS or Product also needs to test each language version before it is released?

I don't think testing on all 300 or so Wikipedias is a good use of our time. We should probably check the number of available task though - we can do that in batches, we built an API for that + I think we are also exporting the information to Grafana.

@Trizek-WMF - I think this gives us enough info to decide on a basic timeline and release strategy. Let's discuss next time we meet and then we can update this task with details.