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.
@К. П.1: Sorry if I missed this page for more than 1 year, but I think saying "thank you very much" isn't helpful, if Russian Wikinews is already acting what the proposed "Tatar Wikinews" is, then creating tt.wikinews.org is weird and I suggest to migrate the test project back to ruwikinews. But if there has benefit to separately launch a tt.wikinews, then these ruwikinews pages in Tatar should consider migrating to the tt.wikinews, and after that, delete on ruwikinews. --Liuxinyu970226 (talk) 04:33, 5 August 2021 (UTC)Reply[reply]
@Liuxinyu970226: Thanks for the question. I wouldn't request Tatar Wikinews at the moment, though would love seing this materialize. Most Tatar Wiki-volunteers concentrate own's efforts on Wikipedia, some self-exiled to Wikidata, so piggy-backing on Russian Wikinews' friendly offering seems most effective for the time being. Writing a Russian version first is easy, especially when the team helps with making it neutral and newsy, so post-translated Tatar copy is a much better read. --Frhdkazan (talk) 20:37, 29 August 2021 (UTC)Reply[reply]
