User talk:SGrabarczuk (WMF)/sandbox
Community Wishlist Survey
ᓱᖁᓯᖅᐹ ᐃᓚ
The 2021 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on 30 ᓄᕕᒻᐳᕆ, or comment on other proposals to help make them better. The communities will vote on the proposals between 8 ᑎᓯᒻᐳᕆ and 21 ᑎᓯᒻᐳᕆ.
The Community Tech team is focused on tools for experienced Wikimedia editors. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!
18:57, 19 ᓄᕕᒻᐳᕆ 2020 (UTC)
04:23, 20 ᓄᕕᒻᐳᕆ 2020 (UTC)
نظرسنجی فهرست آرزوهای اجتماع ویکی‌مدیا در سال ۲۰۲۱ اکنون باز شده‌است! این نظرسنجی روالی را فراهم می‌کند تا اجتماعات پروژه‌های ویکی‌مدیا تصمیم بگیرند که اعضای تیم فنی اجتماع در سال آینده روی چه چیزهایی کار کنند. ما همه را ترغیب می‌کنیم که پیشنهادهایشان را تا پیش از مهلت 30 ᓄᕕᒻᐳᕆ ثبت کنند یا این که روی پیشنهادهای دیگر نظر بدهند و به بهبودشان کمک کنند. اجتماعات ویکی‌مدیا سپس از 8 ᑎᓯᒻᐳᕆ تا 21 ᑎᓯᒻᐳᕆ به پیشنهادهای مختلف رأی خواهند داد.
اعضای تیم فنی اجتماع تمرکزشان بر ابزارهایی است که برای ویرایشگران مجرب ویکی‌مدیا ساخته می‌شوند. !شما می‌توانید پیشنهادهایی را در هر زبانی بنویسید و ما آن‌ها را برای شما ترجمه خواهیم کرد. متشکریم و منتظر دیدن پیشنهادهای شما هستیم!
04:26, 20 ᓄᕕᒻᐳᕆ 2020 (UTC)
A request for translation
ᓱᖁᓯᖅᐹ ᐃᓚ Hello
I'm reaching out to you because you have translated a part of the Community Wishlist Survey documentation. I need your help again. I'd be grateful if you helped with the following:
- Invitation for voting - this is essential and should be translated as soon as possible
- CentralNotice banner - this has been translated to many languages and just a review may be enough
- All the rest of the related documentation - might be good to get this translated, but is of the lowest priority.
I've also prepared a Translation hub with colourful tables to coordinate the translations. You might find that useful.
That's it! If you have any questions, please ask!
I believe your contributions will make it possible for more people to vote and get their wishes granted. Thank you in advance!
06:06, 3 ᑎᓯᒻᐳᕆ 2020 (UTC)
Community Wishlist Survey 2021
ᓱᖁᓯᖅᐹ ᐃᓚ We invite all registered users to vote on the 2021 Community Wishlist Survey. You can vote from now until 21 December for as many different wishes as you want.
In the Survey, wishes for new and improved tools for experienced editors are collected. After the voting, we will do our best to grant your wishes. We will start with the most popular ones.
We, the Community Tech, are one of the Wikimedia Foundation teams. We create and improve editing and wiki moderation tools. What we work on is decided based on results of the Community Wishlist Survey. Once a year, you can submit wishes. After two weeks, you can vote on the ones that you're most interested in. Next, we choose wishes from the survey to work on. Some of the wishes may be granted by volunteer developers or other teams.
We are waiting for your votes. Thank you!
14:53, 11 ᑎᓯᒻᐳᕆ 2020 (UTC)
Technical maintenance planed
ᓱᖁᓯᖅᐹ ᐃᓚA maintenance operation will be performed tomorrow morning UTC time (Wednesday 17th at 07:00 AM UTC).
It will impact all wikis and is supposed to last up to one minute.
During this time, new translations may fail, and Notifications may not be delivered. For more details about the operation and on all impacted services, please check on Phabricator.
A banner will be displayed 30 minutes before the operation.
Thank you, SGrabarczuk (WMF) 17:39, 16 ᕕᐳᐊᕆ 2021 (UTC)
A request for translation
ᓱᖁᓯᖅᐹ ᐃᓚHello!
Thank you for your translation of the instruction of the Desktop Improvements prototype. Next week, we would like to post a banner inviting your community to test the prototype and give feedback. We only need to make one more step - translate three short lines of text in that banner. Would you be able to do this?
Thanks a lot for your support, as usual!
Read-only next Tuesday
ᓱᖁᓯᖅᐹ ᐃᓚA maintenance operation will be performed on Tuesday 22nd at 05:00 AM UTC.
It is supposed to last a few minutes. During this time, you will not be able to save your edits.
For more details about the operation and on all impacted services, please check on Phabricator.
A banner will be displayed 30 minutes before the operation.
Please help making your community aware of this maintenance operation. SGrabarczuk (WMF) 17:33, 16 ᔪᓂ 2021 (UTC)
Server switch
ᓱᖁᓯᖅᐹ ᐃᓚRead this message in another language • Please help translate to your language
The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for up to an hour on Tuesday, 29 June 2021. The test will start at 14:00 UTC (07:00 PDT, 10:00 EDT, 15:00 WEST/BST, 16:00 CEST, 19:30 IST, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday 30 June).
- If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- There will be code freezes for the week of June 28. Non-essential code deployments will not happen.
01:15, 27 ᔪᓂ 2021 (UTC)
Wikisource Satisfaction Survey 2021
ᓱᖁᓯᖅᐹ ᐃᓚHello!
Apologies for writing in English. Please help translate to your language
In the past year, there has been a lot of changes to Wikisource features and tools. This was done by the Community Tech team at the Wikimedia Foundation, grantees funded by the Foundation or through projects like Google Summer of Code. We would like to understand what you feel about the changes. Tell us what you think about such tools as the Wikisource Pagelist Widget or the new Ebook Export tool.
Take the survey in English, French, Spanish, Polish, Hindi or Punjabi. The deadline is 25th July 2021.
This survey will be conducted via a third-party service, which may subject it to additional terms. For more information on privacy and data-handling, see the survey privacy statement (English, Spanish, French, Polish, Hindi and Punjabi).
If you prefer to send your answers via email, copy the text of the survey and send to sgill@wikimedia.org.
If you have any questions or feedback about the survey, write to me at sgill@wikimedia.org.
Thank you!
Read-only tomorrow
ᓱᖁᓯᖅᐹ ᐃᓚHello!
A maintenance operation will be performed tomorrow, Tuesday 10th August, at 05:00 UTC.
During this time, saving edits will not be possible. It will impact 17 wikis, and is supposed to last a few minutes. For more details about the operation, please check on Phabricator.
A banner will be displayed 30 minutes before the operation.
Please help making your community aware of this. Thank you! SGrabarczuk (WMF) 01:49, 9 ᐊᐅᒍᔅ 2021 (UTC)
Update on the OCR Improvements
ᓱᖁᓯᖅᐹ ᐃᓚHello! The OCR Improvements are complete. We, the Community Tech team, are grateful for your feedback from the beginning to the last stage when we were finalizing the interface.
Engine improvements
ᓱᖁᓯᖅᐹ ᐃᓚ
- Reliability
Prior to our work, the OCR tools were separate gadgets. We have added "Wikimedia OCR." It is available under one icon inside the toolbar on all Wikisource wikis. This tool supports two other OCR tools, Tesseract and Google OCR. We expect these tools to be more stable. We will maintain Wikimedia OCR.
The gadgets will remain available. The communities will have sovereignty over when to enable or disable these.
- Speed
Prior to this work, transcription would take upwards of 40 seconds. Our improvements average a transcription time under 4 seconds.
Advanced Tools improvements
ᓱᖁᓯᖅᐹ ᐃᓚ
- Multiple-language support
Documents with multiple languages can be transcribed in a new way.
- Open the Advanced Options
- Select the Languages (optional) field
- Search for and enter the languages in order of prevalence in the document.
- Cropping tool / Multi-column support
We have included a Cropper tool. It allows to select regions to transcribe on pages with complicated layouts.
- Discoverability and accessibility of OCR
We have added an interface for new users. It is pulsating blue dots over the new icon in the toolbar. The new interface explains what OCR means and what transcription means in Wikisource.
We believe that you will do even more great things because of these changes. We also hope to see you at our 2022 Wishlist Survey. Thanks you again for all your opinions and support.
Please share your feedback on the project talk page!
NRodriguez (WMF) and SGrabarczuk (WMF) 01:49, 19 ᐊᐅᒍᔅ 2021 (UTC)
The 2022 Community Wishlist Survey will happen in January
ᓱᖁᓯᖅᐹ ᐃᓚHello everyone,
We hope all of you are as well and safe as possible during these trying times! We wanted to share some news about a change to the Community Wishlist Survey 2022. We would like to hear your opinions as well.
Summary:
We will be running the Community Wishlist Survey 2022 in January 2022. We need more time to work on the 2021 wishes. We also need time to prepare some changes to the Wishlist 2022. In the meantime, you can use a dedicated sandbox to leave early ideas for the 2022 wishes.
Proposing and wish-fulfillment will happen during the same year
ᓱᖁᓯᖅᐹ ᐃᓚIn the past, the Community Tech team has run the Community Wishlist Survey for the following year in November of the prior year. For example, we ran the Wishlist for 2021 in November 2020. That worked well a few years ago. At that time, we used to start working on the Wishlist soon after the results of the voting were published.
However, in 2021, there was a delay between the voting and the time when we could start working on the new wishes. Until July 2021, we were working on wishes from the Wishlist for 2020.
We hope having the Wishlist 2022 in January 2022 will be more intuitive. This will also give us time to fulfill more wishes from the 2021 Wishlist.
Encouraging wider participation from historically excluded communities
ᓱᖁᓯᖅᐹ ᐃᓚWe are thinking how to make the Wishlist easier to participate in. We want to support more translations, and encourage under-resourced communities to be more active. We would like to have some time to make these changes.
A new space to talk to us about priorities and wishes not granted yet
ᓱᖁᓯᖅᐹ ᐃᓚWe will have gone 365 days without a Wishlist. We encourage you to approach us. We hope to hear from you in the talk page, but we also hope to see you at our bi-monthly Talk to Us meetings! These will be hosted at two different times friendly to time zones around the globe.
We will begin our first meeting September 15th at 23:00 UTC. More details about the agenda and format coming soon!
Brainstorm and draft proposals before the proposal phase
ᓱᖁᓯᖅᐹ ᐃᓚIf you have early ideas for wishes, you can use the new Community Wishlist Survey sandbox. This way, you will not forget about these before January 2022. You will be able to come back and refine your ideas. Remember, edits in the sandbox don't count as wishes!
Feedback
ᓱᖁᓯᖅᐹ ᐃᓚ- What should we do to improve the Wishlist pages?
- How would you like to use our new sandbox?
- What, if any, risks do you foresee in our decision to change the date of the Wishlist 2022?
- What will help more people participate in the Wishlist 2022?
Answer on the talk page (in any language you prefer) or at our Talk to Us meetings.
The 2022 Community Wishlist Survey will happen in January
ᓱᖁᓯᖅᐹ ᐃᓚHello everyone,
We hope all of you are as well and safe as possible during these trying times! We wanted to share some news about a change to the Community Wishlist Survey 2022. We would like to hear your opinions as well.
Summary:
We will be running the Community Wishlist Survey 2022 in January 2022. We need more time to work on the 2021 wishes. We also need time to prepare some changes to the Wishlist 2022. In the meantime, you can use a dedicated sandbox to leave early ideas for the 2022 wishes.
Proposing and wish-fulfillment will happen during the same year
ᓱᖁᓯᖅᐹ ᐃᓚIn the past, the Community Tech team has run the Community Wishlist Survey for the following year in November of the prior year. For example, we ran the Wishlist for 2021 in November 2020. That worked well a few years ago. At that time, we used to start working on the Wishlist soon after the results of the voting were published.
However, in 2021, there was a delay between the voting and the time when we could start working on the new wishes. Until July 2021, we were working on wishes from the Wishlist for 2020.
We hope having the Wishlist 2022 in January 2022 will be more intuitive. This will also give us time to fulfill more wishes from the 2021 Wishlist.
Encouraging wider participation from historically excluded communities
ᓱᖁᓯᖅᐹ ᐃᓚWe are thinking how to make the Wishlist easier to participate in. We want to support more translations, and encourage under-resourced communities to be more active. We would like to have some time to make these changes.
A new space to talk to us about priorities and wishes not granted yet
ᓱᖁᓯᖅᐹ ᐃᓚWe will have gone 365 days without a Wishlist. We encourage you to approach us. We hope to hear from you in the talk page, but we also hope to see you at our bi-monthly Talk to Us meetings! These will be hosted at two different times friendly to time zones around the globe.
We will begin our first meeting September 15th at 23:00 UTC. More details about the agenda and format coming soon!
Brainstorm and draft proposals before the proposal phase
ᓱᖁᓯᖅᐹ ᐃᓚIf you have early ideas for wishes, you can use the new Community Wishlist Survey sandbox. This way, you will not forget about these before January 2022. You will be able to come back and refine your ideas. Remember, edits in the sandbox don't count as wishes!
Feedback
ᓱᖁᓯᖅᐹ ᐃᓚ- What should we do to improve the Wishlist pages?
- How would you like to use our new sandbox?
- What, if any, risks do you foresee in our decision to change the date of the Wishlist 2022?
- What will help more people participate in the Wishlist 2022?
Answer on the talk page (in any language you prefer) or at our Talk to Us meetings.
Server switch
ᓱᖁᓯᖅᐹ ᐃᓚRead this message in another language • Please help translate to your language
The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
They will switch all traffic back to the primary data center on Tuesday, 14 September 2021.
Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
- You will not be able to edit for up to an hour on Tuesday, 14 September 2021. The test will start at 14:00 UTC (07:00 PDT, 10:00 EDT, 15:00 WEST/BST, 16:00 CEST, 19:30 IST, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday, 15 September).
- If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Other effects:
- Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
- We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
Talk to the Community Tech
ᓱᖁᓯᖅᐹ ᐃᓚ
Read this message in another language • Please help translate to your language
Hello!
As we have recently announced, we, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on September 15th, 23:00 UTC on Zoom, and will last an hour. Click here to join.
Agenda
- How we prioritize the wishes to be granted
- Why we decided to change the date from November 2021 to January 2022
- Update on the disambiguation and the real-time preview wishes
- Questions and answers
Format
The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (first three points in the agenda) will be given in English.
We can answer questions asked in English, French, Polish, and Spanish. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.
Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.
Invitation link
- Join online
- Meeting ID: 898 2861 5390
- One tap mobile
- +16465588656,,89828615390# US (New York)
- +16699006833,,89828615390# US (San Jose)
- Dial by your location
See you! SGrabarczuk (WMF) (ᐅᖃᓕᒪᔪᖅ) 02:58, 11 ᓯᑎᒻᐳᕆ 2021 (UTC)
בואו נדבר על שיפורי תצוגת מחשב
ᓱᖁᓯᖅᐹ ᐃᓚבואו נדבר על שיפורי תצוגת מחשב
ᓱᖁᓯᖅᐹ ᐃᓚSoon, mass IP blocking may happen
ᓱᖁᓯᖅᐹ ᐃᓚHello!
Communities typically block edits from IP addresses that obscure individual users. Usually, it has been about “open proxies” or virtual private networks (VPNs). Now, there's a new Apple service called iCloud Private Relay that obscures the IP addresses of desktop and mobile users of the Safari browser.
As Apple users adopt this new service, we estimate that 3-5% of all logged-in and logged-out editors will have these obscured IP addresses. If we don't change anything, they may be blocked within a few months. This wiki may be severely affected. A lot of people editing here use the Safari browser. Next, other browser providers may do the same. The problem will grow.
The communities, users with advanced MediaWiki permissions, the Wikimedia Foundation and others need to work together. We all need to decide how the security of the wikis can be maintained. At the same time, the pathways to editing should remain open for all good-faith participants.
Read more on Apple iCloud Private Relay. Answer the questions and comment on its talk page.
Thank you!
Talk to the Community Tech
ᓱᖁᓯᖅᐹ ᐃᓚ
Read this message in another language
Hello
We, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on 27 ᐅᒃᑐᐳᕆ (ᐱᖓᔪᐊ), 14:30 UTC on Zoom, and will last an hour. Click here to join.
Agenda
- Become a Community Wishlist Survey Ambassador. Help us spread the word about the CWS in your community.
- Update on the disambiguation and the real-time preview wishes
- Questions and answers
Format
The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (all points in the agenda except for the questions and answers) will be given in English.
We can answer questions asked in English, French, Polish, and Spanish. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.
Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.
Invitation link
- Join online
- Meeting ID: 83847343544
- Dial by your location
We hope to see you! SGrabarczuk (WMF) (talk) 12:32, 21 ᐅᒃᑐᐳᕆ 2021 (UTC)
Talk to the Community Tech
ᓱᖁᓯᖅᐹ ᐃᓚ
Read this message in another language
Hello
We, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on 27 ᐅᒃᑐᐳᕆ (ᐱᖓᔪᐊ), 14:30 UTC on Zoom, and will last an hour. Click here to join.
Agenda
- Become a Community Wishlist Survey Ambassador. Help us spread the word about the CWS in your community.
- Update on the disambiguation and the real-time preview wishes
- Questions and answers
Format
The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (all points in the agenda except for the questions and answers) will be given in English.
We can answer questions asked in English, French, Polish, Spanish, German, and Italian. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.
Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.
Invitation link
- Join online
- Meeting ID: 83847343544
- Dial by your location
We hope to see you! SGrabarczuk (WMF) (talk) 22:43, 22 ᐅᒃᑐᐳᕆ 2021 (UTC)
Talk to the Community Tech
ᓱᖁᓯᖅᐹ ᐃᓚ Hello!
We, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on 30 ᓄᕕᒻᐳᕆ (Tuesday), 17:00 UTC on Zoom, and will last an hour. Click here to join.
Agenda
- Changes to the Community Wishlist Survey 2022. Help us decide.
- Become a Community Wishlist Survey Ambassador. Help us spread the word about the CWS in your community.
- Questions and answers
Format
The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (all points in the agenda except for the questions and answers) will be given in English.
We can answer questions asked in English, French, Polish, Spanish, German, and Italian. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to sgrabarczuk@wikimedia.org.
Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.
Invitation link
- Join online
- Meeting ID: 82035401393
- Dial by your location
We hope to see you! SGrabarczuk (WMF) (talk) 19:59, 26 ᓄᕕᒻᐳᕆ 2021 (UTC)
Community Wishlist Survey 2022 is coming. Help us!
ᓱᖁᓯᖅᐹ ᐃᓚThe Community Wishlist Survey 2022 starts in less than two weeks (Monday 10 January 2022, 18:00 UTC). We, the team organizing the Survey, need your help.
Only you can make the difference
How many people will hear and read about the Survey in their language? How many will decide to participate? Will there be enough of you to vote for a change you would like to see? It all depends on you, volunteers.
Why are we asking?
- We have improved the documentation. It's easier to use and less textual. This will be for nothing if the new documentation will only be in English.
- Thousands of volunteers haven't participated in the Survey yet. We'd like to improve that, too. Three years ago, 1387 people participated. Last year, there were 1773 of them. We hope that in the upcoming edition, there will be even more. You are better than us in contacting Wikimedians outside of wikis. We have prepared some images to share. More to come.
What is the Community Wishlist Survey?
It's an annual survey that allows contributors to the Wikimedia projects to propose and vote for tools and platform improvements. Long years of experience in editing or technical skills are not required.
Thanks, and be safe and successful in 2022! SGrabarczuk (WMF) (talk) 03:07, 29 ᑎᓯᒻᐳᕆ 2021 (UTC)
Feedback on Vector (2022) conversation
ᓱᖁᓯᖅᐹ ᐃᓚ
Hello! As a member of WikiProject Usability, I wanted to draw your attention to a conversation currently underway on WP:VPR (see the beginning of the discussion) around adopting Vector 2022 as the new default skin.
The Web team at the Wikimedia Foundation has been working on Vector 2022 for the past three years, collaborating with the English Wikipedia community as well as other wikis to ensure that the skin performs better qualitatively and quantitatively for readers and communities than the previous Vector skin. The goal of the new skin is to create a more welcoming and easier to use experience for readers and editors across the wiki. For more details, see our new FAQ.
For the past couple of months, we have collected thoughts from the English Wikipedia community on what changes need to be made to the skin prior to it being considered ready for deployment. Our next step would be to start an RfC to assess whether the community considers Vedtor 2022 ready.
Prior to the beginning of the RfC, we wanted to draw your attention to the current conversation and encourage your feedback on the skin.
Thank you, OVasileva (WMF), SGrabarczuk (WMF) (talk) 12:25, 25 ᐊᐅᒍᔅ 2022 (UTC)
The Vector 2022 skin as the default in two weeks?
ᓱᖁᓯᖅᐹ ᐃᓚ
Hello. I'm writing on behalf of the Wikimedia Foundation Web team. In two weeks, we would like to make the Vector 2022 skin the default on this wiki.
We have been working on it for the past three years. So far, it has been the default on more than 30 wikis, including sister projects, all accounting for more than 1 billion pageviews per month. On average 87% of active logged-in users of those wikis use Vector 2022.
It would become the default for all logged-out users, and also all logged-in users who currently use Vector legacy. Logged-in users can at any time switch to any other skins. No changes are expected for users of these skins.
- Top of an article
-
Vector legacy (current default) -
Vector 2022
- A section of an article
-
Vector legacy (current default) -
Vector 2022
About the skin
ᓱᖁᓯᖅᐹ ᐃᓚ[Why is a change necessary] The current default skin meets the needs of the readers and editors as these were 13 years ago. Since then, new users have begun using Wikimedia projects. The old Vector doesn't meet their needs.
[Objective] The objective for the new skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It draws inspiration from previous requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. We reduced PHP code in Wikimedia deployed skins by 75%. The project has also focused on making it easier to support gadgets and use APIs.
[Changes and test results] The skin introduces a series of changes that improve readability and usability. The new skin does not remove any functionality currently available on the Vector skin.
- The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
- The new table of contents makes it easier to navigate to different sections. Readers and editors jumped to different sections of the page 50% more than with the old table of contents. It also looks a bit different on talk pages.
- The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the wikis we tested on.
- The skin does not negatively affect pageviews, edit rates, or account creation. There is evidence of increases in pageviews and account creation across partner communities.
[Try it out] Try out the new skin by going to the appearance tab in your preferences and selecting Vector 2022 from the list of skins.
How can editors change and customize this skin?
ᓱᖁᓯᖅᐹ ᐃᓚIt's possible to configure and personalize our changes. We support volunteers who create new gadgets and user scripts. Check out our repository for a list of currently available customizations, or add your own.
Our plan
ᓱᖁᓯᖅᐹ ᐃᓚIf no large concerns are raised, we plan on deploying in the week of October 3, 2022. If your community would like to request more time to discuss the changes, hit the button and write to us. We can adjust the calendar.
Also, if you'd like ask our team anything, if you have questions, concerns, or additional thoughts, please ping me here or write on the talk page of the project. We will also gladly answer! See our FAQ. Thank you! SGrabarczuk (WMF) (talk) 04:05, 22 ᓯᑎᒻᐳᕆ 2022 (UTC)
Update on Vector 2022
ᓱᖁᓯᖅᐹ ᐃᓚ
Hey everyone. I'm sorry for not communicating in your language. I'm writing on behalf of the Web team working on the new skin, Vector 2022.
We wanted to apologize for the delays in the deployment of Vector 2022. We know many of you are waiting for this eagerly. We have been delaying the deployment because we have been working on the logos. It has taken us more time than originally expected. Once the logos are ready, we will let you know the exact date of deployment. We are planning for either the next (more likely) or the following week. If your wiki doesn't currently have a localized logo, we encourage you to reach out to us and we can help make one.
We invite you to get involved in the project. Contact us if you have any questions or need any help, particularly with the compatibility of gadgets and user scripts. SGrabarczuk (WMF) (talk) 23:14, 19 ᐅᒃᑐᐳᕆ 2022 (UTC)
Desktop improvements. A new change is coming!
ᓱᖁᓯᖅᐹ ᐃᓚ
(Hello! Please help translate to your language)
Next week (the week of February 6), the Wikimedia Foundation Web team will move some links from the side menu ("sidebar") to the other side of the screen.
This will make it easier to intuitively use all the links and tools within our interface. The table of contents will also appear a bit higher up the screen because the sidebar will be shorter. The latter change would mostly be interesting for editors. This is because readers use the sidebar much more rarely.
Why we are changing this
The interface does not distinguish between the links and tools that are relevant to the website and the links and tools that are relevant to a single page. Main page, random page, recent changes, are in the first group. What links here, related changes, cite this page, belong to the second one. This mix is confusing to new readers. Also new editors are not familiar with what each link does. Mixing these groups makes it less likely for people to explore these tools naturally.
This change also addresses the concern for the location of the table of contents. Previously, some editors using an earlier version of Vector 2022 told us that because the table of contents appeared below the sidebar, it was placed too much down below the page. After this change, the sidebar will be shorter and thus will shift the table of contents further up in the page. Also, this change will reduce the white space on the page by using more of the space for the display of tools.
You can learn more about the page tools feature and the Desktop Improvements project on MediaWiki.org.
Gadgets' compatibility
Technically skilled editors may need to update some gadgets and user scripts. Some of these might become redundant or obsolete. We provide support for users who would like to maintain the compatibility. Please explore this section of our documentation for more information on gadget compatibility.
Let's work together
- Subscribe to our newsletter to receive regular updates.
- Share your ideas and ask questions on our talk page.
- Create a task on Phabricator and add
Desktop Improvements (Vector 2022)tag or write to us if you notice a bug. - Translate the documentation on MediaWiki.org.
Thank you! SGrabarczuk (WMF) (ᐅᖃᓕᒪᔪᖅ) 20:47, 3 ᕕᐳᐊᕆ 2023 (UTC)
Tech/Server switch
ᓱᖁᓯᖅᐹ ᐃᓚTemporary accounts for unregistered editors
ᓱᖁᓯᖅᐹ ᐃᓚRead this in your language • Please help translate to your language • Please tell other users about these changes
In 2024, editors who have not registered an account will automatically begin using temporary accounts. These editors are sometimes called "IP editors" because the IP address is displayed in the page history.
The Trust and Safety Product team gave a presentation at Wikimania about this change. You can watch it on YouTube.
There is more information at m:IP Editing: Privacy Enhancement and Abuse Mitigation.
The Vector 2022 skin as the default in two weeks?
ᓱᖁᓯᖅᐹ ᐃᓚRead this in your language • Please help translate to your language • Please tell other users about these changes
Hello. I'm writing on behalf of the Wikimedia Foundation Web team. In two weeks, we would like to make the Vector 2022 skin the default on this wiki.
If you prefer keeping the current skin select "Vector legacy (2010)" on the appearance tab of the global preferences and save the change. We encourage you to give the new skin a try, though.
Since I last came to you with this question, many things have changed. The skin is now the default on most Wikipedias, and all logos are done! We have also made some tweaks in the skin itself. Below is the text I've sent to you once, but I'm sending it again, just slightly edited, for those who haven't seen it.
If you know what this is about, jump straight to the section "Our plan":
It would become the default for all logged-out users, and also all logged-in users who currently use Vector legacy as a local (but not global) preference. Logged-in users can at any time switch to any other skin. No changes are expected for these skins.
- Top of an article
-
Vector legacy (current default) -
Vector 2022
- A section of an article
-
Vector legacy (current default) -
Vector 2022
About the skin
ᓱᖁᓯᖅᐹ ᐃᓚ [Why is a change necessary] When the current default skin was created, it reflected the needs of the readers and editors as these were 14 years ago. Since then, new users have begun using the Internet and Wikimedia projects in different ways. The old Vector does not meet their needs.
[Objective] The objective for the Vector 2022 skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It introduces a series of changes that aim to improve problems new and existing readers and editors were having with the old skin. It draws inspiration from previous user requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. The PHP code in the other available skins has been reduced by 75%. The project has also focused on making it easier to support gadgets and use APIs.
[Changes in a nutshell] The skin introduces changes that improve readability and usability. The new skin does not remove any functionality currently available on the Vector skin.
- The limited width and pin-able menus allow to adjust the interface to the screen size, and focus on editing or reading. Logged-in and logged-out users may use a toggle button to keep the full width, though.
- The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
- The new table of contents makes it easier to navigate to different sections. Readers and editors jump to different sections of the page 50% more than with the old table of contents. It also looks a bit different on talk pages.
- The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the tested wikis.
- The skin does not negatively affect pageviews, edit rates, or account creation. There is evidence of increases in pageviews and account creation across partner communities.
[Customize this skin] It's possible to configure and personalize our changes. We support volunteers who create new gadgets and user scripts. Check out the repository for a list of currently available customizations and changes, or add your own.
Our plan
ᓱᖁᓯᖅᐹ ᐃᓚIf no large concerns are raised, we plan on deploying on 31 October. If you'd like to ask our team anything, if you have questions, concerns, or additional thoughts, please comment in any language. If this is the first comment to my message, make sure to ping me. We will gladly answer! Also, check out our FAQ. Thank you!
The Vector 2022 skin as the default in three weeks?
ᓱᖁᓯᖅᐹ ᐃᓚRead this in your language • Please help translate to your language • Please tell other users about these changes
Hello. I'm writing on behalf of the Wikimedia Foundation Web team. In two weeks, we would like to make the Vector 2022 skin the default on this wiki.
If you prefer keeping the current skin select "Vector legacy (2010)" on the appearance tab of the global preferences and save the change. We encourage you to give the new skin a try, though.
Since I last came to you with this question, many things have changed. The skin is now the default on most Wikipedias, and all logos are done! We have also made some tweaks in the skin itself. Below is the text I've sent to you once, but I'm sending it again, just slightly edited, for those who haven't seen it.
If you know what this is about, jump straight to the section "Our plan":
It would become the default for all logged-out users, and also all logged-in users who currently use Vector legacy as a local (but not global) preference. Logged-in users can at any time switch to any other skin. No changes are expected for these skins.
- Top of an article
-
Vector legacy (current default)
-
Vector 2022
- A section of an article
-
Vector legacy (current default)
-
Vector 2022
About the skin
ᓱᖁᓯᖅᐹ ᐃᓚ [Why is a change necessary] When the current default skin was created, it reflected the needs of the readers and editors as these were 14 years ago. Since then, new users have begun using the Internet and Wikimedia projects in different ways. The old Vector does not meet their needs.
[Objective] The objective for the Vector 2022 skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It introduces a series of changes that aim to improve problems new and existing readers and editors were having with the old skin. It draws inspiration from previous user requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. The PHP code in the other available skins has been reduced by 75%. The project has also focused on making it easier to support gadgets and use APIs.
[Changes in a nutshell] The skin introduces changes that improve readability and usability. The new skin does not remove any functionality currently available on the Vector skin.
- The limited width and pin-able menus allow to adjust the interface to the screen size, and focus on editing or reading. Logged-in and logged-out users may use a toggle button to keep the full width, though.
- The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
- The new table of contents makes it easier to navigate to different sections. Readers and editors jump to different sections of the page 50% more than with the old table of contents. It also looks a bit different on talk pages.
- The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the tested wikis.
- The skin does not negatively affect pageviews, edit rates, or account creation. There is evidence of increases in pageviews and account creation across partner communities.
[Customize this skin] It's possible to configure and personalize our changes. We support volunteers who create new gadgets and user scripts. Check out the repository for a list of currently available customizations and changes, or add your own.
Our plan
ᓱᖁᓯᖅᐹ ᐃᓚIf no large concerns are raised, we plan on deploying on 14 November. If you'd like to ask our team anything, if you have questions, concerns, or additional thoughts, please comment in any language. If this is the first comment to my message, make sure to ping me. We will gladly answer! Also, check out our FAQ. Thank you! SGrabarczuk (WMF) (ᐅᖃᓕᒪᔪᖅ) 01:07, 26 ᐅᒃᑐᐳᕆ 2023 (UTC)