Change 969971 had a related patch set uploaded (by Kimberly Sarabia; author: Kimberly Sarabia):

[operations/mediawiki-config@master] Deploy vector 2022 to non-English Wikibooks, etc

https://gerrit.wikimedia.org/r/969971

I did write a quick bulk removal command in Python. Is there any desire to have something like this be an option in mediawiki-config or not worth it/out of scope? Thanks cc: @Jdlrobson @Jdrewniak

This is handy script but would likely need to be ported to PHP for the MediaWiki config repo. Probably not in scope for now as this doesn't happen frequently enough.

Change 969971 merged by jenkins-bot:

[operations/mediawiki-config@master] Deploy vector 2022 to non-English Wikibooks, etc

https://gerrit.wikimedia.org/r/969971

Mentioned in SAL (#wikimedia-operations) [2023-10-31T20:03:08Z] <samtar@deploy2002> Started scap: Backport for [[gerrit:969971|Deploy vector 2022 to non-English Wikibooks, etc (T349544)]]

Mentioned in SAL (#wikimedia-operations) [2023-10-31T20:04:29Z] <samtar@deploy2002> samtar and ksarabia: Backport for [[gerrit:969971|Deploy vector 2022 to non-English Wikibooks, etc (T349544)]] synced to the testservers (https://wikitech.wikimedia.org/wiki/Mwdebug)

Mentioned in SAL (#wikimedia-operations) [2023-10-31T20:13:59Z] <samtar@deploy2002> Finished scap: Backport for [[gerrit:969971|Deploy vector 2022 to non-English Wikibooks, etc (T349544)]] (duration: 10m 51s)

I insist on having the deployment rolled back from Ukrainian Wikiquote and Wikinews where I am an (interface) admin. There was an explicit NO to the proposal https://uk.wikinews.org/wiki/Вікіновини:Майдан#The_Vector_2022_skin_as_the_default_in_two_weeks?_ , https://uk.wikiquote.org/wiki/Вікіцитати:Кнайпа/Архів/2022#The_Vector_2022_skin_as_the_default_in_two_weeks?_ in both cases, nothing has changed since the previous proposal, but unfortunately what you, WMF guys, decided to do is to go ad nauseam and use attrition against the community: you posted the same wall of English text to the wiki where only few people understand English again and used no reply to it as an excuse to deploy this. If this is not rolled back I intent to use my Interface admin rights to roll back the changes with a hack, as as it is mentioned neither I nor other community members have the capacity to deal with all the changes that need to be done to adapt to the new skin.

As the other ticket was merged in I will also copy my comment from there,

I found that there was a notification on https://meta.wikimedia.org/wiki/Meta:Babel#The_Vector_2022_skin_as_the_default_in_two_weeks?_ . That is no place for such major sitewide change, it should have been an RFC instead. Babel is saturated with all different kinds of newsletters and nobody discusses important configuration changes there. Here is an example of RfC to introduce a configuration change: https://meta.wikimedia.org/wiki/Meta:Requests_for_comment/Adding_a_local_rollbacker_flag_or_alternatives . It would have been highly inappropriate to just write "we are having this change done in two weeks unless anyone notices this discussion and says no" on Babel. Please stop disregarding community processes and undeploy the change.

I will also reply to @Aklapper's comment wrt https://www.mediawiki.org/wiki/Bug_management/Development_prioritization#Why_wasn't_I_consulted_about_these_changes%3F — I do not expect WMF to consult with the community about any small change that is being done. Of course that is not feasible. But default skin change is a major thing that effects editing and reading for the whole community. The way it was done is not an appropriate process.

@Base - thank you for reaching out to us. I'm sorry to hear that the deployment was a surprise to you - it was not our intention to hide or obscure the news of deployment in any way. In fact, we were going for the opposite - trying to find the pages on each wiki where we would have the best chances of spreading the news and starting a discussion with communities.

We want to continue the conversation around the deployment on-wiki with you and other members of these communities and would be interested in hearing more thoughts before deciding on any subsequent course of action. We initially posted on the Meta:Babel as we thought that was the best general forum for conversation, but if there's pages that will have a better change at getting more people involved - we'd like to start a conversation there instead. Do you have any suggestions on what a more appropriate page or pages would be?

@ovasileva, if you lack people in your team who are familiar with community processes I suggest you post a job posting for Wikimedians to apply as consultants. I am not sure why volunteers should be spending their valuable time to facilitate you in your paid work comprising pushing an unwanted product to the communities.

That said, when it comes to Meta-Wiki I have already written what is a better process. When it comes to ukwn and ukwq the place where you've posted is correct, but you have already posted there a year ago and got a reply. In bigger Wikimedia projects posting the same thread over and over again is directly against the policies and is a sure way to get banned. In smaller wikis such policy is usually not codified but the same principles apply.