Wikilibres:La tavèrna

(Sorry for writing in English. You can translate the proposal.)

Should X!'s edit counter retain the opt-in requirement? Your input is strongly encouraged. Voice your input here.——cyberpower ^Chat_Automation 23 de junh de 2013 a 04.51 (UTC)

Distributed via Global message delivery. (Wrong page? Fix here.)

On July 9, 2013, Universal Language Selector (ULS) will be enabled on this wiki. The ULS provides a flexible way to configure and deliver language settings like interface language, fonts, and input methods (keyboard mappings). Making it available here is the last phase of making ULS available on all Wikimedia wikis.

Please read the announcement on Meta-Wiki for more information. Siebrand 4 de julhet de 2013 a 12.48 (UTC) (via Global message delivery).

First, I’d like to apologize for the English. If you can, please help to translate this for other members of your community.

The legal team at the Wikimedia Foundation would greatly appreciate your input on the best way to manage the "community logo" (pictured here) to best balance protection of the projects with community support. Accordingly, they have created a “request for consultation” on Meta where they set out briefly some of the issues to be considered and the options that they perceive. Your input would be invaluable in helping guide them in how best to serve our mission.

Thank you! --Mdennis (talk) (via the Global message delivery system). 24 de setembre de 2013 a 02.59 (UTC) (wrong page? You can fix it.)

Hi all,

Please join the consultation about the Community logo that represents Meta-Wiki: m:Community Logo/Request for consultation.

This community consultation was commenced on September 24. The following day, two individuals filed a legal opposition against the registration of the Community logo.

The question is whether the Wikimedia Foundation should seek a collective membership mark with respect to this logo or abandon its registration and protection of the trademark.

We want to make sure that everyone get a chance to speak up so that we can get clear direction from the community. We would therefore really appreciate the community's help in translating this announcement from English so that everyone is able to understand it.

Thanks, Geoff & Yana 8 d'octobre de 2013 a 20.40 (UTC)

Hi all,

The Wikimedia legal team invites you to participate in the development of the new Wikimedia trademark policy.

The current trademark policy was introduced in 2009 to protect the Wikimedia marks. We are now updating this policy to better balance permissive use of the marks with the legal requirements for preserving them for the community. The new draft trademark policy is ready for your review here, and we encourage you to discuss it here.

We would appreciate if someone would translate this message into your language so more members of your community can contribute to the conversation.

Thanks,
Yana & Geoff

Hello all,

Please join a discussion about a proposed amendment to the Wikimedia Terms of Use regarding undisclosed paid editing and we encourage you to voice your thoughts there. Please translate this statement if you can, and we welcome you to translate the proposed amendment and introduction. Please see the discussion on Meta Wiki for more information. Thank you! Slaporte (WMF) 21 de febrièr de 2014 a 22.00 (UTC)

Please notice the correct direct link to access Foncionalitats bèta is this one. Thanks for your understanding! Elitre (WMF) 21 de novembre de 2014 a 18.35 (UTC)

Did you know?

Basic table editing is now available in VisualEditor. You can add and remove rows and columns from tables at the click of a button.

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 table editing and performance. Their weekly status reports are posted on mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

VisualEditor was deployed to several hundred remaining wikis as an opt-in beta feature at the end of November, except for most Wiktionaries (which depend heavily upon templates) and all Wikisources (which await integration with ProofreadPage).

Basic support for editing tables is now available. You can add and delete tables, add and remove rows and columns, set or remove a caption for a table, and merge cells together. To change the contents of a cell, double-click inside it. More features will be added in the coming months. In addition, VisualEditor now ignores broken, invalid rowspan and colspan elements, instead of trying to repair them.

You can now use find and replace in VisualEditor, reachable through the tool menu or by pressing ^ Ctrl+F or ⌘ Cmd+F.

You can now create and edit simple <blockquote> paragraphs for quoting and indenting content. This changes a "Paragraf" into a "Blòt de citacion".

Some new keyboard sequences can be used to format content. At the start of the line, typing "* " will make the line a bullet list; "1." or "#" will make it a numbered list; "==" will make it a section heading; ": " will make it a blockquote. If you didn't mean to use these tools, you can press undo to undo the formatting change.

There are also two other keyboard sequences: "[[" for opening the link tool, and "{{" for opening the template tool, to help experienced editors. The existing standard keyboard shortcuts, like ^ Ctrl+K to open the link editor, still work.

If you add a category that has been redirected, then VisualEditor now adds its target. Categories without description pages show up as red.

You can again create and edit galleries as wikitext code.

The current VisualEditor design will be replaced with a new theme designed by the User Experience group. The new theme will be visible for desktop systems at mediawiki.org in late December and on other sites in early January. (You can see a developer preview of the old "Apex" theme and the new "MediaWiki" one which will replace it.)

The Editing team plans to add auto-fill features for citations in January.

Planned changes to the media search dialog will make choosing between possible images easier.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Translations of the user guide for most languages are outdated. Only Ukrainian, Portuguese, Spanish, French, and Dutch translations are nearly current. Please help complete the current translations for users who speak your language.
• Talk to the Editing team during the office hours via IRC. The next session is on Wednesday, 7 January 2015 at 22:00 UTC.
• File requests for language-appropriate "Gras" and "Italica" icons for the character formatting menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• If you would like to help with translations of this newsletter, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Subscribe or unsubscribe at Meta. Thank you!

— Elitre (WMF)

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appearance, 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 ready 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 President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features 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 ready 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 breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.

The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design team. Several new versions of the OOjs UI library have also been released, and these also affect the appearance 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.)

Search 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. Please include a link to a community discussion about the requested change.

The Editing team will soon add auto-fill features for citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating 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 each 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 speak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Please 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.

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Please help complete translations of the user guide for users who speak 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 learn more about this initiative.
• Talk to the Editing team 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, please subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

— Elitre (WMF)

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 make 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, each 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. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

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 team is slowly adding auto-fill features 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 creating 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 each website.

Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please 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 Korean 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" model. Images in the search 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 easier to see more details in images.

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

The pop-up window that appears 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 team 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 headings.

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

The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating 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 team 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)

• Share your ideas and ask questions at mw:VisualEditor/Feedback.
• Can you translate from English into any other language? Please 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 research team wants to see how real editors work. Please sign up for their research program.
• File requests for language-appropriate "Gras" and "Italica" 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 reading this in your favorite language, then please 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 ready. Thank you!

— Elitre (WMF)

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 created 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 learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Auto-fill features 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 created 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 meaningful 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). Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared 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 each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter. (T70425)

Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" each time they want to add another parameter. (T95696) The team added a new property for TemplateData, "Exemple", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (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 feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released 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.

• Share your ideas 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). Learn 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. Instead, 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 please contact James Forrester.
• If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The team is planning the second VisualEditor-related "translathon" for July. Please 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 reading this in your favorite language, then please 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 ready. Thank you!

— Elitre (WMF)

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 created 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 learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Auto-fill features 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 created 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 meaningful 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). Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared 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 each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter. (T70425)

Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "⧼visualeditor-dialog-transclusion-add-param⧽" each time they want to add another parameter. (T95696) The team added a new property for TemplateData, "Exemple", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter. (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 feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released 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.

• Share your ideas 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). Learn 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. Instead, 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 please contact James Forrester.
• If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The team is planning the second VisualEditor-related "translathon" for July. Please 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 reading this in your favorite language, then please 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 ready. Thank you!

— Elitre (WMF)

Apologies for writing in English.

Hi everyone.

Over the last few years, the Wikimedia Foundation has been working towards enabling HTTPS by default for all users, including unregistered ones, for better privacy and security for both readers and editors. This has taken a long time, as there were different aspects to take into account. Our servers haven't been ready 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 already 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 already had to log in through HTTPS. We'll keep an eye on this to make 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)

Apologies for writing in English.

Hi everyone.

