Wikivoyage:Travellers' pub

From Wikivoyage
This is an old revision of this page, as edited by 118.93.67.66 (talk) at 04:22, 6 November 2013 (Some thoughts on flexibility).

Latest comment: 10 years ago by 118.93.67.66 in topic Some thoughts on flexibility
Jump to navigation Jump to search
Welcome to the Pub

The Travellers' Pub is the place to ask questions when you're confused, lost, afraid, tired, annoyed, thoughtful, or helpful. Please check the FAQ and Help page before asking a question though, since that may save your time and others'.

Please add new questions at the bottom of the page and sign your post by appending four tildes (~~~~) to it, but otherwise plunge forward!

  • If you have a question or suggestion about a particular article, use the article's talk page to keep the discussion associated with that article.
  • Issues related to more than one language version of Wikivoyage are discussed in the Wikivoyage Lounge on Meta.

Pull up a chair and join in the conversation!

Experienced users: Please sweep the pub

Keeping the pub clean is a group effort. If we have too many conversations on this page, it gets too noisy and hard to read. If you see an old conversation (i.e. a month dormant) that could be moved to a talk page, please do so, and add "{{swept}}" there, to note that it has been swept in from the pub. Try to place it on the discussion page roughly in chronological order.
  • A question regarding a destination article should be swept to the article discussion page.
  • A discussion regarding a policy or the subject of an expedition can be swept to the policy or expedition discussion page.
  • A simple question asked by a user can be swept to that user's talk page, but consider if the documentation needs a quick update to make it clearer for the next user with the same question.
  • A pointer to a discussion going on elsewhere, such as a notice of a star nomination or a request to comment on another talk page, can be removed when it is old. Any discussion that occurred in the pub can be swept to where the main discussion took place.
Any discussions that do not fall into any of these categories, and are not of any special importance for posterity, should be archived to Project:Travellers' pub/Archives and removed from here. If you are not sure where to put a discussion, let it be—better to spend your efforts on those that you do know where to place.

Great map of Wikipedia articles

Here we should see if we can get WV added to it. Travel Doc James (talk · contribs · email) 17:34, 27 August 2013 (UTC)Reply

Some of the positions are quite badly out. How can they be fixed? Peter (Southwood) (talk): 18:08, 27 August 2013 (UTC)Reply
Fix the coordinates on the corresponding Wikipedia article, I presume. LtPowers (talk) 00:19, 28 August 2013 (UTC)Reply
Equivalent for Wikivoyage: http://maps.wikivoyage-ev.org/w/artmap.php?lang=en As Peter said, fixing coordinates on English Wikipedia is a priority. Wikivoyage should reuse these coordinates (see for instance the property coordinate location at Los Angeles Wikidata). Nicolas1981 (talk) 02:01, 28 August 2013 (UTC)Reply
How often are these updated? My changes do not seem to have any effect. Peter (Southwood) (talk): 12:13, 29 August 2013 (UTC)Reply
I believe it's currently once a month, at the beginning of the moonth, Peter. --W. Franke-mailtalk 16:23, 29 August 2013 (UTC)Reply
Thanks, Frank. That is a rather low frequency. I assume it is a resource hungry process. Where do you get information on this feature? Peter (Southwood) (talk): 17:38, 29 August 2013 (UTC)Reply
Good question. It's a neat map, but I'm not sure how thorough it is. On the pt: version, I can see that articles I added geo to on August 1 are not there yet. Some I added at the beginning of July are now there, yet there are others which have had properly filled-in geo tags for a couple of years now that are not showing up on there. It would be great if we could get it working completely and frequently updated. Texugo (talk) 12:47, 29 August 2013 (UTC)Reply
The WV article map is updated monthly for all language versions at the beginning of the month. Using the latest available data base dump . This can be up to two weeks old. @Texugo: Please list some specific examples of missing items in the map. The only way I can eliminate this errors. -- Joachim Mey2008 (talk) 17:40, 29 August 2013 (UTC)Reply
The one that stood out to me at this time was pt:Osasco, which has had its geo coordinates filled in since sometime in 2011, but does not show up on the map. I may be able to hunt down others... Texugo (talk) 18:25, 29 August 2013 (UTC)Reply
The marker for pt:Osasco is present but in the wrong position . The coordinates in tl:Geo were wrong. - Joachim Mey2008 (talk) 04:15, 30 August 2013 (UTC)Reply
Yes, I noticed that, thanks. I have fixed the coordinates. If I come across anything else, I'll let you know. Texugo (talk) 11:25, 30 August 2013 (UTC)Reply
I like the map, but how is it intended to be used? Peter (Southwood) (talk): 07:52, 31 August 2013 (UTC)Reply
One more way to promote the project. A link to it inviting people to browse via map might be useful. Travel Doc James (talk · contribs · email) 10:52, 31 August 2013 (UTC)Reply
I really, really really really want to embed ArtMap at Destinations. Can we do this? --Peter Talk 03:33, 4 September 2013 (UTC)Reply
I am all for it! With prominent linkage goodness from the front page. That map is fun, and now that our geo coverage is up from around 55% to over 82% of our articles this month, it should be more and more worthwhile. I can't wait to see the 6500 or so new blips show up on the map when it next gets updated on Oct. 1. Texugo (talk) 11:20, 4 September 2013 (UTC)Reply

Destination-specific travel topics

I've noticed there are a lot of articles considered "Travel Topics" that are in fact just an expansion on a given destination article, or are in fact a destination-article in themselves. The (star-topic) Chicago skyline guide is, in a way, just a huge expansion of multiple See listings; while Diving the Cape Peninsula and False Bay (also a star) can be considered a "specialized" destination article, dealing with a specific destination but only listing one kind of activity to be done there. In my opinion, it'll be much for the benefit of our users if the Chicago article was PartOf Chicago and the diving article a PartOf South Africa. Therefore, I would like to suggest creating a new type of article – "Specialized Destination Articles", which are hierarchically destination articles, but their content only deals with one kind of activity or attraction for a given destination. For convenience, these articles can only relate to destinations smaller than countries (e.g. the two aforementioned articles, but Driving in Australia would still be a travel topic, since it's very general). Additional examples for such specialized articles may include Cycling in Copenhagen, Literary London as well as moving Judaean Desert#Hiking trails (written by me) to a new article. What do you think? Tamuz (talk) 22:30, 29 August 2013 (UTC)Reply

Interesting suggestion, I'm intrigued to see how this discussion will play itself out, but right off the bat this is something I'd probably not oppose outright. -- AndreCarrotflower (talk) 00:04, 30 August 2013 (UTC)Reply
Sounds like a good idea to me. Nicolas1981 (talk) 00:10, 30 August 2013 (UTC)Reply
In general we've always requested that such destination-specific information start out in the parent article (London, Copenhagen, etc) and only be moved to a separate article once it gets too extensive for the main article. Otherwise one of two things tend to happen: we get a lot of incomplete topic articles that then need to be merged back into the main article, or we get detailed topic articles without a good summary of that information in the main article. That said, splitting out detailed information into its own article is a fairly common practice, just err on the side of caution - don't split until warranted, and try to make the topic article as broad as possible (ie Cycling in Denmark would be preferable to Cycling in Copenhagen, if such a broad topic makes sense). -- Ryan (talk) 00:28, 30 August 2013 (UTC)Reply
@Tamuz, I don't see how this would significantly differ from the status quo except by changing the hierarchy. Could you explain for example, why Diving the Cape Peninsula and False Bay should be PartOf the Western Cape rather than PartOfTopic Diving in South Africa? Also how you propose the local topics be linked from the destinations they are PartOf, and where applicable other nearby destinations they are not directly PartOf, like all the destinations in the Cape Peninsula and the coast and nearby hinterland of False Bay such as Hout Bay, Camps Bay, Simon's Town, Somerset West, Stellenbosch, Rooi-els etc, but are relevant to travelers visiting that destination? Also, how do you propose the connection between Diving the Cape Peninsula and False Bay and other diving articles such as Diving in South Africa and Scuba Diving should be handled? Peter (Southwood) (talk): 06:05, 30 August 2013 (UTC)Reply
@Ryan I agree completely. Even if my suggestion does get consensus, that doesn't mean people should start creating Hiking around Moscow, not until Moscow#Do starts overflowing with hiking trails.
@Peter The main differences from the current state are (a) that these articles will not be listed under Travel topics (but naturally there should still be a link from the travel topic Diving in South Africa to the Specialized-Destination article Diving the Cape Peninsula and False Bay); and (b) users will have an easier time navigating back from that diving article to its parents Western Cape <- South Africa, which I think should be more convenient, since most people probably wouldn't go from, say, America to South Africa just for a few-day diving safari - they'd probably want to visit other attractions while they're there. Also, in general, I think it'd be more intuitive if travel topics deal mainly with general guidelines and suggestions, while destination articles focus on technical details such as locations, prices, etc... . In my opinion, that diving article currently feels de facto much more like a destination article than a travel topic. Tamuz (talk) 14:19, 30 August 2013 (UTC)Reply
Dive guides are already considered to be their own distinct article type, with their own template and proposed status criteria. Texugo (talk) 15:04, 30 August 2013 (UTC)Reply
But hierarchically they're still a PartOf a travel topic, while in fact they're a destination, which is IMO both confusing and somewhat less convenient for navigation. And, of course, that's just the dive sites at this point, while I'd really like to get Judaean Desert#Hiking trails into its own Hiking in the Judaean Desert article, which I really think should be a PartOf Judaean Desert and not of Hiking and backpacking in Israel. Note that the hiking-in-Israel article is definitely a travel topic since it just lists general guidelines, while Judaean Desert#Hiking trails gives you only destination-specific technical information (path description, arrival info, etc...). Tamuz (talk) 17:44, 30 August 2013 (UTC)Reply
(edit conflict) Hmm, that's news to me. Maybe we should generalize that to incorporate other types of articles as Tamuz is suggesting. LtPowers (talk) 17:45, 30 August 2013 (UTC)Reply
Agreed. Come to think of it, Texugo's message does in fact seem to confirm there's a need for a destination-activity-specific article template; and why should diving be any different from hiking, or skiing, or cycling? Tamuz (talk) 17:50, 30 August 2013 (UTC)Reply
This discussion needs to be combined with the one here, as one will affect the other. Texugo (talk) 19:15, 30 August 2013 (UTC)Reply
I would like to know at what level the articles are to be integrated into the geographical hierarchy, as to the best of my understanding, it does not allow a destination to be PartOf more than one higher level region, and I expect that a large number of these destination/topics will overlap more than one conventional destination. Diving the Cape Peninsula and False Bay is just the one I am most familiar with, and it is most definitely part of several destinations (maybe 10 or more) at more than one level (at least three) in the geographical hierarchy. I don't object to the concept, but also don't see how it can be integrated with the current hierarchy, breadcrumb system and general policy on articles. I predict unforeseen consequences may complicate this issue, we need a fairly precise and detailed analysis of how it can be done and whether the current software will support the proposed changes. A graph or two may clarify the proposal. Peter (Southwood) (talk): 07:48, 31 August 2013 (UTC)Reply
Texugo, I guess the discussion you linked to does propose several options that solve the problem I noted, though in a different way than I proposed. These collapsible lists of Topics-In look like a very good idea. I did see that that discussion has been inactive for the past week. Has it just been abandoned? If so, I'll send a message there and try to revive it.
Additionally, there could be an advantage in viewing these topics-in articles as destination articles, at least in terms of their article-templates. The Dive-Site template looks pretty much like a destination template, and it would be good if articles such as Hiking-in, Cycling-in, etc... would also have a template like this, not as some vague convention but as an actual policy. Tamuz (talk) 22:06, 1 September 2013 (UTC)Reply

{{Pagebanner}}

Why do OtBP and disambiguation have the same icon in this template? --Xiaomingyan (talk) 10:17, 1 September 2013 (UTC)Reply

I've just changed back the edit to Template:Pagebanner that made the icons the same. OtBP and FTT articles now share the same icon - is that right? --Nick talk 11:32, 1 September 2013 (UTC)Reply
Well, this page uses the question mark. I'm a little bit confused now. --Xiaomingyan (talk) 13:04, 1 September 2013 (UTC)Reply
I changed the icon at the top of the Previously off the beaten path page to the "tick" icon. That is used for both OtBP and DotM. FTT has a little pen as an icon. Is that correct? --Danapit (talk) 08:22, 1 November 2013 (UTC)Reply

Category:Articles needing the Geo zoom defined

I added a line to Template:Geo so that, for country/region/huge city articles with no zoom parameter defined, it adds that article to Category:Articles needing the Geo zoom defined, so we can better track and take care of those. Texugo (talk) 14:22, 2 September 2013 (UTC)Reply

Great work! (I've been fixing a few countries' zoom levels as I slowly check for $ howlers).
Folks doing this work will often need to change the map centre too, since many use the co-ordinates of the capital and the capital city is rarely in the middle of the country. --W. Frankemailtalk 18:51, 2 September 2013 (UTC)Reply
Interesting point. Does that mean that in such cases we can not use Wikidata information? Or should we fix Wikidata information? What is the Wikidata policy on this? Nicolas1981 (talk) 04:14, 3 September 2013 (UTC)Reply
From purely a Wikivoyage perspective, my very loud advice would be to ALWAYS check the co-ordinates are appropriate for what you are trying to achieve and set the zoom level to something appropriate too. Remember that if you don't set a zoom level, that level will currently default to 13 (that default level of 13 may be changed in future, so always best to set a zoom level in our templates). A zoom level of 13 is always going to be inappropriate in a country level article (except perhaps for Monaco or San Marino) so "machine edits" like this one where {{geo|17.066666666667|-88.7}} was added, rather than a more appropriate {{geo|17.2|-88.7|zoom=8}}, so the map would be centred more equidistantly between the northern and southern borders of Belize and show more than just a small patch of jungle when opened or this one, where the dynamic map of the third largest country in the world opens at a high magnification view of the tiny village of Hézuò "City" are perhaps not to be encouraged. --W. Frankemailtalk 13:57, 3 September 2013 (UTC)Reply
Checking the ones on my watchlist, I find about half are fine with the default and the others easily fixed.
I also notice that some maps show the old WV logo. Since there is a legal problem with that logo, this should be fixed pronto. Pashley (talk)
Good point. As far as I know, all the maps at still have the old logo. Is it someone at de: that set that all up? Anyone know who to contact? Texugo (talk) 15:15, 3 September 2013 (UTC)Reply
@Nicolas - Wikidata does not store zoom information, so that part is all up to us. As for the centering, I can't imagine why anyone would object to moving the coordinates nearer to the geographic center of any region or country. I have changed a few of them on there myself already, but do not know if there is an official policy. Texugo (talk) 15:19, 3 September 2013 (UTC)Reply
Take, for example, Orleans County (New York). This is a county on the northern shore of New York State, meaning it is bordered to the north by Lake Ontario, with Ontario, Canada across the lake. Legally, then, the northern border of Orleans County is in the middle of Lake Ontario, and the geographic coordinates on Wikipedia reflect that. But that definition is silly for a travel guide; we need only show the land area of the county in our maps. So the centerpoint should be considerably farther south for our purposes. That's a case where there's a disconnect between the WP and WV purposes and I don't know how to resolve it. LtPowers (talk) 00:02, 4 September 2013 (UTC)Reply
I see your point, but since we are not directly using the wikidata coordinates in our geo tag (so far at least), there is nothing to stop us from setting our center point wherever we need to.
I just used AWB to add coordinates from Wikidata to every article lacking them and for which the respective data item had them, adding geo templates to several thousand articles and bringing our total geo coverage way up to 82% of all destination articles. Basically this means there are two sets of articles we need to focus on: the ones in this category I created above (about 2450 articles), which have coordinates but may need to be adjusted or zoomed, and that other 18% (about 4600 articles) that have no geo info, which probably includes many regions which do not correspond to a wikipedia article, articles which are connected to the wrong wikidata item, etc. Texugo (talk) 01:51, 4 September 2013 (UTC)Reply
I imagine we can use WikiData by default, and override as needed for special cases like Orleans County (New York). Nicolas1981 (talk) 05:25, 4 September 2013 (UTC)Reply
Well, we can't use Wikidata coordinates automatically by default, not yet at least, because if you have {{geo}} invoke coordinates directly from wikidata, the articles don't get included in the article map, which is why I copied all those coordinates into manually configured geo templates instead of proposing a more automatic solution. I already had a template-based automatic solution all worked out on pt:, but it seems that the article map scrapes the coordinates from the unexpanded source code, so if the coordinates are not physically written there, they don't get used on the map. Texugo (talk) 11:12, 4 September 2013 (UTC)Reply
artmap.php will be modified to extract its data from Wikidata. I think that in the future, {{geo}} should only be used in cases where Wikidata is not appropriate for some reason. Nicolas1981 (talk) 06:40, 5 September 2013 (UTC)Reply
Proposal to store zoom level on Wikidata Nicolas1981 (talk) 06:35, 5 September 2013 (UTC)Reply

Request for feedback: listing page consolidation

It would be much appreciated if people could provide feedback at Wikivoyage talk:Listings#Proposed consolidation of the SEVEN current Wikivoyage:Listings pages where a discussion about whether to consolidate our seven current Wikivoyage:Listings pages has stalled. There may be a larger point to be made about whether it is desirable or not to consolidate policy pages, so please add your thoughts. -- Ryan (talk) 01:39, 5 September 2013 (UTC)Reply

Bump. I feel strongly that simplifying our documentation for something that is such a core piece of our site's functionality would be a huge win for new users, but the discussion needs additional feedback. -- Ryan (talk) 15:20, 25 September 2013 (UTC)Reply

Best edit counter for Wikivoyage?

I have a strong suspicion that the edit counter I'm using is not very accurate since it shows I've only made a couple of thousand edits over the last year, whereas my current Active users list shows I've made more than one thousand in the last 30 days.

Does anyone know a better one, please? --W. Frankemailtalk 22:44, 7 September 2013 (UTC)Reply

I think you can see edit count in your preferences -- only other way I know of is to use an API. en.wikivoyage.org/w/api.php?action=query&list=users&ususers=USERNAME&usprop=editcount - how accurate that is, is unknown to me... especially if the "initEditCount.php" hasn't updated the sql table lately... (that info is for 1.19 so probably is still valid) The sql table may or may not be accurate... COUNT(*) WHERE rev_user=user_id -- as for extensions or other programs, no idea... Good luck! Matroc (talk) 00:01, 8 September 2013 (UTC)Reply
That API still works and bumps my total up by a thousand or so; thanks! --W. Frankemailtalk 14:24, 8 September 2013 (UTC)Reply

Calculating map zoom level from Wikidata

If all goes well, place items will soon include a "diameter" value that describes "rough diameter of the object in meter, used for selecting the scale of the map and for uncertainty of an area".

Converting this diameter to a Google Maps-type zoom level will probably be implementable in Lua using one of the algorithms suggested as solutions to this question: http://stackoverflow.com/questions/6048975/google-maps-v3-how-to-calculate-the-zoom-level-for-a-given-bounds

Cheers! Nicolas1981 (talk) 06:09, 9 September 2013 (UTC)Reply

Gold Coast

Gold Coast was just linked to by the official Wikipedia Facebook page. Keep an eye on it as traffic may increase for a bit. LtPowers (talk) 23:03, 12 September 2013 (UTC)Reply

They've tweeted as well and they often tweet about our article. --Saqib (talk) 06:49, 13 September 2013 (UTC)Reply

English in OSM maps

My article about Mitzpe Ramon has an embedded map as well as a link to an external one, but the street names in these maps are shown in Hebrew. They use the Mapnik (OSM) layer; now, Open Street Map does have both a Hebrew and an English entry for all of these streets, only the default display name is the Hebrew one. I've tried changing the default name over at the OSM website (which is a sort of a wiki), and it did solve the problem, but it turned out that I acted against their policy and my edits are about to be reverted (so right now, the streets in the northern half of the town do appear in English, but that will be changed back to Hebrew pretty soon). Can anyone who's familiar with the implementation of these dynamic maps provide some help about this? I did notice that the dynamic maps' URL does have a lang=en in the address, but that doesn't seem to work as I've expected. If it's of any help, one helpful user at OSM did point out that the address " http://toolserver.org/~osm/locale/en.html?zoom=16&lat=30.61189&lon=34.80542&layers=BT " does show the names in English. Tamuz (talk) 12:27, 13 September 2013 (UTC)Reply

"lang=en" simply means that your POIs are read from English Wikivoyage, it has nothing to do with the map itself. The link to the map should be changed by the map developer. --Alexander (talk) 12:41, 13 September 2013 (UTC)Reply
There is no function for it now. The link to the map should not be changed because the toolserver is not stable enough and is very slow. WMF are setting up a production server themselves, but no promises on the timeline. Once they get it set up, we will be able to get English names on English Wikivoyage, and Hebrew names on Hebrew Wikivoyage. See the Dynamic maps expedition and Wikivoyage/Wishlist. I suppose it should be made clearer on the "how to" guide? -- torty3 (talk) 13:34, 13 September 2013 (UTC)Reply
Related discussion: Wikivoyage_talk:Dynamic_maps_Expedition#Shanghai_map. Pashley (talk) 13:54, 13 September 2013 (UTC)Reply

Category:Pages linked to a data item for a disambiguation

Hi guys. I added a function to Module:Wikibase and an #ifeq statement to templates IsPartOf, Itinerary, Phrasebookguide, and PartOfTopic which checks whether the corresponding Wikidata item is marked as a WP disambig page. When it is, the article is added to the maintenance category Pages linked to a data item for a disambiguation. Those articles need to have their WD item corrected to correspond to the actual topic rather than the disambig page. (Note that our own disambig pages will not be showing up in the category.) When doing so, please move the links for any other Wikivoyage language versions which may also be present in the disambiguation item. Cheers! Texugo (talk) 17:01, 13 September 2013 (UTC)Reply

What is Module:Wikibase? I can't find any documentation for it. LtPowers (talk) 19:08, 13 September 2013 (UTC)Reply
It is a package of Lua modules for accessing WD properties which are unaccessible via #property. I have adapted it from it:Modulo:Wikibase, where it also still lacks documentation. Texugo (talk) 19:17, 13 September 2013 (UTC)Reply
Some of its functions I do not yet understand, but I will try to put some rudimentary documentation there shortly. Texugo (talk) 19:32, 13 September 2013 (UTC)Reply
OK. I whipped up some quick documentation for Module:Wikibase, to the extent that I understand it. Please have a look. Texugo (talk) 20:39, 13 September 2013 (UTC)Reply
Looks good. Next question: Why are some properties inaccessible via #property? LtPowers (talk) 23:01, 13 September 2013 (UTC)Reply
I'm probably not the best one to answer that question, but I think there are multiple answers depending on the property in question. For example, #property was prepared to call coordinates together and not prepared to call the latitude and longitude separately, which is the only way they are useful without further parsing, the wikipedia and other WV links are not technically properties with unique property names but rather language codes, etc. etc. I don't know why "capital" is included, since that one actually works with #property. Perhaps it would be better to ask Ricordisamoa, who is very active on Wikidata and who is developing Wikibase on it:. Texugo (talk) 02:44, 14 September 2013 (UTC)Reply

WikiProject Indonesia

I just saw this interview and thought Wikivoyagers might be interested in reaching out to those contributors to help improve coverage of Indonesia on Wikivoyage. Sharihareswara (WMF) (talk) 18:57, 16 September 2013 (UTC)Reply

Is anyone in touch with User:(WT-en) Burmesedays? He or she was a good contributor on WT, especially for Indonesian destinations, but as far as I know has never joined us here. I'd issue an invitation, but WT has long since disabled the "email user" feature mainly to prevent such communication and I do not have an email address to use. Pashley (talk) 20:26, 16 September 2013 (UTC)Reply
Burmesedays has vanished—hasn't responded to emails. --Peter Talk 21:32, 16 September 2013 (UTC)Reply

I'm here again at the moment adding content... Pratyeka (talk) 13:26, 17 October 2013 (UTC)Reply

My Voyage

Hi!

This has come up previously (see above), but for whatever reason the topic of conversation moved somewhat My Wikivoyage is the idea for a sort of 'Readers' Portal' (sort of analgous to the Community Portal) that gives the people who use our site a far more personal experience. 'What users?', I hear you cry; whilst this does not have any immediate SEO benefit, it does differentiate us further from another travel-based wiki.

The page I've linked to is only a quick mock-up of what such a page could look like. I'm certainly not suggesting that this is the finished article and would welcome your ideas and comments. My one caveat would be that this probably shouldn't be as complicated a page as our Main Page: MediaWiki doesn't really like images, hence the minimalist look I've gone for (would it be preferable to have all the squares in the same colour?).

Furthermore, the sections alluded to on that page are mostly fictitious, although based in the realms of the possible. Here's a quick description of the ones that don't currently exist:

  • This month's travel article - A space for a travel themed essay by a WV contributor. Still fairly controversial, but suggested previously.
  • Create an itinerary - An opportunity for readers to pull several articles (and listings within?) together to create an itinerary for their next trip. Suggested previously.
  • Where in the world? - Terrible name, but probably where users could go to make a map of their travels thus far. A long-term roadmap resident - is this possible?
  • Trip reports - Link to a directory of trip reports and opportunity to write their own. A button on that page would open a skeleton template to create a report within the user's space and would categorise it so that it would automatically be included in the directory.
  • Reviews - Link to 'How to write a review' and search box for specific locations. Could reviews be a separate tab above a page (between 'Page' and 'Talk'?) where listings are automatically copied (but aren't editable). Users could then write reviews and give a standardised star rating.
  • Notes from the field - Perhaps a description of the latest goings on within WV's editing side. This would be a means of turning readers into editors.

Sorry this is so long and rambles a bit; let me know what you think! --Nick talk 23:10, 16 September 2013 (UTC)Reply

I love the general idea of something like this. Something interactive is just what we need to differentiate ourselves with professional travel guides and that other site. Your mock-up leaves a lot to be desired, but I know you just whipped it up and weren't going for perfection. My concern about the layout would be mobile support—if we have something like this we'll get a lot of visitors directly from locations on their mobile devices. If this project ends up going forward, please put emphasis on that.
As for the individual features, each have their strengths and weaknesses so I'll discuss them individually:
  • "This month's travel article" – I'm not sold on this, but don't really have string feelings about it—it's not the best or the worst.
  • "Create an itenerary" – I like this idea. It's simple, but it helps the traveller.
  • "Where in the world?" – It needs a better name, but I definitely like this! It gets the traveller engaged and interested. I wonder, though… Could we put this into Wikivoyage through an open-source dynamic map? Is it possible to adapt one to fit these purposes?
  • "Trip reports" – I like this. This would not only provide stuff for readers to read but also help us, the editors, to improve articles. We could have a group of editors who patrol these to find any useful information and transfer it to articles. That could greatly help us improve articles that have very little content.
  • "Reviews" – Not sure I like this. What exactly would be the point? It wouldn't help us improve Wikivoyage.
  • "Notes from the field" – Yes, yes, yes, yes! This would be extremely helpful in getting those readers who ignorantly think that editing Wikivoyage is a tedious and thankless job. This would be a great way of showing that it's actually fun! :)
This is a great idea and I hope it makes it off the ground. Thanks! Nick1372 (talk) 02:05, 17 September 2013 (UTC)Reply
Thanks very much for your comments! What do you think would be a better way of displaying the page? I'll have a play, but I'd welcome your ideas! I confess, 'Where in the world?' was a name before it was anything else - I'll get changing the name! Reviews have been on the Wikivoyage:Roadmap for sometime, though I do realise that lots of people's feelings towards them are mixed. I think the hope with those was that a higher level of interactivity (i.e. writing reviews) would draw more people in.
I'll keep working at it, but any more comments would be welcome! :) --Nick talk 10:30, 17 September 2013 (UTC)Reply

Ok, I've completely rebuilt it from the ground up, with mobile compatibility in mind. It's now effectively lots of pagebanners at 9:1 scale, that would act as links to the pages in question. It's still a little rough around the edges, but hopefully this is aesthetically preferable! There are still couple of issues, but in appearance at least, I'd hope that we'd be able to use something like this. See the revitalised, revamped and renovated page here. --Nick talk 14:39, 17 September 2013 (UTC)Reply

The appearance is much improved and no longer reminds of the crappy Windows 8 start page. Regarding the individual features, my thoughts pretty much echo those of Nick1372 in every case. Additionally, as I mentioned before elsewhere, I do not like the name "MyWikivoyage", as it conjures up MySpace and all the cheese that came with it. Texugo (talk) 15:04, 17 September 2013 (UTC)Reply
Glad to hear you prefer how it looks! The name can be changed very easily, so if you have any ideas for better ones, do let me know! Not all the features currently listed would probably survive until implementation (if it is implemented at all), but I think it's best to list as many things as we have ideas for the moment and see what everyone thinks. --Nick talk 15:13, 17 September 2013 (UTC)Reply
The new layout is definitely an improvement. Great job! Nick1372 (talk) 01:30, 18 September 2013 (UTC)Reply
Thanks very much! If you've any ideas for improving either the aesthetic or the content, I'd be glad to hear them! :) --Nick talk 01:34, 18 September 2013 (UTC)Reply

What does everyone else think about its features? Are there any ones that have been missed or should be removed? I've not had that many opinions about the actual concept itself. --Nick talk 11:58, 19 September 2013 (UTC)Reply

I do not like the notion of 'trip reports' at all and am inclined to be quite leery of 'create an itinerary'. We want most information to go into destination articles, not into such reports, and we don't need a bunch more itineraries that may be incomplete or may not meet our criteria for keeping them once the original writer loses interest. We may already have too many itineraries in some areas; see Talk:Banana Pancake Trail#Consolidation? for one discussion.
Of course it is possible to create reasonable itineraries after a trip. I started Yunnan tourist trail and Overland Kunming to Hong Kong after one of mine. With a bunch of contributions from others, I think those are now both worthwhile articles. It seems clear to me that having 'trip reports' is not going to lead in that direction. It seems possible that 'create an itinerary' could, but how do we ensure that? An experienced user could probably just go ahead & create an itinerary with existing tools and get it more-or-less right; see World Heritage Sites Tour in Sri Lanka for a recent example. However, if we are going to encourage new users to create itineraries, then I think we will need to give them quite a bit of guidance.
I am less certain about reviews. They seem to carry a large risk of biased edits, exploitation by marketers, etc. Of course those risks are already present and we have procedures in place for dealing with them. But will allowing reviews overstress those? Pashley (talk) 17:39, 13 October 2013 (UTC)Reply
Thanks for your thoughts! The trip reports would not be instead of articles, but in addition - people like talking about their holidays! Te reports would provide us with a mine of photos and information and users would of course be encouraged to edit the corresponding articles at every step of the way.
'Create an itinerary' would simply be a way for users to string articles together for their ease of use - the tool would not be for creating Wikivoyage itinerary articles; I've perhaps not made that plain enough.
Reviews are quite a controversial topic (not unlike videos), but we could perhaps delay that feature. I've effectively tried to incorporate as much as I can from the roadmap into My Voyage and seen what I could get away with! --Nick talk 23:55, 14 October 2013 (UTC)Reply

Names

And now, a few ideas for names if you're not a fan of 'My Wikivoyage':

  • Voyagers' Club
  • Departure Gate
  • Check-in desk
  • VoyageWiki

Any thoughts or different ideas would be gratefully received! :) --Nick talk 23:27, 17 September 2013 (UTC)Reply

