Jump to content

Talk:Steward requests/Global permissions

Add topic
From Meta, a Wikimedia project coordination wiki

Question

[edit]

Hey everyone, I hope you're all doing well.

Yesterday I sent this mail to one of the admins here, but thinking again, better make my inquiry "public" (so it's pretty much copy-paste of my mail). I wanted to inquire regarding the current process of reinstating the global interface permissions to Sophivorus. I know it's procedure (I myself, as an admin in es.wiki, understand these things), but I honestly don't understand why a user who has been using correctly and actively his permissions needs to go through a voting process allover again (and for the same period of time). I think the system should be programmed to remind users with temporary permissions some time before they expire, especially when they are about to be subjected to the same process from scratch. But that's water under the bridge,

Truth is that precisely now we are in the middle of developing a new set of forms for the Spanish Wikipedia, which I was planning to launch before the weekend, right now it doesn't seem possible anymore, but if we could at least save/make the most from the weekend itself. Obviously, this user will retain his permissions (all the votes are positive), so I'm not asking for the moon and stars here. My question is: Is there a possibility to at least reinstate his permissions on a temporary basis until the vote is concluded? After all, this is resulting to be just an unnecessary pause.

Thanks for your attention. Virum Mundi (talk) 09:16, 6 June 2024 (UTC)Reply

Per global interface editors page I believe Sophivorus could be granted indefinetly (see By default, appointment will be temporary, lasting any time up to a year. A longer appointment may be requested by long-term interface editors after several successful renewals. Requests for renewal can be done by placing a new request on Steward requests/Global permissions. This does not apply to paid employees of the Wikimedia Foundation.). A09|(pogovor) 09:19, 6 June 2024 (UTC)Reply
Re. automated reminders for expiring permissions. This could, of course, be raised as an enhancement request although it could probably be done by a bot. When permissions are granted, a log entry is written that includes the expiry date (e.g., "temporary, until 22:10, 19 July 2024" is written with the log entry). A bot could read the log entries and post a reminder to the User talk page at Meta. MarcGarver (talk) 09:26, 6 June 2024 (UTC)Reply
Generally, we do not grant GIE indefinitely. However, it is correct that it can be granted for a longer period of time if the permission has been held multiple times already; I would grant for two years here given the amount of times they have held the permissions on a one year basis without problems. GIE has, however, not been granted for longer than two-three years, as far as I know. EPIC (talk) 09:28, 6 June 2024 (UTC)Reply
I could look into writing that bot, but there are details I'll need to know. For example, is this going to be opt-in or opt-out? Leaderboard (talk) 16:59, 6 June 2024 (UTC)Reply
Holders of very advanced permissions are normally expected to monitor and maintain their renewals. @Virum Mundi you already commented once that this is not an issue on your project, so how exactly are you being impacted by this? — xaosflux Talk 13:41, 6 June 2024 (UTC)Reply
Thank you all for the input. @Xaosflux: I'm not sure I understand the question. The module is developed at a Meta level according to specifications based on the eswiki needs for the current project, so once he lost access, we can't move forward. As for the bot - this is exactly what I was referring to, but again, right now, for this specific project, it's water under the bridge. The question still stands. Thanks. Virum Mundi (talk) 15:07, 6 June 2024 (UTC)Reply
By "meta" do you mean here, on the metawiki? Because if so they should just apply for standard adminship here for standard maintenance activities. — xaosflux Talk 16:22, 6 June 2024 (UTC)Reply
Also see phab:T153817 which is a feature request to add access expiration notifications. — xaosflux Talk 16:24, 6 June 2024 (UTC)Reply
Hi all, sorry for not attending the whole day, got unsubscribed for some reason. Well, thank you for your input anyhow, too late, weekend's here and tomorrow the vote's due. @Xaosflux Got it, tnx. Cheers. Virum Mundi (talk) 21:47, 8 June 2024 (UTC)Reply

Enable 2FA

[edit]

Hi I'm not sure how the heck I'm supposed to accomplish this, I tried creating a template for 2FA users but I don't know if I managed to do anything at all. Please send help Andash1337 (talk) 13:06, 22 June 2024 (UTC)Reply

Your request is open. — xaosflux Talk 16:35, 22 June 2024 (UTC)Reply

Problems with bot or stewards? Community decides...

[edit]

I've noticed a problem where this bot does clerking on requests and will archive all requests that are marked as "done" regardless of whether the discussion has been completed or not. For example, this request I did was closed as "done" by Ajraddatz, but as you all can see there was a comment left by the steward to which a discussion could develop and after I left a reply to that comment the bot archived it before a response could be made or before the discussion could continue. I decided to revert the archive to allow the discussion to continue, but the bot only archived it again less than 15 minutes later. I would like to ping @Taavi to this discussion because the way I see it the two possible solutions to this problem are to modify the bot so that if replies are made to requests even after the request is marked as "done" there would still be a reasonable amount of time to allow for those replies to have a response to them from the time of the last comment made to the bot archival. The other possible solution is to educate the stewards who are clerking these requests that this is not the forum to be making comments that might open up discussions since these technical limitations of the current forum prevent the discussion from going any further once the steward has set the final status of the request as completed, but if they do make such comments [or want to continue to make such comments when finalizing requests,] then they should at least somehow alert/warn users the discussion can't possibly continue here and leave links for them to the appropriate talk pages or whatever. Huggums537(sign🖋️|📞talk) 23:24, 22 July 2024 (UTC)Reply