This is the first of three conversations, and it will run between now and April 15. The purpose of cycle 1 is to discuss the future of the movement and generate major themes around potential directions. What do we want to build or achieve together over the next 15 years?
We welcome you, as we create this conversation together, and look forward to broad and diverse participation from all parts of our movement.
One position is being filled. More information about this election will be available on Meta-Wiki.
Please note that this year the Board of Trustees elections will be held before the FDC and Ombuds elections. Candidates who are not elected to the Board are explicitly permitted and encouraged to submit themselves as candidates to the FDC or Ombuds positions after the results of the Board elections are announced.
More information on this year's elections can be found on Meta-Wiki. Any questions related to the election can be posted on the election talk page on Meta-Wiki, or sent to the election committee's mailing list, board-electionswikimedia.org.
The Wikimedia Foundation will be testing its secondary data center in Dallas. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to conduct a planned test. This test will show whether they can reliably switch from one data center to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.
They will switch all traffic to the secondary data center on Wednesday, 19 April 2017.
On Wednesday, 3 May 2017, they will switch back to the primary data center.
Unfortunately, because of some limitations in MediaWiki, all editing must stop during those two switches. We apologize for this disruption, and we are working to minimize it in the future.
You will be able to read, but not edit, all wikis for a short period of time.
You will not be able to edit for approximately 20 to 30 minutes on Wednesday, 19 April and Wednesday, 3 May. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Thursday 20 April and Thursday 4 May).
If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.
Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
There will be code freezes for the weeks of 17 April 2017 and 1 May 2017. Non-essential code deployments will not happen.
Wikidata description editing in the Wikipedia Android appBearbeiten
Wikidata description editing is a new experiment being rolled out on the Wikipedia app for Android. While this primarily impacts Wikidata, the changes are also addressing a concern about the mobile versions of Wikipedia, so that mobile users will be able to edit directly the descriptions shown under the title of the page and in the search results.
We began by rolling out this feature several weeks ago to a pilot group of Wikipedias (Russian, Hebrew, and Catalan), and have seen very positive results including numerous quality contributions in the form of new and updated descriptions, and a low rate of vandalism.
We are now ready for the next phase of rolling out this feature, which is to enable it in a few days for all Wikipedias except the top ten by usage within the app (i.e. except English, German, Italian, French, Spanish, Japanese, Dutch, Portuguese, Turkish, and Chinese). We will enable the feature for those languages instead at some point in the future, as we closely monitor user engagement with our expanded set of pilot communities.
As always, if have any concerns, please reach out to us on wiki at the talk page for this project or by email at email@example.com. Thanks!
The Reading web team at the Wikimedia Foundation has been working to enable Page previews, a beta feature known previously as Hovercards, as opt-in behavior for logged-in users and the default behavior for logged-out users across Wikipedia projects. Page previews provide a preview of any linked article, giving readers a quick understanding of a related article without leaving the current page. For this project, we are expecting to collect feedback over the following few weeks and tentatively enable the feature in early May, 2017.
A quick note on the implementation:
For logged-in users who are not currently testing out the beta feature, Page previews will be off by default. Users may turn them on from their user preferences page.
For logged-out users, the feature will be on by default. Users may disable it at any time by selecting the setting cog available in each preview.
For users of the Navigation popups gadget, you will not be able to turn on the Page previews feature while using navigational popups. If you would like to try out the Page preview feature, make sure to first turn Navigation popups off prior to turning Page previews on.
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.
Beta Feature Two Column Edit Conflict ViewBearbeiten
From May 9, the Two Column Edit Conflict View will be available as a beta feature on all wikis. The Two Column Edit Conflict View is a new interface for the edit conflict resolution page. It highlights differences between the editor's and the conflicting changes to make it easy to copy and paste pieces of the text and resolve the conflict. The feature fulfils a request for a more user-friendly edit conflict resolution from the German Community’s Technical Wishlist. Everyone is invited to test the feature and we hope that it will serve you well!
Did you know that you can review your changes visually?
When you are finished editing the page, type your edit summary and then choose "Überprüfe deine Änderungen".
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.
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. 
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. 
The Kategorien item has been moved to the top of the Seitenoptionen menu (from clicking on the "hamburger" icon) for quicker access.  There is also now a "Templates used on this page" feature there. 
You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. 
Tables can be set as collapsed or un-collapsed. 
The Sonderzeichen menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. 
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. 
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. 
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. 
The kind of button used to Vorschau zeigen, Enneringe zeige, 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. 
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. Danke!
We present this work to you very early, so we can include your feedback before and all along the development. You are the core users of this feature, so we want to make sure that it fits your needs and editing processes.
You will find the prototype, description of the features, and a demo video, on this page. Feel free to add any comment or feedback on the talk page. The page is currently not translated in every languages, but you can add your contribution by helping to translate it.
Unfortunately, I won’t be able to follow all the discussions on Wikipedia, so if you want to be sure that your feedback is read, please add it on the Wikidata page, in your favorite language. Thanks for your understanding.
RevisionSlider will be available as a default feature for all users on all wikis from May 17. The RevisionSlider adds a slider view to the diff page so that you can easily move between revisions. The slider view is collapsed by default, and will load by clicking on it. It can also be turned off entirely in the user preferences. RevisionSlider has been a default feature on German, Arabic and Hebrew Wikipedia for 6 months and a beta feature on all wikis for 8 months. The feature fulfills a wish from the German Community’s Technical Wishlist. Thanks to everyone who tested RevisionSlider and gave valuable feedback to improve the feature! We hope that RevisionSlider will continue to serve you well in your work.
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:
New notification when a page is connected to WikidataBearbeiten
(Hilf bitte mit, in deine Sprache zu übersetzen)
The Wikidata development team is about to deploy a new feature on all Wikipedias. It is a new type of notification (via Echo, the notification system you see at the top right of your wiki when you are logged in), that will inform the creator of a page, when this page is connected to a Wikidata item.
You may know that Wikidata provides a centralized system for all the interwikilinks. When a new page is created, it should be connected to the corresponding Wikidata item, by modifying this Wikidata item. With this new notification, editors creating pages will be informed when another editor connects this page to Wikidata.
This feature will be deployed on May 30th on all the Wikipedias, excepting English, French and German. This feature will be disable by default for existing editors, and enabled by default for new editors.
This is the first step of the deployments, the Wikipedias and other Wikimedia projects will follow in the next months.
If you have any question, suggestion, please let me know by pinging me. You can also follow and leave a comment on the Phabricator ticket.
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.
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
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.
Hi, you are invited to participate in the discussion on the proposal to make a banner through m: centralnotice to inform more people around the world about what the Turkish government has done about Wikipedia, ie all the language versions of Wikipedia are You are obscured, so in Turkey it is impossible to view the * .wikipedia.org site. To hope that the Turkish government will remove the block, it is necessary to raise awareness of this fact around the world because it is important to succeed in this mission because Wikipedia can not be seen in Turkey. With this message also for those interested, I invite him to sign the Wikimedian appeal.
If you have any questions or questions do not hesitate to contact me.
Thanks best regards. --Samuele2002(Talk!) 08:27, 8. Yuni 2017 (EDT)
Wikidata changes now also appear in enhanced recent changesBearbeiten
The MediaWiki developers have been slowly improving the accessibility of the user interface. The next step in this transition will change the appearance of some buttons and may break some outdated (non-updated or unmaintained) user scripts and gadgets.
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.
A quick update on the progress of enabling Page Previews (previously named Hovercards) on this project. Page Previews provide a preview of any linked article, giving readers a quick understanding of a related article without leaving the current page. As mentioned in December we're preparing to remove the feature from Beta and make it the default behavior for logged-out users. We have recently made a large update to the code which fixes most outstanding bugs.
Due to some issues with our instrumentation, we delayed our deployment by a few months. We are finally ready to deploy the feature. Page Previews will be off by default and available in the user preferences page for logged-in users the week of July 24th. The feature will be on by default for current beta users and logged-out users. If you would like to preview the feature, you can enable it as a beta feature. For more information see Page Previews. Questions can be left on the talk page in your preferred language.
Note this is to apply to Wikipedia and not necessarily other sister projects, this is only to apply to websites where people are specifically advertising that they will edit Wikipedia for pay and not any other personal, professional, or social media accounts a person may have.
The Reading Infrastructure team at the Wikimedia Foundation is developing a cross-platform reading list service for the mobile Wikipedia app. Reading lists are like bookmark folders in your web browser. They allow readers using the Wikipedia app to bookmark pages into folders to read later. This includes reading offline. Reading lists do not create or alter content in any way.
To create Reading Lists, app users will register an account and marked pages will be tied to that account. Reading List account preferences sync between devices. You can read the same pages on different mobile platforms (tablets, phones). This is the first time we are syncing preference data between devices in such a way. We want to hear and address concerns about privacy and data security. We also want to explain why the current watchlist system is not being adapted for this purpose.
In 2016 the Android team replaced the simple Saved Pages feature with Reading Lists. Reading Lists allow users to bookmark pages into folders and for reading offline. The intent of this feature was to allow "syncing" of these lists for users with many devices. Due to overlap with the Gather feature and related community concerns, this part was put on hold.
The Android team has identified this lack of synching as a major area of complaint from users. They expect lists to sync. The iOS team has held off implementing Reading Lists, as syncing was seen as a "must have" for this feature. A recent technical RfC has allowed these user stories and needs to be unblocked. Initially for Android, then iOS, and with web to potentially follow.
Reading lists are private, stored as part of a user's account, not as a public wiki page. There is no sharing or publishing ability for reading lists. No planned work to make these public. The target audience are people that read Wikipedia and want to bookmark and organize that content in the app. There is a potential for the feature to be available on the web in the future.
Watchlists offer similar functionality to Reading Lists. The Reading Infrastructure team evaluated watchlist infrastructure before exploring other options. In general, the needs of watchlists differ from Reading Lists in a few key ways:
Reading lists focus on Reading articles, not the monitoring of changes.
Watchlists are focused on monitoring changes of pages/revisions.
The Watchlist infrastructure is key to our contributor community for monitoring content changes manually and through the use of automated tools (bots). Because of these needs, expanding the scope of Watchlists to reading purposes will only make the project harder to maintain and add more constraints.
By keeping the projects separate it is easier to scale resources. We can serve these two different audiences and prioritize the work accordingly. Reading Lists are, by their nature, less critical to the health of Wikipedia/MediaWiki.
Multi-project support. Reading Lists are by design cross-wiki/project. Watchlists are tied to specific wikis. While there have been many discussion for making them cross-wiki, resolution is not in the near term.
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.
We wanted to inform you that scholarship applications for Wikimania 2018 which is being held in Cape Town, South Africa on July 18–22, 2018 are now being accepted. Applications are open until Monday, 22 January 2018 23:59 UTC.
Applicants will be able to apply for a partial or full scholarship. A full scholarship will cover the cost of an individual's round-trip travel, shared accommodation, and conference registration fees as arranged by the Wikimedia Foundation. A partial scholarship will cover conference registration fees and shared accommodation. Applicants will be rated using a pre-determined selection process and selection criteria established by the Scholarship Committee and the Wikimedia Foundation, who will determine which applications are successful. To learn more about Wikimania 2018 scholarships, please visit: wm2018:Scholarships.
It is highly recommended that applicants review all the material on the Scholarships page and the associated FAQ before submitting an application. If you have any questions, please contact: wikimania-scholarships at wikimedia.org or leave a message at: wm2018:Talk:Scholarships. Please help us spread the word and translate pages!
"Military history" is one of the most important subjects when speak of sum of all human knowledge. To support contributors interested in the area over various language Wikipedias, we intend to form a user group. It also provides a platform to share the best practices between military historians, and various military related projects on Wikipedias. An initial discussion was has been done between the coordinators and members of WikiProject Military History on English Wikipedia. Now this discussion has been taken to Meta-Wiki. Contributors intrested in the area of military history are requested to share their feedback and give suggestions at Talk:Discussion to incubate a user group for Wikipedia Military Historians.
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 "Visuelle Unterschiede", 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.
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. 
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. Danke!
Wikipedia:Galicia 15 - 15 Challenge is a public writing competition which will improve improve and translate this list of 15 really important articles into as many languages as possible. Everybody can help in any language to collaborate on writing and/or translating articles related to Galicia. To participate you just need to sign up here. Thank you very much.--Breogan2008 (Diskussion) 10:28, 12. Matz 2018 (EDT)
Time to bring embedded maps (‘mapframe’) to most WikipediasBearbeiten
Time to bring embedded maps (‘mapframe’) to most Wikipedias
Hilf bitte mit, in deine Sprache zu übersetzen
Mapframe is a feature that enables users to easily display interactive maps right on wiki pages. Currently, most Wikipedias don’t have mapframe. But fifteen Wikipedias, along with all the other Wikimedia projects, are using mapframe today to display maps on thousands of pages.
A little background: over the last few months, the Foundation’s Collaboration team has been working to improve the stability and user experience of the maps service. In addition, a question about long-term support for the maps service was recently settled, and a small team has been assigned for routine maintenance. Given these developments, bringing the benefits of mapframe to Wikipedias that lack the feature seems both safe and supportable. Nine Wikipedias that use a stricter version of Flagged Revisions will not get mapframe in this release.
Maps are a valuable form of visual data that can improve readers’ understanding across a wide range of topics. If you know of any reasons why mapframe shouldn’t be implemented on your Wikipedia, let us know on the project talk page. Unless we hear from you, we plan to release mapframe to most Wikipedias in May, 2018. So, if you foresee an issue, please let us hear from you. Otherwise, happy mapping!
Hilf bitte mit, in deine Sprache zu übersetzen
Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.
The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
Page issues make sense to readers and they understand how they work
Readers care about page issues and consider them important
Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues
Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page.