@Af420 But the wordmark and the tagline are graphically different if compared to this and this other... We should have everything uniformed on all the skins! Don't you have the logo with the new wordmark and tagline included? Thanks

Hi @Pppery I can do this easily (also for wordmarks and taglines part), just want to know if there's community consensus for all the projects, or if someone should be notified! Thanks :)

In T360851#9950412, @Af420 wrote:

@Superpes15,
That’s true, but I undid all my edit on css and hopefully everything should be fine now.
Best regards
Khan

Hi @Af420, I didn't proceed with scheduling the deployment, because I noticed some problems on your logos. The current logo for old vector (the one you see here) was not enabled via a configuration change, but was added (perphaps by you?) on common.css!

Hi @Wargo, as I said I'll create a patch in the next hour (and I assigned myself the task, so this means that I'll working on it, and it's not nice to see other user creating patches without asking), but since you created a patch, should I create a patch, or do you want to continue with your change? Please note that you have to use git and install Python, tox, pngquant, zopflipng, svgo and rsvg-convert as explained in the readme and cannot perform a logo change via the gerrit web interface, thanks!

In T368712#9942491, @Nux wrote:

Sorry, this should be better:

<?php

$url_LogoSvg = "https://upload.wikimedia.org/wikipedia/commons/d/d1/Wikipedia_Administrator.svg";
$fn_LogoPng = fn($size) => "https://upload.wikimedia.org/wikipedia/commons/thumb/d/d1/Wikipedia_Administrator.svg/${size}px-Wikipedia_Administrator.svg.png";
$wgLogos = [
	'icon' => $url_LogoSvg,		// path to icon, the primary logo for Vector
	'1x' => $fn_LogoPng(135),		// path to 1x version
	'2x' => $fn_LogoPng(270),		// path to 2x version
	'svg' => $url_LogoSvg,		// path to svg-icon (should replace 1x/2x in most places)
];
$wgAppleTouchIcon = $fn_LogoPng(114);
$wgFavicon = $fn_LogoPng(48); // <link rel="icon" href="...">

If I'm reading the code correctly 'svg' should replace other icons in most cases (docs say something different, but e.g. SkinModule.php is using $logo['svg'] as default). Default size might be too big, but we can fix that in CSS, so not a problem.

Gotcha! Wili fix the file :D

Oh, thanks, it was already uploaded on commons! I'll add it to my patch asap :)

In T360851#9936239, @Af420 wrote:

@Superpes15,
Yeah this one is correct :)

@Af420

In T360851#9935960, @Af420 wrote:

@Superpes15,
Yes, even this one, which you're referring to, is a bit wrong. The Tagline consists of three words, which is correct, but there is no space between the last two words, and that is a grammatical mistake. I am going to correct that tagline with the help of my friend, and then I will create a new task.

By the way, should i create a new task? Or can it be done as a part of this task like they have done it on T319320?

@Af420 I mean this one (under the wordmark and, on the old skin, also under the logo) :D

In T366431#9930055, @Guseynaga wrote:

@Superpes15 I realized that I had to wait. But when the name is updated will it be reflected correctly? Indeed, in Vector (2022) the name VİKİPEDİÁ is now indicated incorrectly. It is necessary that it be written - VIKIPEDIJA Sərbəstə Ensiklopedijə.

In T360851#9930390, @Af420 wrote:

Hello @Superpes15, you can use the first one if u can fix the size, because the first one is more of a Pashto type of font. However, if the first one is too complicated and and takes a lot of time to fix it, then please use the second one, because anything would look better than current one

Could you please be more specific about the correct wordmark? Is this one or the other one?

Hi @Xaosflux, please note that the priority should be changed by whoever works on a task or based on the team/project, I already created a patch, which is ready, and I'll schedule it for deployment during the next week, so we can consider it as a normal priority (I'm just waiting for some days after the notification, and I usually don't use prioritization)! Thanks :P

Done!

Done!

Done! I also suggest you discuss about giving rollbacker some other flags (like "patrol" or "autopatrolled" or "markbodedits" that are usually given to RB) :)

In T366431#9925316, @Guseynaga wrote:

@Superpes15 Hello. The problem is unfortunately not resolved. I checked the reflection of the site (Appearance) in the settings. I'm using "Vector legacy (2010)" and the logo hasn't changed. In other versions also:

• “Vector legacy (2010)” reflects VİKİPEDİÁ Ozoda Ensiklopediá. And it should be - VIKIPEDIJA Sərbəstə Ensiklopedijə.
• MinervaNeue displays a logo with the name VİKİPEDİÁ instead of the desired VIKIPEDIJA
  • MonoBook also displays the old name in the logo. It should be - VIKIPEDIJA Sərbəstə Ensiklopedijə.
  • in Vector (2022) - there are changes here, but only in the second part of the phrase. The name VİKİPEDİÁ is incorrect. It should be written - VIKIPEDIJA Sərbəstə Ensiklopedijə.

