Page MenuHomePhabricator

Put commons database in readonly mode
Closed, DeclinedPublic

Description

Per total chaos on Wikimedia Commons with multiple deletions and wheelwarring among jimbo and administrators, I request that the Commons database is temporarily put into readonly mode until the Foundation sorts this out. The actions of the past two days are highly damaging not only to Commons itself, but also in the removal and restoration traffic it is creating in the various other projects.

This has to stop and be sorted out.


Version: unspecified
Severity: enhancement

Details

Reference
bz23435

Event Timeline

bzimport raised the priority of this task from to Lowest.Nov 21 2014, 11:08 PM
bzimport set Reference to bz23435.
bzimport added a subscriber: Unknown Object (MLST).

This is a community and content issue, not a technical one. Nobody's should lock down the database.

WONTFIX?

thor.malmjursson wrote:

With respect to the current issues, I don't feel it is viable to lockdown the Commons db without full community consensus. It will be considered if this can be gained via commons users making an open decision.

(In reply to comment #2)

With respect to the current issues, I don't feel it is viable to lockdown the
Commons db without full community consensus. It will be considered if this can
be gained via commons users making an open decision.

Or that the board pasts a motion of the same effect.

This does need to stop and get sorted out; we don't need to shut down Commons to do it (the vast majority of which is unaffected by the drama). To avoid the cross-project chaos, admins should avoid deleting images that are used on other projects until content policy is settled. [If commons ends up choosing a policy that will remove images used elsewhere, the projects need to be informed so that they can respond accordingly.]

Abigor wrote:

Closed,

discussion should happen first, request after...