Talk:Tech/Server switch

Archives /Archive

Things about 2021 should be in 2021

Why don't create Tech/Server switch 2021 or some thing instead of just adding things here? The title would be misleading; And it's definitely not appropriate to just overwrite old archive with new content, right? —— Eric Liu_（Talk） 06:17, 30 June 2021 (UTC)

The plan is to rename the page and all sub pages to remove the date. To be done soon! Trizek (WMF) (talk) 14:20, 30 June 2021 (UTC)

So is this rename/history preserving plan ongoing? It seems that no subpages had been created yet. —— Eric Liu_（Talk） 07:57, 8 September 2021 (UTC)

The page has already been renamed to be date-agnostic. We keep history of previous server switches in the page history itself. This way, we don't need to copy all the content at each switch and ask translators to redo the work at every event. Trizek (WMF) (talk) 14:18, 8 September 2021 (UTC)

Date (2021 switch back)

@Trizek (WMF): This newsletter states that the server switch will be on September 13, and thus there will be a code freeze that week (i.e. Sep 13–17). However, the train blocker task for next week (Sep 6–10) is closed as “declined”, while the the train blocker task for the week after (Sep 13–17) is open. Based on these tasks, I’d guess the server switch is next week, not the week after. So when will it happen? —Tacsipacsi (talk) 00:00, 1 September 2021 (UTC)

Thank you for your question, Tacsipacsi. The schedule set the priority for the server switch. I'm asking. Trizek (WMF) (talk) 11:22, 1 September 2021 (UTC)

Tacsipacsi, hopefully you spotted this change. I just updated the message accordingly. Thank you very much! Trizek (WMF) (talk) 16:18, 1 September 2021 (UTC)

Proper translated category

Should'nt it be like [[Category:Wikimedia Foundation technical notices{{#translation:}}]] instead of just not showing in translated version? —— Eric Liu_（Talk） 08:01, 8 September 2021 (UTC)

Typo

@Trizek (WMF) there's an error in the text. It says "March 1 2022" bit it should be 2023. --Mannivu · ✉ 20:38, 17 February 2023 (UTC)

Fixed, thank you! Quiddity (WMF) (talk) 20:58, 17 February 2023 (UTC)

Is the date format OK?

I don't know about other languages, but for Finnish the current date format doesn't work, and I don't know how to fix it. The basic format would be "1. maaliskuuta (2023)", but I see "1 maaliskuun (2023)" which doesn't make sense. kyykaarme (talk) 15:47, 28 February 2023 (UTC)

Thank you for reporting it, @Kyykaarme, as I can fix it for next messages.

Is the format D. M (Y) valid for all days, or do you have some exceptions?

Trizek (WMF) (talk) 16:51, 28 February 2023 (UTC)

I did some spying and from the Tech news/fi code I found that it should be j. F"ta" Y. kyykaarme (talk) 18:40, 2 March 2023 (UTC)

Thank you @Kyykaarme. I made the changes, let me know if it is better now. Trizek (WMF) (talk) 16:57, 7 March 2023 (UTC)

Why on Bot Requests

Why Your wiki will be in read-only soon was distributed on Bot Requests or Bots? Bean49 (talk) 10:16, 21 April 2023 (UTC)

I believe it is sent to Distribution list/Bots so that bot-operators are not surprised by the read-only time, if they don't read the announcements elsewhere (Tech News, Village Pump). From a glance at the page-history, the Huwiki target was changed a few months ago. I hope that helps. Quiddity (WMF) (talk) 20:31, 21 April 2023 (UTC)

But it seems that this time it was posted only on the Bots discussion page, at least in my wiki (Finnish WP). Previously it was posted both in the News and in the Bots discussion page, and now only in the Bots page. I never even noticed that it was posted in the Bots discussion page because it's not on my watchlist. Where could one change the target page for this particular message? IMO it's unnecessary to post it in two places and the News page is not ideal, the Tech discussion would be better. kyykaarme (talk) 16:16, 23 April 2023 (UTC)

The target list is chosen by the person who distributes the list, you cannot directly change that (only the lists themselves). Looking at the logs, it was distributed to Distribution list/Bots and Distribution list/Non-Technical Village Pumps distribution list, but not to Distribution list/Technical Village Pumps distribution list (which contains the technical VP of fiwiki) – maybe it’s still not too late to send it to the latter as well? (By the way, the huwiki change was definitely for the worth, the noticeboard is what’s actually read by people.) —Tacsipacsi (talk) 23:13, 23 April 2023 (UTC)

Thanks for the information! I'll wait in case the message "appears" in an appropriate forum and if not, I'll post it myself manually, probably later today. kyykaarme (talk) 06:00, 24 April 2023 (UTC)