I don't have any strong feelings about these alternate names except "VoyageWiki". The use of the word "wiki" isn't helpful at all; it might make visitors think they're in something that requires them to learn wikicode & edit.
I actually like "My Wikivoyage" the best. I don't see an issue with confusing it with MySpace. Keeping the two words apart should be enough of a distinction, no? If that's a bigger problem then I think, though, how about just changing it to be "Your Wikivoyage"? That has pretty much the same effect. Nick1372 (talk) 01:30, 18 September 2013 (UTC)Reply
I think I agree about My Wikivoyage - it's simple, personal and, if we keep the words separate, shouldn't conjure up too many memories of MySpace cheese. The names I've suggested above are pretty second-rate if I'm brutally honest... --Nick talk 01:32, 18 September 2013 (UTC)Reply

Perhaps "Mon voyage" (my voyage) as a variation on "bon voyage"? No need to include the word "wiki". K7L (talk) 01:57, 18 September 2013 (UTC)Reply

I don't think anyone relates "My" to "Myspace" any longer. Its a common descriptor to a personal view across an account - "My Ebay", etc. However, I agree we should consider dropping the wiki. My Voyage. The only problem is, we're not going to own the domain. --Inas (talk) 03:20, 18 September 2013 (UTC)Reply
"My Voyage" sounds good to me too, though as you say, we'd have to check trademarks and the like beforehand. Do either of you have any thoughts about the content and appearance of the page itself? At present, for example, we don't really have a way of creating user maps, unless I've missed something. On that point, is there anything that you'd like to see included that I've left out? As it's My (Wiki)Voyage I'd like to somehow integrate the user page into all of this, though I'm not quite sure how that would work. --Nick talk 07:29, 18 September 2013 (UTC)Reply
A trifling matter, I know, but should it be called My Voyage or MyVoyage? --Nick talk 23:45, 8 October 2013 (UTC)Reply
CamelCase is kinda passé, IMO. LtPowers (talk) 16:10, 9 October 2013 (UTC)Reply
I think you're right. It also means I don't have to move the page again, which can only be a good thing! What do you think the way the page looks now? --Nick talk 16:12, 9 October 2013 (UTC)Reply

Next steps

Hi! Now that a major issue with the structure of the page has been fixed (Thanks Shaun and Ryan!), I was thinking that we could perhaps look into taking the next steps with the freshly re-christened My Voyage. Not all of the features listed are currently ready or approved, so we could do with thinking about that. I've created a few of the sub-pages, but there's still much to do. If you have any other thoughts or ideas about the page or concept as a whole, I'd be very glad to hear them! Wikivoyage has had a difficult week, so it would be good to keep our momentum on things like this going. --Nick talk 21:00, 6 October 2013 (UTC)Reply

Help!

Hi!

I've got some of the proposed features working on the My Voyage page, but some of them are still proving rather difficult to engineer. Whilst we've decided that reviews should probably be put on hold for the moment (see below), it would still be nice to get most of the rest functioning. At present, I'm struggling to think of a way to set up easily creatable itineraries (that might work like the watchlist?) and interactive maps that record a user's travels. If you've any ideas, I'd be really interested to hear them! I was also wondering whether the 'Video' section could be a link to a WV YouTube channel. I realise that videos on the site itself are still highly controversial, but, when mooted at the same time, a YT channel received a slightly less damning reception.

Let me know what you think! :) --Nick talk 16:48, 13 October 2013 (UTC)Reply

Nick, I don't see any possibility where a user can create maps on-wiki unless they request for one and the requested map will be created manually. --Saqib (talk) 17:23, 13 October 2013 (UTC)Reply
Thanks for that Saqib - I was hoping there'd be a way of doing it through JavaScript or something, but we shall see. Any ideas about the rest of it? --Nick talk 18:50, 13 October 2013 (UTC)Reply
Perhaps we will require to install a extension which will allow a user to create and publish customised maps but I'm not sure which one. --Saqib (talk) 05:34, 14 October 2013 (UTC)Reply
A YouTube channel seems like a good idea. We should expand to as many platforms as possible to reach a younger audience. However, I'm a little confused as to what the actual content of the videos would be… Nick1372 (talk) 22:23, 13 October 2013 (UTC)Reply
I'm not sure to be honest either - it just seemed like something we should have! Perhaps travelogues and things? It would give us something to tweet about at least! Are there any features that you feel uncomfortable with? --Nick talk 22:35, 13 October 2013 (UTC)Reply
Not sure I understand the question… Are we still talking about YouTube? Nick1372 (talk) 02:01, 15 October 2013 (UTC)Reply
Whoops! :) The first part of my response is referring to YT . I got a bit confused yesterday and the second part is sort of referring you to Pashley's comments above. Do you have any thoughts about the other proposed features? --Nick talk 02:04, 15 October 2013 (UTC)Reply
Okay. About the specific features themselves, my thoughts are pretty much the same as what I said way back when this discussion started; maybe except for the fact that I like the idea of reviews even less. However, I did look at your mockup. It's coming along nicely, but the Trip Reports part doesn't make it clear enough that the user would not be creating an article. Your participants need to know that their work won't be examined with a microscope against the MOS & that they won't need to learn the complexities of MediaWiki. You'll have a lot more participants if you tell them that they'll have the freedom to write without limits.
Of course, you must also remind them that they don't have complete freedom. You should start making up a concrete policy of what to do with offensive submissions and whatnot.
Just a general note: You should decide now whether the page is going to be in British English or American English.
Other than that, the page looks great. Mobile compatibility is fine, and the starting page images are attention-grabbing. I hope you won't mind if my OCD and I do a little copy editing, though… Nick1372 (talk) 02:40, 15 October 2013 (UTC)Reply
Thanks very much for your thoughts! As stated somewhere on this page (below, I think?) we'll probably exclude reviews, at least for the moment. Please feel free to do whatever you'd like with the pages - it's nice to have someone else working on it as well! :) --Nick talk 03:02, 15 October 2013 (UTC)Reply

Red images

A number of article still have broken images (name of the image appears in red). Is there a list of those?

Many months have passed since the migration and many images have been correctly relinked manually. The remaining is probably mostly in low-traffic articles. Maybe it is time to remove them all by bot or manually? Nicolas1981 (talk) 05:21, 17 September 2013 (UTC)Reply

Nicolas, do you mean these? They should be 1150 by now. Looking at other Nick's nice plot, heir number is slowly yet steadily dropping. Danapit (talk) 06:02, 17 September 2013 (UTC)Reply
I believe you meant to give this link: Category:Pages with broken file links. Texugo (talk) 11:26, 17 September 2013 (UTC)Reply
Oh yes, exactly. Thanks. Danapit (talk) 11:41, 17 September 2013 (UTC)Reply
I have slowly being going through the list of red links. Sometimes finding alternatives on Commons other times simply deleting the reference. A very slow task would be good if others could help. If each of other did one a day the list would be go down at a good pace. Would help wit

Hiding the page titles in the main namespace

Can someone please point me to what our final solution was for hiding the native page titles on articles in the mainspace? I need it for pt: Thanks. Texugo (talk) 17:04, 18 September 2013 (UTC)Reply

If I understand you correctly, you can find it in the {{Pagebanner}} code. Peter (Southwood) (talk): 05:38, 19 September 2013 (UTC)Reply
Or are you referring to this discussion? Peter (Southwood) (talk): 07:38, 19 September 2013 (UTC)Reply
Our banner template is equivalent to the one here, so I don't think it's there. And from the second discussion you mentioned, I had already tried what I thought was the latest fix, adding:
if ($('div.topbanner').length > 0) $('#firstHeading span').hide();
to the .js file. But that doesn't seem to have worked so far, even with purging the cache, unless it for some reason takes a really really long time to start working... Texugo (talk) 11:27, 19 September 2013 (UTC)Reply
There doesn't seem to be any record in the banner expedition discussion of what was actually done, so I guess the best bet will be to ask the people closest involved, which seems to be Andyrom75, Shaundd, torty3 and Ryan. So lets see if the new notification system pings them. Cheers Peter (Southwood) (talk): 16:20, 19 September 2013 (UTC)Reply
You want the following from MediaWiki:Common.js:
        /* Hide normal page title and move location of geo map symbol when a page has a pagebanner */
        $(".topbanner").closest(".mw-body").children(".firstHeading").hide();
        $(".topbanner").closest("#mw-content-text").children("#geoCoord").css({top:0});
The changes that were made to the DISPLAYTITLE magic word required that we use a Javascript hack to hide the title. -- Ryan (talk) 16:43, 19 September 2013 (UTC)Reply
Also note that the current version of pt:MediaWiki:Common.js has an unclosed comment ("/* Esconder títulos no espaço principal quando banner está presente") so any Javascript following that comment won't be executed. -- Ryan (talk) 16:46, 19 September 2013 (UTC)Reply
Well spotted, Ryan! --W. Frankemailtalk 16:50, 19 September 2013 (UTC)Reply
Perfect. Got it working. Thanks so much guys. Texugo (talk) 16:54, 19 September 2013 (UTC)Reply
Well, actually, almost working. It didn't get rid of the line above the breadcrumb, and the geo icon is too high, encroaching on the search box. Any ideas? Texugo (talk) 16:58, 19 September 2013 (UTC)Reply
Try changing:
             if ($('div.topbanner').length > 0) $('#firstHeading span').hide();
...to:
             if ($("div.topbanner").length > 0) {
               $("#firstHeading").hide();
               $("#mw-content-text").children("#geoCoord").css({top:0});
             }
Alternately, if you want to keep en: and pt: in sync then just copy the last three lines of MediaWiki:Common.js. -- Ryan (talk) 17:21, 19 September 2013 (UTC)Reply
I agree that the page looks better without the redundant title, but suspect that removing the <title> tag may be a bad idea in terms of visibility to search engines. I have asked about this at Wikivoyage_talk:Search_Expedition#Questions Pashley (talk) 17:47, 19 September 2013 (UTC)Reply
Sorry, Ryan. I'm getting a little confused. Do I need both the .js code and the .css? I had both when it was doing as described above with the line and geo icon off. I removed the .js code and the title came back. Texugo (talk) 18:17, 19 September 2013 (UTC)Reply
Unless I'm mistaken, hiding the title is done entirely with JS now as there wasn't any way to conditionally hide it for pages with page banners using only CSS. -- Ryan (talk) 20:16, 19 September 2013 (UTC)Reply
Problem now resolved. Thanks for you help. Texugo (talk) 20:30, 19 September 2013 (UTC)Reply

Locally uploading photographs of copyrighted buildings

I would like to upload my own photographs of copyrighted buildings (in Qatar) as a means of working around 'freedom of panorama' restrictions. I couldn't find any pages explaining how to upload directly to Wikivoyage, and so I uploaded them to Wikimedia Commons, which apparently is not the correct way to go about this.

Is there someone here who can explain how to upload directly to Wikivoyage, or possibly even how to move the existing images from Wikimedia Commons to Wikivoyage?

Many thanks, StellarD (talk) 11:06, 20 September 2013 (UTC)Reply

StellarD, you can upload the file here: Special:Upload and this might be the category to put them to: Category:Photos of copyrighted works. Danapit (talk) 11:32, 20 September 2013 (UTC)Reply
Thank you Danapit, this is exactly what I was looking for. StellarD (talk) 11:46, 20 September 2013 (UTC)Reply
No, no, please don't add Category:Photos of copyrighted works directly! All photos of non-free works uploaded locally should include Template:Non-free image, and that takes care of the categorization! If there are any files so categorized without transcluding the template, that needs to be fixed! LtPowers (talk) 00:05, 21 September 2013 (UTC)Reply
I hope I haven't created a mess here. I uploaded the files before LtPowers commented, but didn't add them to Category:Photos of copyrighted works because I didn't see where to do that, which it seems is just as well. They now appear in Category:GFDL_files – is this where they should be? And if not, how do I move them? Thanks, StellarD (talk) 07:37, 21 September 2013 (UTC)Reply
You add a category with the following syntax: [[Category:Some category name]]. But, as noted, please don't do that in this case. The category addition should be handled by the addition of Template:Non-free image. The syntax for that is more complex, but you can see an example of it on the Template page under "Template use". LtPowers (talk) 16:05, 21 September 2013 (UTC)Reply
Would it be possible to update documentation (probably on the upload page) so that it is clear how and when to add categories and when not? --Danapit (talk) 06:51, 24 September 2013 (UTC)Reply
We never add categories manually. On files or on article pages. Until recently we didn't even use categories at all. Categories should be completely invisible to the average casual user, so we don't even mention them on the upload form; it would only confuse people. The Upload form does link to the non-free content policy, which clearly specifies that Template:Non-free image be added to the image description page. LtPowers (talk) 14:14, 24 September 2013 (UTC)Reply
I see. Recently I have uploaded some candidates for featured articles banners and I added the category Category:DotM banners manually. Was that wrong, as well? How else does such photo get to a desired category? Danapit (talk) 15:40, 24 September 2013 (UTC)Reply
Welcome to the wonderful world of wikis. I was unaware of that category, and obviously whoever first used it was unaware that we should only assign categories via templates. The solution here is to create a template that would go on the file description page of such files, rather than manually categorizing each of them. Either that, or delete the category, as I don't quite see its utility, especially since DotM banners should be deleted once they're no longer in use. LtPowers (talk) 17:43, 24 September 2013 (UTC)Reply
Well, scratch that last part, as I forgot we keep the banners in the DotM archives. =) I'm still not sure we need the category, though. LtPowers (talk) 17:44, 24 September 2013 (UTC)Reply

Master list of articles w/o photos

I don't believe there is such a master list. Is there an easy way to generate one? I think there are a number of folks here (including me) who would like to do more work inserting good thumbnails into articles lacking them, and a master list would be a convenient way to know which articles to look at. Ikan Kekek (talk) 00:42, 21 September 2013 (UTC)Reply

You could use Free Image Search Tool enter a category (would recommend a small region to start with as the tool hangs if too many articles). Without any of the source fields ticked you just get a list of pages without images. If you tick Wikimedia Commons it will also display suggestions. --Traveler100 (talk) 10:54, 21 September 2013 (UTC)Reply
Thanks for the suggestion and the link. Ikan Kekek (talk) 10:58, 21 September 2013 (UTC)Reply

Old WV logo on map page

Not sure who can take care of this, but when you click from the map icon on any destination page to bring up the full page dynamic map, they have changed the WV logo in the bottom right corner to the new logo, but the logo which appears in the browser tab is still the old one. It doesn't seem to be just my cache, as far as I can tell. Texugo (talk) 23:36, 21 September 2013 (UTC)Reply

Confirmed. Should be a simple fix by the maintainer. LtPowers (talk) 00:59, 22 September 2013 (UTC)Reply
I changed the favicon. Maybe it is necessary to clear the cache or the reload the page. --RolandUnger (talk) 06:17, 23 September 2013 (UTC)Reply

We need more readers!

One way or another, I shan't be editing on this project for a while (Wikivoyage:User_ban_nominations#User:W._Frank]) so before I go, I'd like to draw your attention to Wikivoyage_talk:Search_Expedition#Action points to boost our readership. All the Best! --W. Frankemailtalk 12:49, 23 September 2013 (UTC)Reply

Thanks Frank. Travel Doc James (talk · contribs · email) 00:22, 1 October 2013 (UTC)Reply
I do think it is important to remove the hard-coded active hyperlinks to (the very censorious and dysfunctional) Wikitravel site on the majority of this site's pages if we ever want to get any visitors from search engines like Google. Most searchers don't go past the first two or three results you know.
Ikan Kekek suggested to me: "Unfortunately, unless Wikimedia Legal changes their minds about what kind of notification needs to be on the affected pages, there may not be much we can do about it." and I then asked him: "Where may I read this (mythical?) legal opinion, please? On the face of it, this (mythical?) legal opinion seems to fly in the face of the requirements of the cc-by-sa-3.0 license used by Wikitravel, Wikivoyage and Wikipedia unless this was a (secret) clause in the out of court settlement with Internet Brands. Do they realise that this (mythical?) strange decision dooms the English language Wikitravel to be inferior to Wikitravel in most search engine results forever (or at least until search engines value "mirror" sites as highly as "original" sites - which probably amounts to forever!). " to which he replied "I seriously don't think this is mythical. I understand that it was a part of the out-of-court settlement. I don't have the info at my fingertips right now and probably won't have time soon to research where you can read this verbatim. My suggestion is, if you can't find it in the Travellers' Pub, please post there and ask.".
Sorry if I've missed this elsewhere but this page is quite big and has already taken a while to skim. --118.93.47.31 23:26, 29 October 2013 (UTC)Reply
I don't know either, perhaps you should ask WM legal. Attribution is necessary, but we have the full history, so should not need to link to WT for history, and attribution is of the contributor, not the site the material was hosted on at the time, so a link to WT seems unnecessary. You may have a good point, and I think it is worth following up with someone who is better aware of the details of the licence. As I understand it, a link to the original site is a substitute for the full history, for uses where providing the full history is inconvenient or impracticable. In the history, all contributors are identified by username on WV, or IP address, which is as full an attribution as you can reasonably hope for. Users who did not migrate to WV are identified by their WT usernames and have an imported user page. I think this exceeds the minimum requirements of CC-by-sa licencing, but I am not an expert. I would also like to see that link removed. Probably all of us would... Peter (Southwood) (talk): 07:37, 2 November 2013 (UTC)Reply
@Peter (Southwood) - according to my reading of what Ikan said above, there's a sharp distinction to be drawn between a) what's legally required in general for any hypothetical situation where CC-BY-SA is involved, and b) what Wikivoyage in particular is required to do per the terms of its out-of-court settlement with Internet Brands, which Ikan seems to be saying is more stringent. If that is the case - and absent an official clarification from WMF Legal, I wouldn't take anyone's word as holy writ - we're hamstrung.
If what Ikan says is true, that begs the question of why the WMF shelled out hundreds of thousands if not millions of dollars of donors' money in legal fees only to sell us out and all-but-ensure they'd never recoup their investment, but then again, I'm neither a businessman nor a legal expert so what do I know? -- AndreCarrotflower (talk) 08:17, 2 November 2013 (UTC)Reply
The question is really down to who has the authority to remove the WT link. Every conversation that I've seen points to the WMF legal department. People giving opinions about it on various pages on WV isn't going to effect that at all. The user PriceGloria said that they would contact this department directly which is probably the best proactive step to take. Andrewssi2 (talk) 08:32, 2 November 2013 (UTC)Reply
I have no special knowledge. I guess it's more accurate to say that WMF Legal refuses to give advice to anyone but the Foundation, and leaves the rest of us to edit at our own risk. See meta:Wikivoyage/Lounge#Google PageRank issues:
"[W]e are ethically obligated to represent only the Foundation. We cannot unfortunately give legal advice to the community at large, particularly in cases like this one that may be complex and where we may not know all that facts. With that in mind, we'd urge you to carefully consider any changes you make, on this issue or any other - you should avoid placing yourself in situations beyond your individual tolerance for legal risk. I have written about the responsibility of contributors to the Wikimedia projects elsewhere, which you may wish to review."
The linked legal advice is:
"An editor is legally responsible for his or her edits and contributions on Wikimedia Projects. The Projects are only hosting venues: the Wikimedia Foundation generally does not edit, contribute to, or monitor the content on the site. For that reason, the Wikimedia Foundation is not responsible for the edits or contributions of the editors.[2] See 47 U.S.C. 230
Editors should be advised to exercise caution and avoid contributing any content that may result in criminal or civil liability, including infringing material, defamatory statements, and privacy violations.
The Wikimedia Foundation strongly supports free speech throughout the world. The Wikimedia Foundation accordingly does not agree with many countries' restrictive laws on content. That said, local courts may try to impose local norms. For that reason, the Wikimedia Foundation should advise editors and administrators who do not comply with their local laws that they do so at their own risk."
So the problem here is that if we decide to do away with the links to WT on scads of articles and get individually sued, we have no indication of whether the WMF would represent us or leave us twisting in the wind. Ikan Kekek (talk) 08:33, 2 November 2013 (UTC)Reply
It shouldn't be utterly impossible to come to some sort of determination of whether hyperlinks are required per the terms of CC-BY-SA 3.0, even without the aid of WMF Legal (perhaps the folks at Creative Commons could shed some light on it?)
As far as I can see - and again, I'm no legal expert; I'm just brainstorming here - the only missing puzzle piece is the additional terms that may or may not be contained in the settlement between IB and the WMF. I'm assuming that those documents are sealed and inaccessible to garden-variety editors. That being the case, would individual editors be legally responsible if they violated the terms of an out-of-court settlement the details of which they were not privy to? Wouldn't the culpability for such a thing fall back on the WMF in that case? The WMF can disclaim responsibility for individual editors' contributions till the cows come home, but if said editors were violating not the law itself but an agreement between two third parties that they had no part in, I imagine that might be a whole other issue.
-- AndreCarrotflower (talk) 08:45, 2 November 2013 (UTC)Reply
I don't know, and without legal advice, I don't think any of us can know. If there are any good civil lawyers who happen to be Wikivoyagers, perhaps we could get some advice on law from them, but it would really be much more reassuring to get advice from WMF Legal, and they have so far refused to give any such advice, claiming that they are ethically obligated to refrain from so doing. It seems like a Catch 22. Ikan Kekek (talk) 08:57, 2 November 2013 (UTC)Reply
Exactly. We clearly need legal expertise, but it seems like it needn't be WMF Legal in particular. I repeat that Creative Commons might be the next people to ask. -- AndreCarrotflower (talk) 09:01, 2 November 2013 (UTC)Reply
I don't think CC attribution is the issue. I think the issue is what's in the settlement. But I wish WMF Legal could at least tell us unambiguously that we cannot get rid of the notices, if that's true. Ikan Kekek (talk) 09:04, 2 November 2013 (UTC)Reply
The results of the suit WMF brought against IB are public, and the only issue for WV was that we need to include Template:WMFLEGAL Disclaimer in a prominent location for three years - see Template talk:WMFLEGAL Disclaimer. That said, while it seems pretty clear from a reading of the license and from standard practice that attribution on the history page should be sufficient, AND since "WT" is not an author of any of the content in question (the contributors are the ones who hold copyright on their contributions), any editor who makes a change to the attribution template would be responsible for that change and thus become a target of any legal action IB chose to take, hence the desire to get WMF legal to vet any change and (ideally) for someone with WMF to actually make the change. -- Ryan (talk) 15:57, 2 November 2013 (UTC)Reply
If I'm reading that talk thread correctly, the legal disclaimer needs to appear on only one policy page. But then why do we have an attribution template on so many pages, if the legal settlement didn't require it? I think something's missing here. Ikan Kekek (talk) 19:19, 2 November 2013 (UTC)Reply
The footer attribution has been there since Wikivoyage launched, preceding the conclusion of the WMF's suit against IB. I assume that the text used was meant to try to be overly cautious in order to prevent further legal complications, since IB had sued two individuals prior to the site launch. -- Ryan (talk) 19:28, 2 November 2013 (UTC)Reply
See also Wikivoyage talk:Main Page Old#Old revisions, which is the last time legal got involved over the footer link. -- Ryan (talk) 19:36, 2 November 2013 (UTC)Reply
Well, that's as clear as mud to me. Before an edit conflict, I was going to post this: So there is nothing in the legal settlement requiring the footer? If that's the case, is the only reason that the footer has been maintained a lack of confidence that the WMF would support anyone who's sued as an individual for getting rid of it? Ikan Kekek (talk) 19:42, 2 November 2013 (UTC)Reply
Does the requirement to display the WT link in a 'prominent location' for three years mean that there is no issue whatsoever in having it removed in (I guess) 2015? --Andrewssi2 (talk) 10:55, 3 November 2013 (UTC)Reply
That seems to be a logical deduction. I guess the 3 years started from the date of the settlement. Ikan Kekek (talk) 11:00, 3 November 2013 (UTC)Reply
My guess is that the footer was added by someone at WV:de during the initial migration, as a super-conservative approach, and now we can't remember why it was done. Maybe User:Hansm or User:RolandUnger would remember. I also guess that it is not required by the settlement terms, and if no-one can show that it is required by the settlement terms, I would be willing to remove it once I find out how to do it. Peter (Southwood) (talk): 16:13, 3 November 2013 (UTC)Reply
The "prominent location for three years" applies only to Template:WMFLEGAL Disclaimer, which does not mention WT by name, let alone link to it, and has nothing to do with the footer. The issue with the footer is not time-bound and is entirely to do with not breaching the license, which I presume is CC-BY-SA 3.0. Forget about the settlement of the suit and focus on interpretation of the license. If it says we need a hyperlink to the original, we need a hyperlink. If it doesn't say that, but says we need to display the URL, then perhaps an unlinked URL will suffice. An unlinked URL would be better than a hyperlinked URL. Nurg (talk) 20:23, 3 November 2013 (UTC)Reply

┌─────────────────────────────────┘

When we started Wikivoyage in 2006 we decided to have a conservative solution to fulfill the regimentation of the CC-by-sa license to name both the author's names and the source of the derivative work (at that time Cc-by-sa 1.0 was the current license) because we had no war chest for a lawsuit. Within some years the German Wikivoyage outnumbers WT. -- At the time of the WMF migration two association members including Hansm were in San Francisco at the WMF. At this time both WMF and our team decided to continue the procedure of mentioning of the source work for the derivative work on legal grounds. About one and a half year ago I emphasized this problem in discussions with James and other admins and named it a huge ad campaign for IB and made several proposals like starting from scratch and to delete all articles without content. But this problem was ignored by the community. One year ago at SF Hansm and DerFussi repeatedly proposed to kill all meaningless content including talk pages. But our proposals were ignored by the community again. As I said the decision to keep the footer was supported by the WMF's legal department for the same reason. Of course I repeat: what should we do furthermore in that case of the appeasement or naïvety of the English community? --RolandUnger (talk) 20:12, 3 November 2013 (UTC)Reply

Oh, we seem to be behind. Purge any page and see. Kudo's for User:Jmh649 :-) JuliasTravels (talk) 21:09, 3 November 2013 (UTC)Reply

Now I've read more about the free advertising for Internet Brands' Wikitravel website on almost every page of this English language site, it seems that the "Germans" (Frank, Hans, Roland, etc) have been right about this all along. I think it's great that Peter Southwood has volunteered to remove the hyperlinked, clickable text on most of our pages and we should educate him this very week so that he can get the job done and start welcoming a tonne of new readers. Now if we can implement the other suggestions about units, section headers, and lead paragraphs, etc, that should be enoguh of a sudden sea change for Google to drop the site duplicate penalty and for this site to finally take its rightful place in the search rankings. Now don't lose this momentum by more anally retentive introspection or personality politics - go for it! --118.93.67.66 21:51, 3 November 2013 (UTC)Reply

Oh, I was dreaming. There's one last hyperlink to deal with. What seems important to me from Ryan's link, is that WMF legal was already involved in this matter. It was just unfinished, it seems?. Their argument for not engaging is not quite as convincing then: it seems that Philippe intended to get back to them on it but nothing came out of it since, right? Can we ping him again and ask if he can perhaps persuade them to dedicate a little bit of their time to it once more? I imagine the main reason they don't really want to (at Legal) is that they're swamped already wit other things. @Roland, I'm sorry you're frustrated with our community. I missed that conversation back then but let it please you that indeed all empty outlines have been deleted since and others are being recreated to lose the attribution. JuliasTravels (talk) 22:37, 3 November 2013 (UTC)Reply
I, too, am sorry that the German Wikivoyage folks who were so helpful to the English-speaking community were dissed this way. Ikan Kekek (talk) 22:42, 3 November 2013 (UTC)Reply
I'm sorry, but dissed? It may be Roland's opinion that we "ignored" certain issues, but if so, I doubt it was intentional and it certainly doesn't rise to the level of active disrespect. LtPowers (talk) 02:27, 4 November 2013 (UTC)Reply
It looks like they felt dissed. Ikan Kekek (talk) 05:08, 4 November 2013 (UTC)Reply
Then you may want to look at Wikidata:Wikidata:Requests_for_comment/VCards_for_Wikivoyage, because they are feeling dissed or ignored there too. -- torty3 (talk) 13:21, 4 November 2013 (UTC)Reply
I was totally unaware of this. What's the best way for us to be aware of these initiatives? Ikan Kekek (talk) 19:04, 4 November 2013 (UTC)Reply
The best way is to read Summit and to participate in it. As far as I remember, it was one of the Summits, where Stefan linked to this Wikidata proposal. --Alexander (talk) 20:41, 4 November 2013 (UTC)Reply
I don't see anything at that Wikidata discussion that indicates disappointment in the response to the proposal. I do see several legitimate criticisms raised and not much attempt to address them. LtPowers (talk) 22:14, 4 November 2013 (UTC)Reply

Source for Central Tokyo map?

This map has an enormous typo (MEGURU -> MEGURO).

How can I fix it? Is there anything better than editing the PNG directly?

I see the "Discussion on defining district borders for Tokyo is in progress" warning, but said discussion is stalled since 2009 so better not wait.

Nicolas1981 (talk) 06:41, 24 September 2013 (UTC)Reply

I'm sure Stefan used an SVG to create this map, but you'll have to ask him for the source. Try dropping him an email. LtPowers (talk) 14:04, 24 September 2013 (UTC)Reply
No reply from Stefan. I GIMPed the PNG manually for now, but for the upcoming re-sectoring of Tokyo we might need to re-create it (them?) from scratch. I hope we don't have too many maps/graphics without sources. Nicolas1981 (talk) 06:39, 27 September 2013 (UTC)Reply

Tokyo Olympics

What do we usually do for the Olympics?

I could not find anything special about the 2012 London Olympics.

The main site for the Tokyo Olympics is an area of reclaimed islands, which is different from Tokyo/Odaiba, and for which Tokyo/Minato is probably too broad. By the way, the central Tokyo map shows it in an area called blueish-gray area which does not have a matching article. Nicolas1981 (talk) 07:43, 24 September 2013 (UTC)Reply

