Wikipedia:Sawala (téknis)

Kawijakan

Téknis

Ajuan

Basa

Nu lian

• Daptar eusi
• munggaran
• panungtung

Kaca sawala bagian téknis digunakeun pikeun nyawalakeun hal-hal téknis ngeunaan Wikipedia. Laporan bug sarta pamundut fitur mah kuduna di Pabrikator (ilikan cara ngalaporkeun bug). Bug anu ngakibatkeun kaancamna kaamanan mah béda deui tempat ngalaporkeunna (ilikan cara ngalaporkeun bug). Mun anyar jabung ka sawala téknis mah alusna maca heula panduan utamana pikeun nulis didieu. Patanyaan ngeunaan MediaWiki nu umum kuduna di tempat dukungan MediaWiki.

VisualEditor News #1—2015

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appéarance, the coming Citoid reference service, and support for languages with complex input requirements. Status reports are posted on mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor réady for deployment by default to all new users and logged-out users at the remaining large Wikipedias. You can help identify these requirements. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice présidént of Engineering Damon Sicore, Product Manager James Forrester and other téam members which bugs and féatures are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor réady for deployment to new users. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins.

Due to some bréaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in éarly January. The téams apologize for the problem.

Recent improvements

The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design téam. Several new versions of the OOjs UI library have also been reléased, and these also affect the appéarance of VisualEditor and other MediaWiki software extensions. Most changes were minor, like changing the text size and the amount of white space in some windows. Buttons are consistently color-coded to indicate whether the action:

• starts a new task, like opening the ⧼visualeditor-toolbar-savedialog⧽ dialog: blue ,
• takes a constructive action, like inserting a citation: green ,
• might remove or lose your work, like removing a link: red , or
• is neutral, like opening a link in a new browser window: gray .

The TemplateData editor has been completely re-written to use a different design based on the same OOjs UI system as VisualEditor. (T67815, T73746.) This change fixed a couple of existing bugs and improved usability. (T73077, T73078.)

Séarch and replace in long documents is now faster. It does not highlight every occurrence if there are more than 100 on-screen at once.(T78234.)

Editors at the Hebrew and Russian Wikipedia requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace. (T86688, T87027.) If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Pléase include a link to a community discussion about the requested change.

Looking ahead

The Editing téam will soon add auto-fill féatures for citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After créating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to contribute to the Citoid service's definitions for éach website, to improve precision and reduce the need for manual corrections.

We will need editors to help test the new design of the special character inserter, especially if you spéak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Pléase contact User:Whatamidoing (WMF) if you would like to be notified when the new version is available. After the special character tool is completed, VisualEditor will be deployed to all users at Phase 5 Wikipedias. This will affect about 50 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh. The date for this change has not been determined.

Let's work together

• Share your idéas and ask questions at mw:VisualEditor/Feedback.
• Pléase help complete translations of the user guide for users who spéak your language.
• Join the weekly bug triage meetings beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC); information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins, and you can also contact James F. to léarn more about this initiative.
• Talk to the Editing téam during the office hours via IRC. The next session is on Thursday, 19 February 2015 at 19:00 UTC.
• Subscribe or unsubscribe at Meta. If you would like to help with translations of this newsletter, pléase subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is réady. Thank you!

— Elitre (WMF)

5 Pébruari 2015 18.30 (UTC)

New Wikipedia Library Accounts Available Now (March 2015)

Apologies for writing in English, please help translate this into your local language. Hello Wikimedians!

The TWL OWL says sign up today!

The Wikipedia Library is announcing signups today for, free, full-access accounts to published reséarch as part of our Publisher Donation Program. You can sign up for new accounts and reséarch materials from:

• Project MUSE — humanities and social science books and journals
• DynaMed — clinical reference tool for medical topics
• Royal Pharmaceutical Society — pharmaceutical information and practice resources
• Women Writers Online — a digital humanities database focused on women's literature
• Newspapers.com — American newspapers database w/ Open Access opportunities (expansion of accounts)

Many other partnerships with accounts available are listed on our partners page. Do better reséarch and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 2 Maret 2015 21.14 (UTC)

Help us coordinate Wikipedia Library's distribution of accounts, communication of access opportunities and more! Please join our team at our new coordinator page.

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

Inspire Campaign: Improving diversity, improving content

This March, we’re organizing an Inspire Campaign to encourage and support new idéas for improving gender diversity on Wikimedia projects. Less than 20% of Wikimedia contributors are women, and many important topics are still missing in our content. We invite all Wikimedians to participate. If you have an idéa that could help address this problem, pléase get involved today! The campaign runs until March 31.

All proposals are welcome - reséarch projects, technical solutions, community organizing and outréach initiatives, or something completely new! Funding is available from the Wikimedia Foundation for projects that need financial support. Constructive, positive feedback on idéas is appreciated, and collaboration is encouraged - your skills and experience may help bring soméone else’s project to life. Join us at the Inspire Campaign and help this project better represent the world’s knowledge!

• Inspire Campaign main page

(Sorry for the English - please translate this message!) MediaWiki message delivery (sawala) 4 Maret 2015 20.01 (UTC)

