The language committee has approved the creation of Wikipedia Khowar.
https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Khowar
Language code: khw
Site URL: khw.wikipedia.org
Project name: ویکیپیڈیا
Project namespace: ویکیپیڈیا
Project talk namespace: تبادلۂ خیال ویکیپیڈیا
Project logo: https://commons.wikimedia.org/wiki/File:Wikipedia-logo-v2-khw.svg
Timezone: UTC
Local file uploads: disabled
Thank you.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Invalid | MF-Warburg | T160865 Create Wikipedia Khowar | |||
| Declined | None | T160870 Prepare and check storage layer for khw.wikipedia |
Change 343572 had a related patch set uploaded (by Dereckson):
[operations/dns] DNS for khw. and kbp. projects
Change 343584 had a related patch set uploaded (by Dereckson):
[operations/puppet] RESTBase: add kbp. and khw.wikipedia
Change 343585 had a related patch set uploaded (by Dereckson):
[operations/mediawiki-config] Add khw.wikipedia logos to static resources
No, but it should be created, otherwise WDQS can't decode URLs to the corresponding Wikipedia name.
Interwikis need to be imported to Wikidata as well: https://www.wikidata.org/wiki/Wikidata:Bot_requests#Import_interwikis_from_Khowar_Wikipedia
Okay. If you've a LDAP login, you can edit this procedure page to add this requirement, so we can be sure it will be checked next times too. Thanks to have created it.
Mentioned in SAL (#wikimedia-operations) [2017-03-20T20:52:24Z] <mutante> DNS - new Wikipedias "khw" (Khowar) and "kbp" (Kabiye) created (T160868) (T160865) ( on ns0/ns1: authdns-gen-zones -f /srv/authdns/git/templates /etc/gdnsd/zones && gdnsd checkconf && gdnsd reload-zones to trigger template recreation after edit to langs.tmpl)
dig khw.wikipedia.org ;; QUESTION SECTION: ;khw.wikipedia.org. IN A ;; ANSWER SECTION: khw.wikipedia.org. 600 IN A 208.80.154.224
Change 343585 merged by jenkins-bot:
[operations/mediawiki-config@master] Add khw.wikipedia logos to static resources
Mentioned in SAL (#wikimedia-operations) [2017-03-27T13:20:44Z] <dereckson@tin> Synchronized static/images/project-logos/: Add khw.wikipedia logos to static resources (T160865) (duration: 00m 43s)
Mentioned in SAL (#wikimedia-operations) [2017-03-28T22:19:56Z] <mutante> DNS - creating new language "dty" (T160865) - running "authdns-gen-zones -f /srv/authdns/git/templates /etc/gdnsd/zones && gdnsd checkconf && gdnsd reload-zones" to trigger re-creation of zone files after change in langs.tmpl. (gerrit:345077) | https://www.ethnologue.com/language/dty
last comment on wrong ticket - should have been 161529 - can't delete it because stashbot made it for me.
Please don't proceed with the creation of the wiki at the moment.
A more detailed explanation will be given soon.
Change 343584 abandoned by Dereckson:
RESTBase: add kbp. and khw.wikipedia
Reason:
One wiki declined, one wiki stalled on language.
Declaiming you (because you aren't working at the task), explanation would come from @MF-Warburg soon.
An explanation has been posted at
https://lists.wikimedia.org/pipermail/langcom/2017-April/001207.html
The next step seems so to find more contributors interested to write
articles in this language and have them contribute on Incubator.
Respected sirs, as you know that I am test admin and tirelessly working since 2008 for creating wikipedia in khowar, i have contributed more than 7000 edits in this project, i have translated most used interface msgs for this project. We are using Internet cafe to write articles for this project, if somebody is also using the same IP and contributing in khowar wiki project, then this is not my fault. On the basis of one IP address one project can not be declined after its approval, this is not fair, this is discrimination with the khowar community. The langcom to check these things before approval and before Phabricator task, we have already received many congratulations messeges for the approval of this project. This is embarrassing for the community. After approval we have issued to press release. I request you all to restore the phabricator task to its original position subject to the condition that the khowar community contribute more articles in khowar language within one month and complete the task, I assure you sir, trust me and give one month time to engage more regular contributors to complete the task. Your kind cooperation will be highly be appreciated. Please restore the Phabricator Task to its original position subject to condition that the Khowar Community shall contribute more ariticles and complete the task within one month Sharp. cheers and Regards
@Rachitrali Status, priority and assignee of a task reflects technical reality and planification, not wishes. As such, please address your concerns with langcom, but let the team handling the requests from the community handle the task properties.
Rachitrali, I suggest that you try to redirect the attention you gained to the Incubator project. That's probably a better use of your time than fighting the LangCom's decision. Please consider advertising https://translatewiki.net/wiki/Portal:Khw to involve people who aren't interested in contributing articles.
It's quite clear that trust in this proposal is not going to be recovered quickly, so it's pointless to keep the task open.
Nemo_biz thanks for your suggestions, at present what you suggest to do.
With Profound Regards Rehmat Aziz Chitrali
Please open the status from ''closed'' to ''stalled'' as we are working on this project.
@Rachitrali @Nemo_bis This task is a request to three specific group of people: 1. ops for DNS/Apache 2. someone with a deploy access willing to create the project 3. someone willing to write the config. When it's non controversial, we could add 4. people willing to help to triage issues. But here, it's now controversial, so if you aren't willing to do 1, 2 or 3, please don't engage in an open/close/prioritize war edit.
@Rachitrali We can't process your request without a LangCom green light per our policies. LangCom communicates using a mailing list, that's where you should send an explanation. We use Phabricator as a working tool, we want to get an overview of open tasks, because it's actionable somehow. Close status isn't a wish, it reflects real prioritization. But here, as LangCom doesn't use Phabricator to organize their approval work, there is nothing actionable, hence "stalled" isn't appropriated. So I suggest you reestablish the previous status "Close declined", and when the situation is solved at LangCom level, you or a LangCom member can reopen the task with a link to the new decision taken.
IMO, I also think that Stalled has more sense than Declined, as we may hope that a random Stalled task has 5~25% possible to be done.
This task is not stalled. It is invalid as long as the project isn't approved by Langcom anymore.