Interesting question. The Brazil article doesn't even refer to the forthcoming Olympics, and the Rio de Janeiro article has only some high level references to them. --Andrewssi2 (talk) 09:45, 24 September 2013 (UTC)Reply
Traditionally, all we've done is put an Olympics template on any bottom-level articles that have an Olympic venue. Template:Sochi2014 is the current one, but you can see how others like Template:London2012 were used in the article histories (example). LtPowers (talk) 14:10, 24 September 2013 (UTC)Reply
We do have a general article for the Olympic Games which could be expanded, and there is also precedent for individual articles for events of a similar scale (see World Cup 2006, World Cup 2010, World Cup 2014, Expo 2005, Expo 2010). I think similar articles for Olympic Games 2014 etc. would be welcome. Texugo (talk) 15:24, 24 September 2013 (UTC)Reply
There is an article London 2012, so I think that something like Tokyo 2020 ( or Tokyo Olympic and Paralympic Games 2020 but that is a bit of a mouthful) would be fine. I am also wondering if we should create Glasgow 2014 for the Commonwealth Games. AlasdairW (talk) 20:25, 24 September 2013 (UTC)Reply
Just to correct Texugo's suggestion, a page would be called Olympic Games 2016, not 2014. --Andrewssi2 (talk) 08:46, 25 September 2013 (UTC)Reply
Although there will be a Winter Olympics in 2014. --Andrewssi2 (talk) 08:47, 25 September 2013 (UTC)Reply
I created the article Tokyo 2020. A map should be added using info form http://tokyo2020.jp/jp/plan/venue/ Nicolas1981 (talk) 10:20, 25 September 2013 (UTC)Reply
I created Pyeongchang 2018 for the winter Olympics, since I was updated that region in South Korea anyhow. --Andrewssi2 (talk) 02:15, 18 October 2013 (UTC)Reply
We have Olympic Games. Should the others be at Olympic Games/Tokyo2020 or some such? Pashley (talk) 13:17, 18 October 2013 (UTC)Reply
I wondered that as well, although the article Olympic Games itself is not very clear in purpose right now, and simply links to Olympic cities.--Andrewssi2 (talk) 01:45, 19 October 2013 (UTC)Reply

Bogus reviews

Bought & paid for, but sometimes busted NY Times story.

I wonder to what extent we need to worry about such things or an w:Internet Water Army paid to flood forums. Are our current defenses adequate? My guess would be 'yes', but it seems worth asking. Pashley (talk) 12:36, 24 September 2013 (UTC)Reply

I saw a similar story in (I think?) USA Today. Frankly, I don't think Wikivoyage is a big enough deal to attract large-scale organized spamming operations like that. As for the small-fish spammers that we do encounter from time to time, the size and activity level of our admin team is more than sufficient to easily deal with them. -- AndreCarrotflower (talk) 00:31, 25 September 2013 (UTC)Reply
Unfortunately, we do have them on the English Wikipedia :/ --Rschen7754 04:08, 25 September 2013 (UTC)Reply

File:Barquinho.jpg in Praia a Mare article

Hello all,

Wikimedia Commons is my "home wiki", and through my work on there, I have identified File:Barquinho.jpg as being a photograph of the Serpentine Lake in Hyde Park, London.

However, I noticed it is in use in the Praia a Mare article on this wiki, with the caption "Dino Island".

I can see this has happened because the Wikimedia Commons file has the same name as the original Barquinho.jpg file on the original WikiTravel article.

As I can't immediately see that the file on WikiTravel has been released under a free license, I don't think it's a suitable candidate to be uploaded to Commons.

Although, I am unsure of the policy as regards to uploading WikiTravel images directly to WikiVoyage - i.e. is there a more relaxed policy here?

So I'd be grateful if anyone here with greater Wikivoyage & Wikitravel knowledge that me could transfer the file over if possible and correct this conflict. Or failing that, I guess we can just delete the reference to the Commons file from the Wikivoyage Praia a Mare article, as it currently stands it's an incorrect image for that page.

Thanks very much for any possible help, Rept0n1x (talk) 19:30, 25 September 2013 (UTC)Reply

I have removed the image from the article, since it is incorrect anyway. Incidentally, the other image in that article was also incorrect. Texugo (talk) 20:00, 25 September 2013 (UTC)Reply
Thank you for removing the incorrect images and for the quick reply. Now that the article is no longer showing the incorrect images - it'll be fine to leave it as is for the time being. But if anyone here in the Wikivoyage community feels it's possible and desirable to transfer the images from the original Wikitravel article, then please feel free to do that. Rept0n1x (talk) 20:30, 25 September 2013 (UTC)Reply
Is there a list of all images that had name collisions? Most of them must probably be replaced or at least re-captioned. Nicolas1981 (talk) 06:41, 27 September 2013 (UTC)Reply

Unfortunately I don't think that there is any way of automatically detecting where the old site had an image name that refers to something different on Commons. Yesterday I was looking at Tarrytown because it was listed as having a red image link (see above) and found that the other image was wrong. In this case the error was less serous. I think that we need to be aware that any image reference from over a year ago that doesn't have a corresponding image may be wrong. It probably doesn't matter if "Someville Main Street" gives a slightly different view, but if the reference is just to an image called "Main Street" then it could be the wrong city. I have seen a similar problem on WP where an image with a common name has been deleted (license queries) and a new image uploaded a month later that happened to have the same name. AlasdairW (talk) 11:36, 27 September 2013 (UTC)Reply

It reminds me of a recent case when I was fixing a red link in Topoľčany, Slovakia (well, removing in fact, as I didn't find any suitable image), something seemed to be wrong with the town hall picture above. Then I realized that there was a US flag hanging and the picture with a generic name (something along "townhall.jpg" lines) was taken in St. Louis, Missouri. Danapit (talk) 12:27, 27 September 2013 (UTC)Reply

How about a script that would for each image used on WV, check whether the image exists on WT, and binary compare the image of WT vs the image of WV? A list of such images would be useful, I guess half of them need to be fixed. Nicolas1981 (talk) 07:35, 29 September 2013 (UTC)Reply

Nicolas, that sounds useful. Danapit (talk) 14:15, 29 September 2013 (UTC)Reply
Well... anyone willing to write said script? :-) I would like to write it but really busy with other open source projects right now... Nicolas1981 (talk) 02:16, 30 September 2013 (UTC)Reply

Old site

wikivoyage-old appears to be off-line, any explanation? --Traveler100 (talk) 06:49, 26 September 2013 (UTC)Reply

It is up to now online. But http instead of https. --RolandUnger (talk) 09:08, 26 September 2013 (UTC)Reply
Ah that was the problem I was jsut adding -old to the page name, now need to remove the s. Thanks. --Traveler100 (talk) 19:32, 26 September 2013 (UTC)Reply

string editing in template

I would like to enhance the listing so you can click on a phone number and this will take your mobile device to the call function, or on your pc use what ever VoIP software you have. This would be useful, particularly for reserving a table at a restaurant or checking opening times. I can get the link to work and take you to the dial function of the device but having problems with the formatting of numbers in articles. I need to strip out the spaces and dashes from phone numbers in the listings for the link to work correctly. Is there a method to replace or strip out characters in a parameter in a template? Alternative would have to have two inputs of the number one without spaces and dashes and one human readable for the article. Not so keen on this as a challenge to maintain.--Traveler100 (talk) 08:36, 28 September 2013 (UTC)Reply

Don't most mobile devices ignore punctuation? At any rate, I can tell you that Mediawiki's template code doesn't do string parsing well at all. Certainly not something I'd like to do on scores of instances per page; it would have a significant affect on performance. Lua can do string parsing. LtPowers (talk) 23:57, 28 September 2013 (UTC)Reply
Correct mobile devices will ignore punctuation but unfortunately html and mediawiki will not ignore (blank) whitespaces. --Traveler100 (talk) 05:24, 29 September 2013 (UTC)Reply
problem solved, was pointed in the right direction. Proposal now to update listings template so there will be a link for smart phones to call a number when it has a good format. See Wikivoyage talk:Listings#Telephone number --Traveler100 (talk) 14:52, 29 September 2013 (UTC)Reply

What is happening exactly?

It seems like I (and I believe not to be the only one) missed some important processes happening behind the scenes of day to day work at WV. I am relatively new here so forgive me I don't get the whole context. Also some discussions seem to be not well concentrated and are dispersed all over the place, which makes it maybe more difficult to understand the underlying problem. Is the entire issue connected to W. Frank ban nomination or is there more to that (I certainly assume so)?

In any case, I am shocked to see two of our finest editors and administrators leaving without much words of explanation.

  • Is there anything we can do to revert the damage that happened already?
  • What is there to change to stabilize the situation and prevent loosing the best people? We can't really afford that!

--Danapit (talk) 16:25, 2 October 2013 (UTC)Reply

Danapit, I am happy that someone has finally raised this topic. It looks like most people care about the strict adherence to policies, but they pay less attention to the fact that prolific contributors leave the project. I don't think I am supposed to explain the reasons, but perhaps I may quote Peter: "too many chefs in this kitchen, and not enough sense to go around". Yes, it is related to the page you mentioned, but I think that it is also more general. Consensus, soft security, and all these things work well as long as people in the community share same ideas and have the ability to listen to each other. This does not work here any longer. Sad, but true. Honestly, I don't know what could be the way out, because the community has to reconsider some basic things, and for this it has to reach the consensus, but consensus can not be reached unless some people step back. And they really step back by emptying their user pages and leaving the project. I am thinking of doing the same.
To be more specific, the current consensus is that we put more effort to protect trolls than to keep long-time prolific contributors (for example, by protecting them from trolls). Unless this stance is reconsidered, more people are likely to leave. --Alexander (talk) 16:35, 2 October 2013 (UTC)Reply
I can't speak for Jan and Peter, but my sense of things is that people are getting overly frustrated with the perceived levels of bureaucracy needed to get things done around here. When the site was smaller it was fairly easy to get unanimous agreements, everyone knew each other fairly well, it wasn't hard to follow all ongoing discussions, etc, but I think we're experiencing severe growing pains and need to revisit some longstanding site norms. At a high-level, I think our Wikivoyage:Consensus policy needs to address what happens when discussion simply fails to reach any agreement - we have far too many discussions that stall, discouraging people from even proposing changes. In addition, I think we need to re-instill the spirit of Wikivoyage:Plunge forward, but also make it clear where the limits should be (example: w:Wikipedia:Be bold#... but please be careful!). In the particular case of Frank, the lack of any specific policy that allowed us to deal with a problem editor led to endless discussion and all manner of tiresome edit patrolling, which could have been reduced if we really did believe in plunging forward and trusted that experienced editors who dealt with a difficult situation in ways that might not follow existing policies to the letter did so in good faith. I don't have any specific proposals for addressing these issues now, but it would be good if everyone could take some time to think through what problems they see and what solutions might work (particularly if those solutions have already been tried elsewhere) so that we can have a meaningful discussion and hopefully allow people to spend more time writing travel guides and less time discussing site policies. -- Ryan (talk) 17:20, 2 October 2013 (UTC)Reply
+1 --Rschen7754 20:07, 2 October 2013 (UTC)Reply

Consensus does not need to be unanimous, all it needs to be is majority. As WV grows unanimous consensus will become a thing of the past. The issue at hand does not appear to be that difficult to solve. Get consensus at the Wikivoyage:User ban nominations board. We could use a more formal Request for Comment process to help facilitate this but that is a different issue. Travel Doc James (talk · contribs · email) 18:43, 2 October 2013 (UTC)Reply