VisualEditor News #2—2015

Did you know?

With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:

Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:

After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to maké changes.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

The weekly task triage meetings continue to be open to volunteers, éach Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instéad, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Léarn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

Recent improvements

VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.

The Editing téam is slowly adding auto-fill féatures for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After créating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for éach website.

Citoid requires good TemplateData for your citation templates. If you would like to request this féature for your wiki, pléase post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh.

Work continues to support languages with complex requirements, such as Koréan and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.

The design for the image selection process is now using a "masonry fit" modél. Images in the séarch results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it éasier to see more details in images.

You can now drag and drop categories to re-arrange their order of appéarance ​on the page.

The pop-up window that appéars when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The téam has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.

Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section héadings.

Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to booléan value, which lets you tell users of the template what they should do instéad. (T90734)

Looking ahead

The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at éach wiki will also have the option of créating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.

The téam is discussing a test of VisualEditor with new users at the English Wikipedia, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon. (T90666)

Let's work together

• Share your idéas and ask questions at mw:VisualEditor/Feedback.
• Can you translate from English into any other language? Pléase check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
• The design reséarch téam wants to see how réal editors work. Pléase sign up for their research program.
• File requests for language-appropriate "Kandel" and "Déngdék" icons for the character formatting menu in Phabricator.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't réading this in your favorite language, then pléase help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is réady. Thank you!

— Elitre (WMF)

10 April 2015 19.48 (UTC)

New Wikipedia Library Accounts Available Now (May 2015)

Apologies for writing in English, please help translate this into your local language. Hello Wikimedians!

The TWL OWL says sign up today!

Today The Wikipedia Library announces signups for more free, full-access accounts to published reséarch as part of our Publisher Donation Program. You can sign up for new accounts and reséarch materials from:

• MIT Press Journals — scholarly journals in the humanities, sciences, and social sciences (200 accounts)
• Loeb Classical Library — Harvard University Press versions of Classical Greek and Latin literature with commentary and annotation (25 accounts)
• RIPM — music periodicals published between 1760 and 1966 (20 accounts)
• Sage Stats — social science data for géographies within the United States (10 accounts)
• HeinOnline — an extensive legal reséarch database, including 2000 law-related journals as well as international legal history materials (25 accounts)

Many other partnerships with accounts available are listed on our partners page, including Project MUSE, JSTOR, DeGruyter, Newspapers.com and British Newspaper Archive. Do better reséarch and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 4 Méi 2015 22.12 (UTC)

We need your help! Help coordinate Wikipedia Library's account distribution and global development! Please join our team at Global our new coordinator signup.

This message was delivered via the Mass Message tool to The Wikipedia Library Global Delivery List

Thank you for the info. Mangga ka para wargi anu sakirana peryogi akses ka pabukon2 anu disebat di luhur, tiasa dipolow ap! --kumincir (sawala) 5 Méi 2015 04.11 (UTC)

Pywikibot compat will no longer be supported - Please migrate to pywikibot core

Sorry for English, I hope soméone translates this.
Pywikibot (then "Pywikipediabot") was started back in 2002. In 2007 a new branch (formerly known as "rewrite", now called "core") was started from scratch using the MediaWiki API. The developers of Pywikibot have decided to stop supporting the compat version of Pywikibot due to bad performance and architectural errors that maké it hard to update, compared to core. If you are using pywikibot compat it is likely your code will bréak due to upcoming MediaWiki API changes (e.g. T101524). It is highly recommended you migrate to the core framework. There is a migration guide, and pléase contact us if you have any problem.

There is an upcoming MediaWiki API bréaking change that compat will not be updated for. If your bot's name is in this list, your bot will most likely bréak.

Thank you,
The Pywikibot development téam, 19:30, 5 June 2015 (UTC)

Pywikibot compat will no longer be supported - Please migrate to pywikibot core

Sorry for English, I hope soméone translates this.
Pywikibot (then "Pywikipediabot") was started back in 2002. In 2007 a new branch (formerly known as "rewrite", now called "core") was started from scratch using the MediaWiki API. The developers of Pywikibot have decided to stop supporting the compat version of Pywikibot due to bad performance and architectural errors that maké it hard to update, compared to core. If you are using pywikibot compat it is likely your code will bréak due to upcoming MediaWiki API changes (e.g. T101524). It is highly recommended you migrate to the core framework. There is a migration guide, and pléase contact us if you have any problem.

There is an upcoming MediaWiki API bréaking change that compat will not be updated for. If your bot's name is in this list, your bot will most likely bréak.

Thank you,
The Pywikibot development téam, 19:30, 5 June 2015 (UTC)

VisualEditor News #3—2015

Did you know?

When you click on a link to an article, you now see more information:

The link tool has been re-designed:

There are separate tabs for linking to internal and external pages. The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has créated new interfaces for the link and citation tools and fixed many bugs and changed some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on mediawiki.org. The worklist for April through June is available in Phabricator.

A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to léarn which group was more likely to save an edit and to maké productive, unreverted edits. Initial results will be posted at Meta later this month.

Recent improvements

