This is the Wikivoyage Lounge on Meta where we discuss the Wikivoyage project in general and issues related to more than one language version. Old discussions are archived.
Monthly reports from each edition of Wikivoyage can be found on the Summit page.
- 1 New terms on community engagement
- 2 Participate in Dispute Resolution Focus Group
- 3 Announcing Map improvements 2018
- 4 Enabling a helpful feature for Template editors
- 5 An update on map internationalization
- 6 Maps in the language of your choice—try it out on testwiki
- 7 Map internationalization launched everywhere—and embedded maps now live on 276 Wikipedias
New terms on community engagement
WMF is currenly trying to redefine the terms of community engagement (which in the pas was operates as Global North vs Global South). The proposal has been open for community discussion: Community Engagement/Defining Emerging Communities. The currently version states directly that WMF will not proactively invest in Wikivoyage due to low impact. More explanations, confirming that this is indeed the case and not an error of interpretation are at the talk page (Talk:Community Engagement/Defining Emerging Communities#Wikivoyage). Whereas it does not come as a surprise - we know that after initial help with migration, which was already not very welcoming (I sometimes felt like WMF people consider us as their hired workforce), the investment in Wikivoyage was zero, and whatever we needed we had to do ourselves (and whatever we did not manage to do ourselves still has not been done), and in this sense I welcome the decision of WMF to state it explicitly. Just writing protests at the talk page is in my experience useless - the decision has been taken, and all we can get would be "we are sorry that you feel this was, but this is our decision". However, I think that we as Wikivoyage community should be aware of this discussion, of the WMF position in general, and possibly discuss whether we are going to react. In any case, now it is clear that coordinating the development effort between different versions (possibly excluding English Wikivoyage, who do not care about other language versions) would be beneficial.--Ymblanter (talk) 12:06, 4 October 2017 (UTC)
- Support your proposal for interlanguage coordination between Wikivoyages. In the case of Spanish Wikivoyage, there are not any editor with knowledge of coding, and due to that we are not by ourselves able to write or develop any tool or extension to improve technically Wikivoyage. But the very few dedicated editors there will be willing to do everything within our reach to collaborate with this project. It's sad and a pity that Wikivoyage will not receive any active support. --Zerabat (discusión) 22:25, 4 October 2017 (UTC)
- Even though I am an enthusiastic Wikivoyage editor in several languages, I can understand that WMF considers Wikivoyage as less important than Wikipedia/Wiktionary. I am glad that they host our Wiki free of charge/ads, and maintain (security bugs etc) the software that runs it. Wikivoyage-specific technical improvement will still be possible via community development and GSoC/etc. I totally agree with you that inter-languages collaboration is important, and I am a living proof that some members of the English Wikivoyage care about other languages :-) Syced (talk) 08:39, 5 October 2017 (UTC)
Participate in Dispute Resolution Focus Group
The Harvard Negotiation & Mediation Clinical Program is working with the Wikimedia Foundation to help communities develop tools to resolve disputes. You are invited to participate in a focus group aimed at identifying needs and developing possible solutions through collaborative design thinking.
If you are interested in participating, please add your name to the signup list on the Meta-Wiki page.
Thank you for giving us the opportunity to learn from the Wikimedia community. We value all of your opinions and look forward to hearing from you. JosephNegotiation (talk) 16:28, 2 November 2017 (UTC)
Announcing Map improvements 2018
Over the next four months, the WMF Collaboration team will be making improvements to mapping software (Kartographer) and related functions. The team’s engagement with maps was prompted in part by the overwhelming support the maps community gave the 2017 Community Wishlist proposal for Kartographer Improvements. The project, which we’re calling Map Improvements 2018, is currently in its very early research and planning stages. It has a limited term and is scheduled to conclude at the end of June.
The immediate goals of the Map Improvements project are:
- To ensure that Kartographer and the associated maps technology stack are stable and can be easily maintained as maps gain a wider audience.
- To accomplish the two “main wishes” named in the Community Wishlist proposal, along with as many of the other wishes as are possible in the time provided. The main wishes are T112948, “All map location names should be shown in the user's language” (an extremely challenging but crucial job), and T180907, “Add zoom level 19.”
Goals that relate to extending maps to a wider audience—such as bringing mapframe functionality to English Wikipedia (as requested by RfC) and making sure that mapframe works properly on wikis that use Flagged Revisions—are also under serious consideration.
Enabling a helpful feature for Template editors
Read this in another language • Please help translate to your language
The team working on TemplateStyles at the Wikimedia Foundation would like to enable TemplateStyles on this wiki.
TemplateStyles is a feature to allow non-administrators to write and manage CSS styles for templates. It allows contributors who edit templates to separate content and presentation. A good web practice that makes it easier to manage the layout of templates. If you don't edit templates, this will not have any impact on your contributions.
TemplateStyles is useful for a few reasons.
- It makes it possible for templates to work better on mobile.
- It cuts out confusion on where to apply CSS rules.
- Editing CSS is currently limited to administrators, which is a major barrier to participation.
- All stylesheets must be loaded on all pages (whether they actually use the page or not), which wastes bandwidth and makes debugging style rules more difficult.
This is an optional feature and no one must use it, but template contributors are encouraged to do so! Please discuss and let us know if there are any concerns. If there are no concerns we will proceed to deploy the feature on the 28th of March.
An update on map internationalization
I wanted to let you know that Collaboration Team is planning to release map internationalization next week for testing on testwiki. When it’s ready, we’ll post a note to let you know. But meanwhile, you might like to check out the detailed post I added last night to the Map Improvements 2018 project board: Special Update on Map Internationalization. It includes a lot of information on the project status, how the feature will work, how we imagine it might be useful, what the known limitations are, etc. . I’m looking forward to getting your input on this challenging but important feature; the best place to leave your ideas and questions is on the project talk page. —JMatazzoni (WMF) (talk) 21:36, 20 April 2018 (UTC)
Maps in the language of your choice—try it out on testwiki
You can now display maps in languages of your choice on testwiki. I made two pages to demonstrate the new features, on testwiki and testwiki2 (embedded maps on test2 are dynamic; those on test are static until you click to pop up an enlargement).
By default, internationalized maps display in the language of the wiki (which is English for the testwikis). So to experiment with these features, you’ll want to use the two new mapframe parameters we’ve added. Just insert them into your mapframe code.
- lang=”xx” Shows map labels in the language you specify with the short language codes used for each wiki.
- lang=“local” Shows map labels in the languages of the territory mapped (essentially opting out of internationalization).
Right now, internationalization works only with mapframe, not maplink (which should be working some time next week). You can read more about this new feature and how to use it on the Map Improvements 2018 project page, under Updates. Our plan is to wait a week or two and assess user comments about the feature. At that point, we’ll decide whether to move forward with a general release or keep making fixes.
Map internationalization launched everywhere—and embedded maps now live on 276 Wikipedias
As of today, interactive (Kartographer) maps no longer display in the language of the territory mapped; instead, you’ll read them in the content language of the wiki where they appear—or in the language their authors specify (subject to availability of multilingual data). In addition, mapframe, the feature that automatically embeds dynamic maps right on a wiki page, is now live on most Wikipedias that lacked the feature. (Not included in the mapframe launch are nine Wikipedias that use the stricter version of Flagged Revisions).
If you you’re new to mapframe, this Kartographer help page shows how to get started putting dynamic maps on your pages. If you’d like to read more about map internationalization: this Special Update explains the feature and its limitations; this post and this one describe the uses of the new parameter, lang=”xx”, which lets you specify a map’s language. And here are some example maps, to illustrate the new capabilities.
These features could not have been created without the generous programming contributions and advice of map-loving volunteers, including Yurik, framawiki, Naveenpf, TheDJ, Milu92, Atsirlin, Evad37, Pigsonthewing, Mike Peel, eranroz, Gareth and Abbe98. My apologies to anyone I’ve missed.
The Collaboration team's Map Improvements 2018 project wraps up at the end of June, so please give internationalized maps and mapframe a try soon and give us your feedback on the project talk page. We’re listening. —JMatazzoni (WMF) (talk) 20:59, 9 May 2018 (UTC)