This topic is about two long-time prolific editors leaving the project. I don't see how a consensus at Wikivoyage:User ban nominations can solve this very serious problem.
As a side note, for Danapit who started this topic: this comment by James is a perfect illustration to my words above. Some people in this community have no ability to listen to others or at least to understand what the conversation is about. --Alexander (talk) 18:58, 2 October 2013 (UTC)Reply
In the limited context of this particular discussion, Doc James' comment does not appear unreasonable. Perhaps if you explained the full context to Danapit your meaning would be more clear. Peter (Southwood) (talk): 19:34, 2 October 2013 (UTC)Reply
I am not sure that I understand you. The question was how to revert the damage and how to prevent further drama. Suggestions are still welcome, but I don't think there is one. I better refrain from further comments about the context. DocJames is already suffering from insults, and I am not sure that he has proper medicine. --Alexander (talk) 21:17, 2 October 2013 (UTC)Reply
"Consensus does not need to be unanimous, all it needs to be is majority." Uh, no, that's not consensus, that's just majority rule (otherwise known as a democracy). Consensus doesn't necessarily mean unanimity, but it does mean general agreement, which isn't exactly the same but pretty close. PerryPlanet (talk) 19:44, 2 October 2013 (UTC)Reply
I'd like to point out the irony that the two admins left precisely at the point at which action has begun to be taken. Ikan Kekek (talk) 20:47, 2 October 2013 (UTC)Reply
It's a bit more nuanced than that. It involves evaluating the strength of the arguments and the level of opposition and support (as in, how strongly the supporters support, and how strongly the opposers oppose). It involves some in the minority realizing that they are in the minority, and becoming okay with the "majority" decision or at least finding it acceptable under the circumstances. It involves compromise to make sure that the rights of the minority are not simply trampled on. It involves recognizing that some people will oppose anything and cannot be reasoned with, and that reluctantly we do have to go with an overwhelming majority to get anything done. --Rschen7754 21:44, 2 October 2013 (UTC)Reply
Fair enough. I was mainly just objecting to Doc's statement that all you needed was a majority (not even "overwhelming majority", but just "majority"). That struck me as a pretty big misread of the definition of "consensus". PerryPlanet (talk) 21:55, 2 October 2013 (UTC)Reply
We define consensus on our wiki, and the definition there seems to be a pretty good one to me. I don't necessarily thing there is too much wrong with how we build our our existing consensus. It saves us from things like flip-flopping between AM/PM styles, and spelling dialects changing with the latest users opinion. Our consensus building doesn't count votes without argument. A simple support or oppose doesn't count. Therefore, all arguments need to be addressed in order to build a consensus.
The issue (as I see it is) once someone goes against an already built consensus, we then need to build another consensus to actually do anything about it. If someone actually does something about it, they are just as likely to be pilloried as the perpetrator.
We perhaps have a general issue to address here. However, I'd like to propose the following to deal with this specific case.
You may find an action has been taken against your editing on our wiki, because it goes outside our policies. Another user may revert your change. Sometimes an admin may block your account to prevent edits against our policies from continuing. You will have the right to discuss any reversion or block, and to find out what the issue is. You have the right to contribute to a consensus building discussion on our policies. However, you do not have the right to make personal comments against another user or admin trying to uphold our policies in good faith. Doing so after a single warning will result in you being banned from the project.
I have infinite time for anyone trying to build the project up by argument and consensus building. Happy to indulge strong argument on article content. Understand that no-one is perfect, (even administrators :-). However, we need to support the people who invest their time in patrolling this site. They can have their decisions questions and discussed, but they can't be disparaged in completely separate contexts, simply for enforcing our consensus policies on our behalf --Inas (talk) 23:32, 2 October 2013 (UTC)Reply
  • What is happening exactly? Well, the answer is nothing. I have formed the opinion that a small body of long-established editors here resist even the most minor changes (Inas's fear-mongering of "flip-flopping" is just one example of an in-built stasis that prevents this site from evolving). My prediction is that WV is going to fade over the next few years, and then die. It's a great pity, but if any attempt to improve it is shafted by time-tested techniques in discussions and an effective veto power by a few people, I can see no alternative. Tony (talk) 01:15, 3 October 2013 (UTC)Reply
That's not what this is about, and it's irritating for you to make that "prediction" in this context. The problem is that there are certain people - one in particular - whose response to being unable to gain a consensus behind their proposals is to make ornery comments about that in multiple situations, deliberately (and sometimes perhaps unwittingly but carelessly) insult admins and other users, and blatantly and knowingly flout consensus in his edits. I will make it plain that I'm talking about User:W. Frank, which you probably already knew. I personally have had a good working relationship with him, I like those edits he makes that are constructive, don't mind his opinions, and sometimes like his sarcastic sense of humor, so this is not at all about me, but Frank's antisocial side has taken up an inordinate amount of admins' time and has chased away an unknown number of editors, including two admins who recently retired out of frustration and another one who just announced that he will concentrate his edits in Russian Wikivoyage instead of here. Frank has been suspended a couple of times recently for persistent ornery and contrary behavior. Like Frank, you are welcome to express your opinions about matters of policy, but you should do so in a way that respects other users, which includes not gratuitously (and, correct me if I'm wrong, repeatedly) predicting the demise of the site because you evidently think those who disagree with you are so much less smart than you because they don't think your minority view on everything should govern site policy. So while I don't think you've ever come close to warranting a block, if you'd like to join Frank and be suspended yourself, just keep up with your annoying "predictions." This site isn't about you, and it isn't about me. But it's essential that an environment for peaceful and productive editing be maintained here, and that surely won't happen with a few individuals engaging in ornery behavior and hostile "predictions." Ikan Kekek (talk) 01:31, 3 October 2013 (UTC)Reply
This kind of aggressive, threatening behaviour is just about convincing me that this site is going to die, actually. So you don't like what you hear? You then insult the editor and threaten to block. It would take a willingness to change, to be flexible, to convince me that this site was a huge waste of money for the WMF to take on. I'm thinking now that it should have stayed with the corporate raiders, left to die of its own accord. Now, instead of insulting and threatening me, you people need to act in a more functional way. Tony (talk) 01:59, 3 October 2013 (UTC)Reply
Sorry Tony, but you are also a part of the problem. You've just been as strident and even inflammatory in your remarks as anyone. It's interesting really, speaking as someone who has never edited a public wiki, not even pressing the "edit" button until the launch of Wikivoyage. Now that I've looked behind the veil at both WP and WV, the distinct thought is that these are perhaps flaws regarding discussion endemic to wikis. The decision making cannot be said to be better at WP, and maybe it is even more entrenched there. The feeling is that a lot of time is being spent on debating, rather than adding content. I've tried to avoid sticking my nose into discussions if I couldn't add anything new and prefer to cut through to the key of the matter, but I, like Alexander, regret not putting my oar in earlier at the user ban nominations. I started precisely because of the mantra of "Plunge forward", and finally removed my initial bugbears of dynamic maps, a listing editor and empty outlines, only to look up and see an exodus.
Community is important, civility is important. I could pretty much predict the same sad demise for WP, yet others have already done this before and been proven wrong. We will see what happens, and whether this discussion does come to a conclusion. -- torty3 (talk) 02:02, 3 October 2013 (UTC)Reply
Or perhaps you are the problem. Tony (talk) 02:05, 3 October 2013 (UTC)Reply
This is exactly what I mean. Why are people running scared in Wikipedia talking about editor retention and lack of newcomers? Because people will not contribute if they feel threatened. I've not been threatened until now and I recognise my previous comment went a little far. Do you recognise the same for yourself? -- torty3 (talk) 02:24, 3 October 2013 (UTC)Reply
(edit conflict) One thing I've learned from editing wikis in the past eight years is that there are enough opinions and personalities out there that every single person who edits will be perceived as a "problem" by someone else at some point, so let's just agree that we're all the problem and move on. While I would like to see all major contributors stick around forever, the site survived the loss of its founder and most of the individuals responsible for making it what it is today, so I'm confident that new users will continue to take up the reins and that we'll be fine in the years to come. That said, this latest episode is a chance for reflection on how we can make things better, and it might benefit all involved to take a few deep breaths, formulate some thoughts, and come back tomorrow with a fresh perspective and some actionable plans for making it easier to achieve (and perhaps even update?) our goals. -- Ryan (talk) 02:30, 3 October 2013 (UTC)Reply
Taking a deep breath is fine, but I think it's important for everyone to know that individuals who create a hostile work environment by being persistently ornery about not getting their way when they're in the minority may end up outside the site. Discussion and disagreement are always welcome, but you are way more likely to persuade people if you are respectful of those who at least initially don't share your opinion, and respect consensus while you argue for changing it. And if you really believe the site will die because it's your way or the highway, there are many highways you can travel without us, so it might be better for you to take one than to add insult to injury, especially at this time, with repeated prophecies of our doom. Ikan Kekek (talk) 02:41, 3 October 2013 (UTC)Reply
There we go again: batter down anyone who threatens your entrenched notions. I don't buckle under pressure, although there will come a time when I see this formulaic resistance to change (and unwillingness to support innovation) as terminal. There are clear signs of an entrenched culture that is rooted in some kind of nostalgia for the site as it was years ago; that is going to kill it off. My recent travels demonstrated starkly how inadequate it is for the needs of travellers, and how a few other sites individually offer a much better user experience in some key respects. Although en.WV does have some strengths, they alone are insufficient to stop its demise in a highly competitive, crowded market for travel information on the internet. The unfriendliness towards anyone who wants to promote change augurs badly for increasing the number of regular editors, particularly the housecleaners we so urgently need to keep its many corners up to date and professional. Tony (talk) 02:43, 3 October 2013 (UTC)Reply
Keep arguing for specific changes! Just do it without being hostile. And sure, the site might die - but realize, it's bigger than me and it's bigger than you. Ikan Kekek (talk) 02:47, 3 October 2013 (UTC)Reply
Because there is very little participation in discussions for bit-by-bit improvements/reforms, they are effectively vetoed by a few editors (you know very well who they are). This is not conducive to a site that needs to adapt and reform to survive. Tony (talk) 02:52, 3 October 2013 (UTC)Reply
I'm one of the people you have yet to persuade to support your proposals on spelling, so you're at least partly talking about me. But I think the reason few people participate in that discussion is that few care. However, it's not like no-one can ever persuade a consensus to adopt changes on this site. People with good arguments and powers of persuasion have achieved the adoption of some major changes, such as pagebanners, a redesigned front page, and the Airport Expedition. There was also much discussion of the possibility of more Wikipedia links (which I was also willing to consider under certain circumstances), but no consensus has yet been achieved. However, some positive things came out of the discussion. I doubt this site will die over the issue of spelling, but if you have other proposals that more people might be interested in, you can try to garner more interest by posting a link to your proposal at Wikivoyage:Requests for comment, and possibly here in the Pub. Ikan Kekek (talk) 03:01, 3 October 2013 (UTC)Reply
@User:Tony1. Sigh. I reject your accusation of fear mongering. It is simply that sometimes there are equally good reasons to do things different ways, and sometimes we have to make a call on one way to do them. Toss a coin, scissors paper rock, whatever. However, once done we don't need to re-consider these decisions every time the same arguments are repeated do we? New ideas, improvements, etc, are in a different league, and should be discussed and tried. But no-one should be too surprised at the lack of interest in a discussion British/American spelling yet again. --Inas (talk) 03:33, 3 October 2013 (UTC)Reply

Making major changes on either WP or WV is hard but not impossible. This is not really surprising. We have large communities who have developed the way things are now and a new idea needs to be good to justify change. What change have you proposed Tony? Travel Doc James (talk · contribs · email) 04:59, 3 October 2013 (UTC)Reply

I will make an observation here at the risk of offending some people, though that is not the intention. There are many people who have the best interests of the project at heart, and feel very strongly that they know what is good for the project. Logically, they will do whatever they can to further what they believe is best for the project. Logically, to them, they feel frustrated when other people will not accept what they know is right. Logically, they take offense when their beliefs are dismissed as unimportant or nonsense, even when the perceived opponent truly believes this to be the case. The truth of their own belief is so self-evident that it is obvious that those who deny it are malicious, stupid, deluded or misinformed. When they still disagree after the point has been explained so clearly that it is impossible to misunderstand, this leaves malicious, stupid and deluded as the remaining options. It is difficult to come to a compromise between true believers with opposing views. Or maybe I am wrong? Is some other explanation why people who seem well-intentioned, friendly and helpful, and work so hard together to produce something of enduring value can be so bitterly opposed over what seems to a third party to be a small matter? Peter (Southwood) (talk): 07:32, 3 October 2013 (UTC)Reply
If you look at the text above, and on this user's talk page, and in the policy articles, you'll see so many examples of people being patient and polite with this user. Ryan, Ikan, have responded calmly and thoughtfully today. In the discussions the arguments placed have been met. The reverse has not been true. At the end of a rant, canning the project and the people on it, a strong community should stand behind the people who've tried to manage this issue, handle it rationally, and make arguments in line with our consensus building way. They shouldn't accommodate the person who has made the attacks, and who has flown off the handle. That's not a cabal or conspiracy. It's recognizing the people who do so much valuable volunteer work for the community, cop the flak, and keep going. I want to encourage new users. I want to encourage disruptive innovation. I want to interact politely with all our community. But we have to accept that there are variety of contributors, and we should make sure the squeaky wheel doesn't get all the oil. --Inas (talk) 10:23, 3 October 2013 (UTC)Reply
Some of us are more able to remain civil in a disagreement than others. Lack of civility is not necessarily an indication of bad faith, but how much one tolerates is also a personal choice. There is also the problem of personal interpretation, and cultural variance. What may be perfectly friendly in one country may be interpreted as hostile or uncouth in another. And that is just regional variations of English without taking into account the difficulties that a non-native speaker may have. However, in some cases almost everyone will agree that an unjustified personal attack has been made. Where and how to draw the line and what to do about it is a complex problem. Perhaps a third party could be chosen as an arbitrator. Someone who is acceptable to both parties in a dispute, and who is not involved, on the pre-condition that the arbitrator's decision will be respected by both sides. It may work, it may not. It may be worth a try. The arbitrator need not necessarily be a Wikivoyager. Peter (Southwood) (talk): 11:06, 3 October 2013 (UTC)Reply
Hmmm. I'm obviously not making my point very well. We already have the situation where an administrator acting in good faith, administering the policies on our site that have evolved by consensus is subject to sideswipes around the wiki, and then has to justify his actions as if they are a party in a personal dispute, rather than a volunteer helping with a mop and a whistle. What we need is more people to stand behind those people who are putting in, instead of feeling they need to pander to the contributor making the noise. I fear another layer of arbitration may just play into the hands of those whose interest is in dispute and drama. --Inas (talk) 11:29, 3 October 2013 (UTC)Reply
I am with Inas in that respect. I would not like to see further levels of arbitration, especially from outsiders who may not be familiar with our processes and policies in the first place. I also agree that admin's using the mop and whistle should be supported in their decisions and not treated like they are in a personal difference-of-opinion dispute where the problem user they are trying to rein in is given equal respect and opportunity to try and discredit said admin. I think we need something like the proposal in the section below. Texugo (talk) 12:49, 3 October 2013 (UTC)Reply

Like Danapit, this sudden turn of events came as a complete surprise to me. The discussions that seem to have led to this position appear to have gone over my head, but that's perhaps a blessing in disguise. I think it's a terrific shame that we've lost several well-liked and experienced editors recently and we must do all we can to draw them back or at least prevent this from happening again.

From what I've seen, there doesn't appear to be a particular area of policy for the community itself rather than the content. With that in mind, I might suggest the two following tenets:

  1. Wikivoyage is fun
  1. There's a place for everyone

I've already written a very basic description of 'Wikivoyage is fun', which you can see by clicking the link. 'There's a place for everyone' would state that all are welcome here and that you will not be marginalised for an opinion or mistake that you've made. I understand that many people already view these as accepted wisdom and I certainly don't mean for them to be patronising, but would it perhaps be good to get these down in writing? Any thoughts welcome! --Nick talk 13:18, 3 October 2013 (UTC)Reply

I really like the "Wikivoyage is fun" essay - once again, I am touched by how much heart you throw into this project - but I'm not really sure what it would have done to help the current situation. The problem is that there isn't a place for everyone - at least not if your intent is to disingenuously subvert, ignore, or act against the consensus of the community, or to insult other users, or to discredit administrators who are simply doing their lowly jobs, or to delegitimize policies in a way that doesn't involve balanced and respectful community discussion. There appear to be some people willing to ignore endless warnings not to do certain things which go against the ideal of WV being a happy and fun community. We need to have a clear, decisive, and documented way to deal with those cases. Texugo (talk) 13:36, 3 October 2013 (UTC)Reply
Reading through the discussion above (and at de:Lounge) I certainly see and understand better what got us into this point and it is shame that things got so far.
Now, I think a policy along the lines proposed by Texugo is way to go. I also believe Nick's Wikivoyage is fun and There's a place for everyone might be an important piece of policy or a guideline. Danapit (talk) 14:06, 3 October 2013 (UTC)Reply
That "Wikivoyage is fun" essay is great. Even though it wouldn't be formal policy, it would be a nice thing to link to when things get too heated, just as a way of saying "chillax". It won't stop the most persistent trouble users (as Texugo noted), but it could be employed to ease tensions with a more moderately-minded individual before things go too far, as well as just a nice general statement about what we're all about. PerryPlanet (talk) 15:36, 3 October 2013 (UTC)Reply

Proposal: Revise policy on dealing with repeated unwanted edits

Discussion transferred to Wikivoyage talk:How to handle unwanted edits#Proposal: Revise policy on dealing with repeated unwanted edits. Peter (Southwood) (talk): 08:30, 7 October 2013 (UTC)Reply

The End

Currently refining our iceberg avoidance techniques so this doesn't happen!

FYI, there is now one admin and bureaucrat less on English Wikivoyage.

"...an admission that our community is not strong, patient, and professional enough to deal with unwanted edits..." Remember all this rubbish? It became reality now. I hope it will be a good lesson to other language versions. --Alexander (talk) 19:58, 3 October 2013 (UTC)Reply

It's a damn shame it came to that. I feel like we should have a funeral or something. But instead, let's focus on revamping our policies- I've always felt like that line you quoted was not quite right. Blocking a user who is steadfastly bent on being disruptive should not in fact reflect poorly on our community - on the contrary: we can be strong and patient, and then if the time comes when that is obviously not going to work, we can be professional enough to put a definitive end to the problem before the disruptive editing weakens our community by driving away exasperated volunteers. Texugo (talk) 20:18, 3 October 2013 (UTC)Reply
Hey Saqib, let's not go that far. We ain't all dead yet! Let's try to stay positive! (edited your caption for a more positive spin) Texugo (talk) 21:03, 3 October 2013 (UTC)Reply
Before we whip out the bagpipes and start playing "Amazing Grace", I would like to point to the discussion right above this one as evidence that many of us are committed to really learn something from all of this and not let the unfortunate loss of a beloved user be for nothing. PerryPlanet (talk) 22:01, 3 October 2013 (UTC)Reply
You know, Alexander, while I greatly appreciate all the work you've done on English Wikivoyage until now, you could choose to work on creating new procedures, such as the ones Texugo is proposing, rather than pronouncing our doom. I don't consider it any more helpful for you to do that than for anyone else to do it. Meanwhile, we'll work on this without your help, and you'll doubtless do great things on Russian Wikivoyage. See you around. Ikan Kekek (talk) 03:13, 4 October 2013 (UTC)Reply
Alexander is just pointing out that this problem was foreseen and considered not worth providing for during the pre-migration policy consolidation and clarification drive. Prophets whose warnings were not heeded and later turn out to happen are often unpopular, So it goes. On the other hand it is quite possible that many disasters have been averted because doom was prophesied and some action was taken (Y2K?). Hard to prove either way in most cases. Peter (Southwood) (talk): 11:13, 4 October 2013 (UTC)Reply

Consensus

We use consensus within the rest of the WM movement. As shown by however it does not require everyone to agree. Travel Doc James (talk · contribs · email) 07:24, 4 October 2013 (UTC)Reply

Whenever possible a compromise that is acceptable by all parties is preferable, When there is a deadlock there should be a way of going forward. The way of breaking the deadlock will work best if previously agreed (by consensus?). How about a two thirds majority of enfranchised voters? That would obviously require a franchise qualification, which could also be contentious. I suggest any user who would qualify for nomination as an admin, just as a starting point. Peter (Southwood) (talk): 11:13, 4 October 2013 (UTC)Reply
Yes sounds reasonable. Travel Doc James (talk · contribs · email) 16:07, 4 October 2013 (UTC)Reply
We need to recognise spiraling conversations as deadlocks where there are continuous attempts to try and convince the last one or two people even though unanimity is not required, especially when it's a matter of who can last the longest. It could simply be a difference of opinion which cannot be resolved. If you find more than three back-and-forths with no forward movement, then disengage. This applies to policy and regions discussions. I am undecided whether polls will help, but it may at least diminish some sore feelings (and probably bring up other new ones). -- torty3 (talk) 03:29, 6 October 2013 (UTC)Reply
I think our consensus policy does guide us here. In order for there to be consensus every argument has to be met. So, it's insufficient to just be a hold-out, saying you don't like a proposal without argument. And its insufficient to just repeat your proposal without addressing the rebuttal arguments. If there remain good arguments against a proposal that haven't been addressed, then we haven't got a consensus.
Once we start doing two thirds votes, then we really have to start worrying about stacking. With some discussions only eliciting comment by two or three people here, a vote of two thirds may just be two. --Inas (talk) 03:40, 6 October 2013 (UTC)Reply
Theoretically yes, if there is common sense to recognise there is or is not consensus, but in practice the arguments just keep going on and on in circles. -- torty3 (talk) 03:49, 6 October 2013 (UTC)Reply
And that's when we need to ask someone else to read through and determine what the consensus is, if there is any. --Rschen7754 07:34, 6 October 2013 (UTC)Reply
In reality, someone (preferably an admin, but not always) not involved in the discussion should be closing it, and they should have the ability to use discretion in the event of votestacking. --Rschen7754 06:42, 6 October 2013 (UTC)Reply
I'm a little confused as to how this part of the thread arose and what it is trying to resolve. Texugo (talk) 06:45, 6 October 2013 (UTC)Reply
Me too, but I think it is a good discussion, and the one that we need to have first. --Rschen7754 07:36, 6 October 2013 (UTC)Reply

To add to my past thoughts on the matter, I would encourage all of you to take some time and explore other Wikimedia projects over the next few weeks or so to see how they do things. While the English Wikipedia does get a lot of things done, I would hate for us to blindly import everything from there, because I would hate to blindly import their systemic problems too. --Rschen7754 06:50, 6 October 2013 (UTC)Reply

Another thought: I think that the fundamental issue that we need to resolve is what consensus is. I think that from that, everything else will follow; once we know how we will make decisions, that will greatly influence the topics above. --Rschen7754 07:36, 6 October 2013 (UTC)Reply

Should this discussion be part of the discussion on How to deal with unwanted edits, which is where it started from, and now moved to Wikivoyage_talk:How_to_handle_unwanted_edits#Proposal:_Revise_policy_on_dealing_with_repeated_unwanted_edits or separately, on Wikivoyage Talk:Consensus? (I think Consensus is the proper place) Peter (Southwood) (talk): 08:40, 7 October 2013 (UTC)Reply
Will it be noticed on those pages, and have adequate participation? --Rschen7754 17:23, 7 October 2013 (UTC)Reply
This has often been a problem on Wikivoyage. Can you suggest a better way of doing it? Peter (Southwood) (talk): 16:25, 8 October 2013 (UTC)Reply
Personally, I think stuff gets lost in the Travellers' pub, and when it is all archived in separate places, it makes things more difficult to find. I would split it into two to three pages, so that edits to sections are more likely to be noticed, and have an automatic archiving bot so that a) we don't spend our valuable time archiving the pub, and b) so that older threads get pushed off the page once they have been inactive for a week or two (or however much time is appropriate). One of these would be a noticeboard for administrators; all the background discussion that caused the kerfluffle of last week should be taking place onwiki anyway, and it provides a place for other Wikimedia users to contact admins.
In short: the infrastructure should be built to serve the needs of the community, not the other way around. We should be spending our time writing a travel guide, not fighting an infrastructure dating back from the Wikitravel days (as early as 2004!) that does not exactly fit our needs today. --Rschen7754 08:50, 9 October 2013 (UTC)Reply

Fully protecting departed admins pages

Is this policy? Usually one leaves them unlocked so others can leave notes of appreciation for their years of service. It is unfortunate to see both User:Peterfitzgerald and User:Jc8136 leave. While they and I may have differed on some minor points I respect both of them a great deal for the work they have put into making WV what it is today. Travel Doc James (talk · contribs · email) 05:19, 3 October 2013 (UTC)Reply

I'm concerned about fullprotecting their talk pages, as it leaves people no way to bring up concerns to them. --Rschen7754 06:06, 3 October 2013 (UTC)Reply
I've only protected the user page of Jc8136, and his talk page is not protected. Peter protected his user page and talk page himself. --Saqib (talk) 06:36, 3 October 2013 (UTC)Reply
Obviously they would be unprotected should they request them to be. It should be their choice. --Inas (talk) 06:54, 3 October 2013 (UTC)Reply

Old User sandbox articles

There are a number of old user sandbox articles around, for example:

Just wondering if it would be better to redirect them to the matching article? Or would it be better to delete them? Or should they just be left alone? -- WOSlinker (talk) 06:16, 3 October 2013 (UTC)Reply

In the past we've generally left them alone unless they are having some effect on mainspace - for example, if the article contains a category or broken image that causes it to show up on a maintenance page, in which case the page may be edited to remove the offending category or image. Is there a specific reason why we would now need to redirect one of these articles? If not, I'd suggest they are harmless enough to be left alone. -- Ryan (talk) 07:00, 3 October 2013 (UTC)Reply
I was just thinking that someone might come across them and read them rather than finding the main article and because the sandbox is old, it could have some obsolete information in it. -- WOSlinker (talk) 09:45, 3 October 2013 (UTC)Reply
How about adding a disclaimerbox at the top of each page. In this case I think it really is a disclaimer, so that one should be appropriate. 105.229.63.46 10:37, 3 October 2013 (UTC)Reply
If the user has migrated here, ask them to deal with it. Otherwise, I'd say delete. Pashley (talk) 12:17, 3 October 2013 (UTC)Reply
One other option I forgot to mention could be to just blank the page, so the history would still be available for everyone to see if needed. -- WOSlinker (talk) 12:32, 3 October 2013 (UTC)Reply
I don't really think it's a problem: why would users find a page like that rather than the article? However, if needed, let's just blank and not delete. I would prefer to be wary of actually deleting any user space stuff without the user being involved, unless we really have to. JuliasTravels (talk) 18:27, 3 October 2013 (UTC)Reply
I think we could just put {{user page}} on them and forget about it. The chance of someone "happening across" them is very very low, I believe. You would have to put at least "User:Name/S..." in the search box to even see them there, so the only way you could come across them is by following a link from that user's user page or a very old discussion, because they shouldn't be linked to from anywhere else. I think the probability of anyone confusing them with real pages is very low, and with the {{user page}} template, practically 0%. Texugo (talk) 18:42, 3 October 2013 (UTC)Reply
That would do it. Peter (Southwood) (talk): 11:27, 4 October 2013 (UTC)Reply
I've tagged a few today in the A-J range. -- WOSlinker (talk) 13:09, 4 October 2013 (UTC)Reply

Two destinations in one

Is it okay to bring two small villages together in one article, also in the title, when they market themselves as one destination? I'm talking about Ford and Etal in the UK. From a travellers' point of view, it seems better to combine them. JuliasTravels (talk) 13:55, 7 October 2013 (UTC)Reply

I don't see why not. As far as I can see, the real question is what naming convention you should use ("Ford and Etal"? "Ford & Etal"? "Ford-Etal"?) Never mind, a quick review of Wikivoyage:Naming conventions suggests that "Ford and Etal" should be fine. PerryPlanet (talk) 14:16, 7 October 2013 (UTC)Reply
I don't object to having a combined page for the two villages, which are about 2 miles apart. However it is worth noting that the website is that of the Ford and Etal estate (the local land owner) rather than the villages themselves. There is an existing outline page for Ford, which should redirect to the new page. AlasdairW (talk) 20:33, 7 October 2013 (UTC)Reply
I'm aware, but it's the closest thing to an official website and pretty much all relevant travel information (including the wider Northumberland tourist information) uses the combination ánd focuses on the estates. The villages are part of the historic estates in this case, rather than the other way around. I left the Ford outline as it was just to await comments here, I'll move that info to the new article then soon. Thanks! JuliasTravels (talk) 15:59, 8 October 2013 (UTC)Reply

Dive guide article type

Is there a reason we can't go ahead and give dive guides their own article type like we've done with airports, instead of lumping them in with the travel topics? They already have a basic template worked out and suggested status criteria. Why don't we give them their own category and status templates? Texugo (talk) 22:30, 7 October 2013 (UTC)Reply

I'm going to say no, there's no reason. Does anyone object? Ikan Kekek (talk) 22:47, 7 October 2013 (UTC)Reply
I concur. --W. Frankemailtalk 00:31, 8 October 2013 (UTC)Reply
I am more-or-less neutral here. It basically sounds like a good idea, but I'm not sure if more article types might become a slippery slope. I'd like to hear from divers, especially Peter, about whether they think it looks useful or necessary. Pashley (talk) 01:04, 8 October 2013 (UTC)Reply
I don't see a potential slippery slope here. It's not like there are dozens of new article types popping up, and they already are a different article type, it's just a matter of whether we recognize, categorize, and track it as such. The thing to decide is whether they will be a sub-type of destination, like airports are, since they are undoubtedly destination based, or if they should be a new species of topic sub-type, so as to preserve the present topic-based breadcrumb situation. Personally, I think they should just be treated as a type of destination articles. Texugo (talk) 01:10, 8 October 2013 (UTC)Reply
I don't think we need another category. It makes sense to have airport categories because airplanes are used by the majority of long-distance travellers. Only divers would be interested in our dive guides. It's covered perfectly fine by travel topics, so I don't think it's necessary. Although, I am with Pashley in wondering what a diver's opinion would be… Nick1372 (talk) 01:12, 8 October 2013 (UTC)Reply
If you're going to oppose, I'd like to hear what you think the disadvantages would be, rather than an "i don't think we need them". I think there are clear advantages from an organizational/maintenance standpoint, having them put automatically into a category which can be tracked automatically, and giving us the ability to have customized status messages which correspond to the already proposed status criteria, etc. If there are no clear disadvantages, I would argue that we should still go ahead with it. Texugo (talk) 01:20, 8 October 2013 (UTC)Reply
Hmm. Thinking about it, you do have a few points. If you have the time and ability to keep track of a category, I don't see why not. You've won me over. (I apologize for my weird answer earlier—I need more sleep.) Nick1372 (talk) 01:36, 8 October 2013 (UTC)Reply
Thanks for having a re-think, Nick - we need to see what Peter (Southwood) thinks about this... --W. Frankemailtalk 01:46, 8 October 2013 (UTC)Reply
  • I really haven't given it any thought. I guess in a way that means I didn't think it would make much difference to me. Having them in a category would definitely be useful for maintenance but does that make them a separate article type? Until fairly recently there was a major taboo on categories, for reasons that escape me at present. I suppose I should ask exactly what is meant by a separate article type.
  • All except one have been written and formatted as a different type of destination article, complete with a logical geographical hierarchy, which usually fits with the mainstream geographical hierarchy, but not 100% - forcing a 1 to 1 match would be inefficient and strained. The single exception is the top level article Scuba diving, which is very clearly a travel topic.
  • As a dyed in the wool pragmatist, I would go with whatever works best, both for the traveller and for us who have to keep the place tidy. My first impression is that the proposal will make no discernable difference to the average user, so what works best for us?
  • This will be setting a precedent, so we should try to come up with something that will work well over the long run, and there is no rush.
  • I guess I should go look what has been done with airports, and come back when I have more to say. Peter (Southwood) (talk): 13:49, 8 October 2013 (UTC)Reply
Yeah, personally, I'd say that airports have already set the precedent here. You ask exactly what is meant by a separate article type. I'd say this:
  • Dive guides would have their own standardized, article template (which they basically already do, but it hasn't been formalized and made substitutable yet)
  • Dive guides would get their own status evaluation criteria, as you've laid out here
  • Dive guides would get their own set of status tags, customized to said status criteria: Template:Outline diveguide, Template:Usable diveguide, etc., instead of the generic topic ones
  • Those status templates would put all dive guides into a Category:Dive guide articles, and additionally into respective status categories: Category:Outline dive guides, Category:Usable dive guides, etc. (This being instead of lumping them in the more general categories for topics)
Advantages for the reader are somewhat marginal - better standardization, more customized presentation of the statuses - but it would have substantial maintenance advantages for tracking, and setting up a substitutable article template will help editors to create new dive guides which are in line with existing ones. Texugo (talk) 14:37, 8 October 2013 (UTC)Reply
Texugo (talk) 14:32, 8 October 2013 (UTC)Reply
Looks like many advantages, only disadvantage a bit of extra short term work substituting the new templates. All the rest would have to be done some time anyway. Peter (Southwood) (talk): 14:49, 8 October 2013 (UTC)Reply
Don't the existing dive guides already share a basic model? All that would be needed is to list out the basic headers and descriptions on a template page similar to WV:Small city article template and then put just the headers into a quick version like WV:Quick small city article template and a skeleton template like Template:Smallcity skeleton. Then we could add a button to MediaWiki:Newarticletext to facilitate creation of new dive guides. Texugo (talk) 15:27, 8 October 2013 (UTC)Reply
Do you mean like these? {{Divesite_skeleton}}, {{DiveRegion}} and {{Divesitelisting}}? Peter (Southwood) (talk): 16:22, 8 October 2013 (UTC)Reply
Exactly. Well, the first two anyway. I knew those existed but somehow couldn't find them. If there are no further objections, I'm going to plunge forward. Texugo (talk) 17:16, 8 October 2013 (UTC)Reply
I see much action on my watchlist. It looks like dive guides are getting a separate geographical hierarchy within each country. Is this all there is to it? 105.226.204.30 06:12, 9 October 2013 (UTC)Reply
Well the above changes have been implemented. The breadcrumb for top-level country dive regions was moved from Scuba diving (a topic article) to the relevant country, so as to avoid a hybrid destination/topic breadcrumb trail. Texugo (talk) 11:34, 9 October 2013 (UTC)Reply

Summit

I would like to remind everyone that we have monthly exchange of reports between different language versions. It takes place on a special Summit page. Each language version will typically have a liaison who follows the discussions on meta and writes a report about recent developments in his/her project. Now, as Peter has left, English Wikivoyage lost its liaison, and it may be good to decide who will be the replacement. --Alexander (talk) 00:16, 8 October 2013 (UTC)Reply

The obvious choice would be Peter (Southwood) - if he's willing to undertake this important task. --W. Frankemailtalk 00:30, 8 October 2013 (UTC)Reply
I am not as involved in the general editing as many others, so I tend to lose track of things that are off my watchlist. If you would all excuse me, I don't think I am suitable for the job. Peter (Southwood) (talk): 14:31, 8 October 2013 (UTC)Reply
User:Nicholasjf21 wrote the summary for last month. Maybe he would like to help us out again? Texugo (talk) 15:29, 8 October 2013 (UTC)Reply
If wanted, I'd be happy to write something, although I don't always feel as clued up on the tech side of things as I perhaps should be. Perhaps I could be part of a team responsible for our submissions? --Nick talk 15:36, 8 October 2013 (UTC)Reply
That's a great suggestion! A dynamic duo! --W. Frankemailtalk 15:39, 8 October 2013 (UTC)Reply
I'll suggest Nicolas1981 as the other member of a dynamic duo since he seems very knowledgeable on the technical side, is in a different time zone and also writes lucidly. He also seems very active and enthusiastic about our development like Nick ... --W. Frankemailtalk 16:01, 8 October 2013 (UTC)Reply

I'd like to thank both Nick and Nicolas1981 for taking up the baton and for being ultra quick (and comprehensive) in producing their first joint Summit report already.

Well done! --W. Frankemailtalk 17:01, 9 October 2013 (UTC)Reply

placement of Template:Wikipedia

We have Template:Wikipedia, which adds:

This article contains content imported from the English Wikipedia article on banana. View the page revision history for a list of the authors.

Common practice has people putting it at the bottom of the article, but I have a couple of questions:

  • Is it absolutely necessary to put this inside the article?
  • Wouldn't a link to the WP page in an edit comment provide a better, more permanent attribution, findable in the same place where other attribution is?
  • If we do have to keep it at the bottom of the article forever and ever, can we please at least redesign the template to include options for multiple articles, so we don't get this kind of ugliness?

Texugo (talk) 02:01, 8 October 2013 (UTC)Reply

No, yes, not applicable.
As long as the edit comment references the actual URL of the edit version that material was copied from, that is certainly all the legal attribution needed. (I don't think EN-WP needs any popularity boost from us at this stage of our relative developments). --W. Frankemailtalk 02:43, 8 October 2013 (UTC)Reply
I'm glad you've brought this up, and would love for us to finally get rid of that unnecessary template in the article. There's absolutely no reason why we would not follow Wikimedia's own rules for re-use. They ask either a full list of authors or a link in the edit summary. They also have a template available for use on the article's talk page (which I still think is overdone when a hyperlink is provided, but I would use it when large parts of an article are as good as copied, which is something we don't want in the first place). They never did ask for any templates in articles themselves. JuliasTravels (talk) 10:13, 8 October 2013 (UTC)Reply
And what to do with pages that already have this template. Would it be sufficient to remove the template and put the link in the edit summary at the same time? Texugo (talk) 11:19, 8 October 2013 (UTC)Reply
I for one don't see why not. I see no difference in requirements between future articles and existing ones that now have the template, so as long as we live up to the described WM practices it should be fine, even when we did more in the past. But it'd be good if others would comment: I remember when I was fairly new here I raised the same argument and did meet resistance to replacing the template. JuliasTravels (talk) 16:22, 9 October 2013 (UTC)Reply
I'd be happy to see this template go. I've never quite understood how to use it correctly and, if the fix is as simple as you suggest, I'm all for losing it. --Nick talk 16:55, 9 October 2013 (UTC)Reply

Some good news

Summer has ended in the Northern hemisphere; however our readership continues to increase. This month a healthy 20% to a 12.8M. Travel Doc James (talk · contribs · email) 08:37, 8 October 2013 (UTC)Reply

Great :-) Now that dynamic maps work, I believe that will increase further! Nicolas1981 (talk) 14:24, 8 October 2013 (UTC)Reply
Missed this - that's great news! --Nick talk 16:53, 9 October 2013 (UTC)Reply

Listing editor and map maintenance

Just a heads-up, I'm going to disable both the listing editor and the maps at 11AM GMT, but it will be done real quick. -- torty3 (talk) 08:39, 8 October 2013 (UTC)Reply

Done. Users can now choose to disable the listing editor and maps in their preferences (Preferences > Gadgets > General), where they are set by default. The in-article maps can now be seen in HTTPS for Mozilla. -- torty3 (talk) 11:30, 8 October 2013 (UTC)Reply
Grrrrrrrrrrrrrrrrrrrrreat! Thanks, guys! --W. Frankemailtalk 14:19, 8 October 2013 (UTC)Reply
Thanks a lot Torty3! So... should we start adding embedded dynamic maps to articles that have all POIs geolocalized? Or maybe more testing on mobile is needed? Nicolas1981 (talk) 14:29, 8 October 2013 (UTC)Reply

Free beer?

As part of an advertising campaign, in Europe but only Canadians can open the big red fridges. Can we provide a map for thirsty travellers? Pashley (talk) 11:21, 8 October 2013 (UTC)Reply

I don't see why not, if we have someone willing to create a map. It would make a nice subsection to Europe#Drink with a paragraph and a map. Do you think we should add a listing to every city where there's a fridge? Nick1372 (talk) 19:34, 8 October 2013 (UTC)Reply
Hmm. Do we want to collaborate with Molson like that? It would be participating to promote an advertising campaign, after all. Texugo (talk) 19:49, 8 October 2013 (UTC)Reply
I agree with Texugo. There is also the fact that they are not useful to most travellers. If a city has so many there's one in every street, then maybe a line in that city' Drink section? Nicolas1981 (talk) 06:10, 9 October 2013 (UTC)Reply
Yeah, I think it's funny enough that a mention is warranted, but definitely not a map. Ikan Kekek (talk) 06:19, 9 October 2013 (UTC)Reply

{{starnomination}} shown as "This page has some issues" on mobile

Featured article candidate icon

Try visiting Tokyo/Roppongi on Android: The first line is "This page has some issues".

Clicking on this message reveals the reason behind: "This article has been nominated for Star article status".

Being nominated for star is not an issue, so the message should not be "This page has some issues".

By the way, the icon for featured article candidates looks like a broken star. Could it be made to look like a star in construction instead? Nicolas1981 (talk) 14:38, 8 October 2013 (UTC)Reply

I like the idea, what does a star under construction look like? Peter (Southwood) (talk): 14:58, 8 October 2013 (UTC)Reply
I can think of some nice concepts but all of them require more detail than would work for a little icon. Like a some scaffolding and a painter with a half finished paint job, or a crane lowering the last piece into place. Animated... Peter (Southwood) (talk): 15:03, 8 October 2013 (UTC)Reply
Yeah, that was the best one I could find that matches the full star on our star templates, but it´s not ideal. Texugo (talk) 15:31, 8 October 2013 (UTC)Reply
How about a pencil that is drawing a star, but has not finished yet? Nicolas1981 (talk) 11:20, 9 October 2013 (UTC)Reply
Hi, other Nick. In my experience with the mobile site, it's not just {{Starnomination}} that produces the "This page has some issues" feature. It's basically every template that uses whatever code is in {{Ombox}}. On Wikipedia, that code is mostly used for cleanup templates, hence those specific words. This could only be solved by directly changing the MediaWiki code. I am not sure how you would be able to even request that, though, without changing what happens on Wikipedia. Nick1372 (talk) 19:32, 8 October 2013 (UTC)Reply
The Mediawiki page in question seems to be MediaWiki:Mobile-frontend-meta-data-issues. We can change the text there without affecting other wikis, but I tried blanking it, and while it then no longer shows the text message, it still displays the little "i" icon. Is there a more appropriate message we can put there? Texugo (talk) 19:46, 8 October 2013 (UTC)Reply
Do we really need to tell readers in the first place? Being in a nomination process does not make the article special, so the easiest might be to remove the ombox from the starnomination template, leaving just the [[Category:Star article nominations]] part. What do you think about it? Nicolas1981 (talk) 03:37, 9 October 2013 (UTC)Reply
No, but telling readers does invite them to read through the article and then join the nomination discussion. Moreover, taking out this one ombox would only fix the issue for this one template, while all the other ombox-using templates continue to have the same problem. I think we need to 1) change that mediawiki page to something more useful/accurate as a temporary measure, maybe something like "some content may not be displayed", and then 2) figure out how to disable the automatic message. Texugo (talk) 11:28, 9 October 2013 (UTC)Reply
I went ahead and changed the message to "some content may not be displayed". It isn't ideal, but it's somewhat more accurate than the default message. Now if we can just figure out how to turn off that message altogether... Texugo (talk) 12:46, 15 October 2013 (UTC)Reply

Speak up about the trademark registration of the Community logo.

Reviews

Hi there!

Reviews have been a long-term resident on the Wikivoyage A-Z of the future, but I thought I'd mention the concept here as it's part of the My Voyage (subtle plug, see topic above) suite of user tools and enhancements that I'm meddling with at the moment. I understand that reviews are among the most controversial features (along with videos) on the MV mock-up, so I wanted to gauge opinion on the subject here. At present, I don't know of a way to implement the reviews as suggested in the roadmap, however, here's my alternative plan:

Reviews occupy a separate tab (next to 'Discussion') at the top of the page. There, all of the listings are automatically copied, but are read-only (is this possible?). Users may then leave comments and ratings (out of 5 or 10?), the latter of which is then averaged and displayed on the main article page alongside the listing in question.

I, like all of you I'm sure, have no desire for this feature to replicate the excesses of sites like trip advisor or for this to become our main endeavour, however, it is a fairly simple way in which users who are unwilling to write for the site may provide content. It's also yet another way of distinguishing ourselves from WT and hopefully boosting our search prospects at the same time.

Any thoughts would be very welcome! --Nick talk 23:18, 8 October 2013 (UTC)Reply

I'd suggest out of 10.
How do we stop IP's gaming the system?
Registered Users may assess only? - then there will be a perverse incentive for hoteliers and restaurateurs to either register multiple accounts or get all their employees signed up. That's what I hate about the Tripadvisor blackmail site. --W. Frankemailtalk 23:41, 8 October 2013 (UTC)Reply
  • For ratings: Unless/until we get all our listings templated and then all integrated with corresponding Wikidata items, this whole idea will be next to impossible to implement because we would undoubtedly need a database to keep track of and average the ratings. If we do that and if Wikidata allows us to store that type of non-factual information there, we could probably set up some kind of thing similar to the listing editor to pop up and allow users to put in a rating, but we will then still have the very challenging problem of keeping it fair, as mentioned above.
  • For reviews: This would probably also be best done with a kind of database so that a page could be dynamically generated to show the reviews for only whichever listing you click on. Otherwise things will quickly become a big mess with multiple written reviews for multiple listings of multiple types all on the same page. This is another type of non-factual info that I'm not sure Wikidata will be willing to accommodate, and will require intensive patrolling on our part, wherever it is stored.
Overall, I'm not convinced that this won't be far more trouble than it's worth, if it is doable at all. I certainly wouldn't want a giant distraction from our main goal of writing great travel guides. Texugo (talk) 00:01, 9 October 2013 (UTC)Reply
I think I'm probably inclined to agree with you - it would require a lot of work to make it usable and we have larger problems at the moment. Any thoughts as to how we could make user-generated maps or easily creatable itineraries? --Nick talk 00:09, 9 October 2013 (UTC)Reply
I have far too little time for WV now to get involved in every discussion, but I just wanted to make sure you are aware that there is a group of editors/community members who believe adding the review feature is a very bad idea and strongly oppose it. Please do not push that through. PrinceGloria (talk) 06:23, 13 October 2013 (UTC)Reply
Would I be right to think that you include yourself in that number PrinceGloria? :) Nothing will or should be 'pushed through' without community approval, although the community sometimes needs to speak a little louder and sooner. --Nick talk 18:54, 14 October 2013 (UTC)Reply
I can't do anything about "sooner" except playing with time tags, but you can count on me shouting "NOOOOOOO" at the top of my lungs. Whenever you wouldn't be sure if it was a no, do let me know and I'll repeat it strongly and clearly. :D PrinceGloria (talk) 21:11, 14 October 2013 (UTC)Reply
I mostly agree with Texugo's thoughts about the implementation, and it would really require a lot of moderation. It's not something to be carried out half-heartedly. Anyway, all the pros and cons from User:Jmh649/Travel reviews, Wikivoyage talk:Roadmap and Wikivoyage:Roadmap/Enable_listings_reviews needs to be summed up and concluded, so anybody new or unfamiliar with the site can understand why it's been considered and not been carried out. Any volunteers? -- torty3 (talk) 12:04, 15 October 2013 (UTC)Reply

Making "Please sweep the pub" less prominent

Moved to Wikivoyage talk:Travellers' pub. Please comment there for discussion about archiving.

Experienced editors in London for a possible edit-a-thon?

I was talking to someone from Wikimedia UK recently along the lines of "wouldn’t it be neat if we could improve the London Wikivoyage guides before Wikimania 2014." (Most are just useable at the moment.) He suggested running an edit-a-thon but this is where it fell down. He’s run edit-a-thons before but doesn’t know anything about Wikivoyage, while I know nothing about either. After pondering this, I think it would be better to try to pass the idea on to someone else. I’m not sure how it would work, or even if it would go ahead, but, if it did, it would probably be with a mix of new editors and curious Wikipedians. (Wikivoyage policy is apparently a stumbling block for the latter.) So, are there any experienced Wikivoyage editors in the London area who might be available to help run an edit-a-thon? If anyone is interested, I can point both parties in the other’s direction and let them see what they can do. - AdamBMorgan (talk) 13:33, 9 October 2013 (UTC)Reply

Quick question: is an edit-a-thon the same thing as a Collaboration? PerryPlanet (talk) 17:34, 9 October 2013 (UTC)Reply
Additionally, you might want to look in to whatever is going on over here. PerryPlanet (talk) 17:41, 9 October 2013 (UTC)Reply
An edit-a-thon is an event in which people work together in person to build content on a wiki. See this. --Saqib (talk) 17:47, 9 October 2013 (UTC)Reply
Saqib's link explains it in more detail but, in summary, it is a little like a collaboration except that everyone is physically in the same room and there may be a tutorial element. The last part is why an experienced Wikivoyager would be needed; they might need to teach some or all of the attendees how bits of Wikivoyage works and probably answer a few questions. (I exaggerated a little about knowing nothing; I just don't know nearly about either, although I have been to one edit-a-thon and I've made it to a mighty triple digits in my Wikivoyage edit count.) - AdamBMorgan (talk) 21:12, 9 October 2013 (UTC)Reply
Wikimedia UK has an office in London and would, I am certain be happy to host this, if it happens. Mozilla spaces in central London have hosted these in the past and are another possibility. Alternatively the Wikimania organisers might be able to get the Barbican to act as host. Check out the wikimania wiki Filceolaire (talk) 22:56, 12 October 2013 (UTC)Reply
Oh my, that's quite brilliant! Do let me know whenever you host that if I can participate as a semi-experienced Wikivoyager but not Wikimania participant or anyway else involved in Wikimedia. I would love to come to London and join in the effort and help in any way I could (if I indeed could and if you'd let me know early enough for me to make my bookings). I guess we'd need a workshop or two on district division to start with, but this could be concurrent to other efforts, as it is quite easy to move stuff between districts if arranged properly. PrinceGloria (talk) 06:32, 13 October 2013 (UTC)Reply

Geonotice

I would like to propose the Geonotice feature on this wiki. Those who don't know what a Geonotice is, please see Wikipedia:Geonotice. With Geonotice enabled, we can announce events related to WV such as above proposed edit-a-thon, meetups and even when a Wikivoyager is travelling to another location and would like to meet local Wikivoyagers in person. --Saqib (talk) 18:09, 9 October 2013 (UTC)Reply

To me it would be a shame to miss out on an event in a location I regularly visit. Also basing physical location off IP address assumes people are not running of remote proxies or simply travelling. One of my annoyances of hotel chain and airline sites is them trying to be clever about what language I prefer to read in based on the access route I am using into the internet or where I just happen to be logged into at the time. This is a site about travelling, keep it global.--Traveler100 (talk) 20:50, 9 October 2013 (UTC)Reply
It's a good idea, but it could probably wait until our meetups page is overflowing. That currently it doesn't seem to be. --Inas (talk) 22:16, 9 October 2013 (UTC)Reply
Well, this can advertise Wikimedia-wide events, and I didn't even know that the meetups page existed until 2 seconds ago. Meanwhile, a geonotice is seen by everyone in the location. --Rschen7754 07:05, 10 October 2013 (UTC)Reply
I have gone to a Wikimedia meetup in Glasgow as a result of a Geonotice on WP. It would be useful to advertise the edit-a-thon (see above) to all editors (all readers?) in SE England, rather than just those that look at a few project pages. AlasdairW (talk) 20:51, 10 October 2013 (UTC)Reply