Over the last few years, the Wikimedia Foundation has been working towards enabling HTTPS by default for all users, including unregistered ones, for better privacy and security for both readers and editors. This has taken a long time, as there were different aspects to take into account. Our servers haven't been ready 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 already 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 already had to log in through HTTPS. We'll keep an eye on this to make 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)

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

You can read and help translate the user guide, which has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mediawiki.org if you can help.
• If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
• Please file requests for language-appropriate "Gras" and "Italica" icons for the styling menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn 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 Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please 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 ready. Thank you!

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

You can read and help translate the user guide, which has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%). There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. We thank the translators for participating and the translatewiki.net staff for facilitating this initiative.

Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.

The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

• Share your ideas and ask questions at mw:VisualEditor/Feedback. This feedback page is now using Flow instead of LiquidThreads.
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mediawiki.org if you can help.
• If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
• Please file requests for language-appropriate "Gras" and "Italica" icons for the styling menu in Phabricator.
• The design research team wants to see how real editors work. Please sign up for their research program.
• The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn 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 Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please 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 ready. Thank you!

Hi everyone,

Many Wikimedia projects already have access to Wikidata and make good use of it to improve their content. You already have access to the interwiki link part of Wikidata. I wanted to let you know that your project will be among the next to receive access to the actual data on Wikidata. It is currently scheduled for September 22nd. From then on you can use data from Wikidata either via the property parser function or Lua.

I hope we'll be able to support you well with structured data. If you have questions please come to d:Wikidata:Wikibooks.

Cheers Lydia Pintscher (WMDE) 9 de setembre de 2015 a 16.12 (UTC)

A while ago I announced that you'll be among the next projects to get access to Wikidata's data. This has now happened. You can access the data via a parser function (#property) and Lua. For more information and to ask questions please come to d:Wikidata:Wikibooks.

I hope you'll be able to do great things with this and that it will make your life easier in the long-run.

Cheers Lydia Pintscher (WMDE) 22 de setembre de 2015 a 15.48 (UTC)

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

You can use the visual editor on smartphones and tablets.

Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "Canvia a edició visual".

The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.

Educational features: The first time ever you use the visual editor, it now draws your attention to the Ligam and ⧼visualeditor-toolbar-cite-label⧽ tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.

Links: It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108, T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558) These "magic links" use a custom link editing tool.

Uploads: Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Inserir Supòrt" tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.

Mobile: Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use it on all devices regardless of size if they wish. (T85630) Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "Suprimir" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.

Rich editing tools: You can now add and edit sheet music in the visual editor. (T112925) There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227, T113354) When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.

On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.

You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "Modificar" and "Modificar lo còdi" tabs into a single "Modificar" tab, similar to the system already used on the mobile website. The "Modificar" tab will open whichever editing environment you used last time.

• Share your ideas and ask questions at VisualEditor/Feedback. This feedback page uses Flow for discussions.
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).
• Local admins can set up the Citoid automatic reference feature for your wiki. If you need help, then please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.
• The weekly task triage meetings are open to volunteers. Learn 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, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please 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 ready. Thank you!

Hi everyone! Apologies for posting in English. Translations are very welcome.

The Community Tech team at the Wikimedia Foundation is focused on building improved curation and moderation tools for experienced Wikimedia contributors. We're now starting a Community Wishlist Survey to find the most useful projects that we can work on.

For phase 1 of the survey, we're inviting all active contributors to submit brief proposals, explaining the project that you'd like us to work on, and why it's important. Phase 1 will last for 2 weeks. In phase 2, we'll ask you to vote on the proposals. Afterwards, we'll analyze the top 10 proposals and create a prioritized wishlist.

While most of this process will be conducted in English, we're inviting people from any Wikimedia wiki to submit proposals. We'll also invite volunteer translators to help translate proposals into English.

Your proposal should include: the problem that you want to solve, who would benefit, and a proposed solution, if you have one. You can submit your proposal on the Community Wishlist Survey page, using the entry field and the big blue button. We will be accepting proposals for 2 weeks, ending on November 23.

We're looking forward to hearing your ideas!

Hi everyone! Apologies for posting this in English. Translations are very welcome.

We're beginning the second part of the Community Tech team's Community Wishlist Survey, and we're inviting all active contributors to vote on the proposals that have been submitted.

Thanks to you and other Wikimedia contributors, 111 proposals were submitted to the team. We've split the proposals into categories, and now it's time to vote! You can vote for any proposal listed on the pages, using the {{Support}} tag. Feel free to add comments pro or con, but only support votes will be counted. The voting period will be 2 weeks, ending on December 14.

The proposals with the most support votes will be the team's top priority backlog to investigate and address. Thank you for participating, and we're looking forward to hearing what you think!

Community Tech via

Hi everyone! Apologies for posting this in English. Translations are very welcome.

We're beginning the second part of the Community Tech team's Community Wishlist Survey, and we're inviting all active contributors to vote on the proposals that have been submitted.

Thanks to you and other Wikimedia contributors, 111 proposals were submitted to the team. We've split the proposals into categories, and now it's time to vote! You can vote for any proposal listed on the pages, using the {{Support}} tag. Feel free to add comments pro or con, but only support votes will be counted. The voting period will be 2 weeks, ending on December 14.

The proposals with the most support votes will be the team's top priority backlog to investigate and address. Thank you for participating, and we're looking forward to hearing what you think!

Community Tech via

Did you know?

A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.

If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Special:Preferences and choosing the setting that you want:

The current plan is for the default setting to have the Edit button open the editing environment you used most recently.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Read this in another language • Subscription list for this multilingual newsletter

Since the last newsletter, the visual editor team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.

You can switch from the wikitext editor to the visual editor after you start editing. The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.

The single edit tab project will combine the "Modificar" and "Modificar lo còdi" tabs into a single "Modificar" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Modificar" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the Fenèstra de modificacion tab of Special:Preferences in the drop-down menu about "Onglets de modificacion:".

The visual editor will be offered to all editors at the following Wikipedias in early 2016: Amharic, Buginese, Min Dong, Cree, Manx, Hakka, Armenian, Georgian, Pontic, Serbo-Croatian, Tigrinya, Mingrelian, Zhuang, and Min Nan. (T116523) Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. The developers would like to know how well it works. Please tell them what kind of computer, web browser, and keyboard you are using.

In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)

• Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
  • Se remembrar del darrièr editor utilizat,
  • Sempre fes servir l’editor visual si és possible,
  • Totjorn utilizar l’editor en mòde font, and
  • Afichar los dos onglets de modificacion. (This is the current state for people already using the visual editor. None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).

If you aren't reading this in your favorite language, then please 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 ready. Mercés !

Did you know?

A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.

If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Special:Preferences and choosing the setting that you want:

The current plan is for the default setting to have the Edit button open the editing environment you used most recently.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Read this in another language • Subscription list for this multilingual newsletter

Since the last newsletter, the visual editor team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.

You can switch from the wikitext editor to the visual editor after you start editing. The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.

The single edit tab project will combine the "Modificar" and "Modificar lo còdi" tabs into a single "Modificar" tab, like the system already used on the mobile website. (T102398, T58337) Initially, the "Modificar" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the Fenèstra de modificacion tab of Special:Preferences in the drop-down menu about "Onglets de modificacion:".

The visual editor will be offered to all editors at the following Wikipedias in early 2016: Amharic, Buginese, Min Dong, Cree, Manx, Hakka, Armenian, Georgian, Pontic, Serbo-Croatian, Tigrinya, Mingrelian, Zhuang, and Min Nan. (T116523) Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. The developers would like to know how well it works. Please tell them what kind of computer, web browser, and keyboard you are using.

In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)

• Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
  • Se remembrar del darrièr editor utilizat,
  • Sempre fes servir l’editor visual si és possible,
  • Totjorn utilizar l’editor en mòde font, and
  • Afichar los dos onglets de modificacion. (This is the current state for people already using the visual editor. None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
• Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).

If you aren't reading this in your favorite language, then please 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 ready. Mercés !

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Among experienced editors, the visual editor's table editing is one of the most popular features.