In T366649#9908080, @Zabe wrote:

@Superpes15 Do you need local file uploads for this wiki?

In T363825#9908081, @Zabe wrote:

@Superpes15 Do you need local file uploads for this wiki?

I thought I had already commented in the subtask, but actually the comment was not published for some internet issue, for the commission work expected on these wikis it's necessary to have local upload enabled (if possible)!

In T367993#9907832, @Homo_ergaster wrote:

We have only discussed about Rollback flag, so it shouldn't have any additional flags.

Done for the logo/wordmark/tagline!
For the other requests, please post a new local discussion on wiki to reach a consensus and open a new task, thanks :)

Yep! It's redundant :) Please let me know when you have left a note on enwiki!

@Homo_ergaster What flags should the rollbacker usergroup have there? Patrol? Autopatrol? Rollback? Suppressredirect? Has it been discussed?

Ok, just for the record, the wordmark is here and the tagline is here. I'll do the patch asap. Thanks :)

In T363825#9901769, @Zabe wrote:

@Superpes15 Can you tell me what the first account should be and to which email I should send the initial password? :)

In T366649#9901793, @Zabe wrote:

@Superpes15 Can you tell me what the first account should be and to which email I should send the initial password? :)

In T366431#9895341, @Guseynaga wrote:

@Superpes15 Can you give an example of what you want to replace as well?

Since the new logo has a completely new wordmark (and tagline), do you also want an updated wordmark/tagline for new vector/mobile skins? I can do it easily, please let me know :)

Done! In a month I'll re-open the task and will restore the previous logo, thanks! Congratulations for the milestone :)

@Skalman For the next time you create a logo (please notify Blåmes about this), please remember that the size of the logo must be 135px in width.
If larger, the logos are automatically reduced to 135px in width (so basically it's not a problem). The point is, when they are reduced to 135px in width, the height must be equal to or less than 155px, otherwise the logos are not accepted :D
I had to fix and re-upload the SVG to commons, and create the svg for vector 2022 and mobile. This explains the delay in creating the patch! The deployment will take place in about 2 hours (I already scheduled it), and the temporary logos will be removed on 13 July, thanks.

In T364247#9879251, @Skalman wrote:

@Superpes15, yes, of course.

@Skalman May I add the same temporary logo (without wordmark and tagline) also for Vector 2022 skin? Thanks :)

In T364247#9873136, @Skalman wrote:

Ping @Superpes15

The file has some issue! I'll try to recreate it :)

We have to wait for 100K pages, but it seems that they are decreasing, so I set the task as stalled (waiting for the goal to be reached)!

In T364247#9809778, @GergesSH wrote:

If it is a temporary matter, add code css:

Done!

Please @Skalman let me know when you reach 100.000 entries :)

Please don't set the priority :) I'll do the patch asap!

Done!

It's for itwiki bot :P

In T363825#9757589, @Ladsgroup wrote:

See T361041: Create wikipedia-pl-sysop.wikimedia.org (was: sysop-pl.wikipedia.org). We will probably put it in wikipedia-it-arbcom.wikimedia.org instead.

In T363813#9757239, @Ladsgroup wrote:

In T363813#9757237, @Superpes15 wrote:

In T363813#9757203, @Ladsgroup wrote:

https://meta.wikimedia.org/wiki/Mailing_lists/Standardization says it should be wikipedia-it-arbcom@lists.wikimedia.org

I noticed and think you're right, but look at the other existing mailing lists, they are all like arbcom-XX. On itwiki they asked me exactly arbcom-it.

Probably obsolete and from the bygone era. New mailing lists shouldn't be created with the old problematic patterns (e.g with -l)

In T363813#9757203, @Ladsgroup wrote:

https://meta.wikimedia.org/wiki/Mailing_lists/Standardization says it should be wikipedia-it-arbcom@lists.wikimedia.org

Done!

In T359553#9612388, @sbassett wrote:

Accounts without Phab MFA enabled:

1. @Ajraddatz

Done! Yep, the correct right is editautopatrolprotected, I added this :) Please note also that bots have this flag by default!

Done!

Done!

In T355990#9531822, @Strainu wrote:

@Superpes15 the discussion has been opened for almost 2 weeks. Can we now move on and implement it? I can do the change if you don't have the time.

@Tchanders Many thanks for your assistance! This is really helpful imho :)

Hi @Niharika, these blocks are amazing and very useful in my opinion, as I have already told you. There is probably an underlying problem in understanding them for some users (at least this is what I noticed during testing). I've often seen admins blocking an action (for example "creation of pages") and a namespace at the same time, thinking that in this way they were blocking the creation of pages only on that namespace (while instead they blocked the "creation of pages" sitewide and any edit to that namespace). Now, I hope that soon we can get to partial blocks (on individual namespaces or pages) also with actions (moving/creating a page) because this would be really useful but, for now, imho the tech documentation should be clarified and this issue must be well explained. Thanks for your work :)

Oh, gotcha, thanks for your explanation!