It's been lying around forever but required a configuration change to be used which probably nobody bothered to set. To avoid it bitrotting forever, we need to figure put how it compares to DairikiDiff in performance and diff quality and decide which of them should be used. Unless there is a very visible tradeoff between performance and quality, I don't think we should keep both alternatives around.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Make wikidiff3 the only diff engine | mediawiki/core | master | +13 -289 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | None | T98348 Implement the Wikimedia Foundation Call to Action 2015 | |||
| Invalid | None | T98358 WMF to integrate, consolidate, and pause or stop stalled initiatives | |||
| Resolved | • DannyH | T121469 Improve diff compare screen | |||
| Resolved | MaxSem | T128896 Decide what to do with Wikidiff3 |
Event Timeline
Comment Actions
Historical background: http://comments.gmane.org/gmane.science.linguistics.wikipedia.technical/39225
Comment Actions
Change 284003 had a related patch set uploaded (by MaxSem):
WIP: Make wikidiff3 the only diff engine
Comment Actions
Can you describe the corpus you used at https://diff-forge.wmflabs.org/wiki/Special:DiffCompare and summarise the results?
Comment Actions
Corpus: those of 100k diffs from enwiki's RC that have differences between the algorithms (~6K diffs total). Results:
root@localhost:[wiki]> select count(*), dv_vote from diff_votes group by dv_vote; +----------+---------+ | count(*) | dv_vote | +----------+---------+ | 45 | -1 | | 148 | 0 | | 37 | 1 | +----------+---------+ 3 rows in set (0.00 sec)
Where -1 means wikidiff3 better, 0 is same shit, +1 is DairikiDiff.