If you select the top of a column or the end of a row, you can quickly insert and remove columns and rows.

Now, you can also rearrange columns and rows. Click "Move before" or "Move after" to swap the column or row with its neighbor.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Japanese, Korean, Arabic, Indic, and Han scripts, and improving the single edit tab interface.

You can switch from the wikitext editor to the visual editor after you start editing. This function is available to nearly all editors at most wikis except the Wiktionaries and Wikisources.

Many local feedback pages for the visual editor have been redirected to mw:VisualEditor/Feedback.

You can now re-arrange columns and rows in tables, as well as copying a row, column or any other selection of cells and pasting it in a new location.

The formula editor has two options: you can choose "Quick edit" to see and change only the LaTeX code, or "Edit" to use the full tool. The full tool offers immediate preview and an extensive list of symbols.

The single edit tab project will combine the "Modificar" and "Modificar lo còdi" tabs into a single "Modificar" tab. This is similar to the system already used on the mobile website. (T102398) Initially, the "Modificar" tab will open whichever editing environment you used last time. Your last editing choice will be stored as an account preference for logged-in editors, and as a cookie for logged-out users. Logged-in editors will have these options in the Fenèstra de modificacion tab of Special:Preferences:

• Se remembrar del darrièr editor utilizat,
• Sempre fes servir l’editor visual si és possible,
• Totjorn utilizar l’editor en mòde font, and
• Afichar los dos onglets de modificacion. (This is the state for people using the visual editor now.)

The visual editor uses the same search engine as Special:Search to find links and files. This search will get better at detecting typos and spelling mistakes soon. These improvements to search will appear in the visual editor as well.

The visual editor will be offered to all editors at most "Phase 6" Wikipedias during the next few months. This will affect the following languages, amongst others: Japanese, Korean, Urdu, Persian, Arabic, Tamil, Marathi, Malayalam, Hindi, Bengali, Assamese, Thai, Aramaic.

• Please try out the newest version of the single edit tab on test2.wikipedia.org. You may need to restore the default preferences (at the bottom of test2wiki:Special:Preferences) to see the initial prompt for options. Were you able to find a preference setting that will work for your own editing? Did you see the large preferences dialog box when you started editing an article there?
• Can you read and type in Korean, Arabic, Japanese, Indic, or Han scripts? Does typing in these languages feels natural in the visual editor? Language engineer David Chan needs to know. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org.
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Join the Tech Talk about "Automated citations in Wikipedia: Citoid and the technology behind it" with Sebastian Karcher on 29 February 2016.

If you aren't reading this in your favorite language, then please 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 ready. Mercés !

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

It's quick and easy to insert a references list.

Place the cursor where you want to display the references list (usually at the bottom of the page). Open the "Inserir" menu and click the "Lista de referéncias" icon (three books).

If you are using several groups of references, which is relatively rare, you will have the opportunity to specify the group. If you do that, then only the references that belong to the specified group will be displayed in this list of references. Finally, click "Inserir" in the dialog to insert the Lista de referéncias. This list will change as you add more footnotes to the page.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs. Their workboard is available in Phabricator. Their current priorities are improving support for Arabic and Indic scripts, and adapting the visual editor to the needs of the Wikivoyages and Wikisources.

The visual editor is now available to all users at most Wikivoyages. It was also enabled for all contributors at the French Wikinews.

The single edit tab feature combines the "Modificar" and "Modificar lo còdi" tabs into a single "Modificar" tab. It has been deployed to several Wikipedias, including Hungarian, Polish, English and Japanese Wikipedias, as well as to all Wikivoyages. At these wikis, you can change your settings for this feature in the "Fenèstra de modificacion" tab of Special:Preferences. The team is now reviewing the feedback and considering ways to improve the design before rolling it out to more people.

The "Salvar" button will say "Publicar la pagina". This will affect both the visual and wikitext editing systems. More information is available on Meta.

The visual editor will be offered to all editors at the remaining "Phase 6" Wikipedias during the next few months. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including: Arabic, Hindi, Thai, Tamil, Marathi, Malayalam, Urdu, Persian, Bengali, Assamese, Aramaic and others.

The team is working with the volunteer developers who power Wikisource to provide the visual editor there, for opt-in testing right now and eventually for all users. (T138966)

The team is working on a modern wikitext editor. It will look like the visual editor, and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices around September 2016. You can read about this project in a general status update on the Wikimedia mailing list.

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.
• Learn how to improve the "automagical" citoid referencing system in the visual editor, by creating Zotero translators for popular sources in your language! Watch the Tech Talk by Sebastian Karcher for more information.

If you aren't reading this in your preferred language, then please 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 ready. Mercés !

The Editing team is planning to change the name of the “Salvar” button to “Publicar la pagina” and “Publicar las modificacions”. “Publicar la pagina” will be used when you create a new page. “Publicar las modificacions” will be used when you change an existing page. The names will be consistent in all editing environments.[17][18]

This change will probably happen during the week of 30 August 2016. The change will be announced in Tech News when it happens.

If you are fluent in a language other than English, please check the status of translations at translatewiki.net for “Publicar la pagina” and “Publicar las modificacions”.

The main reason for this change is to avoid confusion for new editors. Repeated user research studies with new editors have shown that some new editors believed that “Salvar” would save a private copy of a new page in their accounts, rather than permanently publishing their changes on the web. It is important for this part of the user interface to be clear, since it is difficult to remove public information after it is published. We believe that the confusion caused by the “Salvar” button increases the workload for experienced editors, who have to clean up the information that people unintentionally disclose, and report it to the functionaries and stewards to suppress it. Clarifying what the button does will reduce this problem.

Beyond that, the goal is to make all the wikis and languages more consistent, and some wikis made this change many years ago. The Legal team at the Wikimedia Foundation supports this change. Making the edit interface easier to understand will make it easier to handle licensing and privacy questions that may arise.

Any help pages or other basic documentation about how to edit pages will also need to be updated, on-wiki and elsewhere. On wiki pages, you can use the wikitext codes {{int:Publishpage}} and {{int:Publishchanges}} to display the new labels in the user's preferred language. For the language settings in your account preferences, these wikitext codes produce “Publicar la pagina” and “Publicar las modificacions”.

Please share this news with community members who teach new editors and with others who may be interested.

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can easily re-arrange columns and rows in the visual editor?

Select a cell in the column or row that you want to move. Click the arrow at the start of that row or column to open the dropdown menu (shown). Choose either "Move before" or "Move after" to move the column, or "Move above" or "Move below" to move the row.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has mainly worked on a new wikitext editor. They have also released some small features and the new map editing tool. Their workboard is available in Phabricator. You can find links to the list of work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, releasing the 2017 wikitext editor as a beta feature, and improving language support.

• You can now set text as small or big.[19]
• Invisible templates have been shown as a puzzle icon. Now, the name of the invisible template is displayed next to the puzzle icon.[20] A similar feature will display the first part of hidden HTML comments.[21]
• Categories are displayed at the bottom of each page. If you click on the categories, the dialog for editing categories will open.[22]
• At many wikis, you can now add maps to pages. Go to the Insert menu and choose the "Maps" item. The Discovery department is adding more features to this area, like geoshapes. You can read more at mediawiki.org.[23]
• The "Save" button now says "Save page" when you create a page, and "Save changes" when you change an existing page.[24] In the future, the "Salvar" button will say "Publicar la pagina". This will affect both the visual and wikitext editing systems. More information is available on Meta.
• Image galleries now use a visual mode for editing. You can see thumbnails of the images, add new files, remove unwanted images, rearrange the images by dragging and dropping, and add captions for each image. Use the "Options" tab to set the gallery's display mode, image sizes, and add a title for the gallery.[25]

The visual editor will be offered to all editors at the remaining 10 "Phase 6" Wikipedias during the next month. The developers want to know whether typing in your language feels natural in the visual editor. Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. This will affect several languages, including Thai, Burmese and Aramaic.