Wikidata now has a "Wikivoyage banner" property, let's use it!

Wikidata now has a Wikivoyage banner property! Now when you create a banner, it will be used in all languages :-)

1) Could someone modify the pagebanner code to take advantage of that? See Andorra for an example of an article that retrieves a lot of its information from Wikidata.

2) Anyone willing to write a one-time script that would add all existing banners to Wikidata? (example)

Cheers! Nicolas1981 (talk) 02:00, 11 October 2013 (UTC)Reply

Oooh! What a pleasant surprise! That will come in very handy! Unfortunately I have no idea how to make this kind of script. Texugo (talk) 02:17, 11 October 2013 (UTC)Reply
I quickly learned how to write bots (surprisingly easy!), and created BannerBot. For now it just sets the property for one object, so what's needed is the list of destinations-banner couples. Nicolas1981 (talk) 08:30, 11 October 2013 (UTC)Reply
I've fixed the pagebanner code; I believe it works, but check to make sure I didn't bork anything up :) --Rschen7754 09:15, 11 October 2013 (UTC)Reply
Two things to consider: 1) I coded it so that whatever is on Wikidata overrides what is on here. Not sure if that is what the community wants, though doing it the other way can be done too. 2) Hopefully different Wikivoyages didn't choose different pictures for the same page. --Rschen7754 09:17, 11 October 2013 (UTC)Reply
Also, the file name in the pagebanner transclusion will be redundant, and you may want to consider running a local script to remove them (but it is optional - just to reduce confusion). --Rschen7754 09:19, 11 October 2013 (UTC)Reply
Thanks a lot Rschen7754! Personally I think the ability to override locally would be appreciated, see this summit discussion with Alexander. Cheers! Nicolas1981 (talk) 09:45, 11 October 2013 (UTC)Reply
Done, though now the parameter will have to be removed to allow the wikidata stuff to show. --Rschen7754 09:56, 11 October 2013 (UTC)Reply
This appears to have broken the banner - the TOC now appears below the banner, rather than overlaid on top. Any ideas why? --Nick talk 10:46, 11 October 2013 (UTC)Reply
An extra line break had been inserted in there. Should be fixed now. Incidentally, I agree that we need local override capability. I was also thinking, after running the bot to catch wikidata up to speed, we can put a switch in the pagebanner template which checks for pages with local banners but no banner in Wikidata, and adds them to a Category:Banner missing from Wikidata, so that we can keep it in sync as people add more and more banners. (Note that this would not include future cases where we locally override a banner on wikidata, only cases where wikidata has nothing.) Texugo (talk) 11:54, 11 October 2013 (UTC)Reply
There does appear to be another problem with the way you've changed the template though. Right now the logic says:
a) is there something in {{{1}}}?
if yes, use that
if no,
b) is there a wikidata item?
if yes, use that
if no, use the default banner
The problem is that this only works for pages which have nothing in {{{1}}}, whereas articles outside of europe/n. america all have various other default banners written in {{{1}}} other default banners are still taking precendence over wikidata but they should not be. The logic needs to be changed so that a) asks "is there something in {{{1}}} other than one of the various default banners?" This will apparently require yet a third long list switch. Or perhaps the overall logic of the whole template needs to be moved around a little. Texugo (talk) 12:27, 11 October 2013 (UTC)Reply
Now done. I was able to trim some redundant code before I made the change, so it wasn't as bad as I had feared. I have an idea for improving the code - let me see if I can get to it within the next hour. --Rschen7754 18:50, 11 October 2013 (UTC)Reply
Eh, I think it's more readable the way it is set up; WOSlinker made another edit to fix things too. --Rschen7754 19:10, 11 October 2013 (UTC)Reply
Looks great. I added a little switch for Category:Banner missing from Wikidata as well, as discussed below. Texugo (talk) 19:44, 11 October 2013 (UTC)Reply

Okay, maybe I'm being obtuse, but...

  1. Why do we want every Wikivoyage to use the same banners?
  2. What happens if a banner is hosted locally due to copyright issues?

-- LtPowers (talk) 15:05, 11 October 2013 (UTC)Reply

To add, what if a banner has a caption (as do many of the ones I've uploaded)? Will there be a way to provide different captions for each language version? Rastapopulous (talk) 15:31, 11 October 2013 (UTC)Reply
  • It's not that we necessarily want every Wikivoyage to use the same banners, but we do want as many pages to have banners as possible a good, already made and properly sized banner in use on another version is always better than no banner at all, and this is an automatic way to ensure that. With much lower numbers of editors, it would take the other language versions years to create as many banner as en: has in a few months, so there is much interest using the already made good images. And there aren't currently very many pages for which multiple good banner options have been created. If it comes to that, we and other versions always have the choice to override locally.
  • If a banner is hosted locally due to copyright issues, it shouldn't be listed on Wikidata.
  • Captions do not appear to be stored on Wikidata anyway, so any captions will remain local.
Texugo (talk) 15:40, 11 October 2013 (UTC)Reply

Let me also write it here, explicitly. We need a list of exceptions including generic banners used by each language version (en: has generic banners for different continents, ru: is using generic banners for those destinations where a good custom banner can not be drawn, other projects may have their own quirks). These generic banners should not be copied to Wikidata. Then we need a really smart bot that will remove filenames from the {{pagebanner}} template, but only those filenames that match their counterparts in Wikidata. Nick, are you able to do this? --Alexander (talk) 16:43, 11 October 2013 (UTC)Reply

LtPowers: Creating banners is a severe pain. Finding good images, manipulating them, uploading as a derivative, categorizing... Each banner takes a rather long time, English Wikivoyage is slowing after painfully reaching 20%, and other Wikivoyages have no hope of ever reaching 100% if no collaboration happens.
Texugo: Good points. Any idea how a script could check whether a file is hosted locally due to copyright issues?
Alexander: That would be a different bot, right? I guess I could do it, but I will be travelling soon, back in December, so hopefully other people will step in and start coding :-) Nicolas1981 (talk) 16:53, 11 October 2013 (UTC)Reply
I imagine it could check whether the file is in Category:Files to be kept locally. We don't appear to have any banners in this situation yet. Texugo (talk) 16:58, 11 October 2013 (UTC)Reply
Thanks! I updated the bot request. By the way: Rather than create a bot that would maintain Category:Banner missing from Wikidata, how about just run the initial bot again, every week or so? Nicolas1981 (talk) 17:21, 11 October 2013 (UTC)Reply
Category:Non-free Wikivoyage banners exists; is it used anywhere? And it should probably be a subcat of Category:Files to be kept locally. LtPowers (talk) 17:33, 11 October 2013 (UTC)Reply
Hmmm... I couldn't find any templates that insert that category, but it's not a bad idea, and yes, should be a subcategory of the other..
As for running the bot every week or so, well, if somebody is going to keep track of that and do it regularly without fail, that's fine with me. I'm just afraid those things tend to be forgotten after a while. At any rate, I don't think the category would hurt even if the bot were run every week. At least you could see at a glance whether it needs to be run. Texugo (talk) 18:07, 11 October 2013 (UTC)Reply
If an image is nonfree, should it really be used in a banner? --Rschen7754 18:25, 11 October 2013 (UTC)Reply
Why not? Our policies allow it, as long as the reason it's non-free is limited to depicting an important but copyrighted work of art or architecture. LtPowers (talk) 19:17, 11 October 2013 (UTC)Reply
The problem with that is that it comes very close to violating fair use laws. Since we don't have individual articles on sites, the chances that we would need a non-free image as a banner are fairly small. --Rschen7754 23:57, 11 October 2013 (UTC)Reply
Um, no, not even remotely. It would come very close to violating Wikipedia's non-free-use policy, but we are not Wikipedia. Fair use laws are considerably broader than that, and we're well within our rights to editorially use a photograph of a famous attraction in the area about which we are writing. Travel publications do it literally all the time. LtPowers (talk) 02:12, 12 October 2013 (UTC)Reply
At such a high resolution that is needed for the banner, and for decorative use? This really does not seem like a good idea. --Rschen7754 19:17, 12 October 2013 (UTC)Reply
Resolution is irrelevant. The reason Wikipedia requires non-free images to be low-resolution is because Wikipedia deals frequently in book covers and CD covers and screenshots -- images where someone might be able to use the image to recreate the copyrighted work, or for other fraudulent purposes. For travel photographs of buildings and sculptures, which is the extent of what our non-free-image policy covers, resolution is not an issue, with, perhaps, certain image-specific exceptions. "Decorative use" also fails to adequately describe the use to which we put these images. We choose to present them in a decorative fashion, but that hardly makes them any less educational than the more boringly-presented lead images we have long used. I hate to repeat myself, but we really are not Wikipedia. Wikipedia has their rules, and has good reasons for them; we have different rules, and good reasons for them as well. But since our purposes are different, so must the rules be. LtPowers (talk) 18:36, 14 October 2013 (UTC)Reply
That's great and all, but I don't care about local policy, if it doesn't comply with copyright law in the United States and/or puts the Foundation at the risk of being sued. --Rschen7754 07:24, 15 October 2013 (UTC)Reply
If you think that current policy cannot be justified by the doctrine of fair use for educational or informational purposes, please make your argument at Wikivoyage talk:Non-free content. My belief is that fair use is a principle that's important enough that the Wikimedia Foundation would be and should be willing to fight for it, if necessary, but if you think that banners are somehow different from non-banner thumbnails in terms of fair use, that would be worth discussing. Ikan Kekek (talk) 08:00, 15 October 2013 (UTC)Reply
And continue the discussion on some random page that nobody will notice. Eh, I don't think it would be worth it, since people around here don't seem to want to change any policy, or change anything from the Wikitravel days. In the last few weeks I've considered resigning the admin bit quite a few times for that very reason. --Rschen7754 08:10, 15 October 2013 (UTC)Reply
And continue the discussion on a page where there was already some discussion of the policy. I'm not sure who you're thinking of in your broad-brush remark, but I certainly have no great attachment to existing policies, and I'll observe that it would be quite ironic if you follow up resignations over frustration with Frank (and my apologies to Frank for bringing him into this discussion in order to make a point) by resigning because you seem to agree with Frank's viewpoint about admins (other than you). If you want to change a policy, as I've said to Frank, Tony1, and others, you need to make a clear argument and try to persuade others of its truth. I say that not because I disagree with most of Frank's arguments (rather, I agree with some of them, don't care enough to have a pro or con position on others, and disagree on one or two) or with yours (I'm not a lawyer and haven't seen your argument on this policy in detail), but because you know very well that by giving up and just applying a negative stereotype to (other) admins, you won't be able to achieve anything. So if you really would rather make the argument here, with reference to the existing arguments at the talk page I linked to, rather than at the talk page in question, please go ahead. But I would implore you not to repeat the kind of corrosive statement you just made. I can resign, too, and if I do so in the near future, it would be for another reason: Spending unpaid time here will have stopped being fun, in large part because of just the kind of remark you just made. Ikan Kekek (talk) 08:36, 15 October 2013 (UTC)Reply
I don't think you realize how deflating it is to spend time helping the community here, and have your suggestions that might help this site get along better with editors from other Wikimedia sites spurned repeatedly. Perhaps I was a bit too broad in my remark: my comments certainly don't apply to everyone on this site, and I apologize for that. But what I've seen is a bit too much of circling the wagons whenever new proposals are made, and it seems that moving such discussions off to side pages where only regulars will notice is another thing that seems to happen a lot. Plus plenty of other things that other Wikimedians have complained about to me, and which I've largely overlooked. --Rschen7754 08:47, 15 October 2013 (UTC)Reply
Well, I can't speak for others, but I'd like to read your ideas — and in particular, for the purposes of this discussion, your concerns about the use of images that include copyrighted sculptures, etc. Also, for my part, the reason I suggest having discussions on relevant pages is to maintain order and continuity. I do a lot of patrolling, so I don't have trouble finding discussions wherever they happen. Ikan Kekek (talk) 08:57, 15 October 2013 (UTC)Reply
Yeah, the thing is that I don't do a lot of patrolling using RecentChanges - I keep an eye on things on #cvn-wikivoyage, but it doesn't show edits from trusted users. I've been wanting to write up my thoughts on Wikivoyage, but am still trying to find the time to do so. Oh, and in regards to your comment on Wikimedia defending fair use: that does not seem to be the case (also see Meta). --Rschen7754 09:02, 15 October 2013 (UTC)Reply

(unindent to avoid my interruption being a thin worm one word wide)Sorry to bother you, but what is " #cvn-wikivoyage ", please? --W. Frankemailtalk 12:16, 15 October 2013 (UTC)Reply

Fair use is not mentioned, but I don't think that proves conclusively that the WMF wouldn't want to fight for it, if they felt it was necessary. That said, if Wikivoyage's non-free content policy could expose the WMF to a lawsuit, I think the policy needs to go beyond the policy-discussion level and be referred to WMF Legal for them to rule on. Ikan Kekek (talk) 09:30, 15 October 2013 (UTC)Reply
We should probably have some idea of what the law says before trying to second guess the legal professionals about interpretation.
Does WMF have any existing policy on this? If so, we should take a look at it first, as it may solve the problem. (wishful thinking, I know, but we should at least check). Peter (Southwood) (talk): 11:36, 15 October 2013 (UTC)Reply

Okay, another concern: If we offload banners to Wikidata, it becomes nearly impossible to tell when a page on your watchlist has a new banner, or has its banner changed. LtPowers (talk) 02:12, 12 October 2013 (UTC)Reply

Not true. Check "Show Wikidata edits in your watchlist" in preferences. --Rschen7754 19:17, 12 October 2013 (UTC)Reply
Sigh... I have that checkbox checked. The problem is that seeing that an edit has been made to an article's associated Wikidata item doesn't tell me anything about what was changed. It might have been the name of, say, the Esperanto Wikipedia article associated with that item, or the creation of a Wikidata Category associated with that item, or the addition of a translated property to the item, or any number of other things I don't really give a fig about in a Wikivoyage context. And given the scores of Wikidata edits on my watchlist every day, as well as the painfully slow speed of large Wikidata pages, I cannot possibly check the history of each one to see if it's a Wikivoyage-related change or not. LtPowers (talk) 18:36, 14 October 2013 (UTC)Reply
If we can agree that the template should default to the first banner listed, and that any additional banner should be added to the wikidata item rather than replacing the one already there, that would mean that banner changes would have to physically happen here by means of override, and would thus show up on the watchlist as always. Texugo (talk) 20:54, 14 October 2013 (UTC)Reply
The automatic edit summary should explain what was changed. --Rschen7754 00:10, 15 October 2013 (UTC)Reply
The only edit summaries I see on my local watchlist for Wikidata changes all say "Wikidata item changed" and nothing more. Is there something else I should be seeing? LtPowers (talk) 01:15, 15 October 2013 (UTC)Reply
That's odd. User:Lydia Pintscher (WMDE) is that the expected behavior? --Rschen7754 01:42, 15 October 2013 (UTC)Reply

Bot has been approved! Anyone has time to prepare a CSV file containing couples ARTICLE NAME; BANNER FILENAME ? I would use it and start with a hundred of them. By the way, on the English Wikivoyage what are the filename patterns that distinguish generic banners that should not be uploaded? Will I filter them all out with "*default*.*"? Any other pattern? Nicolas1981 (talk) 11:06, 13 October 2013 (UTC)Reply

All the default banners filenames are listed in the code of the template. There are not very many so will list them here too:
Pagebanner default.jpg
Mena-asia_default_banner.jpg
S-amer africa default banner.jpg
Caribbean default banner.jpg
Australia-oceania default banner.jpg
TT Banner.jpg
Generic flying banner.jpg
Default Scuba diving banner.JPG
Itinerary banner.jpg
Welcome banner.jpg
I think that's the lot. Peter (Southwood) (talk): 12:02, 13 October 2013 (UTC)Reply
How does this banner property affect the way new custom banners should be added? Peter (Southwood) (talk): 12:08, 13 October 2013 (UTC)Reply
Banners should be added to the Wikidata item. --Rschen7754 17:13, 13 October 2013 (UTC)Reply
This is something new, we need a suitably detailed explanation on the project page, which is now presumably inapplicable. Peter (Southwood) (talk): 19:17, 13 October 2013 (UTC)Reply
This is overly complicated. It's bad enough we force people to go to another site to upload images, but we also want to force them to go to a third site to put the images into articles? LtPowers (talk) 18:36, 14 October 2013 (UTC)Reply
I think the idea of promoting sharing of data via Wikidata is a good one, and that interfaces for interacting with Wikidata will improve over time and make this easier. For now I would agree that it is burdensome to have to go to Wikidata to add a banner, so at least for the moment it may make sense to have this be a bot task - if a bot finds an English Wikivoyage banner that isn't yet in Wikidata it can add it and update our site accordingly. There are a number of talented bot writers working with Wikidata, so hopefully this would be a proposal we could endorse and one of their bot people could then implement. Would that address the complexity concerns? -- Ryan (talk) 18:46, 14 October 2013 (UTC)Reply
Certainly, though there's the still the issue of identifying changes to watchlisted banners, which is being discussed above. LtPowers (talk) 19:19, 14 October 2013 (UTC)Reply
I think that we need to take this slowly. It is a serous issue if banners can be changed without showing up on everybody's watchlist. A spammer could probably change a load of pages to show his advert before it was noticed, because the edits would not show up here or in most watchlists. The complexity will also put people off - banners are complicated enough as it is, and there is no link from our pages to the Wikidata page. I would also suggest that banners are only transferred after they have been in use here for a month, so that it is easy to change a banner shortly after it has been added. AlasdairW (talk) 21:59, 14 October 2013 (UTC)Reply
Well, such a spammer would certainly be noticed on Wikidata, as we have our own patrollers and admins. --Rschen7754 01:41, 15 October 2013 (UTC)Reply
And such a spammer would have to upload their ads to Commons, where they would not last more than a few minutes. I don't think spam will come this way anytime soon. Sincerely, the worst I can see happening is two editors arguing on which banner is the best... by the way, does this kind of banner dispute happen often on the English Wikivoyage? Nicolas1981 (talk) 01:58, 15 October 2013 (UTC)Reply
If the spammer uploaded an explict advert, it would be noticed on commons. But a lot of marketing photos would be accepted on commons - photos of hotels or restaurants for instance. Our policies restrict the use of hotel photos, so the use of a photo of an uninteresting hotel would normally be noticed and reverted. AlasdairW (talk) 21:54, 15 October 2013 (UTC)Reply
One mild three comment discussion on a replacement that was uncontroversial and a deletion of a touty non-compliant banner with strong agreement are the only cases I know of. It certainly is possible for this to be a problem, but there is a procedure for dealing with it at Wikivoyage:Banner_Expedition#Changing a banner. Peter (Southwood) (talk): 07:08, 15 October 2013 (UTC)Reply
Is it possible to have a script of some kind similar to the listings editor which would update wikidata when the pagebanner template parameters are edited? This should be something that could later be called from VE if/when it comes to WV. I think VE already has facilities for editing some classes of template, and maybe we could borrow from their coding. Peter (Southwood) (talk): 07:26, 15 October 2013 (UTC)Reply
Before answering this question, we need to decide whether we are going to limit wikidata items to having only one banner (in which case it should be hardcoded not to allow more) or whether we will put multiples there (as it currently allows). My proposal is to allow multiples there, so anyone can check there to see what options there are, but have our template here use the first one by default, so that if the banner shown on en: is changed afterward, it has to be changed locally in the override parameter, thus always showing up in recent changes. Texugo (talk) 11:13, 15 October 2013 (UTC)Reply
I see no reason not to allow multiple banners on a Wikidata item. It allows choice to the various languages, and they can all choose which they prefer from the available selection, which will in most cases be one.
It seems like a reasonable idea to have the first banner loaded as the default custom banner, and to require anyone who feels strongly enough to provide a replacement custom banner to make the necessary changes. It is probably not going to happen that often anyway. I am not sure I understand exactly what you are proposing, but it sounds OK. Peter (Southwood) (talk): 11:30, 15 October 2013 (UTC)Reply
It will happen now and then. Some banners have been replaced. Ikan Kekek (talk) 11:42, 15 October 2013 (UTC)Reply
Sure, they have, but the point is that if we follow the above, replacement would continue to happen by changing the attribute here in the template itself (where it can show up in our watchlists), rather than by simply replacing what is listed in the property field on wikidata. Texugo (talk) 11:46, 15 October 2013 (UTC)Reply
I got that and liked that proposal. Ikan Kekek (talk) 11:47, 15 October 2013 (UTC)Reply
All non-generic banners from all Wikivoyages are now in Wikidata :-) Nicolas1981 (talk) 04:17, 16 October 2013 (UTC)Reply
Hm. What about all these? Texugo (talk) 11:47, 16 October 2013 (UTC)Reply
These 472 banners have been missed indeed... Thanks for the feedback! Nicolas1981 (talk) 04:23, 17 October 2013 (UTC)Reply
Done :-) Remaining images should be moved to Commons first. Nicolas1981 (talk) 13:31, 17 October 2013 (UTC)Reply
Some are already on commons (Whale Rock, Train travel in NZ, Travel photography, Tracyton), some were deleted as copvios (Stanley and Port Augusta) and some have to stay on WV for FOP reasons (Loop art tour, SF Mission/Bernal Heights) etc. Peter (Southwood) (talk): 17:39, 17 October 2013 (UTC)Reply
I took care of most of them. Buffalo/Allentown and the Delaware District still needs to be moved to Commons, and the other three are copyrighted works we'll have to keep here. I'll see about putting a switch so we can keep the category clean. Texugo (talk) 17:56, 17 October 2013 (UTC)Reply
Done. Adding fop=yes to the pagebanner template will take them out of the maintenance category. Now all that is left is that Buffalo article. Texugo (talk) 18:02, 17 October 2013 (UTC)Reply
I was away for some time and missed all this discussion about banners move to wikidata. The idea sounds great, but at the same time I am worried about yet another relatively difficult step within the banner creation. I mean how many editors will be motivated enough going through the whole procedure of finding a picture, editing it, uploading to commons, and finally putting it to wikidata? I also find it is important that we keep the option of having different banners for each project.
Because adding banners has been one of my main activities at WV, I still have some open questions, for which I might have missed the answers above.
  • My main concern is how exactly will I find out from the watchlist that a banner was changed and why it happened?
  • If an existing custom banner is changed, there should be a discussion or at least reason behind it other than just personal preference. There is no space for such discussion at wikidata, is there?
  • How would I lead this discussion with anyone from a different language version?
  • Also we have some set of rules (or guidelines) saying what is a good banner and what is not. This might very from one WV to another.
  • Is it allowed or not to upload more than 1 banner to wikidata? If so and there are more than 1 banners, how can I implement a second/third/... one? --Danapit (talk) 07:39, 23 October 2013 (UTC)Reply

Hi, Danapit. The proposal, not yet set up, is:

  • the first banner is added to wikidata
  • the pagebanner template automatically grabs the first banner listed on wikidata unless something is written manually here (override)
  • additional banners can be added to wikidata, but beyond the initial banner, subsequent changes to the banner here will be managed by manually writing in the title (override), so that they show up in recent changes.

Texugo (talk) 10:35, 23 October 2013 (UTC)Reply

Texugo, thank you for the explanation. Still it is not clear to me how we can follow a change in the wikidata banner. This will not appear clearly in the watchlist. Danapit (talk) 18:44, 23 October 2013 (UTC)Reply
Well in the proposed scenario, the only way to change from one banner to a different one would be by manually changing it here, as we always have, so of course it would show up in the watchlist. Texugo (talk) 18:49, 23 October 2013 (UTC)Reply
How could we prevent anyone changing the banner at wikidata? We would have no control over that... It is not enough we agree only to add banners in case they are missing, but not changing them. We can agree here for this scenario, but how are the other wikidata users (non-wikivoyagers) to know? Danapit (talk) 18:57, 23 October 2013 (UTC)Reply
Well, Wikidata has patrollers too, who should prevent people from removing banners there. Wikidata does support adding multiple banner entries, and they do remain there in the order they are added. Texugo (talk) 19:38, 23 October 2013 (UTC)Reply
The other option would be to keep doing everything locally, and have the template not display anything by default but only flag articles (put them in a maintenance category) when wikidata has a banner for an article without one here. I might could be convinced to support that too. The problem I see is that doing it that way would eliminate any incentive for ensuring that banners are written to the data items and would require more manual maintenance to keep up with banners added there by other language versions. Texugo (talk) 19:41, 23 October 2013 (UTC)Reply
Wikidata surely has patrollers, but I am not sure if checking if a banner file is exchanged is high on their priority list. I did this edit some days ago replacing an existing banner file by another one (the old one had wrong size) and nobody complained. I would be inclined to support the other option including the maintenance category. Users working on banner expedition could regularly check that one like they do with crop maintenance category. Danapit (talk) 14:24, 24 October 2013 (UTC)Reply
If we can get someone running a bot to periodically check Category:Banner missing from Wikidata and add the banners to WD to collaborate with other language versions, I would be OK with that solution.Texugo (talk) 14:47, 24 October 2013 (UTC)Reply

Destinations and user experience

For previous discussions on this subject, see Talk:Destinations.

(Just trying out the new tag) After Nick bumped the Destinations page, I thought it should get more eyes on it.

The idea is to add Destinations to the start of each breadcrumb trail: Destinations > Asia > China for example. If the breadcrumbs are too long, it could be possible to reduce their font size.

I'll go further with another suggestion - add the top level regions to the sidebar.

Travel destinations

  • Africa
  • Asia
  • Europe
  • North America
  • Oceania
  • South America
  • Other destinations

And possibly add the article map to the end of that as well. I think the term Places rather than Destinations is better as well. Thoughts? -- torty3 (talk) 23:48, 11 October 2013 (UTC)Reply

Hi! Thanks for raising this!
Those suggestions sound good - perhaps 'Places' could be another collapsible navbar category (above Get involved?) where we could keep those top level destinations?
I'd really like to be able to embed this map (or make all our destinations accessible from PoiMap) on that page, but at present the 'MapFrame' template and associated JavaScript don't support it. Do you think there's any way that we could make that work?
If anyone else has any ideas for the page, it would be great to hear them! --Nick talk 00:26, 12 October 2013 (UTC)Reply
I like this idea a lot. It's my opinion that the name should stay "Destinations", if only for the fact that we call locations destinations 99% of the time around this site (i.e. Other destinations). It would make sense to keep it unified, but I won't go crazy if it's called Places. I don't know how the open source maps work so I can't help you there. Nick1372 (talk) 02:15, 12 October 2013 (UTC)Reply

There is further discussion at Talk:Destinations. Pashley (talk) 21:37, 12 October 2013 (UTC)Reply

I've been having a play with an idea for the new Earth page that you can see here. What do you think? The imagemap isn't quite finished yet, but it can be done very easily. --Nick talk 17:07, 23 October 2013 (UTC)Reply

I would rather think we'd want to incorporate those ideas with embedding of the article map. I think it makes for much more interesting exploring than starting with one of our mediocre continent article does. Texugo (talk) 17:22, 23 October 2013 (UTC)Reply
Believe me - I've tried! The current mapframe doesn't permit it (although could be tweaked by someone knowledgeable) and the other (slight) issue is that it can take an age to load as a result of the number of articles. I'd also have liked to somehow embed Special:Nearby, but that doesn't seem to be possible either. --Nick talk 17:35, 23 October 2013 (UTC)Reply
I know. I've tried too. Do we have any feature requests going on this yet? Texugo (talk) 17:50, 23 October 2013 (UTC)Reply
Artmap can be embedded, but I'm a little reluctant to do so because of the time to load plus will need to mess around with screen width, and would prefer a direct link (ideally in the sidebar). Not sure about Nearby. -- torty3 (talk) 12:42, 24 October 2013 (UTC)Reply
Could you tell us how it can be embedded, in case we want to play around with it? Texugo (talk) 12:55, 24 October 2013 (UTC)Reply

ShareMap - Wikimedia grant

Copied from Wikivoyage_talk:Community_portal#ShareMap_-_Wikimedia_grant --Nick talk 23:15, 12 October 2013 (UTC)Reply

Hello, WikiVoyagers ShareMap is a collaborative map creation tool. It is currently applying for Wikimedia grant to continue project development. One of ShareMap principles is preparing map authoring usable for WikiVoyage authors and readers (even if it is not very project in Wikimedia scale, we really believe in its success).

ShareMap already implemented some experimental features that is dedicated for WikiVoyage authors:

But there is still lot to do.

One of grant results will be creation free mobile off line map viewer application for maps created by Wikimedia community.

I will be very happy for endorsement, opinions or even criticism from all WikiVoyage community member on Wikimedia grant project.

https://meta.wikimedia.org/wiki/Grants:IEG/ShareMap#Part_3:_Community_Discussion

If you would like to learn more about ShareMap project please visit:

--Jkan997 (talk) 23:09, 12 October 2013 (UTC)Reply

Flow

Flow is a new discussion technology for Wikis, it might replace areas like this page. They are looking for volunteer wikiprojects. While we are not a wikiproject, should we ask to join as a prototype? Nicolas1981 (talk) 06:13, 15 October 2013 (UTC)Reply

Flow looks pretty cool, and it'll be really helpful once it's deployed. I for one would be interested in this site joining as a protoype. Either way, it can't hurt to ask. Nick1372 (talk) 23:33, 15 October 2013 (UTC)Reply
If we wanted to become a WikiProject, we could hijack w:WP:TRAVEL or one of its subprojects, they are as dead as dirt. K7L (talk) 13:32, 16 October 2013 (UTC)Reply
1-hour IRC chat 2013-10-24 18:00 UTC until 19:00 UTC at #wikimedia-office I can't attend unfortunately, anyone willing to attend and propose ourselves as a Flow beta test? Nicolas1981 (talk) 09:06, 22 October 2013 (UTC)Reply
I like the idea en-WV becoming a Guinea pig for testing Flow, I would certainly support anything that can make discussions easier to follow, mainly changes in individual threads. I can't attend the chat though. --Danapit (talk) 09:44, 22 October 2013 (UTC)Reply
Yeah, one reason why I think the Traveller's Pub hasn't changed much is because central archives and auto-archiving doesn't really solve the clunky wiki discussion format in terms of multiple simultaneous threads, though I don't know if being the guinea pig is a good idea. Let the WikiProjects have the first round. -- torty3 (talk) 14:09, 22 October 2013 (UTC)Reply

Where are the templates?

Where are the templates for "see", "do", "buy", etc.? Am I just missing them at the bottom or do I actually have to copy them from an article that already has them? ChubbyWimbus (talk) 07:05, 15 October 2013 (UTC)Reply

They've been removed already and moved into the edit bar. --Saqib (talk) 07:23, 15 October 2013 (UTC)Reply

Boost our readership by at least 400% in two months

or get rid of Frank for six!. How can we lose? --92.26.121.21 16:46, 15 October 2013 (UTC)Reply