Auto-fill féatures for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now créated inside a single tool. Inside that tool, choose the tab you want (⧼citoid-citeFromIDDialog-mode-auto⧽, ⧼citoid-citeFromIDDialog-mode-manual⧽, or ⧼citoid-citeFromIDDialog-mode-reuse⧽). The cite button is now labeled with the word "⧼visualeditor-toolbar-cite-label⧽" rather than a book icon, and the autofill citation dialog now has a more méaningful label, "⧼Citoid-citeFromIDDialog-lookup-button⧽", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). Séarch results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appéared over the first match in the link inspector. (T98085)

The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at éach wiki can also créate a custom section for frequently used characters at the top of the list. Pléase réad the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing éach character in the special character inserter. (T70425)

Several improvements have been made to templates. When you séarch for a template to insert, the list of results now contains descriptions of the templates. The paraméter list inside the template dialog now remains open after inserting a paraméter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" éach time they want to add another paraméter. (T95696) The téam added a new property for TemplateData, "Contoh", for template paraméters. This optional, translatable property will show up when there is text describing how to use that paraméter. (T53049)

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design féature is being used for the cite button on wikis where the Citoid service is enabled.

The téam has reléased a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

Let's work together

• Share your idéas and ask questions at mw:VisualEditor/Feedback.
• The weekly task triage meetings continue to be open to volunteers, usually on Wednesday at 12:00 (noon) PDT (19:00 UTC). Léarn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker, though. Instéad, go to Phabricator and "associate" the VisualEditor Q4 blocker project with the bug.
• If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then pléase contact James Forrester.
• If you would like to request the Citoid automatic reference féature for your wiki, pléase post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The téam is planning the second VisualEditor-related "translathon" for July. Pléase follow this task on Phabricator for details and updates! Announcements will follow in due course.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't réading this in your favorite language, then pléase help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is réady. Thank you!

— Elitre (WMF)

13 Juni 2015 10.44 (UTC)

New Wikipedia Library Accounts Available Now (June 2015)

Hello Wikimedians!

The TWL OWL says sign up today!

Today The Wikipedia Library announces signups for more free, full-access accounts to published reséarch as part of our Publisher Donation Program. You can sign up for new accounts and reséarch materials from:

• Taylor & Francis — academic publisher of journals. The pilot includes two subject collections: Arts & Humanities and Biological, Environment & éarth Sciences. (30 accounts)
• World Bank eLibrary — digital platform containing all books, working papers, and journal articles published by the World Bank from the 1990s to the present. (100 accounts)
• AAAS — general interest science publisher, who publishes the journal Science among other sources (50 accounts)

New French-Language Branch!

• Érudit (en Francais) — Érudit is a French-Canadian scholarly aggregator primarily, humanities and social sciences, and contains sources in both English and French. Signups on both English and French Wikipedia (50 accounts).
• Cairn.info (en Francais) — Cairn.info is a Switzerland based online web portal of scholarly materials in the humanities and social sciences. Most sources are in French, but some also in English. Signups on both English and French Wikipedia (100 accounts).
• L'Harmattan — French language publisher across a wide range of non-fiction and fiction, with a strong selection of francophone African materials (1000 accounts).

Many other partnerships with accounts available are listed on our partners page, including an expansion of accounts for Royal Society journals and remaining accounts on Project MUSE, JSTOR, DeGruyter, Highbeam Newspapers.com and British Newspaper Archive. If you have suggestions for journals or databases we should seek access to make a request! Do better reséarch and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 22:08, 15 June 2015 (UTC)

We need your help! Help coordinate Wikipedia Library's account distribution and global development! Please join our team at our new coordinator signup.

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List

HTTPS

Apologies for writing in English.

Hi everyone.

Over the last few yéars, the Wikimedia Foundation has been working towards enabling HTTPS by default for all users, including unregistered ones, for better privacy and security for both réaders and editors. This has taken a long time, as there were different aspects to take into account. Our servers haven't been réady to handle it. The Wikimedia Foundation has had to balance sometimes conflicting goals.

Forced HTTPS has just been implemented on all Wikimedia projects. Some of you might alréady be aware of this, as a few Wikipedia language versions were converted to HTTPS last week and the then affected communities were notified.

Most of Wikimedia editors shouldn't be affected at all. If you edit as registered user, you've probably alréady had to log in through HTTPS. We'll keep an eye on this to maké sure everything is working as it should. Do get in touch with us if you have any problems after this change or contact me if you have any other questions.

/Johan (WMF)

19 Juni 2015 22.01 (UTC)

Content Translation, the new article creation tool is now available as a beta-feature

How to use Content Translation - a short video (English)

Hello, Content Translation has now been enabled as an opt-in beta féature on the Sundanese Wikipedia. To start translating:

1. Pléase enable the Beta féature in your preferences by checking the box for Content Translation.
2. Visit the page Special:ContentTranslation or to your contributions page to open the tool.
3. Click on the button to créate a new translation.
4. In the displayed dialog select the language of the original article and the article name, and the language you would like to translate to. Also add the title of the new article (or the original title will be inserted) and click on to begin. Your language preferences will be remembered for the next time.
5. You will see a screen consisting of three columns. The first column contains the text of the source language and the middle column is for the translated text. Using the third column you can perform several actions such as insert source text, remove the inserted text source text, add or remove links etc.
6. After you translate the article, you can publish it directly as a new page on the Sundanese Wikipedia by using the publish button that appéars. In case the article gets créated by another user while you were translating, you will see an option to save the newly published translation under your user namespace.
7. The number of published pages can be seen on the Content Translation stats page.

Since this is the first time we have installed the tool on this Wikipedia, there are chances that there may be some problems or service disruptions which we are not yet aware of. We will be monitoring the usage to check for any failures or issues, but pléase do let us know on the Content Translation talk page or through Phabricator if you spot any problems. For more information, pléase réad the information available in the User Guide. Our announcement is written only in English, and we would réally appreciate if this message can be translated to réach more users of this Wikipedia. Thank you. On behalf of the Wikimedia Foundation's Language Engineering Téam:--Runa Bhattacharjee (sawala) 30 Juni 2015 17.15 (UTC)

Hasil rarancang

Manawi katampi, ieu rarancangan kaca tepas ti simabdi Pamaké:Uchup19/Kotrétan, anu dioméan tur ditambahan:

