@thiemowmde
could you please have a final look. The developer claimed to have addressed the issues you've mentioned in https://github.com/wmde/mitmachen/pull/38/files.

I looked at the wish-doc again and figured we would like to have numbers for the following levels of experience:

In T233202#5538406, @Lucas_Werkmeister_WMDE wrote:

Please reach out to fellow WMDE deployers for a training or if not possible, RelEng team members.

I’d be happy to help out :) do you have any planned/upcoming deployments to train on? (I can’t think of any from my end.)

This is for an A/B test on Oct 9th: 2 versions of Laika would be tested: one w/o this feature and one with it.

In T233202#5506870, @herron wrote:

@Andrew-WMDE could you please coordinate obtaining a comment of approval here from your supervisor?

Some sources of information to look at:
https://addshore.com/2018/02/wmde-event-logging-intro/
https://www.mediawiki.org/wiki/Extension:EventLogging/Guide

In T232480#5493006, @Masumrezarock100 wrote:

In T232480#5479283, @Tobi_WMDE_SW wrote:

For clarification: the configuration we're talking about would be a configuration of the FileExporter extension. It would enable us to specify certain user-rights which users on certain wikis need to have in order to use the extension to move files to Wikimedia Commons.

What user right are you referring to? Do you mean a new user right will be created?

For clarification: the configuration we're talking about would be a configuration of the FileExporter extension. It would enable us to specify certain user-rights which users on certain wikis need to have in order to use the extension to move files to Wikimedia Commons.

As this is mainly cosmetic and everything is working as expected (e.g. the link is resolved correctly), we consider this not important for the small-default milestone.

This is not demoable on the beta-cluster.

Agreed to invest 3 SP into finding out whether the existing fix is sufficient.

We're having a look whether the existing and merged patches fixed the bug, or we fix it in the WMDE-QWERTY-Sprint-2019-09-04 otherwise.

@jkroll please sum up the investigation results so far here