2017 Community Wishlist Survey/Multimedia and Commons/Fix problems that FlaggedRevs wikis have with Commons
Jump to navigation Jump to search
The survey has concluded. Here are the results!
- Problem: The common problem for all Wikimedia wikis that currently use FlaggedRevs extension (there are currently 45 of them) is that almost every change at Commons at any scope (even a page edit) brings more work to reviewers across the projects that use files from Commons: Холодный Яр − the page after an edit at Commons immediately deems itself unstable and the only way to fix this is to waste time of editors by rereviewing it again manually. It is because FlaggedRevs does, justly, think that any transclusion that is not in a reviewable namespace makes a page unstable, but it is not right to neglect the fact that images from Commons are currently used in thousands upon thousands of pages in 45 Wikimedia projects. Given that this problem persists almost for 10 years in some cases, I propose that we should find a solution already that would satisfy both wikis with and without FlaggedRevs extension enabled.
- Who would benefit: Reviewers and readers at wikis that have FlaggedRevs extension enabled
- Proposed solution: Fix the problem of cross-wiki transclusion or enable FlaggedRevs at Commons for all users, if the latter would help (the solution can be technical and all edits can be reviewed automatically for all users).
- More comments:
- Phabricator tickets:
- Translations: none yet
- This is one of the options, yes. There aren’t any solutions for watching over changes in Commons images from files anyway, so it’s not like any reviewers can affect the situation in any way. Especially if the changes are not in the files themselves but in the pages that are describing them (it also triggers the rereview). stjn[ru] 22:59, 20 November 2017 (UTC)