The team is working on a modern wikitext editor. The 2017 wikitext editor will look like the visual editor and be able to use the citoid service and other modern tools. This new editing system may become available as a Beta Feature on desktop devices in October 2016. You can read about this project in a general status update on the Wikimedia mailing list.

• Do you teach new editors how to use the visual editor? Did you help set up the Citoid automatic reference feature for your wiki? Have you written or imported TemplateData for your most important citation templates? Would you be willing to help new editors and small communities with the visual editor? Please sign up for the new VisualEditor Community Taskforce.

• If you aren't reading this in your preferred language, then please 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 ready. Mercés !

—Elitre (WMF)

Summary: There's a new opt-in Beta Feature of a wikitext mode for the visual editor. Please go try it out.

We in the Wikimedia Foundation's Editing department are responsible for making editing better for all our editors, new and experienced alike. We've been slowly improving the visual editor based on feedback, user tests, and feature requests. However, that doesn't work for all our user needs: whether you need to edit a wikitext talk page, create a template, or fix some broken reference syntax, sometimes you need to use wikitext, and many experienced editors prefer it.

Consequently, we've planned a "wikitext mode" for the visual editor for a long time. It provides as much of the visual editor's features as possible, for those times that you need or want wikitext. It has the same user interface as the visual editor, including the same toolbar across the top with the same buttons. It provides access to the citoid service for formatting citations, integrated search options for inserting images, and the ability to add new templates in a simple dialog. Like in the visual editor, if you paste in formatted text copied from another page, then formatting (such as bolding) will automatically be converted into wikitext.

All wikis now have access to this mode as a Beta Feature. When enabled, it replaces your existing wikitext editor everywhere. If you don't like it, you can reverse this at any time by turning off the Beta Feature in your preferences. We don't want to surprise anyone, so it's strictly an opt-in-only Beta Feature. It won't switch on automatically for anyone, even if you have previously checked the box to "Activar automaticament totas las novèlas foncionalitats en bèta".

The new wikitext edit mode is based on the visual editor, so it requires JavaScript (as does the current wikitext editor). It doesn't work with gadgets that have only been designed for the older one (and vice versa), so some users will miss gadgets they find important. We're happy to work with gadget authors to help them update their code to work with both editors. We're not planning to get rid of the current main wikitext editor on desktop in the foreseeable future. We're also not going to remove the existing ability to edit plain wikitext without JavaScript. Finally, though it should go without saying, if you prefer to continue using the current wikitext editor, then you may so do.

This is an early version, and we'd love to know what you think so we can make it better. Please leave feedback about the new mode on the feedback page. You may write comments in any language. Thank you.

Voting has begun for eligible voters in the 2017 elections for the Wikimedia Foundation Board of Trustees.

The Wikimedia Foundation Board of Trustees is the ultimate governing authority of the Wikimedia Foundation, a 501(c)(3) non-profit organization registered in the United States. The Wikimedia Foundation manages many diverse projects such as Wikipedia and Commons.

The voting phase lasts from 00:00 UTC May 1 to 23:59 UTC May 14. Click here to vote. More information on the candidates and the elections can be found on the 2017 Board of Trustees election page on Meta-Wiki.

On behalf of the Elections Committee,
Katie Chan, Chair, Wikimedia Foundation Elections Committee
Joe Sutherland, Community Advocate, Wikimedia Foundation

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can review your changes visually?

When you are finished editing the page, type your edit summary and then choose "Revisar vòstras modificacions".

In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.

Click the toggle button to switch between visual and wikitext diffs.

The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history. You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has spent most of their time supporting the 2017 wikitext editor mode which is available inside the visual editor as a Beta Feature, and adding the new visual diff tool. Their workboard is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor as a beta feature, and improving the visual diff tool.

• A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#mw-prefsection-betafeatures to enable the ⧼Visualeditor-preference-newwikitexteditor-label⧽.
• A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [26]
• The team have added multi-column support for lists of footnotes. The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [27]
• You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [28]
• The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [29]
• The Categorias item has been moved to the top of the Opcions de pagina menu (from clicking on the "hamburger" icon) for quicker access. [30] There is also now a "Templates used on this page" feature there. [31]
• You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [32]
• Tables can be set as collapsed or un-collapsed. [33]
• The Caractèr especial menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [34]
• A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [35]
• There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K or Command+K respectively. [36]

• The team is working on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [37]
• The kind of button used to Previsualizar, Veire los cambiaments, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [38]
• The outdated 2006 wikitext editor will be removed later this year. It is used by approximately 0.03% of active editors. See a list of editing tools on mediawiki.org if you are uncertain which one you use. [39]
• If you aren't reading this in your preferred language, then please 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 ready. Mercés !

—Elitre (WMF)

Message is available for translation on Meta-Wiki

The Wikimedia movement strategy core team and working groups have completed reviewing the more than 1800 thematic statements we received from the first discussion. They have identified 5 themes that were consistent across all the conversations - each with their own set of sub-themes. These are not the final themes, just an initial working draft of the core concepts.

You are invited to join the online and offline discussions taking place on these 5 themes. This round of discussions will take place between now and June 12th. You can discuss as many as you like; we ask you to participate in the ones that are most (or least) important to you.

Here are the five themes, each has a page on Meta-Wiki with more information about the theme and how to participate in that theme's discussion:

• Healthy, Inclusive Communities
• The Augmented Age
• A Truly Global Movement
• The Most Respected Source of Knowledge
• Engaging in the Knowledge Ecosystem

On the movement strategy portal on Meta-Wiki, you can find more information about each of these themes, their discussions, and how to participate.

Translations of this message are available on Meta-Wiki.

On behalf of the Wikimedia Foundation Elections Committee, we are pleased to announce that self-nominations are being accepted for the 2017 Wikimedia Foundation Funds Dissemination Committee and Funds Dissemination Committee Ombudsperson elections. Please read the letter from the Wikimedia Foundation calling for candidates at on the 2017 Wikimedia Foundation elections portal.

Funds Dissemination Committee
The Funds Dissemination Committee (FDC) makes recommendations about how to allocate Wikimedia movement funds to eligible entities. There are five positions being filled. More information about this role can be found at the FDC elections page.

Funds Dissemination Committee Ombudsperson
The Funds Dissemination Committee Ombudsperson receives complaints and feedback about the FDC process, investigates complaints at the request of the Board of Trustees, and summarizes the investigations and feedback for the Board of Trustees on an annual basis. One position is being filled. More information about this role can be found at the FDC Ombudsperson elections page.

The candidacy submission phase will last until May 28 (23:59 UTC).

We will also be accepting questions to ask the candidates until May 28. You can submit your questions on Meta-Wiki. Once the questions submission period has ended on May 28, the Elections Committee will then collate the questions for the candidates to respond to.

The goal of this process is to fill the five community-selected seats on the Wikimedia Foundation Funds Dissemination Committee and the community-selected ombudsperson. The election results will be used by the Board itself to make the appointments.

The full schedule for the FDC elections is as follows. All dates are inclusive, that is, from the beginning of the first day (UTC) to the end of the last.

• May 15 (00:00 UTC) – May 28 (23:59 UTC) – Nominations
• May 15 – May 28 – Candidates questions submission period
• May 29 – June 2 – Candidates answer questions
• June 3 – June 11 – Voting period
• June 12–14 – Vote checking
• June 15 – Goal date for announcing election results

More information on this year's elections can be found at the 2017 Wikimedia Foundation elections portal.

Please feel free to post a note about the election on your project's village pump. Any questions related to the election can be posted on the talk page on Meta-Wiki, or sent to the election committee's mailing list, board-electionswikimedia.org.

On behalf of the Election Committee,
Katie Chan, Chair, Wikimedia Foundation Elections Committee
Joe Sutherland, Community Advocate, Wikimedia Foundation

You can see and use the old and new versions now. Most editors will only notice that some buttons are slightly larger and have different colors.

• Comparison of old and new styles
• 
  Buttons before the change
• 
  Buttons after the change