• Ngoméan tutumbu icon gambar anu nojo ka tumbu gambarna di commons (aya nu di kana tumbuna masing2 aya nu dibuntukeun)
• Ngoméan subkaca keur lumangsung anu teu kompléks, asalna mah {{Portal:Keur lumangsung/Juli 2015}} jadi {{Portal:Keur lumangsung/{{CURRENTMONTHNAME}}_{{CURRENTYEAR}}. (Supados teu unggal waktu ngaropéa kaca Tepas)
• Nambahan Tombol gabung
• Nambahan kolom Sajarah poé ieu
• Jrd.

Panuhun ka @Kumincir, @Mssetiadi, @Ilham.nurwansah, @A.R Dipusparaga. Diantos kedalanna.--Yusup_Ramdani ✉ 23 Juli 2015 02.24 (UTC)

Sae, ngan aya sababaraha kalimat/istilah anu perlu dibadamikeun deui. 'Sajarah poe ieu', sakumaha dina obrolan sapalih, mun teu manggih nu pas mah samikeun bae 'poe ieu dina sajarah'. Teras 'kamaotan kiwari', naon nya kalimat anu pas? 'kapapatenan'? --kumincir (sawala) 23 Juli 2015 03.38 (UTC)

@Kumincir Muhun kang, parantos. Pami kapapatenan téh lomana mah kapapaitan panginten nya?--Yusup_Ramdani ✉ 23 Juli 2015 03.51 (UTC)

Numutkeun pamendak simkuring mah Nu Pupus Kiwari, Nu Kiwari Pupus, atanapi Nu Pupus Taun Ieu. Memang sok rada sesah nyundakeun ke-an teh. Pilihan sanesna : Papaten Kiwari atanapi papait, nanging papait mah sanes mung ukur kanggo urusan pati, tapi kalebet oge teu damang sareng kasangsaraan sanesna. --Tedi (sawala) 23 Juli 2015 06.13 (UTC)

@Mssetiadi Kumaha pami Nu Kiwari Pupus baé atuh?--Yusup_Ramdani ✉ 23 Juli 2015 06.34 (UTC)

Simkuring ogé panuju Nu Kiwari Pupus baé. --ilhamkang (sawala) 23 Juli 2015 14.15 (UTC)

Muhun kang, urang robih--Yusup_Ramdani ✉ 23 Juli 2015 14.28 (UTC)

Machine translation support to be enabled soon for Content Translation

Tolong bantu terjemahkan ke bahasa Anda

Hello, I wanted to give you a héads up that machine translation support for Sundanese is now réady to be extended to Content Translation (beta féature) using Yandex. It is scheduled to be made active on this Wikipedia on September 14, 2016. This service can be used when translating Wikipedia articles into Sundanese with Content Translation. To start using this service, pléase choose ‘’Yandex.Translate’’ from the ‘’Automatic Translation’’ dropdown menu that you see on the sidebar after you start translating an article. Please note, machine translation is available from all the languages that are supported by Yandex.Translate, but Content Translation can still be used in the usual manner for translating from all languages, with or without machine translation support. For more information, we request you to kindly take a look at the details about machine translation services in Content Translation and about Yandex translation services, including a summary of the legal contract. Please note, the translations made using Content Translation are also used to improve machine translation services.

We look forward to your feedback. You can reach us using the Project Talk page or phabricator ticket. This message could only be written in English and we will really appreciate if it can be translated into Sundanese for other users of this Wikipedia. Thank you. On behalf of WMF Language team: --Runa Bhattacharjee (sawala) 8 Séptémber 2016 13.53 (UTC)

Machine translation support enabled today for Content Translation

Tolong bantu terjemahkan ke bahasa Anda

Hello, machine translation support for Content Translation (beta féature) has now been extended and enabled for users of Sundanese Wikipedia using Yandex. It can be used when translating Wikipedia articles into Sundanese with Content Translation. To start using this service, pléase choose ‘’Yandex.Translate’’ from the ‘’Automatic Translation’’ dropdown menu that you see on the sidebar after you start translating an article. Please note, machine translation is available from all the languages that are supported by Yandex.Translate, but Content Translation can still be used in the usual manner for translating from all languages, with or without machine translation support.

Wikimedia Foundation’s Legal team and Yandex had collaborated earlier to work out an agreement that allows the use of Yandex.Translate without compromising Wikipedia’s policy of attribution of rights, privacy of our users and brand representation. Since November 2015, Yandex machine translation has been used for articles translated for Wikipedias in many languages. For more information, we request you to kindly take a look at the details about machine translation services in Content Translation and about Yandex translation services, including a summary of the legal contract. Please note, translations made using Content Translation are also used to improve machine translation services.

We have tested the service for use on the Sundanese Wikipedia, but there could be unknown problems that we are not aware of yet. Please do let us know on our Project Talk page or phabricator if you face any problems using Content Translation. This message is only in English and we will be very grateful if it could be translated into Sundanese for other users of this Wikipedia. Thank you. On behalf of WMF Language team: --Runa Bhattacharjee (WMF) (sawala) 15 Séptémber 2016 23.48 (UTC)

The Wikimedia Developer Summit wants you

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 incréase the participation of volunteer developers and other contributors déaling with extensions, apps, tools, bots, gadgets, and templates.

Important déadlines:

• 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!

More information: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit

Subscribe to weekly updates: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4

MKramer (WMF) (talk) 14 Oktober 2016 19.07 (UTC)

Developer Wishlist Survey: propose your ideas

At the Wikimedia Developer Summit, we decided to organize a Developer Wishlist Survey, and here we go:

https://www.mediawiki.org/wiki/Developer_Wishlist

The Wikimedia technical community seeks input from developers for developers, to créate a high-profile list of desired 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 idéas before the end of January, either by pushing existing tasks in Phabricator or by créating 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)

Developer Wishlist Survey: Vote for Proposals

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.

Voting phase starts now and will run until February 14th, 23:59 UTC. Click here on a category and show support for the proposals you care for most. Use the 'Vote' and 'Endorse' buttons next to a proposal to do so.

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 considered in the Wikimedia Foundation’s annual plan FY 2017-18 - SSethi_(WMF) (talk) 04:41, 6 February 2017 (UTC)

Wikipedia to the Moon: voting has begun

Hello, after six weeks of community discussion about Wikipedia to the Moon, there are now 10 different proposals for content for the mission. Starting today, you can vote for them on Meta-Wiki, and decide what we will work on: a Wikipedia canon, different lists, the Moon in 300 languages, an astronomy editathon, féatured articles, articles about technology, endangered things, or DNA-related topics. You can even vote against community involvement. Voting is open until 24 June. Sorry that this message is again in English only, but we are using village pumps to réach as many communities as possible, so that everyone knows they can vote. Best, Moon team at Wikimedia Deutschland 10 Juni 2016 15.31 (UTC)

Wikipedia to the Moon: invitation to edit

Three weeks ago, you were invited to vote on how to take Wikipedia articles to the Moon. Community voting is over and the winning idéa is to send all ‘’featured articles and lists’’ to the Moon. This decision means that, starting today, Wikipedians from all language communities are warmly invited to intensively work on their best articles and lists, and submit them to Wikipedia to the Moon. The central site to coordinate between communities will be Meta-Wiki. You will find an overview and more information there. Hopefully, we will be able to represent as many languages as possible, to show Wikipedia’s diversity. Please feel kindly invited to edit on behalf of your community and tell us about your work on featured content!

Best, Moon team at Wikimedia Deutschland 1 Juli 2016 14.10 (UTC)

Open call for Project Grants

Tolong bantu terjemahkan ke bahasa Anda:

Greetings! The Project Grants program is accepting proposals from July 1st to August 2nd to fund new tools, research, offline outreach (including editathon series, workshops, etc), online organizing (including contests), and other experiments that enhance the work of Wikimedia volunteers.

Whether you need a small or large amount of funds, Project Grants can support you and your team’s project development time in addition to project expenses such as materials, travel, and rental space.

• Submit a grant request or draft your proposal in IdeaLab
• Get help with your proposal in an upcoming Hangout session
• Learn from examples of completed Individual Engagement Grants or Project and Event Grants

Also accepting candidates to join the Project Grants Committee through July 15.

With thanks, I JethroBT (WMF) 5 Juli 2016 15.25 (UTC)

New Wikipedia Library accounts available now (August 2016)

Hello Wikimedians!

The TWL OWL says sign up today!

The Wikipedia Library is announcing signups today for free, full-access, accounts to published reséarch as part of our publisher donation program. You can now sign up for new accounts and reséarch materials from:

• Nomos – Primarily German-language publisher of law and social sciences books and journals - 25 accounts
• World Scientific – Scientific, technical, and medical journals - 50 accounts
• Edinburgh University Press – Humanities and social sciences journals - 25 accounts
• American Psychological Association – Psychology books and journals - 10 accounts
• Emerald – Journals on a range of topics including business, education, héalth care, and engineering - 10 accounts

Many other partnerships with accounts available are listed on our partners page, including Project MUSE, EBSCO, DeGruyter, Gale and Newspaperarchive.com.

Do better reséarch and help expand the use of high quality references across Wikipedia projects: sign up today!
--The Wikipedia Library Team 30 Agustus 2016 18.38 (UTC)

You can host and coordinate signups for a Wikipedia Library branch in your own language! Please contact Ocaasi (WMF).

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

New Wikipedia Library Accounts Available Now (November 2016)

Hello Wikimedians!

The TWL OWL says sign up today!

The Wikipedia Library is announcing signups today for free, full-access, accounts to published reséarch as part of our Publisher Donation Program. You can sign up for new accounts and reséarch materials from:

• Foreign Affairs - Journal of international relations and U.S. foreign policy
• OpenEdition - Journals in the social sciences and humanities
• Édition Diffusion Presse Sciences - French and English language scientific journals
• ASHA - Speech–language–héaring journals
• Tilastopaja - Athletics statistics

Expansions

• EBSCO - Many new databases added
• Taylor & Francis - Strategic, Defence & Security Studies collection

Many other partnerships with accounts available are listed on our partners page. Sign up today!
--The Wikipedia Library Team 1 Nopémber 2016 18.30 (UTC)

You can host and coordinate signups for a Wikipedia Library branch in your own language. Please contact Ocaasi (WMF).

This message was delivered via the Global Mass Message tool to The Wikipedia Library Global Delivery List.

New notification when a page is connected to Wikidata

Hello all,

(Tolong bantu terjemahkan ke bahasa Anda)

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.

Thanks go to Matěj Suchánek who developed this feature!

Hatur nuhun! Lea Lacroix (WMDE) (talk)

Wikidata changes now also appear in enhanced recent changes

Hello, and sorry to write this message in English. You can help translating it.

Starting from today, you will be able to display Wikidata changes in both modes of the recent changes and the watchlist.

Read and translate the full message

Hatur nuhun! Lea Lacroix (WMDE) 29 Juni 2017 08.33 (UTC)

(wrong target page? you can fix it here)

Improved search in deleted pages archive

Tolong bantu terjemahkan ke bahasa Anda

During Wikimedia Hackathon 2016, the Discovery team worked on one of the items on the 2015 community wishlist, namely enabling searching the archive of deleted pages. This feature is now ready for production deployment, and will be enabled on all wikis, except Wikidata.

Right now, the feature is behind a feature flag - to use it on your wiki, please go to the Special:Undelete page, and add &fuzzy=1 to the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=1. Then search for the pages you're interested in. There should be more results than before, due to using ElasticSearch indexing (via the CirrusSearch extension).

We plan to enable this improved search by default on all wikis soon (around August 1, 2017). If you have any objections to this - please raise them with the Discovery team via email or on this announcement's discussion page. Like most Mediawiki configuration parameters, the functionality can be configured per wiki. Once the improved search becomes the default, you can still access the old mode using &fuzzy=0 in the URL, like this: https://test.wikipedia.org/w/index.php?title=Special%3AUndelete&fuzzy=0

Please note that since Special:Undelete is an admin-only feature, this search capability is also only accessible to wiki admins.

Hatur nuhun! CKoerner (WMF) (talk) 25 Juli 2017 18.40 (UTC)

Improvements coming soon to Recent Changes

Hello

Sorry to use English. Tolong bantu terjemahkan ke bahasa Anda! Terima kasih.

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.

What is this feature again?

This feature improves Special:RecentChanges and Special:RecentChangesLinked (and soon, Special:Watchlist – see below).

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 colored 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 predictions. They identify real vandalism or good faith intent contributions that need help. They are not available on all wikis.

You can know more about this project by visiting the quick tour help page.

Concerning RecentChanges

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.

Some features will remain as Beta features and will be added later. Learn more about those different features.

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.

Please ping me if you have questions.

On behalf of the Global Collaboration team, Trizek (WMF) 14 Séptémber 2017 15.27 (UTC)

Global preferences available for testing

Apologies for writing in English. Tolong bantu terjemahkan ke bahasa Anda.

Greetings,

Global preferences, a highly request feature in the 2016 Community Wishlist, is available for testing.

1. Read over the help page, it is brief and has screenshots
2. Login or register an account on Beta English Wikipedia
3. Visit Global Preferences and try enabling and disabling some settings
4. Visit some other language and project test wikis such as English Wikivoyage, the Hebrew Wikipedia and test the settings
5. Report your findings, experience, bugs, and other observations

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) 27 Pébruari 2018 00.24 (UTC)

