Wikivoyage:Votes for deletion

From Wikivoyage
(Redirected from Vfd)
Jump to navigation Jump to search
Votes for Deletion

This page lists articles, files and templates that are nominated for deletion. Any Wikivoyager can make a nomination or comment on any nomination. Nominations or comments should follow a rationale based on our deletion policy.

If our deletion policy leads towards a merge or redirect, then coordinate this on the discussion page of the article.

The purpose of this page is limited to the interpretation and application of our deletion policy. You can discuss what our deletion policies should be on the deletion policy discussion page.

Nominating[edit]

  1. Add a {{vfd}} tag to the top of the article, file or template being proposed for deletion, so that people viewing it will be aware. Place the tag at the very top, before everything else.
  2. Add a link to the article, file or template at the end of the list below, along with the reason why it is being listed for deletion. Sign your recommendation using four tildes ("~~~~"). List one article, file or template per entry.
  3. If you're nominating a file for deletion, make sure it's actually located on the English Wikivoyage and not on Wikimedia Commons.

The basic format for a deletion nomination is:

===[[Chicken]]===
* Not a valid travel article topic. ~~~~

Commenting[edit]

All Wikivoyagers are invited to comment on articles, files or templates listed for deletion. The format for comments is:

===[[Chicken]]===
* '''Delete'''.  Not a valid travel article topic. TravelNut 25:25, 31 Feb 2525 (EDT)
* '''Keep'''.  There is a town in [[Alaska]] called Chicken. ~~~~

When leaving comments you may elect to delete, keep, or redirect the article. If you recommend redirection, you may suggest where it should be redirected to. Any attempt to merge content from an article to some other destination must retain the edit history to comply with the attribution (CC BY-SA) requirements of the free license, so it may be possible to merge and redirect but not to merge and delete. Sign your comment using four tildes ("~~~~").

Deleting, or not[edit]

  • If, after 14 days of discussion, the consensus is to delete, an administrator may delete it.
  • If, after 14 days of discussion, the consensus is to redirect or merge, any Wikivoyager may do it. If you make a redirect, please check for any resulting broken redirects or double redirects.
  • If, after 14 days of discussion, the consensus is to keep, any Wikivoyager may remove any VFD notices from that page, and archive the deletion discussion.
  • If there is no consensus after 14 days, allow a further 7 days for discussion.
    • If, after the additional 7 days, there is no consensus, the page should be kept – any Wikivoyager may remove any VFD notices from that page, and archive the deletion discussion.
    • If, after the additional 7 days, there is a consensus, implement it in line with the first three points above.
  • When deleting a template, consider first replacing it wherever it's been transcluded, especially if it served a formatting function. You can do this by adding "subst:" before the template name. Once that's done, you can delete the template without affecting individual uses of it.

Archiving[edit]

After you keep/redirect/merge/delete the article, file or template, move the deletion discussion to the Archives page for the appropriate month. The root Archives page has a directory. Note that it's the month in which the action was taken, rather than when the nomination was first posted, that should be used for the archived discussion; that way, recourse to the deletion log can lead subsequent readers right to the discussion (at least for the pages that were deleted).

When archiving, always make it clear to other editors what the outcome of the discussion was. This can be done by adding the result to the discussion in a separate edit from the one in which you remove the discussion from this page; or you can describe the outcome in the edit summary when you remove the discussion.

If the nominated article, file or template was not deleted, then place another (identical duplicate) copy of the deletion discussion on the discussion page of the article, file or template being kept or redirected.

See also:

Icon delete talk.svg

September 2018[edit]

Rock bottom budget travelling[edit]

Really? Even as a redirect? --Comment by Selfie City (talk about my contributions) 23:46, 11 September 2018 (UTC)