I don't think anyone is arguing to expel Frank for 6 months, at this point. And speaking personally, I hope that there is never a cause for any more blocks of his account of any length. Ikan Kekek (talk) 17:13, 15 October 2013 (UTC)Reply
Like Ikan Kekek, I would not wish to lose Frank for 6 months, however, I appreciate the confidence with which he has put forward his findings and proposals. If we do implement the suggested changes, we'll have to be very organised and diplomatic about it - these are large changes. Personally, I'm happy to see parentheses replaced by a comma and extended lead paragraphs can only be a good thing. I'm slightly concerned about (although not opposed to) a change of headings, if only because I think the ones we've got are very good and will take some time to better. If we want to do this quickly (and in a single swoop), that could be a sticking point, but let's see how we go. Are we going to go ahead with these proposals? Wikivoyage is feeling a little empty at the moment... --Nick talk 18:23, 15 October 2013 (UTC)Reply
Changing our "traditional" section headings are just one (integral and highly important) part of a 5-point plan to kill off our "inferior mirror of Wikitravel" status with Google. Within 4 months of adopting ALL of these linked changes it will be WT that is regarded as an "inferior mirror of us" and then we can change all our section headings back again (if that's the consensus) to ram home WT's inferior status. Job done! --W. Frankemailtalk 18:36, 15 October 2013 (UTC)Reply
Please keep the discussion there if possible.Texugo (talk) 18:54, 15 October 2013 (UTC)Reply
Agreed with Frank. Being "better", while it would be great, isn't really the goal. The goal is to differentiate ourselves from WT, at least as far as Google is concerned. The problem as I see it speaks to what Nick said. Even if they're not improvements, we obviously want any changes we make to section headings, etc. to be at least equally good as what we had before. And what synonyms are there for, say, "Eat", "See", or "Do" that get the point across as well? -- AndreCarrotflower (talk) 19:11, 15 October 2013 (UTC)Reply
Eat: Eating, Dining, Food; See: Sights, Look; Do: Activities, Doing. Are these equally good? Not sure. I think "Food" and "Eating" are as good as "Eat," but "Dining" has other connotations. I think "Sights" is as good as "See," but "Look is inferior. And I think "Activities" is as good as "Do," but "Doing" is a bit strange. Ikan Kekek (talk) 20:50, 15 October 2013 (UTC)Reply
I'm only a recent immigrant to the project but I like your verbs-as-section-titles format and wouldn't want to lose that. I can't think of many obvious alternatives but if you do change the standard sections, keeping to verbs would be nice. (eg. "Get in" could be "Enter", "Get around"->"Traverse" or even "Travel", "Buy"->"Shop", "Sleep"->"Stay" etc). - AdamBMorgan (talk) 21:18, 15 October 2013 (UTC)Reply
Would it work if we just changed some of the sections to present participles? e.g. 'Understand' -> 'About'; 'Get in' -> 'Getting in'; 'Get around' -> 'Getting around'; 'See' -> 'Sights'; 'Do' -> 'Activities' (or controversially, merge 'see' & 'do'?); 'Buy' -> 'Shopping'; 'Eat' -> 'Food'; 'Drink' -> 'Refreshment' (probably the weakest); 'Sleep' -> 'Staying' / 'Accommodatio0n'; 'Connect' and 'Go next' remain. --Nick talk 22:20, 15 October 2013 (UTC)Reply
At the risk of drowning people in suggestions, how about adding the Five W's (and one H) before the verb? Get in would be How to get in; Get around -> How to get around; Understand -> What to know; See -> What to see; Do -> What to do; Eat -> What to eat; Drink -> What to drink; Sleep -> Where to sleep; Buy -> Where to shop; and Stay safe -> How to stay safe. This could be a compromise for those who like the classic ones. Now that I'm actually writing these down, though, they seem long. Oh well, it can't hurt to suggest them… Nick1372 (talk) 00:17, 16 October 2013 (UTC)Reply
Yeah, I think they're pretty clunky and not good. :-) Ikan Kekek (talk) 00:35, 16 October 2013 (UTC)Reply
Stylistically consistent, unambiguous and not worse than the current standard should be the minimum requirement. Better would be good, Worse would not. Peter (Southwood) (talk): 07:34, 16 October 2013 (UTC)Reply
I've tried some new headings in our Wigan article; please feel free to comment or change them - we could use that page as a sort of test bed, without disrupting the ongoing Somerset, Tasmania experiment. --Nick talk 10:12, 16 October 2013 (UTC)Reply

By all means discuss whether you think there are some improved names for section titles, but please don't confuse two entirely separate and distinct issues here.

I wish to increase our readership ten-fold in a few months. This will bring us new problems in the form of increased amounts of spam but it will also bring us new editors and patrollers.

The way to do this is to convince the ever-changing Google algorithms that we are not an inferior mirror site of Wikitravel (which currently beats us in Google's organic search results for most of our articles - the exception being my experimental Somerset, Tasmania article). We only need to do this once, then IB will pull the plug on Wikitravel since their advertising revenue will fall in step with their suddenly diminished readership.

Once we have convinced Google's crawling spiders that we are a changed site we will no longer suffer the crushing duplicate penalties.

Then (within reason) this site can have all the SEO sapping section titles and banners it wants.

This sea change must be a shock and awe, once only occurrence - not a gradual change - for it to work. That is why it is a VERY BAD IDEA to have a series of ad hoc individual experiments now.

By all means discuss what section titles you want to have AFTER "A-Day + 2 months" (maybe you'll decide it's just better to go back to our traditional titles) but, the section titles for "A-Day" must not be synonyms of Wikitravel's existing titles! Remember that "A-Day" is for robot readers - not for human readers. "A-Day + 2 months" when the job is done we can go back to (pretty well) disregarding what the Google spiders read...

I'm going into hospital now so I won't be writing here for some while, so please forgive me that I won't be here to guide your efforts. I wish everyone all the best! --W. Frankemailtalk 10:48, 16 October 2013 (UTC)Reply

I think some of us are getting ahead of ourselves with new section names and such when we haven't established which changes will do the trick, and several of us will be opposed to changing such things if not 100% established that it is what is needed. Again, I would really appreciate it if we would stop here and continue this conversation on Wikivoyage talk:Search Expedition, where this topic is already split into various different threads. We really don't need yet another parallel discussion going on here in the pub when so much has been written about it already there. Texugo (talk) 11:40, 16 October 2013 (UTC)Reply
It's definitely a good idea to keep discussions in one place but please discuss this rationally rather than continue to try and sabotage my experimental article. It's clear that you are implacably opposed to my project to increase readership (why, I'm not even going to hazard a guess at) but surely there can be just ONE exception to the current implementation of the Google search result slaughtering banners in our thousands of articles? I know you hate seeing my empirical results prove what I'm preaching, but try and exercise some judgement and self control, please. --W. Frankemailtalk 12:23, 16 October 2013 (UTC)Reply
I didn't simply revert your removal of the banner - I pointed you to the talk page where User:Torty3 explains how you are wrong about this. And I don't need you to tell me what my opinions are. I am not opposed to increasing readership, though I am opposed to your overly assertive and highly dismissive tactics in trying to force changes through, and I disagree that your results are empirical enough. Texugo (talk) 12:30, 16 October 2013 (UTC)Reply
As important as SEO efforts are, over a year has passed and I'm sure we can allow a few more weeks for some additional testing if that can get us to agree on a strategy. I understand that you're impatient, Frank, and this is our highest priority, but we're not in that much of a hurry. At the same time, I do believe we should allow Frank to have his own "experimental" article without interfering. Let's just agree on a few low-traffic test articles; there's no real harm in that, especially when compared to the gains we're trying to establish. JuliasTravels (talk) 13:35, 16 October 2013 (UTC)Reply
The test articles sound reasonable, but I'd be surprised if "changing everything at once" was hugely different than methodically updating one page at a time for SEO. The search engine is still just going to stumble across updates one article at a time as it isn't pulling the wikivoyage:database dump as one huge block. One option I'd like to see is to allow contributors to create "Whereverville/new" as a complete rewrite of an article on "Whereverville" that doesn't use any descriptive content from the old WT version. Any content added after the move to WV would be put into the new article with attribution, the old article would be discarded once the new one was at least to "usable" and the new page moved into its place. We don't have enough people to do this for every city, but having fresh content for a few of the most popular destinations would improve Wikivoyage. After all, a huge part of the reason why Evan and Maj decided a travel wiki was needed in 2003 is that it can be more current than a printed guide. Anything here that was recycled from WT is by definition anywhere from a year to a decade old, so much of it is stale. K7L (talk) 14:20, 16 October 2013 (UTC)Reply
With regard to Google pagerank, also see bugzilla:52688 and dependency bug (please, no "me too" comments over there). --AKlapper (WMF) (talk) 08:24, 25 October 2013 (UTC)Reply

We have been very successful with a newly created article. But have we had success with a long standing article yet? I tried with Cranbrook British Columbia and while it worked briefly it than stopped working. Travel Doc James (talk · contribs · email) 13:05, 31 October 2013 (UTC)Reply

individual listings in region pages?

Is there a template to tag region articles like Bohol which contain listings that should be moved to city/town pages? I'd removed a bit of obvious fluff "The resort (has) opened their doors to provide you with wonderful facilities and warm service. It is truly a venue you can enjoy with your family, friends, and even your colleagues...You can also find pleasure in their leisure facilities." and fixed incorrectly-formatted telephone numbers, but individual hotels are rarely notable at region level. K7L (talk) 13:37, 16 October 2013 (UTC)Reply

Yes. There is {{movetocity}}, which places the page in Category:Move listings to cities. Texugo (talk) 13:43, 16 October 2013 (UTC)Reply

Button to open POI in map+GPS app

Imagine you backpack around Bangladesh with only a smartphone and no Internet. You have an offline Wikivoyage (HTML files or OxygenGuide or Kiwix) and an offline maps+GPS app. It is already 5pm so you find a reasonable hotel in the Sleep section and want to walk to it, helped by GPS.

PROBLEM: Even though the listing includes GPS coordinates, it is very difficult to send these coordinates to any map app. The "easiest" is to edit the HTML, copy paste the latitude/longitude, and paste them into your map app after removing the template characters... very cumbersome.

IDEA: Our HTML should embed some kind of button to open the system's Map app. See how to do for Android and iOS. Any idea on how to integrate those, or any better solution, are very welcome!

DEBATE: What do you think? Should we implement this now? Only for mobile? How? Cheers! Nicolas1981 (talk) 05:49, 17 October 2013 (UTC)Reply

I'd think that we do not explicitly control how wiki code is converted into HTML in apps like OxygenGuide or WikiSherpa. The app does that. We only control what happens if the user is actually viewing Wikivoyage. A third-party app running from WV:database dumps is going to take the raw listing fields ("lat=", "long=", "wikipedia=" if used) and handle them its own way (WikiSherpa integrates WV, WP and a map IIRC). Let it do so and concentrate just on what happens to a wikivoyager using HTML here. K7L (talk) 14:25, 17 October 2013 (UTC)Reply
Agree with K7L. There is nothing stopping an app consuming Wikivoyage HTML content in the manner you describe in order to achieve this functionality. --Andrewssi2 (talk) 02:01, 21 October 2013 (UTC)Reply
I just came back from travelling WITH an Internet connection, and realized that Wikivoyage's embedded map is not enough. Travellers reading wikivoyage.org online will want to open the map in their favorite GPS/directions app. So I think we should have a small "Open with Geo app" button next to each POI. Nicolas1981 (talk) 04:51, 21 October 2013 (UTC)Reply
If it was easy to implement with a standardised link format like maps:// or geo:// similar to the recent tel:// links that were added, then easy decision. But there are differing systems which would require user agent testing, and then choose one of Windows/Apple/Android/Blackberry. Apps should handle their own formatting and functions. One possibility is leaving the geohack link in, though that will probably take three clicks, one to geohack, one to linked Google/Bing map and one to Google/Apple map app. -- torty3 (talk) 14:22, 22 October 2013 (UTC)Reply
w:Geo URI looks to be a standard, but the great thing about standards is that there so many from which to choose. Here, geo: and tel: mean nothing on the desktop if I have no app installed for either, but some mobile devices might do something sensible with them? K7L (talk) 15:09, 23 October 2013 (UTC)Reply
Well, it's a standard but not the global standard. Seems like geo:// works for Android, while Apple has another standard, and I haven't checked for Windows and BB. -- torty3 (talk) 12:23, 24 October 2013 (UTC)Reply

Quitting due to good newly authored content constantly being removed

In case there's any sane people left here, feel free to browse my history here and on WT (same username). I've had a gutful of this frankly rude and non-constructive content removal and quit. Perhaps you might consider reigning in this activity before it loses you more motivated contributors. See you all later and best of luck with the project. Pratyeka (talk) 02:05, 21 October 2013 (UTC)Reply

Sorry to see you go. Happy trails! And to anyone who's really interested in this, please feel free to look at Pratyeka's talk page and draw your own conclusions as you wish. Ikan Kekek (talk) 02:23, 21 October 2013 (UTC)Reply
I look at it as a sort of rite of passage. Like it's not a real wiki until you have to contend with things like petty tyrants and edit warriors and personal agenda-pushers. Welcome to the big time, Wikivoyage. :-) -- AndreCarrotflower (talk) 03:23, 21 October 2013 (UTC)Reply
The reason I believe in Wikipedia and Wikivoyage is that sites like these represent something akin to the Medieval method of collective authorship, complete with marginalia (the Talk pages), but no longer restricted to a small number of professional scribes and clerical university students, but open to anyone with web access. Anyone who has too big an ego to want to work collectively can't do well here, no matter how good a writer they are. That's unfortunate, but that's the way it is. It's a big worldwide web out there, and everyone who wants to can express themselves somewhere. Ikan Kekek (talk) 03:35, 21 October 2013 (UTC)Reply
I'm very sorry to see you go and I know you're big enough morally to avoid painting yourself into a corner if you do ever want to change your mind. Yes, it is very tough when sparkling prose and professional pictures imparting wisdom to the traveller are messed about by people not keeping our primary policy right to the forefront of their mind: the Travellers' viewpoint should always comes first in any dispute! and being positively unfriendly (I would except Ikan Kekek from that because I do know that - when he's not having a bad day - he can be very helpful). I know you had some happy Burmese days and I hope you continue to have happy Thai days! -- Alice 18:18, 22 October 2013 (UTC)
Hi Pratyeka! Just looking at the small edit war that shows last in your contribution history, I have to agree that these historical images would be a bit too much on an already image-heavy page. How about taking a break to focus on something less controversial, for instance creating banners for Indonesian towns? Cheers! Nicolas1981 (talk) 05:12, 21 October 2013 (UTC)Reply
I do concern that the content added by some users is more 'general trivia' than 'travel guide content', and historical images should really go to the relevant Wikipedia article instead. I wonder if the scope of WV isn't clear and defined enough? Andrewssi2 (talk) 05:46, 21 October 2013 (UTC)Reply
A look at this user's talk page plainly shows that the issue here is not how clearly defined our scope is, and that attempting to calmly reason with the user as Nicolas1981 seems to be doing is unlikely to do any good. The plain fact of the matter is that collaborating on a wiki is not for everyone, and this user's temperament is obviously not compatible with such an endeavor. The user has behaved provocatively and with a complete lack of civility (going so far as to call one of our long-standing admins an "asshole" ), showed a blatant disrespect and disregard for our policy (shrugging off objections to his/her use of first-person pronouns in Dordrecht by saying that he/she is "not really interested in policy" ), and angrily defied repeated attempts by other users to counsel him/her and guide him/her toward being a productive member of our community.
Sad to say, it's often better that people like this leave our community, rather than encouraging them to stay and, in all likelihood, continue to antagonize other editors and cause trouble in general. If it were up to me alone, this user would have been blocked a long, long time ago. It's not our job at Wikivoyage to be bleeding hearts. We give problem editors a certain number of chances to get with the program - and in this case, if anything, we gave this user too many chances - and if that doesn't work, they're out the door. It's not worth the effort; we have bigger fish to fry here. -- AndreCarrotflower (talk) 06:11, 21 October 2013 (UTC)Reply
Even though this user is an admin on the English Wikipedia, they have been involved in some recent controversial actions over there: . As I've said in my essay w:User:Rschen7754/You represent the English Wikipedia!, adminship over there certainly should not grant immunity to blocks/bans here if the community feels they are necessary. --Rschen7754 06:15, 21 October 2013 (UTC)Reply
As a sidebar, one thing I'd like to know is how a user who has expressed such a vehement antipathy to the very concept of "policy" ended up an admin on en.wp. What do admins do other than policy-related stuff? -- AndreCarrotflower (talk) 06:55, 21 October 2013 (UTC)Reply
In the early 2000s, it was very easy to become an admin there. --Rschen7754 07:05, 21 October 2013 (UTC)Reply

────────────────────────────────────────────────────────────────────────────────────────────────────

Must-read. --Saqib (talk) 07:18, 21 October 2013 (UTC)Reply
Thanks, Saqib. Very topical! Ikan Kekek (talk) 07:24, 21 October 2013 (UTC)Reply
I am not familiar with this user, but was surprised to find, after a single interaction with this user in which I explained what I was doing and why, that I was named, twice even, as the reason for their leaving. The way they were putting the article together was very unlike the way we build articles, but they seemed unwilling to take the policies and practices behind that into consideration. Texugo (talk) 19:28, 21 October 2013 (UTC)Reply
meta:Don't be a dick is a pretty good guide for dealing with these sorts of situations, both for the person accused of being problematic, and for ensuring that the accusers themselves aren't being "dickish". While the title makes it tough to cite without further inflaming passions (as the essay notes, telling someone "don't be a dick" is a dick move), I suspect that we will at some point need to draft some sort of civility guideline, and that essay might be a good basis for such a policy. -- Ryan (talk) 20:29, 21 October 2013 (UTC)Reply
*Cough* - I wrote this for a previous issue, but perhaps a sort of crossover between this rather tame effort and meta:Don't be a dick might work? --Nick talk 21:47, 21 October 2013 (UTC)Reply
I like the content of Wikivoyage is fun , although you are right to say it is pretty tame. I think meta:Don't be a dick would actually get everyone's attention and actually be a position that we could (intentional dicks aside) agree on. We should always however strive to remember why we are doing this, which is because it is fun. Andrewssi2 (talk) 09:31, 22 October 2013 (UTC)Reply
Everyone likes Nicholasjf21's "fun" essay, so if we need a civility policy, it should probably be called something like Wikivoyage:Keep Wikivoyage fun. LtPowers (talk) 15:31, 22 October 2013 (UTC)Reply
I am in full agreement with this. And if we could incorporate certain elements of the essay Saqib linked to, that'd be awesome too, just because that page was so relevant to what we've been dealing with lately. Something along the lines of "If you keep getting into arguments and threatening to leave, then you're clearly not having fun and you're making things miserable for everyone else. In which case, just leave." But stated more eloquently than that, obviously. ;) PerryPlanet (talk) 18:43, 22 October 2013 (UTC)Reply

POI editor: Wikipedia page?

How about adding a link to Wikipedia for POIs that have a Wikipedia article? That would allow readers to get in-depth information for a museum, monument, park, waterfall, or any famous place. The French Wikivoyage actually has that. Wikipedia articles could then be used to populate the mini-picture of each POI in the dynamic POI map. Nicolas1981 (talk) 10:10, 21 October 2013 (UTC)Reply

Do you have a French wikivoyage link that would illustrate this? --Andrewssi2 (talk) 10:54, 21 October 2013 (UTC)Reply
I must have dreamt, I can't find anymore... it was probably not the French one, actually. Nicolas1981 (talk) 09:08, 22 October 2013 (UTC)Reply
Lac-Mégantic. But discussion of this has been previously carried out at Wikivoyage talk:Sister project links, and should continue there. It's a rather turbulent discussion, so it would need some new insight for any productive work. -- torty3 (talk) 12:16, 22 October 2013 (UTC)Reply
Yeah, please read all the various previous discussions on this at Wikivoyage talk:Sister project links, Wikivoyage talk:Links to Wikipedia, and Wikivoyage talk:Listings#Listings tags and links to Wikipedia. After reading all those very divided and deadlocked discussions, if you don't have some absolutely novel, revolutionary proposal that will address all the issues raised, you might not want to open that can of worms again. It hasn't been long since the last such discussion finally died down. Texugo (talk) 13:09, 22 October 2013 (UTC)Reply
I'd think the term "can of worms" is a bit harsh. It's just en: that's deadlocked on this, as far as I know, as on some of the others (like fr:) the links weren't debated on any huge scale and the sky hasn't fallen. Ultimately, we do need to attract new en.WP authors to write here or the project (much like the deadlocked {{listing}} debate) will stagnate. K7L (talk) 15:00, 23 October 2013 (UTC)Reply
The point is that we've already been over and over the same arguments quite thoroughly three times in recent months, so if no innovative perspective is brought to the table to address the concerns which have led to the deadlock, it will be a waste of time to drag it all out again and rehash the same stuff. Texugo (talk) 16:35, 23 October 2013 (UTC)Reply
To be clear, the intention isn't to stifle discussion or shuffle it somewhere else. The open-door policy (never closing discussions) is good, but sometimes it will probably be better to let the idea rest and then reassess community support after a set amount of time. Although closing discussions would have prevented fiascoes like the spelling issue. Reading back on it, I think Ryan's comments about Wikivoyage:Consensus are extra relevant now. Maybe a debate style of statement and rebuttal is needed or better summaries, rather than the wall of text discussion in which good points are lost. And if en.WP authors are not contributing just because they cannot add Wikipedia links here, I think that's too bad. -- torty3 (talk) 04:48, 26 October 2013 (UTC)Reply

Wikivoyage POI database for OsmAnd?

The open source Android map+GPS app OsmAnd allows users to add custom POI databases.

It would be great to have a Wikivoyage POI layer. If the whole world is too heavy, we could split in different countries or regions.

Anyone interested? By the way, this database could also be a first step before Wikidata-based interwiki POI collaboration. Nicolas1981 (talk) 10:53, 22 October 2013 (UTC)Reply

Unfortunately, I don't know how to do it, but I believe it is task #1 for the whole project. Offline usage of Wikivoyage is... well, underdeveloped. And OsmAnd is a great tool that gets more and more users, so the export of our POIs to OsmAnd maps will be not only handy for the existing Wikivoyage users, but also a great promotion of Wikivoyage among all people who use OsmAnd. --Alexander (talk) 18:12, 22 October 2013 (UTC)Reply
I just implemented a basic Wikivoyage→OsmAnd transformer. Open source, improvements welcome on Github. Here is a test output, containing all POIs of Rattanakosin, try it with OsmAnd! No metadata yet, everything is a restaurant ;-) Anyone motivated for taking this script to the next level? (command-line OsmAndMapCreator, automatic generation from the Wikivoyage dump, regional packs) Nicolas1981 (talk) 09:35, 25 October 2013 (UTC)Reply

An idea on how to get more visitors/contributors

Here is an idea on how to get more visitors/contributors.

  • Start with a list of our ten most visited articles. Let's say they are "City 1", "City 2" and "City 3" etc.
  • We can then assume they are also amongst the most common searches for travel guides on google. So "City 1 travel guide" is probably one of the most popular searches on google, much more common then "Any_other_city travel guide".
  • We should now make sure these ten articles makes it to the top in a google search. If "City 1 travel guide" has wikivoyage as the top result, that will make a greater impact on the number of visitors than if we are the top result for "City 374 travel guide".
  • Then we also make sure these ten articles are of the best quality possible, make them star articles. This means most of the new visitors will find wikivoyage a useful travel guide and recommend us to others. Link to wikivoyage in blogs, forums etc.
  • I am sure this will make a difference. We will get more visitors and more contributors, and hopefully it will make a snowball effect.

Traveler 712 (talk) 11:25, 23 October 2013 (UTC)Reply

For one related list, see Wikivoyage:World_cities/Large. For discussion of search issues, see Wikivoyage:Search_Expedition and the talk page for that article.
Currently the title text is "City1 - Travel guides at Wikivoyage". Would it make any difference to change it to "City1 travel guide ..."? How should we handle phrasebooks, itineraries and travel topics if we make that change? Pashley (talk) 11:40, 23 October 2013 (UTC)Reply
It seems to me that the competition for the top-searched destinations is fierce - there are thousands and thousands articles, guides, webpages et al. about Paris or New York. Our forte seems to be that we also do cover Menzies, Hilversum and thousands of other less popular destinations, some of them really well. Some day Wikivoyage will be the default search result for all travel-related searched, much as Wikipedia is for almost everything, but until then what can win us viewership and recognition is catering to travellers who really can't find much info elsewhere - and their searches will probably also be ones we have much less competition for, plus it will be easier to be formally (i.e. via an actual hyperlink) referred to by other sites, blogs et alia. PrinceGloria (talk) 13:16, 23 October 2013 (UTC)Reply
I suppose it depends where in New York... filling some gaping holes in places like Oswego, Ogdensburg and Massena may get us traffic with less competition than if we were vying for the top spot in search results for New York City - which many sites already cover well. K7L (talk) 14:52, 23 October 2013 (UTC)Reply
If there are people interested in working on top search cities like Paris, New York, Tokyo (which really could use it!), etc. then by all means plunge forward! To me, it's more difficult to start with pages that are already good. For example, Chicago was a star long ago, so it would take a lot of thought to change the guide enough to make it show up on top of searches. On the other hand, cities that are a mess and have a lot of room for improvement, like Tokyo, Sao Paulo, etc. and pages that have little or no content would be much easier and probably more fruitful to focus on. Anywhere in Africa would give us a strong and quick boost I imagine, as well, since our coverage continent-wide is rather weak. ChubbyWimbus (talk) 01:51, 24 October 2013 (UTC)Reply
By the way, there's a list of most visited articles here sumone10154(talk) 03:45, 29 October 2013 (UTC)Reply
Nice. Looks like our top five cities are London, Paris, L.A., Singapore, and ... Sedona?! LtPowers (talk) 21:51, 30 October 2013 (UTC)Reply
It looks like that statistics page stopped being updated in April. Texugo (talk) 22:01, 30 October 2013 (UTC)Reply

What is more relevant is our atrocious search engine rankings.

If you go to https://startpage.com
(which features results from Google, but anonymised so that the results are not skewed by personalisation, browsing history, geographical location, etc)
and key in a typical search term for any of these "top destinations" (such as "guide london" or "guide paris" or "guide L.A." or "guide singapore" or "guide sedona"),
in every case you will find our "parent" site Wikitravel listed above us.
In most cases we do not even appear on the first page of results!

Why oh why are none of the movers and shakers interested in adopting the action plan proposed here?

Is it because, in a very few weeks, they would then have to cope with a flood of spambots or is it because some name-callers would then have to eat humble pie? Surely this scandal is going to cause some waves with the WMF if their investment remains so obstinately obscure? --118.93.47.31 23:09, 30 October 2013 (UTC)Reply

1) Frank, please log in when you edit. Using an IP makes it look like you're hiding something.
2) You continue to unfairly impugn the motives of large segments of the editing community. This will stop immediately. LtPowers (talk) 00:09, 31 October 2013 (UTC)Reply
Please let's not have a discussion about identities here in the pub. User talk:118.93.47.31 is a better place for it, even if disregarding that 118.93.47.31 is now blocked for one day and cannot respond from that IP in the pub. thanks. Nurg (talk) 00:38, 31 October 2013 (UTC)Reply

I have tried this on one article and while it worked briefly it than stopped working. If we can get this to work for a long established article and work for a significant period of time you will have my complete support to institute it all across WV. Travel Doc James (talk · contribs · email) 09:04, 2 November 2013 (UTC)Reply

Changing prose to bulleted listings

Are edits like this considered appropriate style currently? I may be a little behind in my understanding. But I don't think it's a good idea to be converting perfectly serviceable prose into an awkwardly formatted listing (look at the "directions" field) just to be able to say we have coordinates. LtPowers (talk) 16:50, 23 October 2013 (UTC)Reply

The good part of the change is that it creates a map coordinate. Is it easy to create that without using a listing template? Ikan Kekek (talk) 01:01, 24 October 2013 (UTC)Reply
I still believe we need an alternate, simpler template for inserting only a POI coordinate in prose passages. Texugo (talk) 01:25, 24 October 2013 (UTC)Reply
That would be very good to have. Ikan Kekek (talk) 01:47, 24 October 2013 (UTC)Reply
Yes, that would be indeed very useful. --Danapit (talk) 07:01, 24 October 2013 (UTC)Reply
I thought Template: Poi already did that? Guess I am missing something? - Matroc (talk) 17:41, 24 October 2013 (UTC)Reply
Oh, I have overlooked that one. Template:Poi is marked as experimental though, so not sure if it is ready to be used widely. I see you can select the POI number manually. Maybe it is a silly question, but doesn't it collide with the automatic numbering using listings? --Danapit (talk) 07:28, 25 October 2013 (UTC)Reply
Template:Poi is not compatible with automatic numbering. We can make a new template: {{Marker | type=(see/do/...) | name=(only for map marker) | lat= | long= | image= }}. But User:Torty3 would implement the automatic numbering if possible (@Torty3: listing|marker ?). -- Joachim Mey2008 (talk) 09:24, 25 October 2013 (UTC)Reply
Sure, if people want it enough. I was thinking about inline listings, but did decide that was too complicated in the end and forgot about it amongst the wiki drama and my list of squishy bugs to squish and features to make. -- torty3 (talk) 04:39, 26 October 2013 (UTC)Reply
torty3, I am sure that would be a very useful feature indeed if you find time to work on adding it. --Danapit (talk) 12:05, 1 November 2013 (UTC)Reply

District Template and Section Question

Does the structure of this article does conform to Sections and Template guidelines; Specifically the See subsections:

  • Landmarks
  • Museums
  • Churches and cathedrals
  • Institutions of learning
  • Monuments

If it does, I'll use it for some other district articles.

Also, why does the TOC not appear in this article?
--TheMightyHercules (talk) 23:48, 27 October 2013 (UTC)Reply