Notification from edit summary

Greetings,

The ability to notify other users in edit summaries will be available later this week, on 15 March 2018. Other users can be notified if a link to their user page is provided in an edit summary. Some user-made gadgets and scripts that automatically put user names in edit summaries may need to be changed to put a colon in the link, such as [[:User:Example]]. You can change how you receive these mention notifications in your preferences. This feature was highly requested in the 2017 Community Wishlist survey, and feedback is welcome.

Thanks, happy editing to you. -Keegan (WMF) (talk) 12 Maret 2018 21.09 (UTC)

We need your feedback to improve Lua functions

Hello,

(I’m sorry for writing in English. Tolong bantu terjemahkan ke bahasa Anda)

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 preferred language.

Hatur nuhun! Lea Lacroix (WMDE) 27 Maret 2018 08.56 (UTC)

Time to bring embedded maps (‘mapframe’) to most Wikipedias

Time to bring embedded maps (‘mapframe’) to most Wikipedias

Tolong bantu terjemahkan ke bahasa Anda

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!

CKoerner (WMF) (talk) 24 April 2018 21.38 (UTC)

Wikitext highlighting out of beta

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)

4 Méi 2018 18.55 (UTC)

Improvements coming soon on Watchlists

Hello

Sorry to use English. Tolong bantu terjemahkan ke bahasa Anda! Terima kasih.

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.

