@Jan_Dittrich in general just shoot at it with what ever you think makes sense.
Wed, Sep 20
Tue, Sep 19
Mon, Sep 18
Fri, Sep 15
@Addshore yay, great!
@MoritzMuehlenhoff great, thanks!
I think what's still missing is setting $wgWikiDiff2MovedParagraphDetectionCutoff = 25; for the beta wikis to actually see the new behavior. With that set to 0 (default) the diff will just work as before.
Thu, Sep 14
@Bawolff @Reedy do you have any updates on this? We're aiming for a deployment as a beta feature in October or November 2017, so we should resolve any security review related issues rather soonish. Can you give a brief timeline for this?
Wed, Sep 13
I assume this includes:
- how many users enabled the extension as a beta feature, how many disabled it (similar to what we have for TwoColConflict)
- number of how many searches are submitted using the new form
- separate tracking for each supported keyword: how many times was each keyword used?
@Legoktm @greg, adding the teams Operations and Release-Engineering-Team as I'm not sure who exactly would be in charge of this. Since @Lea_WMDE is currently on leave, please poke me, @Bmueller or @Addshore if you have any questions.
Wed, Sep 6
So, after a short discussion with @Bmueller here's what we suggest:
Tue, Sep 5
There's nothing to do until we have the extension on beta because we cannot test it on local environments.
No conclusion yet how we should handle this case. We will look into it more, to see if there's a way in MediaWiki to deal with it.
This looks good from a first glance. We'll have a look at it together with the whole team today.