CentralNotice/Request/Picture of the Year 2022

Picture of the Year 2022

edit
Central Notice Settings

What is the campaign duration?
  • R1: 17 April 2023 → 1 May 2023
  • R2: 4 May 2023 → 18 May 2023
Which projects will you be targeting?
  • all
What languages will you be targeting?
  • all
Do you wish to show banners to Logged In users, Anonymous Users or Both? Do you want to target users with a specific number of edits or average monthly?
  • Logged In users only

What countries will your campaign target?

  • all

Banner/Campaign Diet:

  • To be determined by Central Notice admin

What is the purpose of the campaign? How will you measure the success of the campaign?

edit
Description - As every year, to announce the Picture of the Year vote. This is the seventeenth edition of POTY. See c:Commons:Picture of the Year.

Metrics -

What banner(s) will you use? What will be your landing page?

edit
Banners - Please reuse the banners from last year, see CentralNotice/Request/Picture of the Year 2021

Landing Page - c:Commons:Picture of the Year/2022
edit
Type of grant -

Link to grant -

Discussion

edit

There were comments from @Ciell: last year about adjusting the image credit and fixing Vector 2022 compatibility issues, which we definitely have enough time this year to fix, but I personally would need pointers on what/how to fix them. Legoktm (talk) 01:06, 4 April 2023 (UTC)[reply]

Central Notice admin comments

edit
Hi, just wanted to add the note that phabricator:T308614 is still open and users cannot review the new texts via the translation extension, and there are a lot of new translations still waiting. Because of this bug only CN admins, stewrads and Meta admins can push new translations to live: the Dutch banner for instance, still showed the old POTY 2020 text. @DerHexer: what is the best approach, check all translations one by one in g-translate and Yandex, assume that translations are correct and push them all to live manually, or to do nothing, only manually push the translations we are familiar with ourselves? Ciell (talk) 15:34, 19 April 2023 (UTC)[reply]
@Ciell: I usually go through Special:MessageGroupStats and approve all at 100 % where the letters fit to the language. ;D Mistakes will be corrected by other readers. Therefore, regular checks make most sense. However, for this banner, I don't see new translations. Am I in the wrong page? Best, —DerHexer (Talk) 15:51, 19 April 2023 (UTC)[reply]
@DerHexer interesting, because the live banners direct me to this one through the "Help with translations!" link in the banner. Ciell (talk) 15:57, 19 April 2023 (UTC)[reply]
Cloning banners is a nightmare. It causes more bad than good, and almost always breaks translations. Thanks, I will go through these. Best, —DerHexer (Talk) 15:59, 19 April 2023 (UTC)[reply]
It's the other way around: The banner was leading to the wrong translation link, I've fixed this now. As this is the same text, I will just copy over the translations and publish them. Best, —DerHexer (Talk) 16:02, 19 April 2023 (UTC)[reply]
Done. Will be on the road from Thursday to Sunday. —DerHexer (Talk) 16:41, 19 April 2023 (UTC)[reply]
Thanks!! Ciell (talk) 16:56, 19 April 2023 (UTC)[reply]
Thank you both <3
Would it be simpler if we had a generic redirect like "Commons:Picture of the Year/Vote" that we change on-wiki every year instead of needing to change in the banners? Legoktm (talk) 16:56, 19 April 2023 (UTC)[reply]
The problem came up when I cloned Seddon’s version of the banner where he thankfully had fixed CSS errors. By doing this, translations from the original version weren’t copied to the new place (I should have cloned the original banner and should have overwritten with Seddon’s source code). Caused additional translation work which could have been copied more easily. Additionally, I didn’t fix the hack we introduced to guide people from banners directly to the target language by using wgPageContentLanguage in project where the banner is displayed. Within this a JavaScript hack, the target translation special page didn’t lead to the right place. I should have tested and fixed it. So all just mistakes on my side and not really anything you could have easified. Landing pages haven’t been an issue here, and I usually don’t forget to update these (but as this has happened, I always ask people to check the preview). By now, I think everything is alright. Best, —DerHexer (Talk) 17:46, 19 April 2023 (UTC)[reply]