We expect the code deployments to happen as[sic] any other week

Are you sure this is "as", and not "at"? Just want to confirm, hehe. Im Zayk (talk) 14:10, 20 September 2023 (UTC)

@Im Zayk, "We expect the code deployments to happen as any other week" is a short for "We expect the code deployments to happen [the same way] as any other week". :)

Trizek_(WMF) (talk) 15:59, 20 September 2023 (UTC)

Oh! Noted; I'll revised my translation ASAP. Thanks for the clarification! Im Zayk (talk) 21:49, 21 September 2023 (UTC)

Data centre switch

Can't this be made seamless? Rich Farmbrough. 22:30 21 September 2024 (GMT). 22:30, 21 September 2024 (UTC)

I've been told that it is the ultimate goal, but it takes time and effort. Trizek_(WMF) (talk) 15:00, 23 September 2024 (UTC)

Ok thank you

The wikis are turning read–only mode i know that a few wikis are turning read–only mode. Jjsjsjshhs (talk) 22:19, 30 September 2024 (UTC)

timef:

Now that {{#timef:…}} is available, it could simplify how we display dates in the message, with less parameters to take into account. {{#timefl:…}} could be used to show local time.

If anyone wants to suggest an update to the message using this new parser function, please be my guest. :)

Trizek_(WMF) (talk) 12:29, 17 October 2024 (UTC)

I’m not sure if it’s a good idea. {{#timef:...}} was designed to work in isolation, that is, outside of sentences (in tables, lists etc.). For example, the German translation used in this message is am fünfundzwanzigsten September, but am {{#timef:2024-09-25|date|de}} would probably produce am fünfundzwanzigster September (if the output wasn’t numeric, hiding this difference). The Hungarian translation is szeptember 25-én, but {{#timef:...}} would put a dot after the day, which is needed in isolation but incorrect when the date is agglutinated. While these two languages wouldn’t be affected (in German, the difference is hidden due to the numeric output, and Hungarian cannot use traditional {{#time:...}} either due to its complicated agglutination rules), other languages may have similar problems. —Tacsipacsi (talk) 23:21, 17 October 2024 (UTC)

Thank you for the initial exploration.

Let's test how it goes with {{#timef:2024-09-25|pretty|lang}} (I use languages we both speak):

• de: 25 September
• hu: szeptember 25
• fr: 25 septembre
• es: 25 septiembre

Current system:

All traffic will switch on '''{{#time:j xg|2024-09-25|{{TRANSLATIONLANGUAGE}}}}'''.

I get:

• All traffic will switch on 25 September.
• de: Der gesamte Datenverkehr wird am 25 September.
• hu: Az átállás 25 szeptember történik meg.
  • For the latter, it was overridden to add name the day (as it is possible); the result is:

  Az átállás szeptember 25-én, szerdán történik meg.

• fr: Le trafic sera basculé le 25 septembre.
• es: Todo el tráfico cambiará al nuevo centro de datos el 25 septiembre.

Using All traffic will switch on '''{{#timef:2024-09-25|pretty|{{TRANSLATIONLANGUAGE}}}}'''., I get:

• All traffic will switch on 25 September.
• de: Der gesamte Datenverkehr wird am 25 September.
• hu: Az átállás szeptember 25 történik meg. (I reused the former sentence.)
• fr: Le trafic sera basculé le 25 septembre.
• es: Todo el tráfico cambiará al nuevo centro de datos el 25 septiembre.

It seems to be close. I note that for Hungarian it is not the same as the translation you provided, but it seems to be better with timef than it is with time.

Since the previous server switch, I consider replacing the current 3-parameters system ({{#time:$defaultformat|$date|$format_language_code}}) with one parameter ($1) that would encapsulate the time magicword and the parameters. This is not directly related to this conversation. The reason is that I'm concerned on not being able to get or update the translation in the right way for several languages. Only two options would be made available: use the parameter ($1) or replace the full sentence like there (updating the message will be up to the translators). Trizek_(WMF) (talk) 12:34, 18 October 2024 (UTC)

Please, do not use "pretty" at all, because it's broken in too many languages. IKhitron (talk) 12:24, 20 October 2024 (UTC)

@IKhitron, I guess this is related to T223772#10225457 and subsequent comments? Trizek_(WMF) (talk) 12:50, 21 October 2024 (UTC)

Yes, and also starting from phab:T223772#10037953 and phab:T223772#10210207. IKhitron (talk) 16:41, 21 October 2024 (UTC)

Thanks. Let's follow up on the task. Trizek_(WMF) (talk) 18:05, 21 October 2024 (UTC)