James,
The reason why I have no intention of entering into private correspondence was made obvious last year based on your statements [1].
I have no wish to put myself at risk of becoming globally banned with no chance of appeal, and with no right to examine evidence, based on bad faith presumptions of one WMF employee who has this unelected power over volunteer contributors. I feel I have more protection from this happening by always sticking 100% to open public discussion rather than indulging your requests for private and unaccountable correspondence. I take the same approach with "banned users" who I also avoid any private correspondence with, out of fear of their use of free speech becoming grounds for a WMF ban against my accounts. Until this situation changes, I see no benefit to the community or myself in changing this approach taken to protect my interests.
Links 1. https://meta.wikimedia.org/wiki/User_talk:WMFOffice#Working_with_banned_user...
Fae
On 14 February 2017 at 23:44, James Alexander jalexander@wikimedia.org wrote:
On Tue, Feb 14, 2017 at 11:53 AM Fæ faewik@gmail.com wrote:
Usecases are appearing, thanks to whomever is intervening, though in a narrow column so hard to read.
Now I can read it, I see that it is out of date. As a test sample, I JethroBT (WMF) was granted m:admin rights in June, these expired by August 2016 and were eventually removed by a volunteer steward in October 2016. Though I JethroBT is an admin on meta right now, this was via a separate use case dated "42676", which I presume is November. Could the spreadsheet be properly reviewed and updated please, including reformatting the date field so it's easy to understand?
Pine - yes this process of "WMF Advanced Permissions" includes admin rights for any WMF website and so by-passes the community procedures.
Fae
Hi Fae,
As I’ve mentioned on previous occasions when you’ve brought up this spreadsheet on the mailing list, it occasionally breaks. That was the case here. If you send me a quick note if you see the issues, we can fix it, as we did today with the use case query (including make sure that it’s multiple columns again.) Pointing that out so it can be quickly fixed is much better done via a private poke that we'll see quickly rather than a public mailing list post that we may not see until after hours or until somebody lets us know about it. Obviously if we ignore your emails or refuse to fix it, then the math changes, and a post to this list makes more sense. I do not, however, think breakage (or overlooking notes about breakage) has been a frequent problem over the past couple years (though we have certainly had a couple breakages).
The public sheet is up to date to the internal version of the data (which is done automatically). However, the automated data collection is better at “adding new” than “removing old.” A member of the team does annual audits of the data to ensure that defunct entries are removed and that everything else matches reality. The time for the next one is coming up.
James
*James Alexander* Manager, Trust & Safety Wikimedia Foundation
PS: I also fixed the weird date thing you were seeing on some of them... not sure what caused that (was just a format display thing). _______________________________________________ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l New messages to: Wikimedia-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe