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.
Once the criteria are met, the language committee can proceed with the approval.
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.
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.
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.
"Wikibooks talk" (the discussion namespace of the project namespace)
Enable uploads
no
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.
"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.
Oppose - This is one out of 5 proposals for a Gilaki wiki. Though Limburgish has so many proposals too there's a difference. There's no activity and Gilaki does not seem to be ready get for a Wikibooks, a Wikinews, a Wikiquote, a Wiktionary nor a Wikiversity. Maybe this will change in the future but not now. If there's any activity shown, I'll become in favour of this request. --OosWesThoesBes 15:56, 1 March 2008 (UTC)Reply[reply]
Oppose - Please make sure the Gilaki Wikipedia is much larger and come back later. --Jeroen 02:10, 21 July 2008 (UTC)Reply[reply]
Oppose - even Gilaki Wikipedia is almost dead. --Z 18:20, 9 May 2012 (UTC))Reply[reply]
Oppose - Gilaki Wikipedia doesn't have good situation right now. Why do you need to establish wikibooks?. So in this moment we need to expand it more. Come back when you made it larger. thanks. TheStrayDog (talk) 12:29, 10 July 2017 (UTC)Reply[reply]
Hoi, please check out the most used MediaWiki messages, they and all the other MediaWiki messages and the messages of the WMF extensions need to be localised. GerardM 12:56, 14 January 2008 (UTC)Reply[reply]
Localisation is still extremely poor: 3% of the most often used messages, 1% of all core messages translated. Siebrand 17:16, 18 May 2008 (UTC)Reply[reply]
Currently 0.92% of the MediaWiki messages and 0.15% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Please help us help your language by localising at Betawiki. This is the recent localisation activity for your language. Thanks, GerardM 10:24, 27 July 2008 (UTC)Reply[reply]
Currently 0.89% of the MediaWiki messages and 0.10% of the messages of the extensions used by the Wikimedia Foundation projects have been localised. Localisation of these messages is a requirement before your request is finally assessed. This is the recent localisation activity for your language. Thanks, GerardM 11:00, 12 November 2008 (UTC)Reply[reply]