Stewards' noticeboard/Archives/2018-07

Steward requests/Global permissions

After a some time, I will go to the country where Wikimedia projects are forbidden. I need editing. Please make my request at SRGP. Marshmallych 12:58, 8 July 2018 (UTC)[]

This section was archived on a request by: --Alaa :)..! 10:06, 10 July 2018 (UTC)[]

bnwiki policy

Hello, i just added bnwiki's policy for Admin activity review/Local inactivity policies. --আফতাবুজ্জামান (talk) 18:17, 12 July 2018 (UTC)[]

@NahidSultan: কোন ভুল থাকলে ঠিক করুন। --আফতাবুজ্জামান (talk) 18:17, 12 July 2018 (UTC)[]

Creation of separate user group for editing sitewide CSS/JS

Hi all,

as you are probably aware, editing of sitewide CSS and JS will soon be restricted to a smaller user group, to make it harder to steal an account with the ability of deploying malicious scripts for all users. Discussion is at Creation of separate user group for editing sitewide CSS/JS; your input would be welcome. --Tgr (talk) 11:06, 9 July 2018 (UTC)[]

Hello again! Your feedback would be particularly welcome on Talk:Creation of separate user group for editing sitewide CSS/JS#Making assigning of techadmin membership central by default? as that would mean extra work for stewards. --Tgr (talk) 11:02, 18 July 2018 (UTC)[]

Regarding tech admins here on meta: I've opened a discussion at Meta:Babel#Tech_Admins, any feedback is welcome. — xaosflux Talk 20:36, 27 July 2018 (UTC)[]

The MediaWiki change is live now (that is, the interface-admin group exists everywhere; admins can still edit Javascript for four more weeks). I sent Creation of separate user group for editing sitewide CSS/JS/announcement 2 to all wikis; expect some requests for help where there are no local bureaucrats. Thanks in advance (and extra thanks to many of you who helped with the process so far)! --Tgr (talk) 13:18, 30 July 2018 (UTC)[]

Also it would be great if you could rename the global interface editor group to global interface admin (interface admin is the group name we ended up with, instead of techadmin), to avoid confusion. (Or keep both if anyone is interested in editing interface messages globally but not CSS/JS files. Seems unlikely though.) --Tgr (talk) 13:26, 30 July 2018 (UTC)[]
Now that I think about it, the code I have been using to make sure people still can edit CSS/JS during the migration period probably does not work for global interface editors (which have a different right management mechanism); someone might have to add editsitecsseditsitejs manually. Sorry for the confusion if that's the case. --Tgr (talk) 13:32, 30 July 2018 (UTC)[]
I've updated the permissions in the group. I'll hold off on a name change now because that'll be a lot of work, but if another steward has the time they can go for it. – Ajraddatz (talk) 15:53, 30 July 2018 (UTC)[]
Shall we also add editsite.* permissions to our group? As for the name change: it is not that simple as it requires sending a patch to the WikimediaMessages repository, etc. With time it can be done though. —MarcoAurelio (talk) 20:26, 30 July 2018 (UTC)[]

Just a heads-up that the permission change is now live. Thanks for all your help so far! --Tgr (talk) 12:25, 27 August 2018 (UTC)[]

modus operandi during migration

As far as I can recall, our modus operandi during the migration period was...

  1. bundle intadmin to sysop if the sysop is temp-sysop.
  2. Grant permanently if sysop is perma-sysop.

(Same for sysop:)

  1. If there are local crat, defer to them.
  2. Only revoke intadmin where there are no crats (Local crats can revoke intadmin) or emergency.

Any change necessary or can we live with this? — regards, Revi 12:40, 27 August 2018 (UTC)[]