User Details
- User Since
- Aug 4 2019, 8:28 PM (216 w, 5 d)
- Availability
- Available
- IRC Nick
- Superpes
- LDAP User
- Superpes15
- MediaWiki User
- Superpes15 [ Global Accounts ]
Sat, Sep 23
Jul 13 2023
Done!
Done!
Done!
Jul 12 2023
Hi @satdeep_gill! I'm sorry, but the request is not very clear for me :( First of all, I suppose that with "Validator" you mean "autopatroller", but I need to be sure before doing a change, so I need the name of the group. Then, which user rights does this usergroup need (only autopatrol?)? Sysop can add users to this group, but who can remove user from this group? Also, I don't understand what the following means: "Many users are incorrectly marking pages as Validated and that gives a wrong impression that so many pages have been validated but actually it is a misrepresentation". Thanks for the understanding and for your patience!
I'll schedule the patch in some hours. Please note that patrolmarks is not needed for patroller usergroup (because this right is included into patrol right). Thanks!
Hi @Bennylin I only see the discussion about the name change in your link! Could you please open a new thread? Thanks!
Hi @Bennylin I only see the discussion about the name change in your link! Could you please open a new thread? Thanks!
Hi @Ninjastrikers! Don't you prefer that patroller have also autopatrol right? Do you want to keep the two flags separate? Thanks :)
Jul 11 2023
Many thanks @Anoop :3
Jul 10 2023
Will create a patch and schedule it on 13 July!
Jul 2 2023
Jun 30 2023
Jun 13 2023
Jun 12 2023
Hello @Malikxan. Which rights should this group have? I see that you already have the rollbacker group with only the rb flag. Thanks!
Done for now! Will reopen it in a month! :)
Fatto!
Jun 10 2023
Oh, are you sure is it "Cicicarada" and not "Ciciarada"? I'll use Ciciarada in the doubt, since you mentioned it also in the local discussion and it's the current "discussion:" translation in the other namespace :)
Jun 9 2023
Jun 8 2023
@Qaraqalpaqpan It's likely a cache issue! Logo was changed also for legacy (2010) vector - as you can see here - and I see the correct one even on Special:Preferences (and saw it during the test before the deploy)! Probably it need some time - surely less than a week - to purge, if was not manually purged during the deploy :) You can also remove the .css config, no problem :D
Ok, I'll do the change, and will schedule the deployment on 12 June :)
Done!
Done!
Done!
Per conoscenza: @Patafisik_WMF :)
Done!
Yep, agree, there is no reason to use these tones and assume bad faith here. Stjn's request makes sense, but it is much more logical, given that protection currently concerns groups with autoreview, to create the editautoreviewprotected level. If there is any change in the future, we will fix it. Thanks!
P.S. Sorry for the delay, but I've been busy in these days, I scheduled the patch deployment in a few minutes.
Jun 2 2023
I can do the patch, but I'll wait a bit for some sysadmins opinions, per this page. Thanks.
Hi @Kyykaarme. FTR The following groups have the autoreview flag on fiwiki: autoreview, bot, editor, reviewer and sysop, so I'll add them to the allowed usergroups. Thanks!
May 29 2023
Hi @Qaraqalpaqpan I suppose you also need the change for new 2022 Vector and mobile tagline! Am I right? :)
Yep, I understand. We also have in a lot of project "editautopatrolprotected", but it's not bound to AP usergroup. In case, we can add extendedconfirmed protection in the future, but imho we should use it only when the extendedconfirmed group exists (otherwise it could create some confusion, and currently the project doesn't need an exclusive protection to autoreview)! Also, if in the future you will add extendedconfirmed usergroup, well, it's a bit confusing! So, for now, imho it's logical and also better to add "editautoreviewprotected" :)
It's easy, we already have "editautoreviewprotected" (which is used for groups which have this flag and not only for the autoreview usergroup), we shouldn't call it extendedconfirmed :) I'll do this!
Hi, If needed I can start updating the logos in the various projects in an alphabetical order! Also the list should be updated, because in the last months we added a lot of logos/wordmarks/taglines. Thanks.
May 22 2023
Done!
Done!
May 21 2023
@Qaraqalpaqpan The labels in the extension are already translated as "Qaralama beti" ("sandbox") and "Siziń qaralama betińiz" ("your sandbox")! Please let me know if something needs to be changed! Thanks :)
@SummerKrut Sure! I’m happy to do this change as soon as possible :) Thanks
May 15 2023
The discussion started a few hours ago, so I'll wait a few days, then I'l do the patch! Thanks :)
May 14 2023
@colt_browning Unfortunately the previous discussion clearly asked for some precise flags, and I don't see abusefilter-view-private and abusefilter-log-private there. I think you should start a new local discussion, as per policy we cannot do a configuration change without a local discussion/consensus. Please consider also that the discussion you linked is not recent and may not reflect the current consensus. It would be useful to know if also ruwiki ArbCom has an internal consensus and need for this. So, my suggestion is to start a discussion and come back here after a week, then we'll do the change! Thanks for your understanding :)
May 11 2023
Uhm, I'm still not convinced that extended confirmed is the best solution, according to my previous reply, but I'm pinging some sysadmins here, so they can give us their opinions! @Urbanecm @TheresNoTime @Zabe :)
May 10 2023
Done!
Hello @SatyamMishra, since the projects doesn't have a large number of users like enwiki, and since you want that sysops will handle the flag, wouldn't it better to create "autopatrolled" usergroup and an "only autopatrolled" protection level? Then, we can also let only autopatrolled moving the pages, editing protected page, and so on, letting sysops to handle the flag!
May 8 2023
@hubaishan The size of the logo uploaded on Commons was wrong, and I already fixed it. To comply with HD rules, a logo should be 135px wide x max. 155px tall (so it can be less tall). I'll upload the patch soon, thanks :)
Oh yep, indeed! It seemed strange to me that it wasn't assigned by default by the extension, but I hadn't checked :/
May 7 2023
May 3 2023
Are you referring to the infobox? Please specify this in the title of the task, because it may seem that the tagline and wordmark are not seen in the logo at the top left, and that doesn't seem to be the case!
May 1 2023
Done! @herisson_grognon let me know if everything is there are any problems :)
Done!
Done!
Apr 30 2023
Hi @herisson_grognon! Please read how to request a wiki configuration change. We need a local discussion on the village pump to change the logo (and remember to specify if this is needed for Vector legacy or Vector 2022 skin). After a week, even if there is no reply, I'll do the patch! Thanks for your understanding :)
Apr 29 2023
Apr 28 2023
Thanks <3
Apr 27 2023
All should be done! @xavidegr Please let me know if there are any issues and many thanks for your patience :)
FTR: Local discussions:
Thanks (I'm doing the patches).
Apr 26 2023
Apr 24 2023
Done! Also NamespaceDupes was run :)
Done!
@Sjoerddebruin Luckily everything should be automated. See NamespaceDupes.php on mediawiki. I will schedule the patch for the late backport (or for tomorrow if I can't this evening)! Thanks :)
Apr 21 2023
@TadejM While I think there's no problem in adding it for a new content namespace (for example draft - while on Wikipedia namespace a discussion is needed imho), you should discuss it on a relevant page or in the village pump, per policy. You linked a discussion on the user talk. Thanks for your understanding!
Apr 20 2023
@Zabe The problem is the size, the script resize the logos to 135px wide, and, to comply with the HD rule, logos should be 135px wide x max. 155px tall. In the first case the logo is resized to 135px x 163px, while the guwwikinews logo is resized to 135px x 191px (so they cannot be used because they're taller). I had the same problem for trwikiquote (see T334732) ! I'm creating a new versions of both logos and will try to use them :)
Apr 17 2023
Done! @MustafaMVC Now the Vector legacy logo is the new HD version and shouldn't be white borders anymore! Let me know if something is wrong :)