@ECohen_WMDE @Lena_WMDE I ran into the following questions regarding the tracking.

@daniel I vaguely remember something popping up about changes to the edit conflict detection lately in combination with you - can you confirm / deny? :-)

Increasing story points to take into account that an aggregation from the event data also needs to be happening beforehand.

Needs to be triaged before the next maintenance sprint.

Adding more points to take aggregation of EventLogging data into account.

In T260186#6634102, @Ivi104 wrote:

@WMDE-Fisch Thank you for responding. I've managed to isolate the issue. The problem only happens when VisualDiff beta feature is enabled. Please confirm if you can reproduce the issue when enabling VisualDiff and doing the steps described in my previous comment.

All done here \o/

Approved this morning in dev meeting.

@awight Just looked into the board and the configured filter. Do we really monitor all projects checked above there? Or did I miss a setting?

FYI: Would want to get

• https://gerrit.wikimedia.org/r/c/mediawiki/extensions/RevisionSlider/+/584262 and
• https://gerrit.wikimedia.org/r/c/mediawiki/extensions/RevisionSlider/+/584263

merged before we continue on this. At least on the first one are unaddressed comments. @awight *poke*

In T198372#6620285, @thiemowmde wrote:

I think what was written in the comment T198372#4380653 still applies. With T194132 we list only the first reason why a file can not be imported. But we neither list all of the templates and categories, nor can we distinguish between direct and indirect template usages. I.e. the task asking for "which template" is still unresolved, as far as I'm aware of.

I just checked the code it seems that this issue was fixed in T194132: Parse the file info wikitext to forbid files with a wrong licence. In the error message added there we show the blocking template / category.

In T185734#6619572, @MGA73 wrote:

I can't reproduce this error. Is it still a problem or can it be closed?

First realization:
They way how source code including formatting white space is displayed is really bad in Two-Column-Edit-Conflict-Merge

In T225826#6615535, @awight wrote:

Trying to fix basic things about the wiki so it becomes usable...

I'd like to hear other people's thoughts about persistence. Should we keep the database contents on the host filesystem, so that it's available across container instances, and provide a clean script to delete it? Or should the default be to rebuild a wiki from scratch, importing only a controlled set of fixture pages? I'm leaning towards the latter. If you want to save some pages, Special:Export them, this isn't a very common use case in my experience.

Looks good to me so far. And thanks for creating the tickets related to the stuff revealed.

Got a reply here and it seems there's no issue from that user. We also heard nothing else from the original creator of that thread from over a year ago. Closing the ticket.

@Andrew-WMDE Might want to base the work here on https://gerrit.wikimedia.org/r/c/mediawiki/extensions/RevisionSlider/+/639588 where I already did some more ground work :-)

In T188625#6597132, @awight wrote:

Responding to the JS hook works well :-) -- Only half-tested locally, we should validate on the beta cluster.

In T244059#6602753, @thiemowmde wrote:

I'm sorry, but I can't really follow these arguments. Just because a community is "technical" doesn't mean everybody knows what an abbreviation like WMDE means. We are used to it, sure. But we are not the audience. The target audience is the public looking at Special:Version. None of the links I follow on this page or in the footer of the page uses the abbreviation "WMF", for example. If the company is mentioned, it's the full name.

Another analogy for comparison:

• Wikidata + WMDE → ~30,000 times, starting with rather strange search results.
• Wikidata + Wikimedia Deutschland → more than 10 times more often.

*blocking the task for pair programming*

*blocking the task for pair programming*