This language has been verified as eligible. The language is eligible for a project, which means that the subdomain can be created once there is an active community and a localized interface, as described in the language proposal policy. You can discuss the creation of this language project on this page.
If you think the criteria are met, but the project is still waiting for approval, feel free to notify the committee and ask them to consider its approval.
A committee member provided the following comment:
No doubts about the eligibility of the language; when the activity criteria are fulfilled, it can be approved. --MF-W 15:31, 27 March 2013 (UTC)Reply[reply]
The community needs to develop an active test project; it must remain active until approval (automated statistics, recent changes). It is generally considered active if the analysis lists at least three active, not-grayed-out editors listed in the sections for the previous few months.
"Wikivoyage talk" (the discussion namespace of the project namespace)
Default is "no". Preferably, files should be uploaded to Commons.
If you want, you can enable local file uploading, either by any user ("yes") or by administrators only ("admin"). Notes: (1) This setting can be changed afterwards. The setting can only be "yes" or "admin" at approval if the test creates an Exemption Doctrine Policy (EDP) first. (2) Files on Commons can be used on all Wikis. (3) Uploading fair-use images is not allowed on Commons (more info). (4) Localisation to your language may be insufficient on Commons.
Thai is the only official language in Thailand. It is very closed to Lao and is mutually intelligible to Lao. Main users of Thai are therefore Thai and Lao people. The combined population of the two countries is over 70 millions. Wikipedia, Wikisource, Wiktionary, Wikiquote and Wikibooks are all well established in Thai. (Thai Wikinews was closed due to long period of inactivity.)
As Thailand has gone into upper middle income economy, there is clearly a need for online free travel guide both for domestic and international travels. Thai government currently issues 1.5 million passports per year and has recently added an additional alphabet to passport number to cope with the growing demand. Thai speakers, however, have a very limited access to quality free online travel guide in Thai. We currently rely on information from travel agents/providers, blogs and Wikipedia. I believe that the Thai Wikivoyage can definitely cater for this growing number of Thai travellers.
It is expected that the Thai Wikivoyage will mutually benefit the five academically-oriented existing projects. We have observed so far a very close collaboration and rapid transfer of expertise between the Thai Wikimedia projects. The anticipated benefits are threefold. See Wikimedia-TH discussion (in Thai).
Wikivoyage can serve as an entry point of volunteers for a more saturated/academically-oriented projects. Because Wikivoyage is rather simple and personal, it is perhaps easier to start contributing based on individual's experience. When people run out of personal stories and start doing research for more information, they will realize the importance of source referencing and can move on to Wikipedia and/or other projects.
Unlike a proposal to open Thai Wikiversity which may undesirably draw contributors from the other five projects, I anticipate that Wikivoyage will eventually draw its own contributors. Perhaps, some will come from those who had tried Wikipedia or other projects and decided that it is not for them.
The Thai Wikivoyage will undoubtedly help increase content upload to/used from Wikimedia Commons. Please note the "no upload policy" below.
Localized logo made by Aristitleism using free font from "คุณแอนแห่งเว็บฟ๐นต์"
I propose that we start with a standard Wikivoyage site (default settings/copy most of the settings from English Wikivoyage and Thai Wikipedia) but no upload. This will reduce sysop workload and liability to a minimal and will encourage the use of Wikimedia Commons. --Taweethaも (talk) 06:31, 23 March 2013 (UTC)Reply[reply]