Requests for new languages/Wikivoyage Gilaki

From Meta, a Wikimedia project coordination wiki
submitted verification final decision

This proposal has been rejected.
While this request has technically been rejected, in reality this is a request that has been sitting open or on hold for a long time with little evidence of a community coming together to build a project. If a community comes together in the future and makes a new request, LangCom would consider that new request without prejudice.

A committee member provided the following comment:

Only a main page and one content page were created in this test. Test can remain on Incubator, and if it ever becomes reasonably active, then the community can make a new request. StevenJ81 (talk) 14:04, 11 October 2019 (UTC)[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.
  • The community needs to complete required MediaWiki interface translations in that language (about localization, translatewiki, check completion).
  • The community needs to discuss and complete the settings table below:
What Value Example / Explanation
Proposal
Language code glk (SILGlottolog) A valid ISO 639-1 or 639-3 language code, like "fr", "de", "nso", ...
Language name Gilaki Language name in English
Language name گيلکي Language name in your language. This will appear in the language list on Special:Preferences, in the interwiki sidebar on other wikis, ...
Language Wikidata item Q33657 - item has currently the following values:
Item about the language at Wikidata. It would normally include the Wikimedia language code, name of the language, etc. Please complete at Wikidata if needed.
Directionality no indication Is the language written from left to right (LTR) or from right to left (RTL)?
Links Links to previous requests, or references to external websites or documents.

Settings
Project name ويکي‌سفر "Wikivoyage" in your language
Project namespace ويکي‌سفر usually the same as the project name
Project talk namespace گب_ويکي‌سفر "Wikivoyage talk" (the discussion namespace of the project namespace)
Enable uploads yes 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.
Optional settings
Project logo This needs to be an SVG image (instructions for logo creation).
Default project timezone Asia/Rasht "Continent/City", e.g. "Europe/Brussels" or "America/Mexico City" (see list of valid timezones)
Additional namespaces For example, a Wikisource would need "Page", "Page talk", "Index", "Index talk", "Author", "Author talk".
Additional settings Anything else that should be set
submit Phabricator task. It will include everything automatically, except additional namespaces/settings. After creating the task, add a link to the comment.

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.

Proposal[edit]

Discussion[edit]

Arguments in favor[edit]

@Pirsharafshah: That's fine, and it's good to try to get your test marked as "eligible". However, you need to get a community together to start building a test project at incubator:Wy/glk. StevenJ81 (talk) 14:03, 25 April 2017 (UTC)[reply]

Arguments aganist[edit]

  • Oppose -- this language is very small, also because this is one of Iranian language which is not Useful in this country, because everyone who are going to school in Iran have to speak and write farsi..--Bloch khan (talk) 11:58, 30 September 2017 (UTC)[reply]

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.