Echoing Martin:

Week 5, year 2021 exists at 위키백과:질문방/2021년 제5주.

Note: The pages for Jan~Feb was created by someone @ Korean Wikipedia
Community, so I just created for the remainder of 2021.

All the 2020 items were created. The future (2022 onward) tasks which I am not sure.

about a month late, but creating march~december 2021 weekly pages.

Can you confirm this is about https://ca.wikimedia.org or somewhere else?

HTTPS is about HTTPS within Wikimedia sites. Removing.

@Sotiale was hit by this in zhwiki.

Account disabled.

From the description

However I'm concerned that something like this might be too ambitious for us at this time.

Deployed. (Thanks Martin)

hmm no, the syntax is {{YYYY}}년 제{{WW}}주, so it would become 2020년 제11주. so I guess the syntax is 'kowiki' => '위키백과:질문방/{{#time:o}}년 제{{#time:W}}주',.

This now requires 52 weekly pages, instead of 12 monthly pages, due to the community resolution at T254364: Change Korean Wikipedia archive model to weekly (Growth team not handling 254364 is blocking the actual move from the community, though.)

@kostajh is ^ sufficient or do you need something more?

Quite a few animals, train stations (specifically in Japan), cities in China (the mainland), and otherwise diverse topics. One "1946 (Year)" page.

Korean Wikipedia community has a requirement that any and all mentors must be eligible to run for an Request for Admin[1], due to not-enough-experienced editors offering bad answers to questions. I would expect anyone who can claim mentee to meet some higher-than-autoconfirmed criteria to claim mentee.

It might be that:

That is probably...

It might not be just password reset: I see insecure content warning on everywhere in wp-admin.php, but not on the actual blog.

From the task description

New format is 위키백과:질문방/YYYY년 제WW주. (when WW is below 10, there's no 0 preceding, so Week 9 is 제9주, not 제09주.)

In T254364#6280679, @revi wrote:

@MMiller_WMF: it's been decided by the time this was filed, waiting for WMF to change the logic.

@MMiller_WMF: it's been decided by the time this was filed, waiting for WMF to change the logic.

MacOS Mojave, FF 77.0.1 (stable), can reproduce.

Looks like abuselog also has this "collapse" thing. I want to ask for the same thing (no collapsing at all) - across the whole interface. Maybe give me some checkbox on prefs. I don't want to work-around all of the collapsible-boxes which continues to increase.

In T254649#6199347, @Beetstra wrote:

Should we not get rid of the word ‘spam’? It is a blocklist for external links, which are often, but certainly not only, spam

To simplify, I started single thread on VP, with a project summary at the top of the section (first subsection). I am sending out notifications to mentors via MassMessage in a short time.

TechBlog has slightly modified version of this.

Not really MS Windows cuz Can Reproduce on macOS.

Andre: Sayme's config:

PS: Removed comment below: Meant to edit the comment but unknowingly clicked" quote".

In T250468#6066499, @revi wrote:

T250468#6066466 is reproducible on kowiki. Also seen on Windows 10 Education (10.0.18363.778) Chrome C81.

T250468#6066466 is reproducible on kowiki. Also seen on Windows 10 Education (10.0.18363.778) Chrome C81.

For me...

In T237267#6061293, @JAnD wrote:

I understand that there is problem with confusing name, but the new
<syntaxhighlight> is more prone to typing error (syntaxghilight), longer and less understandable for non-english speakers.
Pitty, that new name is not shorter.

kowiki

• One user removed, last edit late March 2020. Was not responding to the Qs.
• Ellif did not get any question for a month. He did not reply for the last question asked - early March. Active otherwise. Probably a nudge?
• 유자차 seemed to be the one with the most Qs for last month or so. He replied to almost all questions, which is probably barnstar-worthy.

In T233608#6059742, @revi wrote:

It was fine, until I tried protect.py - P10991 and P10992, which seem to say I am not logged in when I execute protect.py but successfully logs me in via login.py.

It was fine, until I tried protect.py - P10991 and P10992, which seem to say I am not logged in when I execute protect.py but successfully logs me in via login.py.

Yeah, I was in the wrong branch/tag, thanks to naive (and unverified) thinking that there would be origin/stable branch. Git went to 2019 edition. My bad.

It seems it is indeed still happening.

For march (Revision 26164172):

In T242825#6000141, @revi wrote:

Same as in, like this.

Same as in, like this.

All Chorme User Agent will look same across devices. No mitigation is unacceptable from CU Point of View, and make CheckUser extension useless given the stake of Google Chorme's semi-monopoly.

In T242825#5994892, @revi wrote:

Tracking bug on Chromium side: https://crbug.com/955620

Tracking bug on Chromium side: https://crbug.com/955620

Pywikibot master (instead of stable, silly)

@chasemp Feel free to consider current list final for the time being. One stewards' confirmation is not closed but I think it's fine to go ahead (given current voting status).

It might be a good idea to have redundancy? I listed them anyways knowing they have acl*security via acl*security_volunteer and acl*security_developer , respectively.

We have a list of stewards who are stepping down (will update after saving this comment) but the final list (including those who failed our reconfirmation process) will be produced after March 7 (fastest date).