Are Commons admins approved temporarily? I know some Wikipedias (including Hebrew) don't have permanent adminship and re-approve admins every once in a while, but it's probably a disastrous policy for Commons if it's the case. Anyway, as much as I am surprised that no top WLM organizer is a Commons admin (although there's clearly at least one admin on this mailing list), it's possible to get around this, although not easy. Lily has a good channel to the WMF and most of us are long-time users who know many others + many developers. The solution can be technical, and it can come from the WLM: perhaps a new user group that can only see historical revisions and restore without some of the other admin rights, perhaps an options to archive images that "need" to be deleted on groups of Commons policy, but aren't opposed by the foundation's legal team (might be a solution for URAA images as well), etc. I know that many in the community don't want any WMF interference, and the WMF wants to repair community ties—both are completely understandable. I don't want to suggest that we should interfere with these processes, but do think we can implement some kind of solution on the side. After all, WLM is a big project that costs a ton of resources. Just in terms of money, the WMF (or sometimes local donations) funds it with tens of thousands of dollars, directly or indirectly. It's therefore worth investing a little bit more to technically support projects like WLM. —Yan (Ynhockey). On Tue, Jan 31, 2017 at 10:57 AM, Federico Leva (Nemo) < nemowiki(a)gmail.com&gt; wrote: > WereSpielChequers, 31/01/2017 09:39: > >> I'm not an admin on commons, but where I am an admin it would be >> expected that you would check the history of a file before deleting it. >> > > It's expected on Commons too, see <https://commons.wikimedia.org > /wiki/Commons:Deletion_policy#Speedy_deletion>. > > When mistakes happen on Commons, we're sometimes too quick at > generalising. Currently Commons has issues with one or two rampant admins > who make semi-random deletions en masse (and even edit war on deletion > requests). Hopefully the situation is temporary. > > Nemo > >