What is this feature again?

This feature is used by default on Special:RecentChanges, Special:RecentChangesLinked and as a Beta feature on Special:Watchlist.

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 colored 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 predictions. They identify real vandalism or good faith intent contributions that need help. They are not available on all wikis.

You can know more about this project by visiting the quick tour help page.

About the release on Watchlists

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.

On behalf of the Collaboration team, Trizek (WMF) 7 Juni 2018 13.14 (UTC)

Update on page issues on mobile web

Update on page issues on mobile web

Tolong bantu terjemahkan ke bahasa Anda 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.

So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:

• 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.

CKoerner (WMF) (talk) 12 Juni 2018 20.58 (UTC)

Tidy to RemexHtml

The Parsing team will be replacing Tidy with RemexHtml at this wiki on 5 July 2018.

Some pages at this wiki use outdated HTML. This change may change the appearance of those pages. Special:LintErrors has a complete list of affected pages.

Read this e-mail message for more information. Read the instructions at mw:Help:Extension:Linter. You can ask questions at mw:Talk:Parsing/Replacing Tidy. Thank you for helping fix these problems.

m:User:Elitre (WMF) 2 Juli 2018 14.38 (UTC)

Consultation on the creation of a separate user group for editing sitewide CSS/JS

(Tolong bantu terjemahkan ke bahasa Anda)

Hi all,

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!

Thanks!
Tgr (talk) 9 Juli 2018 10.50 (UTC) (via global message delivery)

Technical Advice IRC Meeting

We'd like to invite you to the weekly Technical Advice IRC meeting. The Technical Advice IRC Meeting (TAIM) is a weekly support event for volunteer developers. Every Wednesday, two full-time developers are available to help you with all your questions about Mediawiki, gadgets, tools and more! This can be anything from "how to get started" and "who would be the best contact for X" to specific questions on your project.

The Technical Advice IRC meeting is every Wednesday 3-4 pm UTC as well as on every first Wednesday of the month 11-12 pm UTC.

If you already know what you would like to discuss or ask, please add your topic to the next meeting: Technical Advice IRC meeting

Cheers, -- Michael Schönitzer (WMDE) (talk) 14:27, 30 July 2018 (UTC)

Enabling a helpful feature for Template editors

Hello.

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.

You can learn more about TemplateStyles on MediaWiki.org. Technical documentation is also available.

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.

Thank you.

CKoerner (WMF) (talk) 6 Agustus 2018 21.28 (UTC)

Wikidata Bridge: edit Wikidata’s data from Wikipedia infoboxes

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 stored 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)
  • but we also welcome also communities who volunteer to be part of the first test round.
  • 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:

• Read and help translating the documentation pages
• Follow the updates and participate in the first feedback loop
• Talk about it with your local community

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.

Thanks for your attention, Lea Lacroix (WMDE) 24 Juni 2019 13.03 (UTC)

Wikipédia basa Sunda atawa Wikipédia Sunda?

Aya kamandang yén ngaran Wikipédia basa Sunda diganti jadi Wikipédia Sunda sangkan leuwih ringkes, sarta Wikipédia basa séjén saperti basa Jawa jeung basa Minangkabau ogé geus ngaganti ngaranna jadi Wikipédia Jawa jeung Wikipédia Minangkabau. Salian ti éta, dileungitkeunna kecap "basa" ogé sangkan ieu wikipédia bisa ngawengku réa hal, utamana ngeunaan Sunda, saperti budaya Sunda, jeung sajabana. Kumaha kamandang sadérék ngeunaan hal ieu? --A2613 (sawala) 12 Juli 2019 02.56 (UTC)

• Satuju Satuju dirobah jadi Wikipédia Sunda Harditaher (sawala) 12 Juli 2019 03.12 (UTC)
• Satuju Haméh teu panyang teuing.--yusup_ramdani ✉ 12 Juli 2019 04.05 (UTC)
• Satuju kumincir (sawala) 12 Juli 2019 04.15 (UTC)
• Satuju ilhamkang (sawala) 2 Séptémber 2019 04.13 (UTC)

Google Code-In will soon take place again! Mentor tasks to help new contributors!

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 5 Nopémber 2019 07.28 (UTC)

