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.
A committee member provided the following comment:
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.
"Wikinews 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.
I oppose for now. The Dusun language don't even have a Wikipedia (current request). It seems that there's no interested community and the development project has little content. I do think that they should concentrate first in a Wikipedia --if it gets approved-- and then, when a sizable community and manpower is avalaible, they should request the creation of other sister projects. Rationale isn't convincing and does not provide any useful information nor demostrates a "need". -- Dferg☎ talk 16:27, 21 April 2011 (UTC)Reply[reply]
Oppose Low activity on beta Wikipedia, there's absolutely not a community that can grow up the project and Wikinews really needs daily contributes. --Gce (talk) 21:54, 27 May 2017 (UTC)Reply[reply]
Strong oppose There is no single "Dusun" language, the ISO code [dtp] define it as "Kadazan Dusun": https://iso639-3.sil.org/code/dtp. My best recommendation is to rename the project if there are any contributors who want to develop these project, or simply cancel the proposal since there is no factual single entity of "Dusun language". (Dirk Gret (talk) 15:05, 20 September 2022 (UTC))Reply[reply]
Comment There is no rule which states is mandatory to a language community to have a Wikipedia before being allowed to ask for another language edition of other sister projects. Maybe this decision of chosing Wikinews first instead of Wikipedia would be strange, but you should ask proposer(s) the reason behind their decision before opposing. --Zerabat (discusión) 01:34, 1 March 2018 (UTC)Reply[reply]