Notice that it's coming this week:

In T217273#5246397, @Elitre wrote:

SOmething tells me this is actually done... :D

In T214713#5246412, @Elitre wrote:

Also, the messaging has been posted on wiki since.

In T31928#5157608, @DonTrung wrote:

Odd, let's try again. @Keegan

I'm not sure where this feature request will go, but the user points out that snm, Inari Sami, likely does not work either and would like it to.

In T205484#5058493, @Elitre wrote:

So... was this related to 213553 or not? :) I'm trying to understand if I should send a satisfaction survey for the former or we want to wait until this is over to do it. Thanks!

Commons:Licensing already says 1924. I've posted notices about the UW update:

Testing page

Help page is started here: https://www.mediawiki.org/wiki/Help:File_statements

This release is taking place in two parts, so community testing periods are a week long instead of two weeks to accommodate.

In T218156#5019237, @DonTrung wrote:

Note that I use the Ecosia browser on Google Android, it isn't available for Microsoft Windows 10 Mobile. I don't often get this, but it occurs usually after uploading and publishing 3 (three) times without reloading the page. If I reload the page I don't get this issue after uploading another file 📁.

I'm unable to replicate this in Chrome mobile.

Survey has gone out.

These have been pushed and are live.

Mentioned at https://commons.wikimedia.org/wiki/Commons:Village_pump/Copyright#Captions/Structured_data_licensing

This is done

In T213462#4892496, @Yann wrote:

@Keegan As I said above, there is a very simple fix: force page reload after editing captions.

In T213462#4875706, @Yann wrote:

@Jdforrester-WMF Hotcat worked very well until the Captions were added. The issue could be solved forcing a page reload after editing Captions.

Logs: https://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2019-01-10

In T213040#4867765, @Tgr wrote:

The upload form tends to be heavily scripted even on normal wikis, and Commons have their homegrown UploadWizard alternative plus the system of abusing language codes for upload types... so it's definitely a big deal in the sense that it requires a bunch of gadgets to be re-tested, and requires a feature flag exposed as an URL parameter so people can meaningfully test it. I guess that should also alleviate concerns about what comes from where, because you can just check the old UI.

Is there a timeframe for pushing the conversion out?

In T212176#4830766, @Jdforrester-WMF wrote:

Oh, right, now I understand the concern you have. Yes, this different display is because the Commons community has customised its AbuseFilter error messages to look like this (though they look slightly worse given the context), and Beta Commons has a copy of these hacky templates and styling (whereas the Labs instance is running vanilla MediaWiki).

If you want to get rid of these, you'll need to convince the Commons community that that's a good idea, and either we build an entirely parallel set of messages for WBMI (eurgh) or the Commons community drops their current over-rides of these messages (for both WBMI and wikitext editing), which I imagine they'd be loathe to do.

Not sure where to go with this. @Keegan will definitely have views.

https://commons.wikimedia.org/wiki/Commons:Structured_data/Get_involved/Feedback_requests/Statements_2

https://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2018-11-01

No real workflow to follow here.

We did these things

In T182672#4644995, @Elitre wrote:

This task was about " the first six months of 2018" and 3 specific types of change.
Let's update accordingly? TY!

Village pump, email, MassMessage, and WIkidata updates left.

Consultation is up at https://commons.wikimedia.org/wiki/Commons:Structured_data/Get_involved/Feedback_requests/Search_prototype

@kaldari No translation, but the problem ran deeper. The wiki is dead with no identifiable active discussion space. They have no village pump, the Main Page talk page is a red link, and no other centralized communication center could be found. Usually when this happens I find the most active user and tell them, but ps.wikivoyage doesn't even have any active users. I think it's safe to say we can remove the extension without harming the community.

Log: