Page MenuHomePhabricator

Deployment of Vector 2022 to Meta-Wiki
Closed, DuplicatePublic1 Estimated Story Points

Description

  • Deploy Vector 2022 to this project.
  • Make sure @sgrabarczuk is aware of when the deployment is happening.
  • Projected deployment date: Tuesday 31st

Event Timeline

Jdlrobson triaged this task as Medium priority.Oct 23 2023, 5:55 PM
NBaca-WMF set the point value for this task to 1.Oct 24 2023, 4:58 PM
NBaca-WMF added subscribers: ovasileva, NBaca-WMF.

Estimated at one point, but we hadn't previously anticipated this work, may need to alter sprint commitments to accommodate (CC'ing @ovasileva for context ) or consider taking this on next week - revisit at Thursday Task Sync on Oct 26

There was no community consensus for this configuration change, why was it done?

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.

There was no community consensus for this configuration change, why was it done?

See https://www.mediawiki.org/wiki/Bug_management/Development_prioritization#Why_wasn't_I_consulted_about_these_changes%3F .
Please do not reopen tickets; it is possible to add a comment without changing task status. Thanks.

it is possible to add a comment without changing task status

Q2349101

it is possible to add a comment without changing task status

Q2349101

@Base could you please elaborate on your comment (looks like "save" was pressed too early?) Thanks!