I guess sections are OK if the destination really has many things to see. TOC is visible as a single line within the banner at the top. Nicolas1981 (talk) 03:03, 28 October 2013 (UTC)Reply
Sections are definitely OK when there's a lot to see. How many and which ones you want depends on the kind of sights there are in the district. Check out some of our star district articles, like San_Francisco/Chinatown-North_Beach#See, Paris/1st_arrondissement#See or Chicago/Bronzeville#See. I actually think institutions of learning should only be listed under see when their buildings have architectural or other "passive attraction" value. Otherwise, they should probably go in a separate "Learn" section after "Do". JuliasTravels (talk) 17:21, 28 October 2013 (UTC)Reply
Just as a tiny sidenote, I believe that "learn" fits more in the city-level articles than district-level ones. People generally choose to settle in a city for a longer time to learn, not in a particular district, as oftentimes travelling from one district of a city to another for instruction is not impossible. PrinceGloria (talk) 19:54, 28 October 2013 (UTC)Reply
We don't generally list things that require one to "settle" to do. Most Learn listings should be for things like a one-day cooking class or a week-long language course. No reason those should be featured on the main city page. Texugo (talk) 19:57, 28 October 2013 (UTC)Reply
Well, for now those sections are filled with advice on long-term learning, universities and such, so I thought this is how they are meant to be used. The short-term learning options would be much more limited in choice, I presume, and I do not believe this is tied to a particular location within a city - you usually need to commit a few hours in a row, if not a full day, or a few hours over consecutive days or weeks to learn anything. This means that this advice should not be grouped with tourist attractions, which generally work around the principle of "while you're there, why don't you also see this/do this/eat there". Participating in a learning experience requires a different level of planning and it in turn would rarely be tied to a particular district one would discover, but rather a city one plans to spend a longer time in. PrinceGloria (talk) 22:01, 28 October 2013 (UTC)Reply
That is no stronger an argument for putting them on the main article than it would be for putting hotels there. Things are featured/summarized on the main page because of their importance to the overall experience of the city, not because of the overall city experience's importance to them individually. Texugo (talk) 22:18, 28 October 2013 (UTC)Reply
Going back a little bit, I don't completely agree with what Texugo said upthread. While travellers might not have much need to know how to enroll in long-term classes in a city they're visiting for only a brief period, I find that providing brief bits of general information about area colleges and universities is a good way to give readers a better idea of the overall identity or "feel" of a city. This is especially true, I think, for district articles of Huge Cities—even more so when the district in question contains a large university that's a major component of its distinct identity, e.g. Buffalo/Elmwood Village. This information probably should not be in the form of listings, however. -- AndreCarrotflower (talk) 22:50, 28 October 2013 (UTC)Reply
I was not so much giving a personal opinion as a reflection of the traditional advice on the subject. While I agree with you that in some cases, a brief mention of local universities might have cultural relevance, I think those are the exceptions to the general rule - describing the community colleges of the typical small-to-medium size town is largely irrelevant and unneeded. In any case, they should not be See listings unless there is something actually worthwhile to see on campus, and should not be Learn listings unless they actually do offer something short-term that is available and might be interesting for a traveller. A brief prose description in the Understand section (or, more likely, a mention in relation to college nightlife areas) is fine, if it is truly relevant to the identity of the city. Random info about Cumbersome County Community College or Bumpkin River Technical School should be broadly discouraged. Texugo (talk) 00:13, 29 October 2013 (UTC)Reply
I agree completely with Texugo. Unfortunately, we've let articles go (and even feature/star them) with excessive information in their Learn sections, which causes the error to proliferate. We should probably be making that a point of emphasis in nomination discussions going forward. LtPowers (talk) 01:05, 29 October 2013 (UTC)Reply
Even if we don't put it in the "Learn" section, I maintain that this information can and should be included somewhere. Again, it may not serve the traveller to know how to enroll in semester-long university classes in a city s/he won't be located in for nearly that long, but it certainly does serve the traveller to better acquaint him/herself with the identity of the place s/he chose to visit. -- AndreCarrotflower (talk) 02:17, 29 October 2013 (UTC)Reply
I agree with Andre's point, and I'd also say that in the case of college towns like Clinton (New York), it would be ridiculous not to give a link to the local college's website, because even if the college had no architectural significance and didn't host cultural events that might interest people not studying or employed by the college, it's pretty much the only game in town. Ikan Kekek (talk) 04:30, 29 October 2013 (UTC)Reply

[indent reset] I agree with most of what's been said above. I firmly believe the info on the town's character as an university town should go into "understand" rather than a separate section, plus a mention of a "seeable" / "visitable" establishment of an educational institution should go into either "see" or "do", depending on the character of the institution.
I find it an unusual case when there is anything to "learn" that is not simply a "do" and merits a separate section, and I would still maintain most of it will be better dealth with on the city level of larger cities, much as it will be better to list embassies, hospitals or airports on the city level than confine them to district and deprive the city level of that information. Which does not mean that individual district articles should not contain mentions of such in their "understand" or "orientation" sections if the placement of the city-unique services/institutions within those districts affects their characters or orientation within them. PrinceGloria (talk) 05:45, 29 October 2013 (UTC)Reply

In really huge cities, I think that while examples of institutions of learning are worth briefly mentioning, actual entries for them normally belong in district articles. For example, there are a lot of concerts and lectures at the New School University, and those should be listed with a link to the New School's Events Calendar in the Manhattan/West Village article (I'm not sure if they are), not the Manhattan article. Ikan Kekek (talk) 06:06, 29 October 2013 (UTC)Reply
This look an awful lot like a "Do" to me. We don't have separate category for "Sports", so why would we need a separate category for "doing" things in educational institutions. Those are all "do". If there is a lot of things to "do" in a districts, we're doing pretty well with third-level headings. PrinceGloria (talk) 09:47, 29 October 2013 (UTC)Reply
You may well be right. I guess the only issue I have is whether it's worth whatever extra work it would make to eliminate all the "Learn" subtitles and move most of the entries to "Do," plus some to "See." Ikan Kekek (talk) 09:51, 29 October 2013 (UTC)Reply
Let's just refrain from putting any more "Learn" sections to newly-created and expanded articles, and we can deal with the extant one as we go, on a case-by-case basis. There's a lot of cleanup to do and quite a few of us are actually doing this as we speak, as long as we agree to do this that way (and not add to the problem by creating new "Learn" sections) it will be dealt with in due course. PrinceGloria (talk) 10:15, 29 October 2013 (UTC)Reply
I haven't checked, but there may be some article templates showing an optional "Learn" subtitle that would need to be deleted if there is a consensus behind that. Also, Where you can stick it may need to be checked. Ikan Kekek (talk) 10:27, 29 October 2013 (UTC)Reply
I am very happy to stop using 'Learn' sections. I find that people often want to list universities which isn't actually relevant traveler information. (Unless the university is worth visiting, such as Heidelberg, but then it should be listed under 'see') I think specific courses (cooking, language learning etc) are still good things to have however. Andrewssi2 (talk) 10:30, 29 October 2013 (UTC)Reply
It is true that the purpose of the Learn section is often misunderstood not only as a place to list universities, colleges and even public schools, but also as a section to list random trivia the reader might want to know or even resources for "learning more" about the destination. Not quite sure how I feel about all the work it would take to deprecate it though. Texugo (talk) 11:58, 29 October 2013 (UTC)Reply
Even where a course of study is a few weeks (like Chicoutimi-Jonquière, the Collège du Jonquière is well-known to Ottawa swivel servants for a three-week intensive French as a second language programme with no students from the local area) the brief mention of the school in "understand" with the rest of the industrial history of the town (pulp/paper, aluminium) is enough. A "learn" section would add little.
Yes, a school could legitimately end up dominating an article if a huge university is in an otherwise small town. An article on "State College PA" would be incomplete without turning Paterno's statue 180 degrees "so that he can look away and turn a blind eye to the Sandusky affair" if that school and team are the town's most notable landmarks. Nonetheless, info like "Normal IL was named for a 'normal school' or state teacher's college" belongs in "Understand" and the campus itself (if architecturally notable or home to museums or concert halls) likely is "See" (with any specific activities there "Do"). We don't need "Learn" as another section as the school is described as seen by travellers, not temporary four-year resident students. K7L (talk) 14:50, 29 October 2013 (UTC)Reply
It's not only universities though. One question is whether we want to stick an open university lecture series, a cooking school, a wine and cheese pairing class, a local crafts workshop, and 5 Spanish conversation schools together in a single subsection of Do. Texugo (talk) 15:00, 29 October 2013 (UTC)Reply
I'm of the opinion that there isn't much practical distinction between 'learn' and 'do'. I'm thinking 'Learn' should become deprecated in that it remains valid for existing articles and for new articles where there exist a lot of learning opportunities (as in your list). However it should not actually be required for new articles, or for old articles that people wish to refresh without it. Would such an approach be too vague for WV? Andrewssi2 (talk) 15:27, 29 October 2013 (UTC)Reply
Personally, if the article template is to be changed in such a manner, I would really rather not just do it halfway. And actually, I think the Do section is already often overburdened with subsections (Parks, Theater, Music, Sports, Festivals, Events, Beaches, Hiking trails, organized tours, boating excursions, train rides, etc., etc.). I think taking a course in something is a different enough type of activity that we can leave it alone. Just because it is technically doing something doesn't mean it has to go in Do. After all, drinking, clubbing, doing laundry, and using the internet are also "activities" but we don't need to put everything in Do. Texugo (talk) 16:18, 29 October 2013 (UTC)Reply

Oops...

The pagebanner for Syracuse (New York) defaults to the image for the city of the same name in Sicily. How does one go about changing that? -- AndreCarrotflower (talk) 20:01, 29 October 2013 (UTC)Reply

Fixed. Someone added the Italian banner to the wrong wikidata item. Now that I removed it, it has no default. Texugo (talk) 20:05, 29 October 2013 (UTC)Reply
That banner was added because it's on fr:Syracuse, which was incorrectly associated with the English and Dutch articles on the New York city, presumably even before the interwiki links were migrated to Wikidata. The correct solution is to move the banner image definition, and the French Wikivoyage link, to the correct Wikidata item. (As it turns out, that banner is already on the Syracuse, Sicily Wikidata item, but keep it mind for future reference. And the French article link still needed to be moved, which I've done.) LtPowers (talk) 21:55, 30 October 2013 (UTC)Reply

Click on a POI to open in your favorite Android navigation/GPS app

OxygenGuide (offline version of Wikivoyage, usable on smartphones) now embeds coordinates: Click on the "(map)" symbol of a POI, and your favorite navigation app (such as OsmAnd) will guide you to that point!

If users like it and a solution is found for iOS, it might make sense to implement the same feature on the live Wikivoyage?

Coordinates are getting more useful everyday! If you have 10 minutes, pick a random article and fill all latitudes/longitudes :-)

Cheers! Nicolas1981 (talk) 07:30, 30 October 2013 (UTC)Reply

Exciting stuff! Can it really be "27000 destinations, only 86 Megabytes" !?? --118.93.47.31 09:14, 30 October 2013 (UTC)Reply
Actually 25706 destinations in 92MB (473MB unzipped), updated :-) Nicolas1981 (talk) 09:37, 31 October 2013 (UTC)Reply
If the idea is to update every listing, could some of this be done by a 'bot? K7L (talk) 17:46, 30 October 2013 (UTC)Reply
Finding latitude/longitude usually requires looking at the map on the hotel's website, checking on Google Street View, Wikimapia or OpenStreetMap... everyone has their own methods, but I would say it is difficult to execute by bot. In particular, I think that using an address geolocalization service is not reliable enough. (maybe reliable enough for some countries, but not for the whole world). Nicolas1981 (talk) 09:37, 31 October 2013 (UTC)Reply

Are we doing something big to boost our readership / editorship / search engine rankings?

I see there is a multitude of discussions everywhere - here, at Expedition talk pages and elsewhere, and I believe a majority of them are not just W.Frank's ASBO parades. I have a limited amount of time for WV, and I am just a humble editor, so I admit it is beyond me to follow all of them and make sense of their tangents.

I am seeing our Alexa positioning and editor count essentially flatlining (ok, let's call it "levelling"), so I was wondering if I should treat it as a sign of our dismay at a lack of solution to move WV from where it is to where it belongs (i.e. as the no. 1 go-to site for travel guide information), or just a calm before a storm which will elevate WV one level ahead again, thanks to an ingenious solution that is brewing or just small concerted efforts of whose combined significance we are unaware?

So, what is the scoop? What plan do the WV boffins have? Thanks for letting us casual editors know! PrinceGloria (talk) 06:06, 31 October 2013 (UTC)Reply

I'm not aware of anything that isn't already on Wikivoyage:Search Expedition, but there may be actions underway at WMF or by others (see Bugzilla: 52688). There have been a number of proposals made for improvement, but most of the low-hanging fruit (links from WP, getting the word "travel" on pages, in titles, and in incoming links) has already been taken care of. The value of some of the remaining proposals aren't entirely clear - changing headings would signal to Google that one of the most important page structures has changed, but it isn't clear how much effect that will have on rankings and would require agreement on new headings, which is contentious. Removing or modifying the WT footers is something everyone wants to do, but given past history that isn't something that seems plausible without a legal OK. Changing URLs from "city" to "city, state" has been suggested, but that's another big change whose value isn't clear. Given the magnitude of those changes, unless one or more individuals take on the task of providing some measurable way of determining their value it may be tough to push them through - I don't think anyone wants to go to the effort of finding consensus for new headers, changing every article on the site, and then fail to see any SEO benefit.
In lieu of all of the above changes, one thing that will clearly help us is continued evolution over time. Having pages that have been in Google's index for a longer time helps, having more incoming links help, and getting additional contributions that make our articles different from WT will help. If any further proposals are made that can be implemented without major site changes then those would probably be implemented immediately, but at least for the moment my impression is that we're mostly just working on an article-by-article basis to try to make sure our content evolves and is distinct from WT, thus signalling to Google that this site isn't just a clone. -- Ryan (talk) 07:04, 31 October 2013 (UTC)Reply
Thanks for the roundup, so I am right in believing we are not actually DOING anything at the moment, we now have many proposals and are unsure if they will work and if anybody has the willingness to put the effort in those. Did anybody try to do a reasonably convincing test on any of those - even including stuff mentioned in your second paragraph (they all probably do work with Google, but how effective are they vs. other stuff)? Is anybody in charge with getting the OK from legal to stop linking to WT? PrinceGloria (talk) 07:08, 31 October 2013 (UTC)Reply
WMF Legal stated that they can't provide advice on the footer issue: meta:Wikivoyage/Lounge#Google PageRank issues. You would need to read through Wikivoyage talk:Search Expedition for updates on your other questions. -- Ryan (talk) 07:14, 31 October 2013 (UTC)Reply
Hi PrinceGloria, I think it is great to want to make actions to improve the rankings of WV however my observation is that this is task is not straightforward and actually discussion is causing friction within the WV community. My view is that as 'casual editors' we can make a real difference for now by just improving content, and even by creating new articles that have no links back to WT. It is frustrating to wait, however I believe that by playing the 'long game' the site will eventually solve its ranking issues. Andrewssi2 (talk) 07:42, 31 October 2013 (UTC)Reply
In other words, forget it. If we want to change the footer, we do so at our own legal risk, which no one wants to take. If we want to make major changes to section headings, we need consensus, at the exact time when our lack of ability to form consensus anymore is frustrating longtime editors off the project. The best way to effect change is to continue to evolve the site, yet the process of evolution is glacially slow and getting slower as editors leave. -- AndreCarrotflower (talk) 07:46, 31 October 2013 (UTC)Reply
It's only "causing friction" because some admins are too thin-skinned and precious. All that counts is what works - not who is for it or agin it. Frank's told you exactly and precisely what needs to be done and more fool you if you don't suck it and see. As other IP's have said (and been censored for saying it) Wikivoyage has nothing to lose collectively and everything to gain. If it doesn't work within a matter of weeks, all you have to do is go back to your old "dead museum curator" mentality when it comes to the sacred lead format and sub-section titles.
Don't be so defeatist, AndreCarrotflower. The resultant ten=fold boost to our readership will boost our editor ranks too - and don't forget that some of the players that "took their ball off the pitch" have already returned with brand, shiny new accounts. What does " W.Frank's ASBO parades" mean, PrinceGloria? Would you translate, please? --203.173.196.38 07:57, 31 October 2013 (UTC)Reply
I plan on writing an essay about my thoughts regarding the future of Wikivoyage... whenever I find the time, things have been crazy the last few weeks :/ In the meantime, I'm still around, just keeping quiet :)
I am kind of disappointed by WMF Legal's response (among other things) but oh well, we gotta make the best of what we have. --Rschen7754 08:07, 31 October 2013 (UTC)Reply
Yes, the legal conversation has to be directed towards the lawyers and discussing it here between ourselves will only cause unnecessary grief. Keeping the WT link was the cost of forking the project, and only the layers have the means to correct that, if they can. Andrewssi2 (talk) 08:33, 31 October 2013 (UTC)Reply
As a total sidenote, can we pause for a brief moment and consider banning edits by unregistered users altogether since we seem to have so few editors anyway? It is a unique feature of MediaWiki projects among all other "social" and "crowdsourced" media around. I'll get round to formally suggesting that sometime later, just some food for thought now. PrinceGloria (talk) 08:19, 31 October 2013 (UTC)Reply
I myself was an unregistered editor for 2 years or more. Many good edits are made by unregistered users. If you're suggesting we should require people to register before they edit, I'd suggest that's exactly the wrong thing to do if we want to be user-friendly and welcome more editors. Ikan Kekek (talk) 08:29, 31 October 2013 (UTC)Reply
The WMF would never allow that; they've rejected lesser measures on other wikis before. --Rschen7754 08:35, 31 October 2013 (UTC)Reply
And rightly so. What would the slogan be then? "The travel guide that anyone can edit...once you've registered, been fingerprinted, and had a blood sample taken"? :-) Ikan Kekek (talk) 08:47, 31 October 2013 (UTC)Reply
For the record: while I think it goes without saying that Frank is the author of the IP edits in question, which is troublesome given the accusations of sockpuppetry that have dogged him since as far back as I remember, that doesn't negate the fact that the proposals he has put forth are interesting and, I think, worthy of far, far more consideration than has been given to them thus far. -- AndreCarrotflower (talk) 08:37, 31 October 2013 (UTC)Reply
I have always respected Frank's proposals. My only objection to Frank, ever, has been his sometimes off-putting delivery. Ikan Kekek (talk) 08:47, 31 October 2013 (UTC)Reply

[Back on topic] We sure should all do our best and focus on the core of Wikivoyage, i.e. editing, improving, expanding and creating articles. And I am quite sure everybody does, as much as time allows. We are really changing this place around massively, it looks nothing like the garbage dump we inherited from "big brother" not so long ago.
HAVING SAID WHICH, I believe we need to push forward harder. I believe we need to be proactive and, being a relatively small and cohesive group of editors still, act in unison. I do not consider what was linked to above as a formal answer from WMF's legal team, and I will pursue one in clear writing, preferably with a stamp, signature and on company paper. This is a WMF site, and we need help from WMF. This way or another. And we need clear answers. I urge you to continue pursuing those regarding the active hyperlinks to Wikitravel for until a solution is found or the inability to do anything about them is made clear to us in a way that leaves no other options. I believe we are far from that.
I also believe we could make a list of proposed "search engine optimization" actions and start formalized experiments e.g. on a test group of 10 articles each, over a predetermined time and under predetermined circumstances. If we need some tech help from WMF to better frame those tests and their circumstances, let's ask for it. If we believe we can do that ourselves, let us just start a subpage at the Search Expedition, list and schedule the tests and put timely updates on results there.
Any other actions, apart from just editing the articles, trying to remove WT links and "search engine optimization" that have been suggested and I missed? PrinceGloria (talk) 08:19, 31 October 2013 (UTC)Reply

make a list of proposed "search engine optimization" actions and start formalized experiments
Yes, this is what we should do. I don't think anyone has a problem with testing the proposed changes individually to find out what works. All I had a problem with was the assertion that all the proposed changes should be implemented immediately without testing the individual effectiveness of each. Texugo (talk) 10:11, 31 October 2013 (UTC)Reply
Yes, a more systematic approach is much needed, one new article with no pre-fork counterpart and absolutely no duplicate content is not representative of 99% of all articles, and this is not even considering the raft of variables involved. Anyone and I really mean anyone with the time and inclination, could step up to help organise it. It isn't in an admin's remit alone (what I realised with the dynamic maps, for better or worse). I'd like to see less stark lines drawn.
One important thing is that Hazard-bot at WP still has not added links to some pages, I'm not sure whether it's because of the placement of templates? Otherwise, Wikidata has superseded the need to compare data dumps, and someone could go through the articles with AWB like how Texugo did.
Another angle to pursue more aggressively is social media like Twitter, Google+ and Reddit. Places like Manchester still have WT links in their sidebar, and some Reddit sub-communities have gladly changed them over to WV - they just like Wikipedia a lot. This comes pretty close to stealth marketing though.
For good news, regardless of all the over-obsession with WT, did you know that the number of very active contributors have been higher than any point of history? Pages views have also been growing 20% a month. -- torty3 (talk) 10:54, 31 October 2013 (UTC)Reply
Thanks torty3. This was a point bothering me today during this conversation which was although WV obviously has problems in many areas (social, technical, whatever), the community has actually created a far superior 'product' to WT in a very short period of time. 20% page view growth is great, and even if resolving some issues is moving at a snail's pace we are still nevertheless going to get there. Andrewssi2 (talk) 11:15, 31 October 2013 (UTC)Reply
Thanks for your thoughts torty3 and Andrewssi2!
  • I've just contacted the mods of that Reddit page to ask if they'd be prepared to change the link.
  • Two weeks ago, I changed (just) the headings in our Wigan article to see what effect that would have on its own. From what I can discern, it hasn't had a great SEO impact as yet, but I suppose that could change.
  • Twitter followers have been rising rapidly of late and, as I haven't had quite as much time as I used to, I've shared the credentials with the WMF's social media team who are also posting on our behalf. It would, however, be good to push social media as a whole a bit harder.
It's great to read that things are improving - I hope that by the time the site's 1st WMF birthday comes, we'll have pushed our way to the top (or near the top) of the pack. --Nick talk 14:06, 31 October 2013 (UTC)Reply
If you don't mind, when you do tests like that at Wigan, please formalize them somewhere at the Search Expedition so people know what's going on. Texugo (talk) 14:10, 31 October 2013 (UTC)Reply
I did mention it at the time in Wikivoyage:Travellers'_pub#Boost_our_readership_by_at_least_400.25_in_two_months, but I'm not sure anyone noticed. I'll post about it in the Search Expedition now. --Nick talk 14:16, 31 October 2013 (UTC)Reply
Yeah, we actually need to go through all the discussions so far and consolidate everything to make a table to track all the experiments with the titles, dates, and what was changed. Texugo (talk) 14:23, 31 October 2013 (UTC)Reply

(indent) Having an attractive homepage would certainly help, too. Right now we still have the white captions that are mostly unreadable on the pictures. Having a sloppy-looking homepage is not doing us any favors, especially since the possibility of having a front page feature is supposed to be a way to encourage users to improve articles. Right now, the incentive is rather low in my opinion, because the features are not presented well. I've lost track of the discussions (if any are still occurring) because I myself can't do that sort of thing, but I have to admit that for me, the current front page actually makes me NOT want to make a page featurable. If I work hard enough to get an article up to standard, I wouldn't want it featured as an image with illegible writing over it. ChubbyWimbus (talk) 16:07, 31 October 2013 (UTC)Reply

I don't have as much trouble with the homepage as you do, but it does sound like both of us would like for there to be the option of black text in the captions on the images for the featured articles. How hard is that to do? It doesn't seem like it should be hard. Ikan Kekek (talk) 17:44, 31 October 2013 (UTC)Reply
This seems like a thread that could easily go in a lot of directions and become hard to follow, so would it be OK to move discussions about the main page to Talk:Main Page? In particular, Talk:Main Page#Main page readability is a discussion I started a long time ago but haven't had time to follow-up on. -- Ryan (talk) 17:56, 31 October 2013 (UTC)Reply

Manchester on Reddit now links to the WV article in its sidebar - yay! As for the Main Page, I'm sure it would be easy to add a black text option, although Mark would know more about that. --Nick talk 00:23, 1 November 2013 (UTC)Reply

Well done Nick! I believe that such tireless inbound-linking, allied with content improvement, is the most efficient way to improve rankings. This can be done by anyone at the local level. Share links about a recent trip on Twitter, blog about a place you've been, embed links, add POIs :-) Nicolas1981 (talk) 06:55, 1 November 2013 (UTC)Reply

Map of all destinations in a country, with labels

I am going on a trip without much preparation, and what I really feel the need for is a map that shows all destinations of the country, so that I can see where the interesting stuff is.

The nearest thing I have is this: http://www.cheriot.com

Because most of the time I won't be connected to the Internet, I took screenshots of the map, but the fact that you have to click on a icon to make its name appear makes the images less useful. Is there a website/mashup where destination names are visible as labels? The rendition algorithm for optimal label display (or non-display in crowded areas) is tricky to develop, but it would be very useful, and may be used as a switch on POI maps too.

Cheers! Nicolas1981 (talk) 12:15, 31 October 2013 (UTC)Reply

That site does not load for me. Texugo (talk) 13:04, 31 October 2013 (UTC)Reply
Quite slow but works for me here... maybe because I am logged in already? Nicolas1981 (talk) 06:44, 1 November 2013 (UTC)Reply

GPS tracks

I am thinking of getting the Suunto Ambit2. Wondering if people know if the GPS tracks it collects can be placed on maps from Open Street Maps to show were hiking trails etc are? Travel Doc James (talk · contribs · email) 15:23, 31 October 2013 (UTC)Reply

Yes, tracks (transformed into roads or paths) are very welcome on OpenStreetMap! Depending on where you live, there can still be a lot of work to do, even for relatively big streets. Nicolas1981 (talk) 06:42, 1 November 2013 (UTC)Reply
More interested in mountain bike trails / hiking trails. Will see what I can do. Travel Doc James (talk · contribs · email) 08:53, 2 November 2013 (UTC)Reply

Proposal for a Maintenance panel

OK, so I've been spending some of my time trying to make a super one-stop maintenance panel that organizes every possible maintenance-related tool, statistic, link, and graphic into one page in a hopefully user-friendly arrangement with mouseover explanations for everything. So far it includes:

  • Links to maintenance-related WV pages
  • Links to external pages and tools
  • Links to maintenance-related Special pages
  • Links and numbers for maintenance categories, with annotated links to the respective templates
  • Statistics and bar graphs for standard templates with links to pre-filled catscan searches to find what's missing
  • A revamped version of the type vs. status matrix, with annotated links to the respective templates and bar graphs
  • Summary of non-zero statistics from Special:Statistics
  • Special links for administrators
  • User-related links

I can't really think of anything else that's missing. Is there anything to add? My hope is to move this into the WV namespace, redirect WV:Article status stats and WV:Cleanup status stats there, and hopefully put a link to it in the sidebar under tools. I´ve been using something like this daily on pt: for months and find it very useful for spotting problems/things to do. I hope others find it useful as well. What I've got so far is here. Please play around with it some and give me your comments/suggestions. Thanks! Texugo (talk) 18:53, 31 October 2013 (UTC)Reply

Thanks for the effort Texugo! I am testing it and like it a lot. --Danapit (talk) 09:07, 1 November 2013 (UTC)Reply
Very handy indeed! I'm probably a bad judge, but I can't think of anything to add either :-) Thanks, Texugo. JuliasTravels (talk) 12:19, 1 November 2013 (UTC)Reply

Collaboration with Kiwix

Kiwix is getting interested in Wikivoyage: http://www.kiwix.org/wiki/Wikivoyage

Kiwix is a powerful app for offline wikis. The whole Wikivoyage WITH images takes 1GB, the app reads directly from the compressed ZIM file. It supports search (which is not supported by OxygenGuide-Android). Kiwix runs

Kiwix runs on Android/Windows/Mac/Linux. Open source. Any volunteers? Nicolas1981 (talk) 07:36, 1 November 2013 (UTC)Reply

Looks interesting, although seems mostly targeted at Android phones? Additionally the todo tasks are for Android developers? (which is cool and everything, but not something every developer can easily contribute to) Such an app would be awesome on an iPod Touch actually :) Andrewssi2 (talk) 11:41, 1 November 2013 (UTC) Andrewssi2 (talk) 11:41, 1 November 2013 (UTC)Reply
IMHO, it would be awesome if this app was Android only, to have people finally ditch those c**ppy iPods for Android devices :D PrinceGloria (talk) 06:05, 2 November 2013 (UTC)Reply
Would be great. Search is super nice. Travel Doc James (talk · contribs · email) 08:51, 2 November 2013 (UTC)Reply

Very poor coverage of listings for LGBT bars/clubs

I've started to realize the coverage for LGBT bars and clubs on WV is terrible. Even places that are specifically called out as being major gay destinations often have few or no LGBT listings.

Examples of important articles with poor listings of LGBT bars/clubs:

There's not some policy I haven't noticed that prevents us from listing places specifically as (or specifically because they are) LGBT-targeted, right? I know several print guidebooks I have list quite a few of them. --Bigpeteb (talk) 20:35, 1 November 2013 (UTC)Reply

Wikivoyage:Information for LGBT travelers is the only relevant guideline on the subject that I'm aware of. By all means, add listings for LGBT bars and clubs - the only concern that has been raised in the past was that information applicable to LGBT travelers should usually be integrated into the rest of the guide, rather than called out in separate sections, for reasons outlined in that policy page. -- Ryan (talk) 21:11, 1 November 2013 (UTC)Reply
Wikivoyage:LGBT Expedition probably merits a mention too; though it's been stuck in neutral since January, perhaps you might be able to spark interest in it anew. -- AndreCarrotflower (talk) 22:27, 1 November 2013 (UTC)Reply

Help pages clean up

I've been trying to clean up the formatting on the Irish pages for a while now. The biggest problem I have is following the manual of style pages. I find them hard to remember, scan and long-winded. Therefore I've tried to come up with my own version of the time and date format page that I think is easier to use.

Some things I've tried to improve:

  • Large bold examples. This is to make it easier to scan the page quickly. You should be able to tell how to do most formatting from the examples alone, without having to read the text.
  • Correct examples only. I've only ever used correct examples. If you see an example on the page, you know you can use it. This also helps keep the page shorter.
  • Short. I've tried to keep the page and notes as short as possible. It shouldn't need a "This page in a nutshell" box at the top. I also got rid of the introductory paragraph at the top which doesn't actually say anything.
  • Consistent formatting. I've tried to make the page as consistent as possible. For instance, all the examples are always shown on the left, instead of a random position in a sentence. This should help people quickly scan the examples to find the one they are looking for.

The new version is at Wikivoyage:Time and date formats/New version.

46.7.249.24 20:47, 2 November 2013 (UTC)Reply

Personally I don't like the large font. I haven't considered the rest - the font size is too overpowering. If you are willing to try normal size I would take another look. Otherwise I would not see it replacing the existing page - although you could keep it for use by yourself and others who like it as an alternative. Good on you for trying an improvement though. Nurg (talk) 00:01, 3 November 2013 (UTC)Reply
I do prefer this page, in terms of its conciseness and cleanliness, especially with the consistent formatting to see examples on the left and further explanation on the right. The bad examples are always confusing. What do others think? -- torty3 (talk) 00:09, 3 November 2013 (UTC)Reply
I think it would helpful to have some form of cheatsheet if people find it useful. Would creating such a page at Wikivoyage:Cheatsheet/Time and date formats and Wikivoyage:Cheatsheet/Listings be ok? -- torty3 (talk) 23:39, 3 November 2013 (UTC)Reply
That sounds like a reasonable idea to me. My only two concerns would be: 1) keeping the number of these "cheatsheets" small so it doesn't create extra work to keep them in sync with the policy pages and 2) that these "cheatsheets" should be lists of examples taken from the main policy page or some other concise version of info already on the policy page, and not be used to create alternatives to established policy. -- Ryan (talk) 23:51, 3 November 2013 (UTC)Reply

Alice's proposal

