Tue, Jul 20
Mon, Jul 19
Sun, Jul 18
Mon, Jul 12
Thu, Jul 1
Jun 27 2021
@Zabe It seems that you have assigned the removal of flood from self to WIkisource, not Wikibooks. Also with that change you can safely remove add/remove flood from 'crats.
Jun 26 2021
Jun 19 2021
How about giving this to autoconfirmed users instead of creating an entirely new group with such limited scope?
Jun 6 2021
My response above was to MarcoAurelio, but will supply a response to JEumerus' question below.
Jun 5 2021
Jun 3 2021
May 29 2021
May 27 2021
You should also include WSL (by dual-booting the iMac/Macbook Air). That's a killer Windows 10 feature that I think is being underreported.
May 21 2021
May 19 2021
May 18 2021
May 13 2021
May 12 2021
Going bold, anyone can feel free to revert if people think my action is inappropriate. I can't, in good faith, allow a proposal that has not been discussed beforehand and raises so many questions.
Why is such a drastic change not widely announced? I've never heard of this plan before today. At the very least you have got to be informing every community with an active bureaucrat. I would support allowing bureaucrats to verify 2FA - that should be a no-brainer. Such a ridiculous proposal with no notice...
May 9 2021
For the record, it works properly when trying to rename the same user globally (returns an error saying that "you cannot rename yourself"). The problem is only local.
May 5 2021
May 3 2021
Some notes (as requested at #wikimedia-cloud)
May 1 2021
Not UBN level, especially when it's just a logo.
Apr 30 2021
Plus, how did https://sysop-it.wikipedia.org/w/index.php?title=Pagina_principale get approved in that case (in 2020) (https://phabricator.wikimedia.org/T256545)? I would argue that no WMF-based NDA information occurs there, and it does feel like differential treatment when compared to this request.
Apr 29 2021
The username of the first account on the private wiki should be Acagastya, with email firstname.lastname@example.org.
Some context: Wikinews requires a significant amount of off public wiki discussion for things like reviewing (they have a rigorous process before an article gets published; an actual workflow involves sharing private audio details with other reviewers during an interview). In the past they used to run an independent private wiki http://www.wikinewsie.org/wiki, which was operated by an admin whose heart has stopped for over 6 months. Now, when discussing on IRC, they've expressed a desire to host a private wiki on WMF servers. I've hence filed a request on their behalf, and @Acagastya can confirm if needed.
Apr 28 2021
Apr 27 2021
I don't see a problem personally; this user is clearly trusted.
Apr 19 2021
@Aklapper Sorry, saw this only now. I've merged them.
Mar 29 2021
Loginwiki is also a source - some stewards reported ~20000 IP checks just on that wiki per year, which if you ask me (as a non-steward) is ridiculously high.
Mar 24 2021
Mar 15 2021
Setting the same as in the (duplicated) task: https://phabricator.wikimedia.org/T103290
Mar 13 2021
Mar 8 2021
Feb 27 2021
Feb 4 2021
(Setting priority as high as indeed the lack of it is causing significant issues). Also see https://en.wikibooks.org/wiki/User_talk:QuiteUnusual#Blocking_using_abusefilter
Jan 24 2021
But then support for upgrading to intermediate, unsupported, versions must be provided? If I recall correctly, the current guidance is to "ignore" support requests that involve upgrading to an unsupported version. Would a patch be issued if a bug exists in an old version that prevents upgrading to a newer one?
Nov 27 2020
BTW: I should note that the usergroup for reviewer is actually "editor", not sure if that impacts @Urbanecm's patch. https://en.wikibooks.org/w/index.php?title=Special:ListUsers&group=editor
Nov 26 2020
Aug 28 2020
How about change the minimum from -2 LTS to -3 LTS? Considering that existing documentation encourages users with really old versions to upgrade, but it is indeed kind of ridiculous to expect a perfect upgrade from a version as old as 1.2. I think -3 LTS is a reasonable balance of giving users running old versions a one-path method to upgrade while keeping the scripts reasonable.
Aug 13 2020
How is this anywhere close to unbreak-now level?
Apr 4 2019
The issue no longer occurs to me. Waiting for a response from original poster (@Wang_Qiliang) before closing.
Apr 3 2019
It's happened twice for me in the last hour when trying to import just the latest revision (when trying to import everything, it times out as usual).