Where's the harm? Ikan Kekek (talk) 00:00, 12 September 2018 (UTC)
Where's the bonus in keeping it? --Comment by Selfie City (talk about my contributions) 00:02, 12 September 2018 (UTC)
Wouldn't it be better to spend time improving the travel guide rather than nominating harmless redirects for deletion? I think deletion discussions for redirects that are not particularly useful but still entirely harmless are basically a waste of the community's time. —Granger (talk · contribs) 01:12, 12 September 2018 (UTC)
IMO, deletion nomination discussions are part of improving Wikivoyage. --Comment by Selfie City (talk about my contributions) 01:15, 12 September 2018 (UTC)
For some deletion discussions that's certainly true. What I said is that deletion discussions for redirects that are not particularly useful but still entirely harmless are a waste of time. —Granger (talk · contribs) 01:18, 12 September 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────And what pray is the benefit of meta level discussions such as this one? Or indeed my going onto the second meta level? Hobbitschuster (talk) 01:31, 12 September 2018 (UTC)

I agree with Mx. Granger. SelfieCity, your enthusiasm is wonderful, but please don't look for problems that aren't there. Ikan Kekek (talk) 02:03, 12 September 2018 (UTC)
Leave it because:
  1. Wikivoyage:Deletion policy#Redirects says "As a general rule redirection pages should not be deleted."
  2. It's harmless.
  3. Waste of community time discussing it, as said by Granger. Nurg (talk) 08:25, 12 September 2018 (UTC)
Keep. Pashley (talk) 15:09, 8 October 2018 (UTC)