However, this change also affects some user scripts and gadgets. Unfortunately, some of them may not work well in the new system. If you maintain any user scripts or gadgets that are used for editing, please see mw:Contributors/Projects/Accessible editing buttons for information on how to test and fix your scripts. Outdated scripts can be tested and fixed now.

New print to pdf feature for mobile web readers

The Readers web team will be deploying a new feature this week to make it easier to download PDF versions of articles on the mobile website.

Providing better offline functionality was one of the highlighted areas from the research done by the New Readers team in Mexico, Nigeria, and India. The teams created a prototype for mobile PDFs which was evaluated by user research and community feedback. The prototype evaluation received positive feedback and results, so development continued.

For the initial deployment, the feature will be available to Google Chrome browsers on Android. Support for other mobile browsers to come in the future. For Chrome, the feature will use the native Android print functionality. Users can choose to download a webpage as a PDF. Mobile print styles will be used for these PDFs to ensure optimal readability for smaller screens.

The feature is available starting Wednesday, Nov 15. For more information, see the project page on MediaWiki.org.

Mercés !

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can now use the visual diff tool on any page?

Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.

If you enable the Beta Feature for "⧼visualeditor-preference-visualdiffpage-label⧽", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.

Click the toggle button to switch between visual and wikitext diffs.

In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.

This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has spent most of their time supporting the 2017 wikitext editor mode, which is available inside the visual editor as a Beta Feature, and improving the visual diff tool. Their work board is available in Phabricator. You can find links to the work finished each week at mw:VisualEditor/Weekly triage meetings. Their current priorities are fixing bugs, supporting the 2017 wikitext editor, and improving the visual diff tool.

• The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
• The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [40]
• Wikitext syntax highlighting is available as a Beta Feature for both the 2017 wikitext editor and the 2010 wikitext editor. [41]
• The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. It is very popular and useful to editors, although it can be a bit tricky to set up. Your wiki can have this service. Please read the instructions. You can ask the team to help you enable citoid at your wiki.

• The team will talk about editing tools at an upcoming Wikimedia Foundation metrics and activities meeting.
• Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
• The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. You can request multi-column support for your wiki. [42]
• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Mercés !

—Elitre (WMF)

Global preferences are now available, you can set them by visiting your new global preferences page. Visit mediawiki.org for information on how to use them and leave feedback. -- Keegan (WMF) (talk)

(Mercé de nos ajudar a traduire dins vòstra lenga)

Hi all!

