According to the OBSOLETE file [1] in SVN, Oversight/HideRevision was made obsolete in core itself in 1.16, and was supposed to be deleted from the repo at 1.17
Is there any reason we can't just disable it?
Do we need to do any config migration (Aaron?)?
Or is it enough just to remove "require( "$IP/extensions/Oversight/HideRevision.php" );" from CommonSettings.php?
Version: unspecified
Severity: normal
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T106123 Extensions needing to be removed from Wikimedia wikis | |||
| Resolved | Krenair | T34628 Disable Oversight extension on Wikimedia wikis | |||
| Resolved | Krenair | T62373 Convert Oversight revisions to (revision deleted) suppressed on Wikimedia wikis | |||
| Resolved | • csteipp | T20598 Create a maintenance script to convert oversighted content to suppressed with revision deletion, and the corresponding log entries too | |||
| Resolved | MarcoAurelio | T109327 Don't use deprecated message group-oversight-member |
I believe its not as simple since we still have all the old over sighted entries that may need to be accessed (unlikely) one day, Although I do believe we have removed the rights globally so no one can actually oversight new materials.
I believe there was talk at one stage of doing a conversion to revdel for the old contents but that was never done because we couldn't decide what levels it should be revdel'ed under (bleh, just do it as the crat levels) and possibly (but I don't remember 100%) a format issue with how they are stored and couldn't be converted into the revdel table format or something.
(In reply to comment #1)
Does WMF even have revision delete enabled?
Yes, It's what is used now.
reachouttothetruth wrote:
The Oversight extension has no way to un-oversight revisions anyway. So disabling shouldn't make a difference. As long as the hidden table is kept, nothing should be lost, right? And then hopefully eventually it can be converted to RevDel.
(In reply to comment #5)
Bug 18598 was closed, hence unless new blockers pop up this is ready for
execution.
Not really, only after bug 60373 is resolved, which may take a while.
(In reply to comment #6)
(In reply to comment #5)
Bug 18598 was closed, hence unless new blockers pop up this is ready for
execution.Not really, only after bug 60373 is resolved, which may take a while.
Meh, that's a duplicate in practice. And not even properly tagged. Fixing.
Change 231900 had a related patch set uploaded (by Reedy):
Stop branching Extension:Oversight
Change 231900 abandoned by Alex Monk:
Stop branching Extension:Oversight
Reason:
Duplicate of https://gerrit.wikimedia.org/r/224298/
Change 224298 had a related patch set uploaded (by Alex Monk):
No longer branch Extension:Oversight