As above..
Version: unspecified
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz26045
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T24094 Add a "(un)?watch this revision" options to CodeReview | |||
| Resolved | None | T26382 Allow option to disable CodeReview e-mails after commenting on a revision | |||
| Declined | Feature | None | T20379 Allow to amend or delete ones own remarks in CodeReview | ||
| Declined | None | T26279 CodeReview's parsers suck | |||
| Declined | Feature | None | T24968 CodeReview doesn't prevent duplicate comment submissions | ||
| Declined | Feature | None | T30823 CodeReview needs search for comments | ||
| Declined | None | T28045 Switch CodeReview to use LiquidThreads |
Event Timeline
Comment Actions
Having CodeReview support multiple commenting backends (i.e. [[mw:Extension:Comments]], LiquidThreads, etc.) would be nice. However, that's not a high priority since the current system works well enough.
Additionally, this bug will never (or at least in the forseeable future) be fixed as-is, because the current version of LiquidThreads is "no longer actively maintained" (as per https://www.mediawiki.org/w/index.php?title=Extension:LiquidThreads&oldid=794592) and it has plenty of open bugs, and the planned new version, 3.0, is "on hold" or "canceled" (as per https://www.mediawiki.org/w/index.php?title=LiquidThreads_3.0&oldid=647230). Therefore it doesn't seem beneficial to switch a working, albeit simplistic, backend to something that has many known issues and no-one to actively (try to) resolve said issues.
Comment Actions
In addition to a lack of support for LiquidThreads, the CodeReview MediaWiki extension has been abandoned in favor of using Gerrit for Wikimedia wikis, adding to the reasons that this bug will never be fixed.
(tangentially...)
It may be difficult to believe, but Gerrit's discussion system is actually worse than LiquidThreads' (and Bugzilla's). That said, Gerrit's discussion system has shown some improvement over the past year; for example, it no longer collapses comments so aggressively. It's still fairly hostile to collaboration, however.