Al-Qādisiyyah[edit]

  • Middle East stub article with no content created by brand new user with no email who appeared right after the ban of User:Alphaomegaone. The only content in the article other than location is a mention of invading Muslims. ARR8 (talk) 00:45, 20 September 2018 (UTC)
  • From w:Al-Qādisiyyah (historical city) and w:Modern usage of al-Qādisiyyah it would seem that the historic battle between Muslims and Persians at this location is the only claim to fame for this point, and the battle is notable in the history of Islam. The history should be mentioned somewhere (either in the Islam article or in the closest geographic destination with enough to see and do to make a reasonable-size, usable article. Al-Qādisiyyah should then be redirected; it's notable, but (like Promontory Summit) there´s not enough to say about this place to fill an article. -K7L (talk) 01:05, 20 September 2018 (UTC)
It seems like it has been deleted already. I’d say a listing in “see” in some article about the battle location, or a paragraph in the understand section of a destination article, would be appropriate. --Comment by Selfie City (talk about my contributions) 01:14, 20 September 2018 (UTC)

October 2018[edit]

Ferries in the Mediterranean[edit]

An article that is so out of date and going nowhere that we might as well delete it. If you want to keep it, please say how you'll improve it. Or you can always have it moved to your userspace. Hobbitschuster (talk) 22:29, 5 October 2018 (UTC)

Not sure. It is a valid topic, but an unmaintained article may be worse than none. Pashley (talk) 22:45, 5 October 2018 (UTC)
  • Oh, this is a tough one. There are a lot of dead links that give the impression that the article is going out of date. Yet, as Pashley said, this is a valid travel topic. There is hope in this article, but it might need to be largely written to be once again up to date. This seems like more work than is worth it, considering that it's not a really important travel topic. Also, it's quite a long article, so it was to be improved, a lot of work would be necessary. Therefore, I leaning toward delete for this article, and that's the stance I'm taking. It doesn't seem to be our usual policy to go this way, but in this case I think it's the best option — but not by a lot. --Comment by Selfie City (talk about my contributions) 23:20, 5 October 2018 (UTC)
  • I don't know how useful an article like this is to travellers, but it just got a whole bunch of updates before the nomination here. I did some updates in 2017. A ferry was added in 2016. Before that, there wasn't much activity other than the import from the predecessor site. I am not inclined to delete. Ground Zero (talk) 04:17, 6 October 2018 (UTC)
Thanks for doing this research, which moves me to neutral, seeing both sides of this situation. --Comment by Selfie City (talk about my contributions) 04:26, 6 October 2018 (UTC)
  • Keep. In the Mediterranean, like in the Baltic Sea and seas around Britain ferries are a common way for getting across. I think it's useful to have an overview of ferry lines, though the article (as the other ones?) could probably use an update. ϒpsilon (talk) 09:01, 6 October 2018 (UTC)
The problem with any article that lists a bunch of services and not many alternatives is keeping it up to date. I think our travel topics should generally not include a bunch of links to other company websites since a travel topic should focus on useful information, that is, paragraphs, rather than long lists. This article is designed to be a list, which means it would need quite a lot more real content. Is anyone ready to add some and improve this article? --Comment by Selfie City (talk about my contributions) 13:50, 6 October 2018 (UTC)
  • I agree that it should have more prose content, but I think a list is also good to include. But now we're talking about how to improve the article, which is best discussed on the article's talk page. Keep. Ikan Kekek (talk) 19:18, 6 October 2018 (UTC)
Joining the consensus: keep. Pashley (talk) 15:08, 8 October 2018 (UTC)
  • Keep - viable topic. Gizza (roam) 00:59, 18 October 2018 (UTC)

RAP[edit]

Currently a redirect to Rapid City#By plane. However, I think the musical genre of rap is definitely a viable travel topic (we already have Jazz, and Wikivoyage:Requested articles includes an idea for an East Coast hip hop tour). If we already had a travel topic article about rap, the best solution would be to turn RAP into a disambiguation page; since we don't yet, and since Rapid City Regional Airport is not nearly major enough to absolutely need its IATA code to redirect, I think it would be prudent to delete the redirect and not needlessly hinder the creation of such a travel topic article. -- AndreCarrotflower (talk) 01:56, 8 October 2018 (UTC)

Sure, Support Support. I created the page. It could just as easily be one of the hardcoded IATA redirects, like USA IATA. I don't predict the Rapid City IATA code changing often. ARR8 (talk) 02:06, 8 October 2018 (UTC)
To be clear, the support means support deletion. ARR8 (talk) 02:12, 8 October 2018 (UTC)
  • Delete. Honestly, I think that turning IATA codes into redirects is a waste of time. The exception is huge airports like Atlanta Airport. --Comment by Selfie City (talk about my contributions) 02:48, 8 October 2018 (UTC)
  • Delete I think there was never any actual consensus on creating all those IATA code redirects, but in this example there clearly is something people think of before they think of a minor joke airport in the middle of nowhere... Hobbitschuster (talk) 12:58, 8 October 2018 (UTC)
  • OK, I'll go along with consensus & say delete.
As for the more general question of IATA redirects, that was discussed somewhere & the conclusion was they were a good idea. I spent a few hours creating several dozen, all the ones with five or more links on "pages wanted". I think the fact that many had 7 or 8 red links is fairly good evidence they are worthwhile. Pashley (talk) 14:43, 8 October 2018 (UTC)
Updated: Create a disambig page instead. Ikan Kekek (talk) 03:57, 18 October 2018 (UTC)
  • Comment: MediaWiki, by default, is case-sensitive on all but the first character of titles. RAP is not the same article as rap or rap music (with or without the silent leading 'c'). K7L (talk) 20:20, 8 October 2018 (UTC)
    True. This does not show in the search field with the Vector (current default) interface until Rap is created, but when it is, the two coexist as separate pages. So no need to remove the airport redirect, if the other page is created – as article, redirect or disambiguation page. --LPfi (talk) 08:34, 11 October 2018 (UTC)
    Those were my two concerns - that the capitalization might prevent the creation of a new page, and that it might interfere with autocomplete for people trying to search for rap. If neither is true, then I suppose it would be better to have as few hardcoded redirects as possible - so I now lean keep on this. If there's any reason why the presence of this redirect would actually hinder the creation of a new page, I'll vote to delete again. Otherwise, I don't think it does any harm. ARR8 (talk) 12:41, 11 October 2018 (UTC)
    Other than leaving w:Rapid City Regional Airport with KRAP as its ICAO code? I suppose it's harmless. :) K7L (talk) 01:09, 13 October 2018 (UTC)
    Ha, sounds like the eventual switch to ICAO will be a memorable event for Rapid City. ARR8 (talk) 01:43, 13 October 2018 (UTC)
    ...as in "this is your captain speaking, we're descending from 25,000 feet and are about to land in, well this could get messy..."? K7L (talk) 04:50, 13 October 2018 (UTC)
  • Delete I have not changed any search settings, and when I type "rap" into the search, it takes me to the airport. Same with "Rap", so it does not seem to be case-sensitive. ChubbyWimbus (talk) 03:02, 13 October 2018 (UTC)
    As I said above: until Rap is created. RAP is just considered the closest match until then. --LPfi (talk) 14:49, 13 October 2018 (UTC)
  • Keep Redirects like this are very high-value, especially for mobile search. It's much easier to type "LAX" in your phone than to migrate by breadcrumbs or standard links. As always, redirects are cheap, so there's not much incentive to delete them. —Justin (koavf)TCM 03:10, 13 October 2018 (UTC)
  • I was actually just coming over here to say that I’m still for deleting when, as I typed in “vfd” to get to this page, my search term came out as “bff” and I was redirected to the Scottsbluff Airport information. To make it clear, I do not support airport IATA redirects. In most cases I think it’s a waste of time reverting them, but per User:ChubbyWimbus and this other redirect incident I support delete for this redirect. Some earlier comments pulled me a little from the delete zone but I’m now a solid delete supporter again. --Comment by Selfie City (talk about my contributions) 04:20, 13 October 2018 (UTC)
    Comment: Well, keep in mind removing the redirect wouldn't help you in this case. If you delete bff, entering bff into the search wouldn't take you to VFD, it'll just take you to a search for the term "bff." ARR8 (talk) 14:34, 13 October 2018 (UTC)
  • Keep - Adding IATA redirects has identified a good number of errors on airport descriptions and use of incorrect codes on Wikipedia. Helps readers not make any incorrect bookings, or at least save some time and confusion. Adding Rap solves the search issue. Currently redirect to Music, but if people think this could be a travel topic then should be changed to an article. --Traveler100 (talk) 05:04, 17 October 2018 (UTC)
  • Keep. As a rule, I find the IATA redirects useful—it's easier to search "ORD" or "SFO" than to type the whole name of the airport. And in some cases it's hard to remember the exact name of the airport (is it Guangzhou Baiyun? Or just Baiyun? For me it's easier to search for "CAN"). And sometimes it's not obvious which article an airport will be covered in—easier to type "RDU" than to remember if its main listing is in the Raleigh, Durham, or Research Triangle article. Now that Rap has been created, this redirect seems to do no harm, so there's no need to delete it. —Granger (talk · contribs) 14:40, 17 October 2018 (UTC)
  • Comment - If we keep "RAP" as an airport redirect, we need to create a disambiguation, because of the common and possibly travel-related meaning of "rap". There have been some other disambiguation pages that have included airport redirects. Ikan Kekek (talk) 14:48, 17 October 2018 (UTC)
    Why is a disambiguation page necessary? Would a reader ever type the word in all caps when looking for the type of music? —Granger (talk · contribs) 15:20, 17 October 2018 (UTC)
It doesn't matter if you type in all caps or not. It's not case-sensitive. Whoever said that was mistaken. Rap, rap, RAP, rAp, RaP, rAP, RAp: All take you to the same place. You can do the same with any location (ex: pittsBUrgh takes you to Pittsburgh). ChubbyWimbus (talk) 15:55, 17 October 2018 (UTC)
@ChubbyWimbus: That's not correct, and I encourage you to test it for yourself by typing "RAP" and "Rap" into the search box. Once two pages are created that differ in capitalization, the search function respects that difference (with the caveat that, as K7L said, the first character of a page title is not case-sensitive). —Granger (talk · contribs) 16:21, 17 October 2018 (UTC)
If you think people usually distinguish by case when typing in search boxes, I would beg to differ. I hardly ever use capital letters to search in Wikipedia, and many of our users are familiar with Wikipedia. Ikan Kekek (talk) 17:46, 17 October 2018 (UTC)
Agree, that is why the IATA code redirect will not affect most searches people enter. --Traveler100 (talk) 17:59, 17 October 2018 (UTC)
But if we want to help people looking for the IATA code, we need for them to be able to access it using lowercase letters, too, which is why a disambig would be helpful in this case. I think it's very problematic that people have to use ALL-CAPS to access any of the other IATA code redirects. I didn't know that until now. Ikan Kekek (talk) 18:13, 17 October 2018 (UTC)
The main reason for the IATA template was to provide an easy and clear link from multiple pages to a single page detailing a non huge airport. --Traveler100 (talk) 18:24, 17 October 2018 (UTC)
OK, duly noted. But don't you think it's a problem if someone searches for an airport using lower-case letters and doesn't find it that way? Ikan Kekek (talk) 18:28, 17 October 2018 (UTC)
That's a fair point. It could be solved by a Template:hatnote in the Music article, or by a disambiguation page as you suggest. It feels slightly silly to me to create a disambiguation page for an IATA code and a genre of music that we don't actually have an article for, but I don't strongly object.
By the way, to clarify, you don't usually need to use all-caps to access IATA code redirects. Searching for "ord", "sfo", or "can" works just fine. The software only takes capitalization into account in searches when there are two pages that differ only in capitalization (like RAP and Rap). —Granger (talk · contribs) 00:40, 18 October 2018 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────I have a related question: are there any times railroads or other modes of transport share the names of airport codes? I'm thinking if there was, for example, a train station's name that was abbreviated to "ATL" in Atlanta, or "SJC" in San Jose. This could really pose a problem for IATA redirects. --Comment by Selfie City (talk about my contributions) 01:43, 18 October 2018 (UTC)

Indeed there is. BUF is the IATA code for Buffalo Niagara International Airport and also the Amtrak identifier for Buffalo-Depew train station. -- AndreCarrotflower (talk) 03:23, 18 October 2018 (UTC)
That seems like a problem to me. Someone could type in a redirect for the train station but suddenly find themselves at the airport article. And if we're talking about an Amtrak idenification, it seems very possible that IATA/Amtrak codes could be identical in multiple cases. --Comment by Selfie City (talk about my contributions) 03:26, 18 October 2018 (UTC)
Please study the functionality. If the three letter code has more than one meaning for a travel related topic then there is a dis-ambiguous page which covers all possibilities, for example MGM. The letters used in the IATA template will however always take you to the airport listing or page. This activity has corrected a lot of errors on the site, improved information on airports and provided additional functionality yo readers. You really think it is worth removing all this over a topic that is only indirectly travel related that does not exist! Also should assume reader has some intelligence, why would you type in bff in a travel site if you want to know what other meaning it has, that is what Wikipedia is for. Traveler100 (talk) 04:46, 18 October 2018 (UTC)
I recall the {{IATA}} template contained a few hard-coded checks for silliness like ROC IATA and PRC IATA (the names of countries Taiwan and mainland China) along with a few others, like GTA IATA (which could be either Grand Theft Auto or Greater Toronto Area). It's nothing that hasn't come up before; I think we can handle the difference between RAP and rap music, as it's less messy than the ICAO code. K7L (talk) 05:24, 18 October 2018 (UTC)
  • Keep. I suppose few people use all caps to search for the music genre, and those who do will not be surprised when ending up in the wrong place. It seems this is the only real concern. The rest of the discussion is useful, but does not directly affect the value of the IATA redirect. --LPfi (talk) 15:52, 18 October 2018 (UTC)

Texhoma[edit]

A page with no content that has never been edited by a human. Also, isn't an actual place - the Wikidata item it's connected to is for a disambiguation between two places. ARR8 (talk) 03:52, 11 October 2018 (UTC)

  • Keep - Valid search term. But it should probably be reduced to a disambig unless someone wants to work on it. The Oklahoma side shows 3 places of interest. If someone knows something about them, there could be listings for them. Ikan Kekek (talk) 04:22, 11 October 2018 (UTC)
  • Keep and redirect. Ground Zero (talk)
  • Keep, since it seems to pass the sleep test. However, I think the article's wording "pair of towns" should be changed to "a town" because it is de facto one town in two states. --Comment by Selfie City (talk about my contributions) 13:32, 11 October 2018 (UTC)
  • Keep, because we don't delete real places. I don't know whether it should be its own article or a redirect to somewhere nearby. —Granger (talk · contribs) 14:12, 11 October 2018 (UTC)
  • Keep. It could be converted into a disambig page. The two communities have a total population of 1300, and the main attraction appears to be the border sign. Stratford (Texas) and Guymon are the nearest places that we do have articles for, and they are about the same distance away. AlasdairW (talk) 21:00, 11 October 2018 (UTC)
  • Comment - It's not a disambig page unless it links to individual articles for at least two different non-contiguous places with the same name (such as Portland (Oregon) as a colony of Portland (Maine). If there are a pair of articles linked for adjacent, contiguous places (like Nogales or Niagara Falls, split by the Mexico and Canada borders respectively) the general description page is an {{extraregion}}, not a {{disambig}}. If this is a Glenrio-sized speck on a map, there aren't and won't be two separate articles (or enough content to justify same) so nothing to disambiguate. K7L (talk) 01:42, 12 October 2018 (UTC)
Yes, I agree that both sides of the city should be treated as one destination. The only reason that the city is officially two separate cities is because the state line cuts through the middle of it. --Comment by Selfie City (talk about my contributions) 02:19, 12 October 2018 (UTC)

Sanskrit phrasebook[edit]

The Indian version of Latin: culturally indispensable, but of zero use to travellers. The phrasebook itself is almost empty, so is not even good as a gimmick. If the much more complete Esperanto phrasebook qualified for deletion, with however many millions of speakers that conlang has, then a language which no-one has spoken outside of religious ceremonies for hundreds of years surely must too. Some of the interesting information on the history and features of Sanskrit could be moved elsewhere, perhaps to Indian subcontinent#Talk or the 'Understand' section of that page. --ThunderingTyphoons! (talk) 13:59, 19 October 2018 (UTC)

  • Not another phrasebook nominated for deletion! But my vote is different this time for these reasons: #1, I intend for it to be permanent, and #2, I vote to keep. Travelers interested in the religious ceremonies or ancient texts would find the phrasebook useful in a way that would not have been the case for Esperanto. --Comment by Selfie City (talk about my contributions) 14:05, 19 October 2018 (UTC)
This phrasebook provides translations for some numbers, and nothing else. And has done so since 2010. It will not help travellers interested in religious ceremonies or ancient texts. It would be of some help in playing a Sanskrit bingo game, but nothing beyond that. Delete. Ground Zero (talk) 14:21, 19 October 2018 (UTC)

After reading that article, I've decided to vote keep. It's not like keeping it would do any harm. Besides, we can always add a notice saying it's a dead language. Vulcandor (talk) 23:11, 20 October 2018 (UTC)

So what use is a phrasebook for a dead language no-one speaks? There are plenty of things which would do no harm if they existed, but which wouldn't serve the traveller.--ThunderingTyphoons! (talk) 23:23, 20 October 2018 (UTC)
ARR8, thanks for the link. More reason to keep the phrasebook. --Comment by Selfie City (talk about my contributions) 01:37, 21 October 2018 (UTC)
I guess we have to keep it then, even though it is useless in it's current state. Ground Zero (talk) 04:33, 21 October 2018 (UTC)
Keep for now, per Ground Zero, ARR8. Ikan Kekek (talk) 07:01, 21 October 2018 (UTC)
Yes, this changes things rather and the guide should be kept and expanded. Good research, ARR8. --ThunderingTyphoons! (talk) 10:21, 21 October 2018 (UTC)
Indeed, a somewhat better analogy than Latin may be Hebrew, which was a dead language but revived. Sanskrit hasn't been revived to the same extent but about 20,000 people in India and 1,500 people in Nepal reported speaking Sanskrit as a first language in their most recent respective censuses. I'm a bit skeptical about whether any of those people are monolingual but you never know. I studied Sanskrit a long time ago and still have a few books on it. I'll expand what I can, though it was taught a similar sense to Latin and Ancient Greek (learning how to read ancient texts rather than have a conversation with someone and ask where the nearest toilet is). Gizza (roam) 10:34, 21 October 2018 (UTC)

Rojava[edit]

Why do we even need this? Within a year from today, it will either be attacked by Turkey or Syria, if not both. Vulcandor (talk) 20:10, 21 October 2018 (UTC)

I spent what seemed like forever cleaning up junk articles like "Jazira Canton." Vulcandor (talk) 20:13, 21 October 2018 (UTC)
Yes, a user by the name of Libertarianmoderate — you may have heard of him — created some nearly empty region articles for dangerous places a little while ago. And since he was blocked, he has continued to resurface under other usernames as a sockpuppet. --Comment by Selfie City (talk about my contributions) 20:16, 21 October 2018 (UTC)
  • And my opinion is keep. We generally don't delete articles about real places. --Comment by Selfie City (talk about my contributions) 20:17, 21 October 2018 (UTC)