Alice has e-mailed me to say she is not currently have a technical possibility to post this message without compromising her password (keyloggers in Internet cafes, etc), but asks that I do so on her behalf:
"I (and others) have noticed the good work you've been doing with our Irish articles in adding lots of useful information, kicking them into our special listings format and making the formatting consistent and readable - so a special thanks for that!
I also agree with your basic premise that we should try and make our MoS pages easier to understand and remember. In this regard, unless it compromises comprehension, I think it's best to
1) have as few exceptions as possible
2) start with the most general cases first
3) try to follow world-wide standards where they exist
4) in listings, abbreviate to the shortest possible form unless it compromises comprehension
5) Be consistent in temporal formatting. Most human brains find it easier if there are consistent rules. I think that we should list the larger periods of time first and then the steadily smaller durations. eg:
  • when combining days or months with time, put the years, seasons and months first, then days of the week and finally the times eg: Template:Xt rather than Template:!xt.
  • when listing alternative date ranges (for example, seasonal opening hours) separate the alternatives with a semi-colon eg: Template:Xt
  • for all seven days, use Template:Xt. Do not use "every day" or "Su-Sa". eg: Template:Xt
I like the way that you have dropped the unnecessary (and confusing for newbies non-breaking HTML) space between the amount and the unit.
Consequently, I would much prefer if we changed the phrase at Wikivoyage:Measurements#Avoid_orphaned_units of Template:!xt to:
Template:Xt
I also think that, in listings especially, we can shorten the current abbreviation for hour/hours of Template:!xt to Template:Xt so that we would see "N'Boli Airport is 42km (1.5h) drive since in some places you'll have to drive at less than 30km/h on the potholed roads".
Thanks for giving some thought to issues of style and formatting and for greatly improving our Irish articles! Alice".
--118.93.67.66 04:08, 3 November 2013 (UTC)Reply

WP Signpost

Anybody noticed this? --Saqib (talk) 21:20, 2 November 2013 (UTC)Reply

Many of us might remember that this user has quite a history of conflict with our community (here, here, here, and elsewhere). This is very clearly a hit piece, and the circumstances under which this article was written should be brought to the WMF's attention posthaste. -- AndreCarrotflower (talk) 21:43, 2 November 2013 (UTC)Reply
I would encourage all of you to leave comments, and present our side of the story. --Rschen7754 21:46, 2 November 2013 (UTC)Reply
Please, if you do comment on this story only point out factual issues and do not make this personal. A point worth mentioning is that the quote from Amsterdam was cherry-picked to remove context - it is three sentences in the signpost article, but six paragraphs in Amsterdam#Cannabis and other drugs. If comments on that article focus on factual issues that makes it clear that something is amiss, but dredging up the author's past history here is likely to just make everyone look bad and be counter-productive. -- Ryan (talk) 21:54, 2 November 2013 (UTC)Reply
Strongly disagree with Ryan. In point of fact, in one of the "here"s that I linked to above (I'm on my mobile phone now and don't really have the patience to scroll back and figure out which one), this user stated as a thinly veiled threat he was an editor for the Signpost and therefore we should not cross him. There's no way this article complies with the Signpost's standards of journalistic ethics. -- AndreCarrotflower (talk) 21:59, 2 November 2013 (UTC)Reply
The Signpost has long been known for attacking sister projects (such as Commons recently, and I believe Wikinews has been attacked in the past). I for one have no issues calling the conflict of interest what it is (though others may disagree), though the factual errors should definitely be mentioned. --Rschen7754 22:00, 2 November 2013 (UTC)Reply
It's a deliberately misleading article that uses photos acknowledged not to be on Wikivoyage in order to attack Wikivoyage. The fact that he's following through with a threat based on an unimportant argument about spelling that he was a jerk about, and due to that, finally induced to leave this project, is a useful context for readers. The links should be given, with people invited to make up their own minds. It's also hardly of no use to prospective travelers if a potential destination is indicated as primarily visited by sex tourists. That's factual information, and can be used by people wanting to avoid such an atmosphere just as easily as it can be used by sex tourists, who were more likely to know this already, in any case. Ikan Kekek (talk) 22:17, 2 November 2013 (UTC)Reply
(edit conflict) Rschen added a comment with a link to the user's block nomination here, which is hopefully sufficient to provide background on the personalities involved. I'm very concerned that people will respond to this article with attacks against the author rather than the author's message, which is absolutely the wrong thing to do and only makes Wikivoyage look bad - please, please, please be sure to respond civilly. -- Ryan (talk) 22:19, 2 November 2013 (UTC)Reply
Perhaps we should let the link to the nomination speak for itself, and not add any commentary about it then - that seems like a fair solution. --Rschen7754 22:22, 2 November 2013 (UTC)Reply
In my estimation, attacks against the author are 100% valid given the background and the context of the situation. We should remember that larger wikis like Wikipedia, which I imagine that the signpost draws most of the readers from, are far more used to problem users like Tony than we are at Wikivoyage. I don't think that being frank about what kind of a user Tony demonstrated himself to be will make us look bad. If it makes him look bad, hey – he has no one to blame but himself. -- AndreCarrotflower (talk) 22:40, 2 November 2013 (UTC)Reply
Whether they are valid or not, I strongly believe that "attacks against the author" will do more harm than good. That said, I don't want to give the impression that I'm trying to censor anyone from speaking their mind and will bow out of this discussion after one last comment - the article was published on Wikipedia, so please be aware that a core policy on that site is w:Wikipedia:Civility (in particular, no personal attacks) and just as we expect people who contribute here to respect our policies, contributions to Wikipedia should respect that site's policies. -- Ryan (talk) 23:04, 2 November 2013 (UTC)Reply
I acknowledge and appreciate your desire not to censor, Ryan. I think it's worthy of mention, though, that there's a difference between engaging in cheap ad hominems and addressing, in a frank way, problems that have as their root one particular person and their personality or behavior that is wholly unsuited for a collaborative project like Wikivoyage (or Wikipedia, or any wiki). And there's a way to call into question the motivations and good faith of a particular editor without being uncivil. I certainly would like us Wikivoyagers to conduct ourselves in a way that does our project proud, but let's not roll ourselves up into the fetal position either. -- AndreCarrotflower (talk) 03:08, 3 November 2013 (UTC)Reply
I haven't commented because I'm not sure I'd adopt the right tone, but points I might like to be made - and would like second (third, etc.) opinions on (or you can post them yourself, if you like) - are (1) Tony1 was not "censored"; he merely had the weird idea that if his proposals on spelling are not adopted, Wikivoyage will die. (2) He was suspended not for "criticism," but for being a dick (insert link to policy here), which all (or most?) Wikiprojects recognize as something not to be. (3) He never took action on any of the deviations with the sex tourism policy written about in this piece when he was here, when he could have edited them or at least brought them up as an issue if he had cared about them half as much as his concerns about spelling. Ikan Kekek (talk) 03:31, 3 November 2013 (UTC)Reply
On a side note, the reasons why Tony1 was blocked could have been better documented, so there wouldn't be as much debate from onlookers next time around. --Rschen7754 03:38, 3 November 2013 (UTC)Reply
It's not truly terrible publicity, therefore it's good publicity. We're wanting to attract more readers and editors, right? Let's try to leverage it for even more benefits - whether that's leveraging the publicity, or trying to get more traction with the problems we're struggling with, like search engines. Use social media to publicise the Signpost article. Contact the news media and con them into thinking there's a scandal at WV that they need to publicise. Better than demonstrating that we're a defensive bunch who object to mild commentary or criticism, and would prefer to be ignored. Nurg (talk) 03:52, 3 November 2013 (UTC)Reply
@Ikan: excellent points, especially your third one, which had flown completely over my head till you brought it up. -- AndreCarrotflower (talk) 03:57, 3 November 2013 (UTC)Reply
Nurg, that's really interesting outside-the-box thinking. If we publicize this, we both get more publicity and give the lie to the claim that we can't tolerate any criticism. That said, though, it's still a crap article. Ikan Kekek (talk) 04:03, 3 November 2013 (UTC)Reply
Yeah, I'm ashamed of it as an English Wikipedian. --Rschen7754 04:29, 3 November 2013 (UTC)Reply
Surely it would have been easier for him to edit the articles where those parts are/were to be found instead of writing such an article about it. But if this is how you look at Wikivoyage that's probably asking too much. I also love how his contributions to, or in this case about, Wikivoyage always pop up exactly when a certain other user who is also interested in time formats, spelling and such is officially away. Nurg, I think that's a brilliant idea.ϒpsilon (talk) 09:18, 3 November 2013 (UTC)Reply
As for our content, I'm sure we should perhaps clean up or some info here or there (the same is true for any wiki, definitely WP), but I wonder it edits like these is what we're after now? JuliasTravels (talk) 21:18, 3 November 2013 (UTC)Reply
I certainly don't think so. There's a line between seeming to advocate illegal actions and posting information helpful to travelers who could find themselves in over their head if they decide to indulge. The way I understand the policies on sex and drugs on this site is that we don't promote illegal drug use or prostitution but provide information sufficient to help travelers understand the nature of areas they might choose to visit or avoid, and safety information to help travelers avoid unnecessary danger. And just as it's dangerous to restrict the sex education of teenagers to a recommendation of abstinence, in my opinion, it would be irresponsible for a travel guide to just pretend that none of our readers will indulge in illicit drugs or sex. Ikan Kekek (talk) 21:49, 3 November 2013 (UTC)Reply

It seems that the editor-in-chief has endorsed the story. Quite honestly, I am ashamed to be part of the English Wikipedia today. --Rschen7754 04:11, 4 November 2013 (UTC)Reply

I'd like to say that treating a slam on a site the author was induced to leave for being a jerk as valid journalism, without even stating that he checked on the backstory, reflects the editor's lack of professional journalistic ethics, but I don't know the editor, so I'm choosing not to be the one to make that statement, if anyone does. Ikan Kekek (talk) 04:22, 4 November 2013 (UTC)Reply
(edit conflict) On a positive note, it's good that this sort of article was Tony's follow-through on his threats against Wikivoyage , rather than something that was not so easy to recognize as biased (and thus likely to actually do some damage to our project). In addition, attention from the Signpost has resulted in a number of edits that cleaned up articles that were in violation of Wikivoyage:Illegal activities policy, and has also resulted in some readers of the Signpost making other contributions here. In a perfect world the Signpost would not have allowed an article that appears to basically be a sensationalist hit piece, and would instead focus on being a tool for highlighting debates, successes, and lessons learned in different projects in order to facilitate more cross-project collaboration, so hopefully this episode can be a catalyst for moving the Singpost more in that direction. -- Ryan (talk) 04:43, 4 November 2013 (UTC)Reply
I do wonder if a more global newsletter, written and hosted from Meta, might be a better solution than trying to have the English Wikipedia Signpost cover everything, and sometimes with suboptimal results like what happened here. But then I've already got enough as it is going on... --Rschen7754 04:53, 4 November 2013 (UTC)Reply

Is it worth writing an op-ed for inclusion in a future edition as our/my response? I've started something here. --Nick talk 10:57, 4 November 2013 (UTC)Reply

No it is not -> w:WP:DIVA. We spent too much time and effort feeding the egos of people (or a person?) who did nothing but effectively threw a wrench into our gearbox to have some limelight shine on them. However well do/does they/he/she/it play on our emotions, let's not let the time and stamina we have set aside for WV go astray.
We have managed to remove the link to WT in the meantime, but we still need to set up good testing methods for various SEO methods discussed. Let's focus on that (and other ways of improving WV, including simply writing articles) instead, shall we? PrinceGloria (talk) 12:22, 4 November 2013 (UTC)Reply
PS. It would be a good idea to write about Wikivoyage for the signpost, but not as a reply to somebody wanting to cause just that, but to highlight how fun and useful it is, and how Wikipedians can help out and have fun at the same time, e.g. directing content they can contribute, but that is inappropriate for WP, here (provided it's appropriate here). We do need for it to be spaced in time enough not to draw any attention to said op-ed by our dear friend.
I'm inclined to agree with Ryan and PrinceGloria. Let's not waste too much time on this. The link to WT is not yet gone, but working on content still seems like a far better way to spend time than sinking deeper into that non-constructive discussion. People may draw conclusions of all kinds, but only a fool will still believe that article is fully true and unbiased. I hear the Signpost sadly does this kind of thing more often. Let's move on and welcome any people that have found their way here through it. JuliasTravels (talk) 12:34, 4 November 2013 (UTC)Reply
I don't have any deep knowledge of WP policies, but I feel using real names of some wikivoyagers in recent discussions the way Tony1 started with is a huge no-go. Am I wrong? Danapit (talk) 09:38, 5 November 2013 (UTC)Reply
It's a questionable practice. However, if you have not disclosed it anywhere on Wikimedia and it gets mentioned, then you can ask for it to be oversighted (w:en:WP:RFO). --Rschen7754 10:19, 5 November 2013 (UTC)Reply

Calendar of events

Apparently you dont permit the creation of calenders for events despite this being a significant part of helping people to decide when or if to visit a place/region. Can some please explain why of if its possible please link to a MOS or policy which I can follow Gnangarra (talk) 11:19, 3 November 2013 (UTC)Reply

I see this is your first post, so welcome to Wikivoyage! You come here with some misconceptions, it would appear. Listings of events are welcome, as long as they are of events that could interest a visitor. Such listings should be put in "Do" in destination articles, and can have their own subsection if that would make the section more easily readable. Is there something else you'd like to know? Ikan Kekek (talk) 11:50, 3 November 2013 (UTC)Reply
So how far ahead can these events be listed and how many, I've been working with local Government authorities developing Wikitowns, including Wikivoyage content is a natural progression these places each have multiple events/festivals every month to put a list in the location article would create unmanageable articles so the logical would be to have a Calender. Highlighting a couple of major events in the To DO section makes sense, but it also a logical extension to have a "Calender of Events" so that travellers can plan their journey to take in events that interest them. Gnangarra (talk) 11:58, 3 November 2013 (UTC)Reply
We do have a Calendar of events and festivals section, but it is fairly neglected as for now. ϒpsilon (talk) 12:03, 3 November 2013 (UTC)Reply
[Edit conflict] I'm not sure if I'm understanding correctly, but it sounds like the calendar you have created and are updating is official or at least semi-official for each town. If that's the case, the relevant town's calendar could be linked to once per destination article. Usually, the website for the town's office of tourism or, failing that, municipal website is linked to from the name of the town at the beginning of the article, but I see no problem with (also) linking a separate site that has a calendar of events on it, at an appropriate place in the "Do" section of the article. Your plan of posting some highlights of events and also linking the calendar sounds good to me. Ikan Kekek (talk) 12:07, 3 November 2013 (UTC)Reply
not looking to link to an "official municiple" as locations have more than official municiple events, the whole purpose is for one the community as a whole can update and maintain from a WikiTravel prespective is creates a gate way that keeps people frequenting the site, maintain content rather than just a passing add my B&B, or Restaurant. It will also bring people back to the site to look at whats happening. Looking at Calendar of events and festivals could I then make this into a template for Calendar of events and festivals in Foo where foo could be a town, a region or municipality which already have an article... and transclude the current month into the location article its associated with.Gnangarra (talk) 13:13, 3 November 2013 (UTC)Reply
On the subject of the neglected calendar of events. Is there anyway in MediaWiki to set up a displayable database? Wondering if it is possible to enter events by type, date and location then be able to create tables on region pages or list events by dates, types and regions. Traveler100 (talk) 12:22, 3 November 2013 (UTC)Reply
We could use the Semantic Mediawiki extension, which makes it easy to add calendars. (One day, Wikidata might allow for this, but it's too limited now.) -- Ypnypn (talk) 17:01, 3 November 2013 (UTC)Reply

These are all great ideas for encouraging local participation and, thus, more editors! --118.93.67.66 20:26, 3 November 2013 (UTC)Reply

Thanks for the input, I have created a subset for Toodyay#Do(alt perma link) to demonstrate how it could look utilising current formatting, all sub pages are red links at the moment.. Gnangarra (talk) 09:15, 4 November 2013 (UTC)Reply

Strongly support this innovation - there are many locations that I know in Australia that rely on the calendrical issue to attract visitors to a location on a specific date in the year, and so have such a device included, and accepted is great to see ! sats (talk) 09:48, 4 November 2013 (UTC)Reply

I like this, too. Ikan Kekek (talk) 10:12, 4 November 2013 (UTC)Reply
I do not see any avantage to the new experiment over the normal way of including a full section of events. The new suggestion unnecessarily splits content over thirteen additional pages and I seriously doubt that anything but metropoles would actually come close to being able to usefully fill that many pages with events actually relevant to the traveller. Certainly a "small town of about 1000 people" could easily fit all its events into the standard Do subsection. I wouldn't mind discussing how to better feature events, possibly differentiating them from other listing types or other changes, but splitting small articles into 14 is not going to be the answer. Texugo (talk) 02:30, 5 November 2013 (UTC)Reply
I share Texugo's concerns. I didn't realize that that would be the result. It's problematic not to have at least the most important events listed in the destination guide. I'm OK with the experimental articles supplementing the highlights, if there is a huge number of events to list (e.g., over 20), but putting the highlights in the destination guide is important for Wikivoyage's goal of being easily printable. Is that something you can work on, Gnangarra? Ikan Kekek (talk) 02:49, 5 November 2013 (UTC)Reply
I voiced similar concerns at Talk:Calendar of events and festivals in Toodyay (specifically, I'm not sure I understand what the benefits of this approach are vs something like Marina del Rey#Events), but despite any reservations I don't think it hurts to allow this experiment to continue and see what Gnangarra comes up with. Some sort of event calendar would be useful on Wikivoyage, but ideally we want something dynamic that could be shared across articles, thus allowing (for example) a single dataset to be used to generate city-specific, region-specific, and date-specific calendars so that we could embed a calendar in every article, feature an automatically-generated "today's events" list on the main page, allow users to search for events during specific time periods, etc. Technically I don't think that's currently possible, but maybe there will be some way to do it with a combination of wikidata and lat/long tagging in the future? In any case, this is a problem that would be nice to eventually solve, and allowing some experimentation might generate some useful ideas. -- Ryan (talk) 03:31, 5 November 2013 (UTC)Reply
I agree, Ryan. Ikan Kekek (talk) 03:53, 5 November 2013 (UTC)Reply
The idea of being able to shift, share and manipulate to create different calenders is an interesting concept, but its definately outside my skill set though I know a good programmer that could create a bot to refresh each monthly page once that month has finished. What I see is these calenders as being somewhere for communities to keep updating and engage with Voyage on practical level while they are at it they'll also maintain other location article content as opposed to the current 'hit n run' add my business thats occurring now. Addressing Texugo concern the value of having a monthly Calender(list of events) page is that people can then directly share this in emails, on social media and embedding in/linking to from other sites which will improve the reach of Wikivoyage attracting even more people to the project. For that to be successful it needs to be a simple process to add an event. Highlighting a few significant regular events in the main article is sensible, but the calender can be more specific about the actual details include other once off or dynamic timing without causing the main article to go stale. Gnangarra (talk) 07:51, 5 November 2013 (UTC)Reply
All of these are really interesting ideas, and I think you should continue to have the latitude to develop this. Ikan Kekek (talk) 08:21, 5 November 2013 (UTC)Reply
I don't mind the experiment continuing, but just to reply: I don't think being able to "share this in emails, on social media and embedding in/linking" is an added value for the overwhelming majority of cities/months that would be empty or have 1-2 items. I'd also like to point out that having a calendar that shows only the current month really isn't what we want either, since toward the end of the month you aren't displaying anything that looks ahead very far, and more importantly, people tend to plan ahead for future trips or may want to see when the best time for a trip would be. I'd say anything which will end up requiring 12+ clicks to fully see what's going on would be bad, especially for the vast majority of destination articles which have less than one thing per month, if any. Texugo (talk) 10:32, 5 November 2013 (UTC)Reply
Your point are well taken. What I was hoping would happen is that the events would appear in the destination guide. If there's a way that can be devised to display the next couple of months' events on a rotating basis in the destination guide by transcluding (I think that's the word) the calendars of those months from another article, that would be a good thing, along with the highlighted events throughout the year that should be at least mentioned in the destination guide (I think it's OK for more details to be somewhere else, as Gnangarra proposes). I should say to Gnangarra: Please don't feel threatened by this discussion. It looks like we've all agreed to give you latitude, and we're bringing up things to think about while developing this calendar. Ikan Kekek (talk) 11:24, 5 November 2013 (UTC)Reply
The transclusion bit is easy. I've created a quick template to transclude any calendar pages, if they exist, for the current and subsequent two months: {{upcoming events}}. The month can be forced too. {{upcoming events|Toodyay|month=8}} will transclude the August-October range like so:

Template:Upcoming events

There are only two calendar pages at present, so the full function is hard to see. The <noinclude> tags should probably be extended around the table in the calendar article, or that will be transcluded up to three times. The images might cause problems too, depending on the article and the length of the calendar. - AdamBMorgan (talk) 13:44, 5 November 2013 (UTC)Reply
done the noinclude fix and add a note for image to be included before that the </noinclude> tag Gnangarra (talk) 15:49, 5 November 2013 (UTC)Reply
I am still not seeing what the point is. The only net result I see is that we have more pages to edit, we complicate formatting, and we hide events which are more than a few weeks into the future, which doesn't make sense for travellers who are planning further ahead. Why would we not just keep everything on the destination page, showing all the events together in a single calendar section as we have done up til now? Where has this approach so far presented a problem that needs fixing? Texugo (talk) 13:53, 5 November 2013 (UTC)Reply
If there turn out to be few events in Toodyay, you may be right. I think if there are more than 30 events over the course of a year, we might not want to list all of them at once. Furthermore, if this experiment works well, it may be useful to repeat it with much bigger cities that have hundreds of events per year or more. So let's see where this goes. Ikan Kekek (talk) 13:59, 5 November 2013 (UTC)Reply
If there are more than 30 events over the course of a year, we might not want to list them all, period. For small-to-medium-sized cities, a list of more than 30 will probably include things like the regional toilet seat manufacturer's association trade show and the local ham radio operator's annual club picnic. We don't need to list every possible event anyway - when there are a lot, we choose the best recommendable ones, just like we do with any other kind of list we generate. Metropoles with the huge city template and dozens of dozens of events that are recommendable are the only type of article where I could imagine the need for a calendar management system, though the fact they can be distributed in district articles largely takes care of the volume. Even then, I don't think it would be right to hide things depending on the current date. I usually have to plan trips 6-9 months in advance and I'm sure this is not that unusual. Texugo (talk) 14:22, 5 November 2013 (UTC)Reply
I've got thick skin and the scares that come from 9 years of editing wikiprojects(long term sysop on en and commons), I come peace I not trying to harm Wikivoyage. I have at a guess everyone here has met politicians that would turn up to a door opening if they thought they'd get their mug on TV to not really take offense at idiotic examples but they do make your arguments rather hard to take seriously, because everyone knows that a picnic for locals would be a closed event, and that a local manfacturers trade show would be an invite only. Gnangarra (talk) 15:37, 5 November 2013 (UTC)Reply
planning trips 6,9 12 months in advance is only one way people would plan, but thats not the only way people plan. More frequently I have a day where I can do something, I'll be looking maybe 1 or 2 days in advance either we should not assume people who mangage to navigate from google and can read a calender to know when they are taking their holiday cant the work out that if they want to know whats happening in May rather than next week they could click on that link, over the next 6,9, 12 months these people will return to see what else is happening after a few visits they'll think oh whats happening at home oh look I can help out here. I agree we dont want every event but as a rough guide any event thats ticketed or open to the public should be in the detailed calender. Like all projects there is an editor bias using this bias in selecting/recommending events isnt encouraging broad participation. Lets take an example of Fremantle Festival it runs from Oct 25 to Nov 10 its been running for over 100 years so this meets any inclusion criteria no matter how strict infact it'd meet Wikipedia notability guidelines for an article there as well. This year the festival has more than 100 individual events and the majority of them would be of interest to visitors but every event wouldnt be of interest to every visitor, that is one festival. To even offer a brief coverage of these two weeks it'd be a sizable list, (enough that an argument could be made for its own article here but thats a whole different tangent and another can of worms I have no intention of opening) yes some months will quieter than others but for continuity reasons alone and future automation needs accepting of some small things. Another cause is that with October 2014 there would be very few events scheduled that could be included in the calender today but in july it'll have grown substantially and june will be blank the calenders will organic in nature growing and shrinking depending on how far in the future it is. Gnangarra (talk) 15:37, 5 November 2013 (UTC)Reply

Maybe my examples were a little silly, but people do indeed add some very dubious events from time to time. Anyway, it sounds like what you are looking to do is to greatly expand the level of detail we offer to include whole event schedules, such as the whole two-week schedule of over 100 mini-events of the Fremantle Festival, or the full schedule of a music or film festival like SxSW in Austin. Keeping this kind of thing updated can start to get out of scope, which is why we typically link to the official site for the event, where the schedule is bound to be given in full and constantly up-to-date. It's kind of analogous to the reason why we don't have separate pages to give intimate details on museum collections or train schedules. Texugo (talk) 16:17, 5 November 2013 (UTC)Reply

not trying to create whole event schedules, just highlighting that a festival with 100 events even listing 1 in 3 is 30odd all I was trying to show is that 30 is any easily achievable while still keeping relavence, like wise you wouldnt create an article to list every piece in a museum's collection the description of the museum would sufficienlty cover the highlights so that a person could decide if it something they would vist but you would note a travelling exhibition as an event. Likewise maintaining train schedules would be a waste of resources, but noting the last train for the service or a unique special event service would both be items you'd consider including in a calender. Gnangarra (talk) 02:37, 6 November 2013 (UTC)Reply

CAPTCHA broken for IP's

Thanks for both your comments. Immediately moving to Wikivoyage_talk:Listing editor for more in-depth discussion. -- torty3 (talk) 23:34, 3 November 2013 (UTC)Reply

Thanks for the ultra-rapid response, torty3 - it's much appreciated! --118.93.67.66 09:10, 4 November 2013 (UTC)Reply

Template:PrintDistricts

This template appears to have been changed unilaterally last month (although I may have missed a discussion). Whilst I am in favour of losing (or at least diminishing) the role of printing in this warning, I'd want to change the new wording to something a little more pithy: perhaps "XXX is a huge city with several district articles which contain information about specific sights, restaurants, and accommodation."

It may also be worth thinking about the SEO impact of changing this common template - the previous wording was exactly the same as its WT counterpart. --Nick talk 02:24, 5 November 2013 (UTC)Reply

Your wording is good, Nick and it's also good to always have SEO at the back of our minds until WV is sunk. --118.93.67.66 11:47, 5 November 2013 (UTC)Reply
I'm hoping you meant 'WT' :P And the wording looks fine. James Atalk 11:49, 5 November 2013 (UTC)Reply
Aw shucks, my evil plan is revealed by my own Freudian slip. Off to sell my IB shares... Ibobi 04:15, 5 November 2013 (UTC)

Some thoughts on flexibility

I think I've learned something from the experiment so far in creating calendars for Toodyay. My first response to an attempt to create a separate "Toodyay Calendar" was to delete it, because we've never had an article like that before, and my understanding was that it is a bad idea and against policy to have separate non-destination articles that are purely lists of events in a particular town. And then an interesting thing happened: Someone gave a sensible explanation of how a calendar might fit into and actually be of use to this project, and someone else explained that there was a calendar template lying dormant that I had no knowledge of.

Similarly, when I first saw a bunch of templates being created with names like "People born in Delaware" or something similar, my first reaction was not to delete them but to think that they were likely candidates to be nominated for deletion because they were not destination articles. Now that I see what they look like and what their purpose is, I'm fine with them.

So what's the point of all of this? The point is that I, and perhaps we (if the shoe fits, wear it, and please don't be too annoyed at me if this doesn't apply to you), should not be overly hasty to delete things just because they're different from the way we've done things and are used to things being done. We have new, interesting contributors to this project and all of us (I think) hope there will be many more. We should really consider giving them a lot of latitude, ask them friendly questions, and see what explanation they give for how their new styles of articles, templates, and user boxes can fit into this project, either in a harmless way, or better yet, a truly constructive way that makes this site better. This site is going to grow and change based on the creativity of new as well as established users, and also through the expectations that people familiar with sister Wiki-projects have. Let's give anyone who is not vandalizing, touting, or plagiarizing an even warmer welcome than we do now, if we can. Ikan Kekek (talk) 11:58, 5 November 2013 (UTC)Reply

Nice post. I think, if we want to be more friendly to new contributors, we should make use of the new 'thank you' feature more often, just like I did for you, Ikan. It will send the user a notification thanking them for their edit. Dale Carnegie argued that if you wanted people to learn from their mistakes, congratulate them for their successes (good edits) rather than criticising them for their mistakes (bad edits, policy violations, etc). James Atalk 23:44, 5 November 2013 (UTC)Reply
I heartily agree with both Ikan and JamesA. I confess that from time to time I may have been less than flexible - it's a character trait I have both on- and off-wiki of which I'm not particularly proud - and will try to remember this conversation in the future. I hope others feel the same way. -- AndreCarrotflower (talk) 00:44, 6 November 2013 (UTC)Reply
I've been thinking along the same lines for a while. --Rschen7754 00:46, 6 November 2013 (UTC)Reply
Good point about the "thank you" feature. I haven't been using it, and I should. Ikan Kekek (talk) 02:44, 6 November 2013 (UTC)Reply
Great post, Ikan. You're forgiven for this.
Where's this "thank you" feature page please, I've searched and can't find it. --118.93.67.66 04:22, 6 November 2013 (UTC)Reply

Introducting Beta Features

(Apologies for writing in English. Please translate if necessary)

We would like to let you know about Beta Features, a new program from the Wikimedia Foundation that lets you try out new features before they are released for everyone.

Think of it as a digital laboratory where community members can preview upcoming software and give feedback to help improve them. This special preference page lets designers and engineers experiment with new features on a broad scale, but in a way that's not disruptive.

Beta Features is now ready for testing on MediaWiki.org. It will also be released on Wikimedia Commons and MetaWiki this Thursday, 7 November. Based on test results, the plan is to release it on all wikis worldwide on 21 November, 2013.

Here are the first features you can test this week:

Would you like to try out Beta Features now? After you log in on MediaWiki.org, a small 'Beta' link will appear next to your 'Preferences'. Click on it to see features you can test, check the ones you want, then click 'Save'. Learn more on the Beta Features page.

After you've tested Beta Features, please let the developers know what you think on this discussion page -- or report any bugs here on Bugzilla. You're also welcome to join this IRC office hours chat on Friday, 8 November at 18:30 UTC.

Beta Features was developed by the Wikimedia Foundation's Design, Multimedia and VisualEditor teams. Along with other developers, they will be adding new features to this experimental program every few weeks. They are very grateful to all the community members who helped create this project — and look forward to many more productive collaborations in the future.

Enjoy, and don't forget to let developers know what you think! Keegan (WMF) (talk) 19:48, 5 November 2013 (UTC)Reply

Distributed via Global message delivery (wrong page? Correct it here), 19:48, 5 November 2013 (UTC)
I checked this out before, and must say, I like the Media Viewer feature. It would work a charm with our static maps, which are often too small to see when in an article thumbnail. Once they start looking for sitewide tests, I recommend we put our hand up. James Atalk 01:06, 6 November 2013 (UTC)Reply