خبره دا ده چې اوس د اکثره ميډياويکي مخونو جوړولو ضرورت نشته هغه ځکه چې translatewiki.net ته هر څه ډايرکټ شوي دي، خو انټرفيس ايډيټر دا مقصد نه دی چې هغه پښتو ته پيغامونه ترجمه کړي، انټرفيس کې بې شماره کينډۍ دي د هغو کينډو جوړولو ضرورت دی، په هغه کې د پښتو املا ضرورت نشته که مثال په توگه ځني ځاينو کې پښتو املا هم اړتيا وي نو هغه چې انټرفيس ايډيټر وليکي نو د هغه څخه وروسته پازوالان هم هغه سمولای شي نو که تاسې دا گڼله چې ځني ځای کې تېروتني دي نو پازوال هغه سمولای شي، د انټرفيس ايډيټر اختيار صرف په يو څو مخونو کې وي نور خو باقي چې څومره مخونه دي هغه صرف پازوال په اختيار کې وي، انټرفيس ايډيټر ته تر دې هم اختيار نه وي چې هغه په هغه مخونو کې لاسوهنه وکړي کوم چې پازوالانو protect کړی وي، بلکې د انټرفيس ايډيټر صرف يو څو مخونو کې ايډيت کولای شې، يو ځل به بيا زه خبره وکړم چې انټرفيس کې اکثره مخونه اوس ټرانسليټ ويکي کې ډايرکټ ژباړل کېږي خو ځني مخونه داسې دي چې هغو کې د ترجمې نه بلکې د کينډو ضرورت وي، په هغه کې پښتو املا دومره وي هم نه ، او که وي او تاسې ته ښکارېده چې څه قسمه تېروتنې دي پکې نو هغه هر پازوال سمولای شي۔ ټولې ويکيپيډياگانې د انټرفيس ايډيټر گروپ لري او زه خواهش کوم چې پښتو ويکي کې هم دا گروپ انسټال شي او پښتو ويکي د نورو څخه وروستو پاتي نشي. ددې يوزر گروپ د انسټالولو څخه وروسته هر پازوال دا کولای شي چې ځني کارنانو ته دغه اختيار(right) ورکړي او يا يي ترې بېرته واخلي۔--کارن:UsmanKhan 14:39, 24 اپرېل 2016 (UTC)
او کوم تجويز چې تاسې پېښ کړي دي زما په خيال دا تجويز ستاسې ښه دی چې کار دې په يو څو څانگو کې ويشل شي، زما په خيال دا ډېر ښه تجويز دی او همداسې پکار ده چې هر کس ته مونږ يو کار وکړو چې ستاسې دې سمولو کوښښ کوئ، خو په دې تجويز عمل کولو څخه وړاندي به په بانډارځای (وړاندېزونه) والا مخ کې رای شماري وشي ددي لپاره چې د نورو کارنانو رای واخيستی شي چې ايا هغوي ددې تجويز په حق کې دي او که دا تجويز ناسم گڼي، د زياتو کارنانو د خوښې مطابق به کار وکړی شي، داسې نه چې نور کارنان دومره وخت ويکيپېډيا ته نشي ورکولای او مونږ پرې دا زمه واري وتړو چې تاسې به دا کار کوئ، هر انسان خپلواکه دی ، هر يو ته د هغه د خوښې مطابق کار ورکول پکار دي--کارن:UsmanKhan 14:59, 24 اپرېل 2016 (UTC)
سلام او نیکۍ هیلي ستا سو ته:
ګرانو د پښتو ویکی لیکوالانو، واقعا زه ډير په دي باندي کار کووم چي د خپل لیکنۍ سمه کرم واقعا واقعا . ام زما تقصیر نه دۍ.دلته خو خلک حتی پښتو نه غږیګي واقعا زماکم څوک هم پښتو لیکلۍ نه شي هیڅ څوک هم نشته چي تینه زده کرم.ولي زه بیسواده نه یم!عربي او انګلیسي او فارسي باندي سمه پوهیګم او پوهنتون ته زم زه د دی ورتیا لرم چي علمي او پوهنیز مقالات ولیکم(زما لیکني د محتوا کمه ستونزه نه لري او زه هغي سرچینه باندي پام نیسم ) زما پښتو لیکنه که کم زره ناسمه ده خو زه څه وکرم واقعا دونه ډير وقت نلرم چي کینمه ډیر وقت کیدم پښتو باندي
اما پښتو زما ستونزه ده هغه هم په لیکنو کې ،واقعا زما حیف راځي چي د پښتو ژبه د علمی او ځیني نور موضوعاتونه محروم پاتي شي او واقعا دا موضوع زما ویکي تا رولي نه بیکاریم او نه خرابکار.واقعا زما ته هم ډیر ناخاشیني حس دۍ چي یو شی لیکم اما محتوا دهغي سمه اما لیک کې ناسم وي :(.چون ویکی مرجع دی اوباید سم وي.
که زما د رای پیغام هم نه وو خو !ولي که کم روباټ یا ده سي کم شي وي چي لکه زما غوندي خلکو سره مرسته وکری په سمه لیکونوکي واقعا ښه به وې.که زما ویکی ته ستونزه جوره کرۍ ده، نو کم څوک که زماته پښتو سمه لیکنه کې مرسته کولۍ شي لطفا د لطف زمانه دریغ کوئ مه.
The Wikimedia Developer Summit is the annual meeting to push the evolution of MediaWiki and other technologies supporting the Wikimedia movement. The next edition will be held in San Francisco on January 9–11, 2017.
We welcome all Wikimedia technical contributors, third party developers, and users of MediaWiki and the Wikimedia APIs. We specifically want to increase the participation of volunteer developers and other contributors dealing with extensions, apps, tools, bots, gadgets, and templates.
Important deadlines:
Monday, October 24: last day to request travel sponsorship. Applying takes less than five minutes.
Monday, October 31: last day to propose an activity. Bring the topics you care about!
The Wikimedia technical community seeks input from developers for
developers, to create a high-profile list of desi improvements. The scope of the survey includes the MediaWiki platform (core software, APIs, developer environment, enablers for extensions, gadgets, templates, bots, dumps), the Wikimedia server infrastructure, the contribution process, and documentation.
The best part: we want to have the results published by Wednesday, February 15. Yes, in a month, to have a higher chance to influence the
Wikimedia Foundation annual plan FY 2017-18.
There's no time to lose. Propose your ideas before the end of January,
either by pushing existing tasks in Phabricator or by creating new ones. You can find instructions on the wiki page. Questions and feedback are welcome especially on the related Talk page.
The voting phase is expected to start on February 6 (tentative). Watch this space (or even better, the wiki page) - SSethi_(WMF) January 21st, 2017 3:07 AM (UTC)
Almost two weeks ago, the Technical Collaboration team invited proposals for the first edition of the Developer Wishlist survey!
We collected around 77 proposals that were marked as suitable for the developer wishlist and met the defined scope and criteria. These proposals fall into the following nine categories: Frontend, Backend, Code Contribution (Process, Guidelines), Extensions, Technical Debt, Developer Environment, Documentation, Tools (Phabricator, Gerrit) and Community Engagement.
What happens next?
Proposals that will gather most votes will be included in the final results which will be published on Wednesday, February 15th. These proposals will also be conside in the Wikimedia Foundation’s annual plan FY 2017-18 - SSethi_(WMF) (talk) 04:41, 6 February 2017 (UTC)
New notification when a page is connected to Wikidata
The Wikidata development team is about to deploy a new feature on all Wikipedias. It is a new type of notification (via Echo, the notification system you see at the top right of your wiki when you are logged in), that will inform the creator of a page, when this page is connected to a Wikidata item.
You may know that Wikidata provides a centralized system for all the interwikilinks. When a new page is created, it should be connected to the corresponding Wikidata item, by modifying this Wikidata item. With this new notification, editors creating pages will be informed when another editor connects this page to Wikidata.
This feature will be deployed on May 30th on all the Wikipedias, excepting English, French and German. This feature will be disable by default for existing editors, and enabled by default for new editors.
This is the first step of the deployments, the Wikipedias and other Wikimedia projects will follow in the next months.
If you have any question, suggestion, please let me know by pinging me. You can also follow and leave a comment on the Phabricator ticket.
Sorry to use English. مهرباني وکړئ خپلي ژبې ته د ور ژباړلو لپاره مرسته وکړئ! مننه
In short: starting on 26 September, New Filters for Edit Review (now in Beta) will become standard on Recent Changes. They provide an array of new tools and an improved interface. If you prefer the current page you will be able to opt out. Learn more about the New Filters.
Based on a new design, it adds new features that ease vandalism tracking and support of newcomers:
Filtering - filter recent changes with easy-to-use and powerful filters combinations, including filtering by namespace or tagged edits.
Highlighting - add a colo background to the different changes you are monitoring. It helps quick identification of changes that matter to you.
Bookmarking to keep your favorite configurations of filters ready to be used.
Quality and Intent Filters - those filters use ORES pictions. They identify real vandalism or good faith intent contributions that need help. They are not available on all wikis.
Starting on 26 September, New Filters for Edit Review will become standard on Recent Changes. We have decided to do this release because of a long and successful Beta test phase, positive feedback from various users and positive user testing.
If your community has specific concerns about this deployment or internal discussion, it can request to have the deployment to their wikis delayed to October 1, if they have sensible, consistent with the project, actionable, realistic feedback to oppose (at the development team's appreciation).
You will also be able to opt-out this change in your preferences.
Concerning Watchlists
Starting on September 19, the Beta feature will have a new option. Watchlists will have all filters available now on the Beta Recent Changes improvements.
If you have already activated the Beta feature "⧼eri-rcfilters-beta-label⧽", you have no action to take. If you haven't activated the Beta feature "⧼eri-rcfilters-beta-label⧽" and you want to try the filters on Watchlists, please go to your Beta preferences on September 19.
How to be ready
Please share this announcement!
Do you use Gadgets that change things on your RecentChanges or Watchlist pages, or have you customized them with scripts or CSS? You may have to make some changes to your configuration. Despite the fact that we have tried to take most cases into consideration, some configurations may break. The Beta phase is a great opportunity to have a look at local scripts and gadgets: some of them may be replaced by native features from the Beta feature.
Once the team has feedback on design issues, bugs, and other things that might need worked out, the problems will be addressed and global preferences will be sent to the wikis.
Please let me know if you have any questions. Thanks! --Keegan (WMF) (talk) ۰۰:۲۴, ۲۷ فبروري ۲۰۱۸ (UTC)
(I’m sorry for writing in English. مهرباني وکړئ خپلي ژبې ته د ور ژباړلو لپاره مرسته وکړئ)
If you’re regularly using Lua modules, creating and improving some of them, we need your feedback!
The Wikidata development team would like to provide more Lua functions, in order to improve the experience of people who write Lua scripts to reuse Wikidata's data on the Wikimedia projects. Our goals are to help harmonizing the existing modules across the Wikimedia projects, to make coding in Lua easier for the communities, and to improve the performance of the modules.
We would like to know more about your habits, your needs, and what could help you. We have a few questions for you on this page. Note that if you don’t feel comfortable with writing in English, you can answer in your prefer language.
Mapframe is a feature that enables users to easily display interactive maps right on wiki pages. Currently, most Wikipedias don’t have mapframe. But fifteen Wikipedias, along with all the other Wikimedia projects, are using mapframe today to display maps on thousands of pages.
A little background: over the last few months, the Foundation’s Collaboration team has been working to improve the stability and user experience of the maps service. In addition, a question about long-term support for the maps service was recently settled, and a small team has been assigned for routine maintenance. Given these developments, bringing the benefits of mapframe to Wikipedias that lack the feature seems both safe and supportable. Nine Wikipedias that use a stricter version of Flagged Revisions will not get mapframe in this release.
Maps are a valuable form of visual data that can improve readers’ understanding across a wide range of topics. If you know of any reasons why mapframe shouldn’t be implemented on your Wikipedia, let us know on the project talk page. Unless we hear from you, we plan to release mapframe to most Wikipedias in May, 2018. So, if you foresee an issue, please let us hear from you. Otherwise, happy mapping!
Wikitext syntax highlighting, also known as CodeMirror, has been moved out of Beta Features and is available in the 2017 Wikitext Editor on all wikis. Syntax highlighting helps you see problems in your wikitext before previewing or publishing text. Please try out the tool if you did not do so while it was being developed, and feedback is welcome. - Keegan (WMF) (talk)
Sorry to use English. مهرباني وکړئ خپلي ژبې ته د ور ژباړلو لپاره مرسته وکړئ! مننه
In short: starting on June 18, New Filters for Edit Review (now in Beta) will become standard on Watchlists. They provide an array of new tools and an improved interface. If you prefer the current page you will be able to opt out. Learn more about the New Filters.
Based on a new design, that feature adds new functions to those pages, to ease vandalism tracking and support of newcomers:
Filtering - filter recent changes with easy-to-use and powerful filters combinations, including filtering by namespace or tagged edits.
Highlighting - add a colo background to the different changes you are monitoring. It helps quick identification of changes that matter to you.
Bookmarking to keep your favorite configurations of filters ready to be used.
Quality and Intent Filters - those filters use ORES pictions. They identify real vandalism or good faith intent contributions that need help. They are not available on all wikis.
Over 70,000 people have activated the New Filters beta, which has been in testing on Watchlist for more than eight months. We feel confident that the features are stable and effective, but if you have thoughts about these tools or the beta graduation, please let us know on the project talk page. In particular, tell us if you know of a special incompatibility or other issue that makes the New Filters problematic on your wiki. We’ll examine the blocker and may delay release on your wiki until the issue can be addressed.
The deployment will start on June 18 or on June 25, depending on the wiki (check the list). After the deployment, you will also be able to opt-out this change directly from the Watchlist page and also in your preferences.
How to be ready?
Please share this announcement!
If you use local Gadgets that change things on your Watchlist pages, or have a customized scripts or CSS, be ready. You may have to make some changes to your configuration. Despite the fact that we have tried to take most cases into consideration, some configurations may break. The Beta phase is a great opportunity to have a look at local scripts and gadgets: some of them may be replaced by native features from the Beta feature.
Please share your questions and comments on the feedback page.
مهرباني وکړئ خپلي ژبې ته د ور ژباړلو لپاره مرسته وکړئ
Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.
The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
Page issues make sense to readers and they understand how they work
Readers care about page issues and consider them important
Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues
Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.
I'm preparing a change in who can edit sitewide CSS/JS pages. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which are executed in the browser of all readers and editors.) Currently all administrators are able to edit these pages, which poses a serious and unnecessary security risk. Soon, a dedicated, smaller user group will take over this task. Your community will be able to decide who belongs in this group, so this should mean very little change for you. You can find out more and provide feedback at the consultation page on Meta. If you are involved in maintaining CSS/JS code, or policymaking around adminship requests, please give it a look!
The team working on TemplateStyles at the Wikimedia Foundation would like to enable TemplateStyles on this wiki.
TemplateStyles is a feature to allow non-administrators to write and manage CSS styles for templates. It allows contributors who edit templates to separate content and presentation. A good web practice that makes it easier to manage the layout of templates. If you don't edit templates, this will not have any impact on your contributions.
TemplateStyles is useful for a few reasons.
It makes it possible for templates to work better on mobile.
It cuts out confusion on where to apply CSS rules.
Editing CSS is currently limited to administrators, which is a major barrier to participation.
All stylesheets must be loaded on all pages (whether they actually use the page or not), which wastes bandwidth and makes debugging style rules more difficult.
This is an optional feature and no one must use it, but template contributors are encouraged to do so! Please discuss and let us know if there are any concerns. If there are no concerns we will proceed to deploy the feature on the 9th of August.
Hi, the mw.util.jsMessage() function was deprecated in 2012, and will soon not be working. According to phab:P7840 there's at least one gadget using this function on your wiki, but it is likely it won't cause much of a problem anyway. We don't see this function being used much and this message is mainly to be on the safe side. There's a migration guide that explains how to use mw.notify instead. See phab:T193901 for more information. /Johan (WMF)
Sorry for writing this message in English - feel free to help us translating it :)
Hello all,
Many language versions of Wikipedia use the content of Wikidata, the centralized knowledge base, to fill out the content of infoboxes. The data is sto in Wikidata and displayed, partially or completely, in the Wikipedia’s language, on the articles.
This feature is used by many template editors, but brought several issues that were raised by communities in various places: not being able to edit the data directly from Wikipedia was one of them.
This is the reason why the Wikidata Bridge project started, with the goal of offering a way to Wikipedia editors to edit Wikidata’s data more easily. This will be achieved by an interface, connected to the infobox, that users can access directly from their local wiki.
The project is now at an early stage of development. A lot of user research has been done, and will continue to be done through the different phases of the project. The next steps of development will be achieved by the development team working at Wikimedia Deutschland, starting now until the end of 2019.
In order to make sure that we’re building a tool that is answering editors’ needs, we’re using agile methods in our development process. We don’t start with a fixed idea of the tool we want to deliver: we will build it together with the editors, based on feedback loops that we will regularly organize. The first version will not necessarily have all of the features you want, but it will keep evolving.
Here’s the planned timeline:
From June to August, we will build the setup and technical groundwork.
From September to November 2019, we will develop the first version of the feature and publish a test system so you can try it and give feedback.
Later on, we will test the feature on a few projects, in collaboration with the communities.
We will first focus on early adopters communities who already implemented a shortcut from their infoboxes to edit Wikidata (for example Russian, Catalan, Basque Wikipedias)
Then we will reach some of the big Wikipedias (French, German, English) in order to see if the project scales and to address their potentially different needs.
Even later, we can consider enabling the feature on all the other projects.
In any case, no deployment or big change will be enforced on the projects without talking to the communities first, and helping the template builders to prepare for the changes they will have to do on the infoboxes’ code.
If you want to get involved, there are several ways to help:
More ideas will be added on this page along the way
If you have any questions for the development team, feel free to ask them on the main talk page. You can also ask under this message, but if you expect an answer from me, please make sure to ping me.
Hi everybody! Google Code-in (GCI) will soon take place again - a seven week long contest for 13-17 year old students to contribute to free software projects. Tasks should take an experienced contributor about two or three hours and can be of the categories Code, Documentation/Training, Outreach/Research, Quality Assurance, and User Interface/Design. Do you have any Lua, template, gadget/script or similar task that would benefit your wiki? Or maybe some of your tools need better documentation? If so, and you can imagine enjoying mentoring such a task to help a new contributor, please check out mw:Google Code-in/2019 and become a mentor. If you have any questions, feel free to ask at our talk page. Many thanks in advance! --Martin Urbanec ۰۷:۲۸, ۵ نومبر ۲۰۱۹ (ہ ن و)
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 delive. 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.
Tools play an essential role for the Wikimedia projects, and so do the many volunteer developers who experiment with new ideas and develop and maintain local and global solutions to support the Wikimedia communities. The Coolest Tool Award aims to recognize and celebrate the coolest tools in a variety of categories.
Among anyone and everyone you know who has an account on wiki.
Promote the Survey on social media, via instant messaging apps, in other groups and chats, in your WikiProject, Wikimedia affiliate - wherever contributors with registered accounts may be.
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.
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.
This award is highlighting software tools that have been nominated by contributors to the Wikimedia projects. The ceremony will be a nice moment to show appreciation to our tool developers and maybe discover new tools!
Over the next months we will gradually change the audio and video player of Wikis from Kultura to Video.js and with that, the old player won’t be accessible anymore. The new player has been active as a beta feature since May 2017.
The new player has many advantages, including better design, consistent look with the rest of our interface, better compatibility with browsers, ability to work on mobile which means our multimedia will be properly accessible on iPhone, better accessibility and many more.
The old player has been unmaintained for eight years now and is home-brewn (unlike the new player which is a widely used open source project) and uses deprecated and abandoned frameworks such as jQuery UI. Removing the old player’s code also improves performance of the Wikis for anyone visiting any page (by significantly reducing complexity of the dependency graph of our ResourceLoader modules. See this blog post.). The old player has many open bugs that we will be able to close as resolved after this migration.
The new player will solve a lot of old and outstanding issues but also it will have its own bugs. All important ones have been fixed but there will be some small ones to tackle in the future and after the rollout.
What we are asking now is to turn on the beta feature for the new player and let us know about any issues.
The fourth edition of the Coolest Tool Award welcomes your nominations! What is your favorite Wikimedia related software tool? Please submit your favorite tools by October 12, 2022! The awarded projects will be announced and showcased in a virtual ceremony in December.
This award is highlighting software tools that have been nominated by contributors to the Wikimedia projects. The ceremony will be a nice moment to show appreciation to our tool developers and maybe discover new tools!
Yesterday the Wikimedia Foundation noted that in the interests of the security of our users, the Graph extension was disabled. This means that pages that were formerly displaying graphs will now display a small blank area. To help readers understand this situation, communities can now define a brief message that can be displayed to readers in place of each graph until this is resolved. That message can be defined on each wiki at MediaWiki:Graph-disabled. Wikimedia Foundation staff are looking at options available and expected timelines. For updates, follow the public Phabricator task for this issue: T334940
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.
Hello. For many years, community members have requested an easy way to re-use references with different details. Now, a MediaWiki solution is coming: The new sub-referencing feature will work for wikitext and Visual Editor and will enhance the existing reference system. You can continue to use different ways of referencing, but you will probably encounter sub-references in articles written by other users. More information on the project page.
We want your feedback to make sure this feature works well for you:
Sign up here to get updates and/or invites to participate in user research activities.
Wikimedia Deutschland’s Technical Wishes team is planning to bring this feature to Wikimedia wikis later this year. We will reach out to creators/maintainers of tools and templates related to references beforehand.
Apologies for cross-posting in English. Please consider translating this message.کينډۍ:Tracked
Hello everyone, a small change will soon be coming to the user-interface of your Wikimedia project.
The Wikidata itemsitelink currently found under the General section of the Tools sidebar menu will move into the In Other Projects section.
We would like the Wiki communities feedback so please let us know or ask questions on the Discussion page before we enable the change which can take place October 4 2024, circa 15:00 UTC+2.
More information can be found on the project page.
Hello everyone, I previously wrote on the 27th September to advise that the Wikidata item sitelink will change places in the sidebar menu, moving from the General section into the In Other Projects section. The scheduled rollout date of 04.10.2024 was delayed due to a necessary request for Mobile/MinervaNeue skin. I am happy to inform that the global rollout can now proceed and will occur later today, 22.10.2024 at 15:00 UTC-2. Please let us know if you notice any problems or bugs after this change. There should be no need for null-edits or purging cache for the changes to occur. Kind regards, -Danny Benjafield (WMDE) ۱۱:۲۹, ۲۲ اکتوبر ۲۰۲۴ (نړیوال وخت)
