Wikiqısebend:Portalê cemati
![]() Arşiv |
---|
- en: Requests for the bot flag should be made on this page. This wiki uses the standard bot policy, and allows global bots and automatic approval of certain types of bots. Other bots should apply below, and then request access from a steward if there is no objection.
Read-only next Tuesday[bıvurne]
A maintenance operation will be performed on Tuesday 22nd at 05:00 AM UTC.
It is supposed to last a few minutes and will affect 31 wikis. During this time, you will not be able to save your edits. For more details, please check on Phabricator.
A banner will be displayed 30 minutes before the operation.
Please help making your community aware of this. SGrabarczuk (WMF) 20:36, 16 Heziran 2021 (+03)
Request for adminship[bıvurne]
I request administrator access on diq.wiktionary:
- Language Code: diq
- Meta-Wiki Request Link: m:Requests for permissions
- Local User Page: User:Mirzali
-- Mirzali (mesac) 20:36, 12 Temuz 2021 (+03)
Support I support him. He is a native speaker, has good knowledge on the main dialects and on the standard written language, also about the technical issues of Wikipedia. --Asmen (mesac) 19:07, 14 Temuz 2021 (+03)
Support I support Mirzali. He did his best for improved our Wikipedia --Belekvor 16:08, 15 Temuz 2021 (+03)
Support I support Mirzali as admin, because he knows the Zazaki language very well and has a big knowledge and experience about Wikipedia and the MediaWiki system. He does always his best to develope Zazaki and Wikipedia. He is also very kind and friendly to the users and finds everytime a solution for each problem. Umut Akkoç (mesac) 15:24, 18 Temuz 2021 (+03)
Request for adminship[bıvurne]
I request administrator access on diq.wiktionary:
- Language Code: diq
- Meta-Wiki Request Link: m:Requests for permissions
- Local User Page: User:Mirzali
- Supports
-- Mirzali (mesac) 06:10, 30 Temuze 2022 (+03)
Bot policy[bıvurne]
Hello. To facilitate steward granting of bot access, I suggest implementing the standard bot policy on this wiki. In particular, this policy allows stewards to automatically flag known interlanguage linking bots (if this page says that is acceptable) or bots that fix double redirects. The policy also enables global bots on this wiki (if this page says that is acceptable), which are trusted bots that will be given bot access on every wiki that allows global bots.
This policy makes bot access requesting much easier for local users, operators, and stewards. To implement it we only need to create a redirect to this page from Project:Bot policy, and add a line at the top noting that it is used here. If you use or prefer to use a dedicated project page for handling bot flag requests, that is also acceptable. Please read the text at Meta-Wiki before commenting. If you object, please say so; I hope to implement in two weeks if there is no objection, since it is particularly written to streamline bot requests on wikis with little or no community interested in bot access requests. Thank you for your consideration. --Rschen7754 03:52, 12 Tebaxe 2022 (+03)
The Vector 2022 skin as the default in two weeks?[bıvurne]

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[bıvurne]
[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?[bıvurne]
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[bıvurne]
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.
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 gladly answer! Also, see our FAQ. Thank you! SGrabarczuk (WMF) (talk) 07:15, 22 Keşkelun 2022 (+03)
Community Wishlist Survey 2023 opens in January[bıvurne]
Kerem kerê zıwanê ho rê tadayışi rê pheşti bıdê
(There is a translatable version of this message on MetaWiki)
Merheba
The Community Wishlist Survey (CWS) 2023, which lets contributors propose and vote for tools and improvements, starts next month on Monday, 23 January 2023, at 18:00 UTC and will continue annually.
We are inviting you to share your ideas for technical improvements to our tools and platforms. Long experience in editing or technical skills is not required. If you have ever used our software and thought of an idea to improve it, this is the place to come share those ideas!
The dates for the phases of the Survey will be as follows:
- Phase 1: Submit, discuss, and revise proposals – Monday, Jan 23, 2023 to Sunday, Feb 6, 2023
- Phase 2: WMF/Community Tech reviews and organizes proposals – Monday, Jan 30, 2023 to Friday, Feb 10, 2023
- Phase 3: Vote on proposals – Friday, Feb 10, 2023 to Friday, Feb 24, 2023
- Phase 4: Results posted – Tuesday, Feb 28, 2023
If you want to start writing out your ideas ahead of the Survey, you can start thinking about your proposals and draft them in the CWS sandbox.
We are grateful to all who participated last year. See you in January 2023!
Teşekur! Community Tech, STei (WMF) 19:44, 15 Kanun 2022 (+03)
Your wiki will be in read only soon[bıvurne]
Enê nesaci yewbina zıwan de bıwane • Kerem kerê zıwanê ho rê tadayışi rê pheşti bıdê
Weqıfa Wikimedia ravêrdışê merkezanê datayanê yeweni ra dıyıni test kenê 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.
All traffic will switch on 1 March. Test seate 14:00 UTC de dest pê bo.
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 Wednesday 1 March 2023.
- 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.
- GitLab will be unavailable for about 90 minutes.
Trizek (WMF) (Werênayış) 00:21, 28 Sıbate 2023 (+03)
Wikimania 2023 Welcoming Program Submissions[bıvurne]
