Discuss the creation of this language project on this page. Votes will be ignored when judging the proposal. Please provide arguments or reasons and be prepared to defend them (see the Language proposal policy).
The language committee needs to verify the language is eligible to be approved.
Check that the project does not already exist (see list).
Ensure the requested language is sufficiently unique that it could not exist on a more general wiki.
Ensure that there are a sufficient number of native editors of that language to merit an edition in that language.
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.
"Wikipedia 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.
2.The language must ordinarily have a valid ISO 639 1–3 code (search).
If there is no valid ISO 639 code, you must try to obtain one. The Wikimedia Foundation does not seek to develop new linguistic entities; there must be an extensive body of works in that language. The information that distinguishes this language from another must ordinarily be sufficient to convince standards organizations to create an ISO 639 code.
Under very unusual circumstances, and provided there has first been an effort to obtain an ISO 639–3 code, the Language Committee may be willing to consider projects in languages having a valid BCP 47 language tag. Languages having neither an ISO 639 code nor a BCP 47 tag will not be considered under any circumstances.