In T341767#9011745, @Func wrote:

You should have brought up this during backport window in the IRC channel.

But it seems not needed since that namespace change only did localisation, Wikiquote is still the canonical namespace and accessible anyway.

Done!

Done!

Done!

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 :)

Many thanks @Anoop :3

Will create a patch and schedule it on 13 July!

In T340397#8983871, @MichalSobkowski wrote:

Thanks for corrections to my request. However, I am a little disappointed that such a simple change took so long. When will there be a chance to complete this task?

In T338826#8926231, @Malikxan wrote:

Additionally, the pages created by patrollers should be autopatrolled by default.

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!

In T338621#8920476, @Sciking wrote:

Yes, thanks, that's "Ciciarada" as originally requested. Thanks a lot!

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 :)

Ciao @Sciking :) Remember to delete 1 and 2 (the only 2 pages in the Purtaal ns) :) Obviously also the Descüssiun Purtaal namespace will be removed! Buon weekend :)

In T338468#8916922, @thcipriani wrote:

Now that @Superpes15 has NDA, they can attend a deployment training slot (note: use this form to set one up if you haven't coordinated with @ArielGlenn already).

After some training, we can get you deploying. Until then, let's hold this

@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

In T338468#8915005, @TheresNoTime wrote:

Either way, no harm in signing up for some training while you wait :-)

In T338468#8914550, @taavi wrote:

Is there any activity this Gerrit query does not see? In general I'd like to see deployers have experience with developing MediaWiki itself so they're familiar with it's internals (which helps reviewing patches and troubleshoot issues when things go wrong).

Ok, I'll do the change, and will schedule the deployment on 12 June :)

Done!

Done!

Done!
Per conoscenza: @Patafisik_WMF :)

Done!

In T337641#8887420, @Qaraqalpaqpan wrote:

In T337641#8887069, @Superpes15 wrote:

In T337641#8886952, @Qaraqalpaqpan wrote:

In T337641#8886860, @Superpes15 wrote:

Hi @Qaraqalpaqpan I suppose you also need the change for new 2022 Vector and mobile tagline! Am I right? :)

Dear @Superpes15, you are absolutely right, as some users are using Vector 2022 (especially administrators). So kindly support with new logo for new Vector 2022 and mobile tagline also. Thank you in advance.

Thanks! FTR tagline is here :)

Hi @Superpes15, thank you. Before I thought about adding tagline by myself to Commons, but after checking some other wikipedias, I relized, that mainly it was created by WMF. Also I worried, that maybe my file will not match to some size requests. So thank you for your effort.

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.

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!

In T337641#8886952, @Qaraqalpaqpan wrote:

In T337641#8886860, @Superpes15 wrote:

Hi @Qaraqalpaqpan I suppose you also need the change for new 2022 Vector and mobile tagline! Am I right? :)

Dear @Superpes15, you are absolutely right, as some users are using Vector 2022 (especially administrators). So kindly support with new logo for new Vector 2022 and mobile tagline also. Thank you in advance.

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.

Done!

Done!

@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

The discussion started a few hours ago, so I'll wait a few days, then I'l do the patch! Thanks :)

@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 :)

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 :)

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!

@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, I'm stupid, the extensions is disabled by default, in fact in the projects in which it's enabled, sysops have the sfsblock-bypass flag! Closing as invalid :)

Oh yep, indeed! It seemed strange to me that it wasn't assigned by default by the extension, but I hadn't checked :/

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!

Done! @herisson_grognon let me know if everything is there are any problems :)

Done!

Done!

In T335642#8815481, @herisson_grognon wrote:

Hi @Superpes15, in fact the change has already been discussed: https://fr.wikibooks.org/wiki/Wikilivres:Le_Bistro/2023#Uniformiser_le_nom_du_wiki_en_adoptant_uniquement_le_nom_et_le_logo_en_fran%C3%A7ais

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 :)

In T335208#8814909, @A09090091 wrote:

@Superpes15 I think there's unanimous consensus to proceed with this task as no opposing votes were given. Our community is also not that big, so ~10 votes is not common to see in RfCs.

Thanks <3

All should be done! @xavidegr Please let me know if there are any issues and many thanks for your patience :)

In T335208#8807226, @A09090091 wrote:

Opened a local discussion at Pod lipo.

In T331823#8810140, @xavidegr wrote:

For now, the project logo that should remain as it is, https://commons.wikimedia.org/wiki/File:Viccionari.svg , and not https://commons.wikimedia.org/wiki/File:Wiktionary-logo.svg. Cheers! :)

FTR: Local discussions:

1. Catalan Wikibooks;
2. Catalan Wikinews;
3. Catalan Wikiquote;
4. Catalan Wikisource;
5. Catalan Wiktionary.

Thanks (I'm doing the patches).

In T331823#8809947, @xavidegr wrote:

I think the last comment from @Vriullop is not legit, as the discussion is clearly still ongoing whether what should we do with the logo. Taking advantage of a ticket that was focused in the wordmark to quickly change the logo when the ticket is almost closed is not a nice move.

Especially when the "common" logo is not common at all and after 13 years of a partially failed voting many languages have refused it, readapted (ko), have voted against it, or simply have not to implement it (en, ru, eu, ku, de, etc.).

Therefore, the logo change should be placed on hold or even in another ticket.

In T331823#8809764, @Vriullop wrote:

As for Catalan Wiktionary, per discussion at https://ca.wiktionary.org/wiki/Viccionari:La_taverna#Petici%C3%B3_de_nou_canvi_de_logo_escrit_a_Phabricator, the proposed wordmark is https://commons.wikimedia.org/wiki/File:Wiktionary-wordmark-ca.svg with the common logo as https://commons.wikimedia.org/wiki/File:Wiktionary-logo.svg, not the current logo of Vector legacy.

In T331823#8807030, @Base wrote:

But really from my perspective this is a bug and regression introduced by WMF, rather than a site request </wmf bashing>

In T331823#8806594, @xavidegr wrote:

The notification to each village pump has been posted now for at least a week. In some projects, the few comments have been all positive towards the proposed change. Thank you.

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 :)

@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!

@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 :)

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 :)

In T331823#8784885, @xavidegr wrote:

I must say that I do not clearly see why should be a discussion rather than a simple notification.