‎Improving the translation support for the Sundanese Wikipedia

Hi!

Content translation has been successful in supporting the translation process on many Wikipedia communities, and we want to help additional wikis with potential to grow using translation as part of a new initiative.

Content translation facilitates the creation of Wikipedia articles by translating content from other languages. It has been used already to create more than half a million articles. In addition, the tool provides mechanisms to encourage the creation of good quality content, preventing the publication of lightly edited machine translations. In general, our analysis shows that the translations produced are less likely to be deleted than the articles started from scratch.

Sundanese Wikipedia editors have used Content translation to create more than three hundred articles. Given the size of the editing community, we think that there is potential to use translation to create more articles, expand existing ones, and attract new editors that learn how to make productive edits. Translation can help the community to reduce the language gap with other languages and grow the number of editors in a sustainable way. In order to achieve this goal, we want to collaborate with you to make Content translation more visible in the Sundanese Wikipedia and support new ways to translate.

As a first step, during the next weeks we plan to enable Content translation by default on the Sundanese Wikipedia. That will make it easy for users to discover the tool through several entry points. However, users not interested in translation will still be able to disable it from their preferences.

Please feel free to share any comment in this conversation thread.

Thanks! --Amir E. Aharoni (WMF) (sawala) 3 Agustus 2020 12.45 (UTC)

Hello everyone. We have enabled Content translation by default on the Sundanese Wikipedia.

Now it is easy for users to discover the tool through several entry points. However, users not interested in translation can disable it from their preferences.

We expect this will help translators to create more content of good quality in Sundanese. We’ll be monitoring the statistics for Sundanese as well as the list of articles created with the tool. Content translation provides quality control mechanisms to prevent the abuse of machine translation and the limits can be adjusted based on the needs of each community. Please, feel free to share your impressions about the content created and how the tool works for the community. This feedback is essential to improve the tool to better support your needs.

Thanks! --Amir E. Aharoni (WMF) (sawala) 11 Agustus 2020 12.00 (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) 16 Pébruari 2021 17.45 (UTC)

Coolest Tool Award 2021: Call for nominations

The third edition of the m:Coolest Tool Award is looking for nominations!

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.

The awarded projects will be announced and showcased in a virtual ceremony in December. Deadline to submit nominations is October 27. More information: m:Coolest Tool Award. Thanks for your recommendations! -- SSethi (WMF) for the 2021 Coolest Tool Academy team 19 Oktober 2021 05.57 (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.

Translate important messages

Promote the Survey 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.

Why are we asking?

• We have improved the documentation. It's friendlier and easier to use. This will mean little if it's only 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) 29 Désémber 2021 03.15 (UTC)

Save the Date: Coolest Tool Award 2021: this Friday, 17:00 UTC

<languages />

Hello all,

The ceremony of the 2021 Wikimedia Coolest Tool Award will take place virtually on Friday 14 January 2022, 17:00 UTC.

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!

Read more about the livestream and the discussion channels.

Thanks for joining! andre (talk) -08:02, 6 January 2022 (UTC)

Last two days for submitting proposals

Tomorrow is the last day for submitting proposals for the Community Wishlist Survey 2022.

Also, everyone is welcome to translate, promote, and discuss proposals. SGrabarczuk (WMF) (talk) 22 Januari 2022 14.45 (UTC)

Rollout of the new audio and video player

Tolong bantu terjemahkan ke bahasa Anda

Hello,

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.

You can track the work in T100106

Thank you, Amir 17 Pébruari 2022 17.59 (UTC)

Coolest Tool Award 2022: Call for nominations

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.

MediaWiki message delivery 3 Oktober 2022 18.30 (UTC)

Join the Coolest Tool Award 2022: Friday, Dec 16th, 17:00 UTC

The fourth edition of the Wikimedia Coolest Tool Award will happen online on Friday 16 December 2022 at 17:00 UTC!

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!

Read more about the livestream and the discussion channels.

Thanks for joining! -Komla

MediaWiki message delivery 5 Désémber 2022 18.53 (UTC)

Graph extension disabled

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

--MediaWiki message delivery (sawala) 19 April 2023 17.36 (UTC)

Automatic citations based on ISBN are broken

Apologies if this message does not reach you in your favorite language. You can help translate it centrally at Meta. Thanks for your help.

We have recently become unable to access the WorldCat API which provided the ability to generate citations using ISBN numbers. The Wikimedia Foundation's Editing team is investigating several options to restore the functionality, but will need to disable ISBN citation generation for now.

This affects citations made with the VisualEditor Automatic tab, and the use of the citoid API in gadgets and user scripts, such as the autofill button on refToolbar. Please note that all the other automatic ways of generating citations, including via URL or DOI, are still available.

You can keep updated on the situation via Phabricator, or by reading the next issues of m:Tech News. If you know of any users or groups who rely heavily on this feature (for instance, someone who has an upcoming editathon), I'd appreciate it if you shared this update with them.

Elitre (WMF), on behalf of the Editing team.

MediaWiki message delivery (sawala) 11 Méi 2023 19.45 (UTC)