To improve the security of our readers and editors, permission handling for CSS/JS pages has changed. (These are pages like MediaWiki:Common.css and MediaWiki:Vector.js which contain code that is executed in the browsers of users of the site.) A new user group, interface-admin, has been created. Starting four weeks from now, only members of this group will be able edit CSS/JS pages that they do not own (that is, any page ending with .css or .js that is either in the MediaWiki: namespace or is another user's user subpage).

You can learn more about the motivation behind the change here.

Please add users who need to edit CSS/JS to the new group (this can be done the same way new administrators are added, by stewards or local bureaucrats). This is a dangerous permission; a malicious user or a hacker taking over the account of a careless interface-admin can abuse it in far worse ways than admin permissions could be abused. Please only assign it to users who need it, who are trusted by the community, and who follow common basic password and computer security practices (use strong passwords, do not reuse passwords, use two-factor authentication if possible, do not install software of questionable origin on your machine, use antivirus software if that's a standard thing in your environment).

Thanks!
Tgr (talk) 30 de julhet de 2018 a 17.45 (UTC) (via global message delivery)

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can use the visual editor on a mobile device?

Tap on the pencil icon to start editing. The page will probably open in the wikitext editor.

You will see another pencil icon in the toolbar. Tap on that pencil icon to the switch between visual editing and wikitext editing.

Remember to publish your changes when you're done.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the Editing Team has wrapped up most of their work on the 2017 wikitext editor and the visual diff tool. The team has begun investigating the needs of editors who use mobile devices. Their work board is available in Phabricator. Their current priorities are fixing bugs and improving mobile editing.

• The Editing team has published an initial report about mobile editing.
• The Editing team has begun a design study of visual editing on the mobile website. New editors have trouble doing basic tasks on a smartphone, such as adding links to Wikipedia articles. You can read the report.
• The Reading team is working on a separate mobile-based contributions project.
• The 2006 wikitext editor is no longer supported. If you used that toolbar, then you will no longer see any toolbar. You may choose another editing tool in your editing preferences, local gadgets, or beta features.
• The Editing team described the history and status of VisualEditor in this recorded public presentation (starting at 29 minutes, 30 seconds).
• The Language team released a new version of Content Translation (CX2) last month, on International Translation Day. It integrates the visual editor to support templates, tables, and images. It also produces better wikitext when the translated article is published. [43]

• The Editing team wants to improve visual editing on the mobile website. Please read their ideas and tell the team what you think would help editors who use the mobile site.
• The Community Wishlist Survey begins next week.
• If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Mercés !

—Whatamidoing (WMF) (talk)

Change coming to how certain templates will appear on the mobile web

Mercé de nos ajudar a traduire dins vòstra lenga

Hello,

In a few weeks the Readers web team will be changing how some templates look on the mobile web site. We will make these templates more noticeable when viewing the article. We ask for your help in updating any templates that don't look correct.

What kind of templates? Specifically templates that notify readers and contributors about issues with the content of an article – the text and information in the article. Examples like Template:Unreferenced or Template:More citations needed. Right now these notifications are hidden behind a link under the title of an article. We will format templates like these (mostly those that use Template:Ambox or message box templates in general) to show a short summary under the page title. You can tap on the "Learn more" link to get more information.

For template editors we have some recommendations on how to make templates that are mobile-friendly and also further documentation on our work so far.

If you have questions about formatting templates for mobile, please leave a note on the project talk page or file a task in Phabricator and we will help you.

Mercés !

Mercé de nos ajudar a traduire dins vòstra lenga

The Wikimedia Foundation security team is implementing a new password policy and requirements. You can learn more about the project on MediaWiki.org.

These new requirements will apply to new accounts and privileged accounts. New accounts will be required to create a password with a minimum length of 8 characters. Privileged accounts will be prompted to update their password to one that is at least 10 characters in length.

These changes are planned to be in effect on December 13th. If you think your work or tools will be affected by this change, please let us know on the talk page.

Mercés !

A new beta feature will soon be released on all wikis: The FileExporter. It allows exports of files from a local wiki to Wikimedia Commons, including their file history and page history. Which files can be exported is defined by each wiki's community: Please check your wiki's configuration file if you want to use this feature.

The FileExporter has already been a beta feature on mediawiki.org, meta.wikimedia, deWP, faWP, arWP, koWP and on wikisource.org. After some functionality was added, it's now becoming a beta feature on all wikis. Deployment is planned for January 16. More information can be found on the project page.

As always, feedback is highly appreciated. If you want to test the FileExporter, please activate it in your user preferences. The best place for feedback is the central talk page. Thank you from Wikimedia Deutschland's Technical Wishes project.

The Wikimedia Foundation is planning a global consultation about communication. The goal is to bring Wikimedians and wiki-minded people together to improve tools for communication.

We want all contributors to be able to talk to each other on the wikis, whatever their experience, their skills or their devices.

We are looking for input from as many different parts of the Wikimedia community as possible. It will come from multiple projects, in multiple languages, and with multiple perspectives.

We are currently planning the consultation. We need your help.

We need volunteers to help talk to their communities or user groups.

You can help by hosting a discussion at your wiki. Here's what to do:

1. First, sign up your group here.
2. Next, create a page (or a section on a Village pump, or an e-mail thread – whatever is natural for your group) to collect information from other people in your group. This is not a vote or decision-making discussion: we are just collecting feedback.
3. Then ask people what they think about communication processes. We want to hear stories and other information about how people communicate with each other on and off wiki. Please consider asking these five questions:
   1. When you want to discuss a topic with your community, what tools work for you, and what problems block you?
   2. What about talk pages works for newcomers, and what blocks them?
   3. What do others struggle with in your community about talk pages?
   4. What do you wish you could do on talk pages, but can't due to the technical limitations?
   5. What are the important aspects of a "wiki discussion"?
4. Finally, please go to Talk pages consultation 2019 on Mediawiki.org and report what you learned from your group. Please include links if the discussion is available to the public.

You can also help build the list of the many different ways people talk to each other.

Not all groups active on wikis or around wikis use the same way to discuss things: it can happen on wiki, on social networks, through external tools... Tell us how your group communicates.

You can read more about the overall process on mediawiki.org. If you have questions or ideas, you can leave feedback about the consultation process in the language you prefer.

Thank you! We're looking forward to talking with you.

Read this in another language • Subscription list for this multilingual newsletter

Did you know?

Did you know that you can use the visual editor on a mobile device?

Every article has a pencil icon at the top. Tap on the pencil icon to start editing.

Edit Cards

This is what the new Edit Cards for editing links in the mobile visual editor look like. You can try the prototype here: 📲 Try Edit Cards.

Welcome back to the Editing newsletter.

Since the last newsletter, the team has released two new features for the mobile visual editor and has started developing three more. All of this work is part of the team's goal to make editing on mobile web simpler.

Before talking about the team's recent releases, we have a question for you:

Are you willing to try a new way to add and change links?

If you are interested, we would value your input! You can try this new link tool in the mobile visual editor on a separate wiki.

Follow these instructions and share your experience:

📲 Try Edit Cards.

The mobile visual editor is a simpler editing tool, for smartphones and tablets using the mobile site. The Editing team recently launched two new features to improve the mobile visual editor:

1. Section editing
   • The purpose is to help contributors focus on their edits.
   • The team studied this with an A/B test. This test showed that contributors who could use section editing were 1% more likely to publish the edits they started than people with only full-page editing.
2. Loading overlay
   • The purpose is to smooth the transition between reading and editing.

Section editing and the new loading overlay are now available to everyone using the mobile visual editor.

This is a list of our most active projects. Watch these pages to learn about project updates and to share your input on new designs, prototypes and research findings.

• Edit cards: This is a clearer way to add and edit links, citations, images, templates, etc. in articles. You can try this feature now. Go here to see how: 📲 Try Edit Cards.
• Mobile toolbar refresh: This project will learn if contributors are more successful when the editing tools are easier to recognize.
• Mobile visual editor availability: This A/B test asks: Are newer contributors more successful if they use the mobile visual editor? We are collaborating with 20 Wikipedias to answer this question.
• Usability improvements: This project will make the mobile visual editor easier to use. The goal is to let contributors stay focused on editing and to feel more confident in the editing tools.

• Wikimania: Several members of the Editing Team will be attending Wikimania in August 2019. They will lead a session about mobile editing in the Community Growth space. Talk to the team about how editing can be improved.
• Talk Pages: In the coming months, the Editing Team will begin improving talk pages and communication on the wikis.

The VisualEditor on mobile is a good place to learn more about the projects we are working on. The team wants to talk with you about anything related to editing. If you have something to say or ask, please leave a message at Talk:VisualEditor on mobile.

PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

Mercé de nos ajudar a traduire dins vòstra lenga

Bonjorn. The Readers Web team at the WMF will work on some improvements to the desktop interface over the next couple of years. The goal is to increase usability without removing any functionality. We have been inspired by changes made by volunteers, but that currently only exist as local gadgets and user scripts, prototypes, and volunteer-led skins. We would like to begin the process of bringing some of these changes into the default experience on all Wikimedia projects.

We are currently in the research stage of this project and are looking for ideas for improvements, as well as feedback on our current ideas and mockups. So far, we have performed interviews with community members at Wikimania. We have gathered lists of previous volunteer and WMF work in this area. We are examining possible technical approaches for such changes.

We would like individual feedback on the following:

• Identifying focus areas for the project we have not yet discovered
• Expanding the list of existing gadgets and user scripts that are related to providing a better desktop experience. If you can think of some of these from your wiki, please let us know
• Feedback on the ideas and mockups we have collected so far

We would also like to gather a list of wikis that would be interested in being test wikis for this project - these wikis would be the first to receive the updates once we’re ready to start building.

When giving feedback, please consider the following goals of the project:

• Make it easier for readers to focus on the content
• Provide easier access to everyday actions (e.g. search, language switching, editing)
• Put things in logical and useful places
• Increase consistency in the interface with other platforms - mobile web and the apps
• Eliminate clutter
• Plan for future growth

As well as the following constraints:

• Not touching the content - no work will be done in terms of styling templates or to the structure of page contents themselves
• Not removing any functionality - things might move around, but all navigational items and other functionality currently available by default will remain
• No drastic changes to the layout - we're taking an evolutionary approach to the changes and want the site to continue feeling familiar to readers and editors

Please give all feedback (in any language) at mw:Talk:Reading/Web/Desktop Improvements

After this round of feedback, we plan on building a prototype of suggested changes based on the feedback we receive. You’ll hear from us again asking for feedback on this prototype.

Mercés ! Quiddity (WMF) (talk)

Read this in another language • Subscription list for this multilingual newsletter

Inside this newsletter, the Editing team talks about their work on the mobile visual editor, on the new talk pages project, and at Wikimania 2019.

What talk page interactions do you remember? Is it a story about how someone helped you to learn something new? Is it a story about how someone helped you get involved in a group? Something else? Whatever your story is, we want to hear it!

Please tell us a story about how you used a talk page. Please share a link to a memorable discussion, or describe it on the talk page for this project. The team wants your examples. These examples will help everyone develop a shared understanding of what this project should support and encourage.

The Talk Pages Consultation was a global consultation to define better tools for wiki communication. From February through June 2019, more than 500 volunteers on 20 wikis, across 15 languages and multiple projects, came together with members of the Foundation to create a product direction for a set of discussion tools. The Phase 2 Report of the Talk Page Consultation was published in August. It summarizes the product direction the team has started to work on, which you can read more about here: Talk Page Project project page.

The team needs and wants your help at this early stage. They are starting to develop the first idea. Please add your name to the "Getting involved" section of the project page, if you would like to hear about opportunities to participate.

The Editing team is trying to make it simpler to edit on mobile devices. The team is changing the visual editor on mobile. If you have something to say about editing on a mobile device, please leave a message at Talk:VisualEditor on mobile.

• On 3 September, the Editing team released version 3 of Edit Cards. Anyone could use the new version in the mobile visual editor.
• There is an updated design on the Edit Card for adding and modifying links. There is also a new, combined workflow for editing a link's display text and target.
• Feedback: You can try the new Edit Cards by opening the mobile visual editor on a smartphone. Please post your feedback on the Edit cards talk page.

• In September, the Editing team updated the mobile visual editor's editing toolbar. Anyone could see these changes in the mobile visual editor.
  • One toolbar: All of the editing tools are located in one toolbar. Previously, the toolbar changed when you clicked on different things.
  • New navigation: The buttons for moving forward and backward in the edit flow have changed.
  • Seamless switching: an improved workflow for switching between the visual and wikitext modes.
• Feedback: You can try the refreshed toolbar by opening the mobile VisualEditor on a smartphone. Please post your feedback on the Toolbar feedback talk page.

The Editing Team attended Wikimania 2019 in Sweden. They led a session on the mobile visual editor and a session on the new talk pages project. They tested two new features in the mobile visual editor with contributors. You can read more about what the team did and learned in the team's report on Wikimania 2019.

• Talk Pages Project: The team is thinking about the first set of proposed changes. The team will be working with a few communities to pilot those changes. The best way to stay informed is by adding your username to the list on the project page: Getting involved.
• Testing the mobile visual editor as the default: The Editing team plans to post results before the end of the calendar year. The best way to stay informed is by adding the project page to your watchlist: VisualEditor as mobile default project page.
• Measuring the impact of Edit Cards: This study asks whether the project helped editors add links and citations. The Editing team hopes to share results in November. The best way to stay informed is by adding the project page to your watchlist: Edit Cards project page.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

The 2020 Community Wishlist Survey is now open! This survey is the process where communities decide what the Community Tech team should work on over the next year. We encourage everyone to submit proposals until the deadline on November 11, 2019, or comment on other proposals to help make them better.

This year, we’re exclusively focusing on smaller projects (i.e., Wikibooks, Wiktionary, Wikiquote, Wikisource, Wikiversity, Wikispecies, Wikivoyage, and Wikinews). We want to help these projects and provide meaningful improvements to diverse communities. If you’re a member of any of these projects, please participate in the survey! To submit proposals, see the guidelines on the survey page. You can write proposals in any language, and we will translate them for you. Thank you, and we look forward to seeing your proposals!

Read this in another language • Subscription list for this multilingual newsletter

The Editing team has been working on the talk pages project. The goal of the talk pages project is to help contributors communicate on wiki more easily. This project is the result of the Talk pages consultation 2019.

The team is building a new tool for replying to comments now. This early version can sign and indent comments automatically. Please test the new Reply tool.

• On 31 March 2020, the new respon tool was offered as a Beta Feature editors at four Wikipedias: Arabic, Dutch, French, and Hungarian. If your community also wants early access to the new tool, contact User:Whatamidoing (WMF).
• The team is planning some upcoming changes. Please review the proposed design and share your thoughts on the talk page. The team will test features such as:
  • an easy way to mention another editor ("pinging"),
  • a rich-text visual editing option, and
  • other features identified through user testing or recommended by editors.

To hear more about Editing Team updates, please add your name to the "Get involved" section of the project page. You can also watch these pages: the main project page, Updates, Replying, and User testing.

– PPelberg (WMF) (talk) & Whatamidoing (WMF) (talk)

Read this in another language • Subscription list for this multilingual newsletter

This issue of the Editing newsletter includes information the Talk pages project, an effort to help contributors communicate on wiki more easily.

• Reply tool: This is available as a Beta Feature at the four partner wikis (Arabic, Dutch, French, and Hungarian Wikipedias). The Beta Feature is called "Eines de Discussió". The Beta Feature will get new features soon. The new features include writing comments in a new visual editing mode and pinging other users by typing @. You can test the new features on the Beta Cluster now. Some other wikis will have a chance to try the Beta Feature in the coming months.
• New requirements for user signatures: Soon, users will not be able to save invalid custom signatures in Special:Preferences. This will reduce signature spoofing, prevent page corruption, and make new talk page tools more reliable. Most editors will not be affected.
• New discussion tool: The Editing team is beginning work on a simpler process for starting new discussions. You can see the initial design on the project page.
• Research on the use of talk pages: The Editing team worked with the Wikimedia research team to study how talk pages help editors improve articles. We learned that new editors who use talk pages make more edits to the main namespace than new editors who don't use talk pages.

– Whatamidoing (WMF) (talk)

Read this in another language • Subscription list for this multilingual newsletter

Seven years ago this month, the Editing team offered the visual editor to most Wikipedia editors. Since then, editors have achieved many milestones:

• More than 50 million edits have been made using the visual editor on desktop.
• More than 2 million new articles have been created in the visual editor. More than 600,000 of these new articles were created during 2019.
• The visual editor is increasingly popular. The proportion of all edits made using the visual editor has increased every year since its introduction.
• In 2019, 35% of the edits by newcomers (logged-in editors with ≤99 edits) used the visual editor. This percentage has increased every year.
• Almost 5 million edits on the mobile site have been made with the visual editor. Most of these edits have been made since the Editing team started improving the mobile visual editor in 2018.
• On 17 November 2019, the first edit from outer space was made in the mobile visual editor. 🚀 👩‍🚀
• Editors have made more than 7 million edits in the 2017 wikitext editor, including starting 600,000 new articles in it. The 2017 wikitext editor is VisualEditor's built-in wikitext mode. You can enable it in your preferences.

Whatamidoing (WMF) (talk)

Hi all,

It is my honor to introduce Abstract Wikipedia, a new project that has been unanimously approved by the Wikimedia Foundation Board of Trustees. Abstract Wikipedia proposes a new way to generate baseline encyclopedic content in a multilingual fashion, allowing more contributors and more readers to share more knowledge in more languages. It is an approach that aims to make cross-lingual cooperation easier on our projects, increase the sustainability of our movement through expanding access to participation, improve the user experience for readers of all languages, and innovate in free knowledge by connecting some of the strengths of our movement to create something new.

This is our first new project in over seven years. Abstract Wikipedia was submitted as a project proposal by Denny Vrandečić in May 2020 ^[1] after years of preparation and research, leading to a detailed plan and lively discussions in the Wikimedia communities. We know that the energy and the creativity of the community often runs up against language barriers, and information that is available in one language may not make it to other language Wikipedias. Abstract Wikipedia intends to look and feel like a Wikipedia, but build on the powerful, language-independent conceptual models of Wikidata, with the goal of letting volunteers create and maintain Wikipedia articles across our polyglot Wikimedia world.

The project will allow volunteers to assemble the fundamentals of an article using words and entities from Wikidata. Because Wikidata uses conceptual models that are meant to be universal across languages, it should be possible to use and extend these building blocks of knowledge to create models for articles that also have universal value. Using code, volunteers will be able to translate these abstract “articles” into their own languages. If successful, this could eventually allow everyone to read about any topic in Wikidata in their own language.

As you can imagine, this work will require a lot of software development, and a lot of cooperation among Wikimedians. In order to make this effort possible, Denny will join the Foundation as a staff member in July and lead this initiative. You may know Denny as the creator of Wikidata, a long-time community member, a former staff member at Wikimedia Deutschland, and a former Trustee at the Wikimedia Foundation ^[2]. We are very excited that Denny will bring his skills and expertise to work on this project alongside the Foundation’s product, technology, and community liaison teams.

It is important to acknowledge that this is an experimental project, and that every Wikipedia community has different needs. This project may offer some communities great advantages. Other communities may engage less. Every language Wikipedia community will be free to choose and moderate whether or how they would use content from this project.

We are excited that this new wiki-project has the possibility to advance knowledge equity through increased access to knowledge. It also invites us to consider and engage with critical questions about how and by whom knowledge is constructed. We look forward to working in cooperation with the communities to think through these important questions.

There is much to do as we begin designing a plan for Abstract Wikipedia in close collaboration with our communities. I encourage you to get involved by going to the project page and joining the new mailing list ^[3]. We recognize that Abstract Wikipedia is ambitious, but we also recognize its potential. We invite you all to join us on a new, unexplored path.

Yours,

Katherine Maher (Executive Director, Wikimedia Foundation)

1. ↑ Abstract Wikipedia
2. ↑ User:Denny
3. ↑ Abstract Wikipedia mailing list

The FileExporter and FileImporter will become a default features on all wikis until August 7, 2020. They are planned to help you to move files from your local wiki to Wikimedia Commons easier while keeping all original file information (Description, Source, Date, Author, View History) intact. Additionally, the move is documented in the files view history. How does it work?

Step 1: If you are an auto-confirmed user, you will see a link "Move file to Wikimedia Commons" on the local file page.

Step 2: When you click on this link, the FileImporter checks if the file can in fact be moved to Wikimedia Commons. These checks are performed based on the wiki's configuration file which is created and maintained by each local wiki community.

Step 3: If the file is compatible with Wikimedia Commons, you will be taken to an import page, at which you can update or add information regarding the file, such as the description. You can also add the 'Now Commons' template to the file on the local wiki by clicking the corresponding check box in the import form. Admins can delete the file from the local wiki by enabling the corresponding checkbox. By clicking on the 'Import' button at the end of the page, the file is imported to Wikimedia Commons.

Bonjorn. Apologies for cross-posting, and that you may not be reading this message in your native language: translations of the following announcement may be available on Meta. Mercé de nos ajudar a traduire dins vòstra lenga. Mercés !

We are excited to share a draft of the Universal Code of Conduct, which the Wikimedia Foundation Board of Trustees called for earlier this year, for your review and feedback. The discussion will be open until October 6, 2020.

The UCoC Drafting Committee wants to learn which parts of the draft would present challenges for you or your work. What is missing from this draft? What do you like, and what could be improved?

Please join the conversation and share this invitation with others who may be interested to join, too.

To reduce language barriers during the process, you are welcomed to translate this message and the Universal Code of Conduct/Draft review. You and your community may choose to provide your opinions/feedback using your local languages.

To learn more about the UCoC project, see the Universal Code of Conduct page, and the FAQ, on Meta.

Mercé de nos ajudar a traduire dins vòstra lenga

Bonjorn. Please help pick a name for the new Wikimedia wiki project. This project will be a wiki where the community can work together on a library of functions. The community can create new functions, read about them, discuss them, and share them. Some of these functions will be used to help create language-independent Wikipedia articles that can be displayed in any language, as part of the Abstract Wikipedia project. But functions will also be usable in many other situations.

Bonjorn. Reminder: Please help to choose the name for the new Wikimedia wiki project - the library of functions. The finalist vote starts today. The finalists for the name are: Wikicode, Wikicodex, Wikifunctions, Wikifusion, Wikilambda, Wikimedia Functions. If you would like to participate, then please learn more and vote now at Meta-wiki. Mercés ! --Quiddity (WMF)

Sorry for sending this message in English. Translations are available on this page. Feel free to translate it in more languages!

As you may know, you can include changes coming from Wikidata in your Watchlist and Recent Changes (in your preferences). Until now, this feature didn’t always include changes made on Wikidata descriptions due to the way Wikidata tracks the data used in a given article.

Starting on December 3rd, the Watchlist and Recent Changes will include changes on the descriptions of Wikidata Items that are used in the pages that you watch. This will only include descriptions in the language of your wiki to make sure that you’re only seeing changes that are relevant to your wiki.

This improvement was requested by many users from different projects. We hope that it can help you monitor the changes on Wikidata descriptions that affect your wiki and participate in the effort of improving the data quality on Wikidata for all Wikimedia wikis and beyond.

Note: if you didn’t use the Wikidata watchlist integration feature for a long time, feel free to give it another chance! The feature has been improved since the beginning and the content it displays is more precise and useful than at the beginning of the feature in 2015.

If you encounter any issue or want to provide feedback, feel free to use this Phabricator ticket. Thanks!

Lea Lacroix (WMDE) 30 novembre de 2020 a 14.39 (UTC)[respon]

Hello all,

The ceremony of the 2020 Wikimedia Coolest Tool Award will take place virtually on Friday, December 11th, at 17:00 GMT. This award is highlighting tools that have been nominated by contributors to the Wikimedia projects, and the ceremony will be a nice moment to show appreciation to the tools developers and maybe discover new tools!

You will find more information here about the livestream and the discussions channels. Thanks for your attention, Lea Lacroix (WMDE) 7 decembre de 2020 a 10.55 (UTC)[respon]

Nous invitons tous les utilisateurs enregistrés à voter à la consultation des souhaits de la communauté pour 2021. Vous pouvez voter dès à présent et jusqu’au 21 décembre pour autant de souhaits différents que vous voulez.

Dans la consultation, nous collectons les envies de nouveaux outils ou d’amélioration d’outils existants pour les contributeurs expérimentés. Après le vote, nous ferons de notre mieux pour honorer vos désidératas. Nous commencerons par les plus populaires.

Nous, l’équipe Technologies communautaires, sommes l'une des équipes de la Fondation Wikimedia. Nous créons et nous améliorons les outils de contribution et de modération du wiki. Les tâches sur lesquelles nous travaillons sont décidées en fonction des résultats de la consultation sur les souhaits des communautés. Une fois par an, vous pouvez soumettre vos souhaits. Après deux semaines, vous pouvez voter pour ceux qui vous intéressent le plus. Ensuite nous choisissons parmi les souhaits de l'enquête ceux sur lesquels nous allons travailler. Certains souhaits pourront être développés par des développeurs bénévoles ou par d'autres équipes.

Nous attendons vos votes. Merci !

From April 15, you can enable line numbering in some wikitext editors - for now in the template namespace, coming to more namespaces soon. This will make it easier to detect line breaks and to refer to a particular line in discussions. These numbers will be shown if you enable the syntax highlighting feature (CodeMirror extension), which is supported in the 2010 and 2017 wikitext editors.

More information can be found on this project page. Everyone is invited to test the feature, and to give feedback on this talk page.

From April 29, it will be possible to suggest values for parameters in templates. Suggested values can be added to TemplateData and will then be shown as a drop-down list in VisualEditor. This allows template users to quickly select an appropriate value. This way, it prevents potential errors and reduces the effort needed to fill the template with values. It will still be possible to fill in values other than the suggested ones.

More information, including the supported parameter types and how to create suggested values: [1] [2]. Everyone is invited to test the feature, and to give feedback on this talk page.

Read this in another language • Subscription list for this multilingual newsletter

Earlier this year, the Editing team ran a large study of the Reply Tool. The main goal was to find out whether the Reply Tool helped newer editors communicate on wiki. The second goal was to see whether the comments that newer editors made using the tool needed to be reverted more frequently than comments newer editors made with the existing wikitext page editor.

The key results were:

• Newer editors who had automatic ("default on") access to the Reply tool were more likely to post a comment on a talk page.
• The comments that newer editors made with the Reply Tool were also less likely to be reverted than the comments that newer editors made with page editing.

These results give the Editing team confidence that the tool is helpful.

Looking ahead

The team is planning to make the Reply tool available to everyone as an opt-out preference in the coming months. This has already happened at the Arabic, Czech, and Hungarian Wikipedias.

The next step is to resolve a technical challenge. Then, they will deploy the Reply tool first to the Wikipedias that participated in the study. After that, they will deploy it, in stages, to the other Wikipedias and all WMF-hosted wikis.

You can turn on "Eines de Discussió" in Beta Features now. After you get the Reply tool, you can change your preferences at any time in Special:Preferences#mw-prefsection-editing-discussion.

–Whatamidoing (WMF) (talk)

Hello everyone,

We hope all of you are as well and safe as possible during these trying times! We wanted to share some news about a change to the Community Wishlist Survey 2022. We would like to hear your opinions as well.

Summary:

In the past, the Community Tech team has run the Community Wishlist Survey for the following year in November of the prior year. For example, we ran the Wishlist for 2021 in November 2020. That worked well a few years ago. At that time, we used to start working on the Wishlist soon after the results of the voting were published.

However, in 2021, there was a delay between the voting and the time when we could start working on the new wishes. Until July 2021, we were working on wishes from the Wishlist for 2020.

We hope having the Wishlist 2022 in January 2022 will be more intuitive. This will also give us time to fulfill more wishes from the 2021 Wishlist.

We are thinking how to make the Wishlist easier to participate in. We want to support more translations, and encourage under-resourced communities to be more active. We would like to have some time to make these changes.

We will have gone 365 days without a Wishlist. We encourage you to approach us. We hope to hear from you in the talk page, but we also hope to see you at our bi-monthly Talk to Us meetings! These will be hosted at two different times friendly to time zones around the globe.

We will begin our first meeting September 15th at 23:00 UTC. More details about the agenda and format coming soon!

If you have early ideas for wishes, you can use the new Community Wishlist Survey sandbox. This way, you will not forget about these before January 2022. You will be able to come back and refine your ideas. Remember, edits in the sandbox don't count as wishes!

• What should we do to improve the Wishlist pages?
• How would you like to use our new sandbox?
• What, if any, risks do you foresee in our decision to change the date of the Wishlist 2022?
• What will help more people participate in the Wishlist 2022?

Answer on the talk page (in any language you prefer) or at our Talk to Us meetings.