Hi,
The language committee and WMF Board have approved the creation of Wikipedia in Adyghe.
Language code: ady
Site URL: ady.wikipedia.org
Project name: Википедие
Project namespace: Википедие
Project talk namespace: Википедием и тегущыӀэн
Project logo: http://commons.wikimedia.org/wiki/File:Wikipedia-logo-v2-ady.png
Timezone: UTC
Language name: адыгабзэ
Enable uploads: yes
Thank you.
Meta reference: https://meta.wikimedia.org/wiki/Requests_for_new_languages/Wikipedia_Adyghe
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Krenair | T125501 Create Adyghe Wikipedia | |||
| Resolved | None | T122513 Another Wikidata issue with addWiki: Cannot spawn child: PopulateSitesTable |
Just a note regarding uploads (@Nemo_bis might have more info). It was my
understanding that projects without a valid exemption doctrine policy will
not be allowed to do local uploads, so I'm not sure if uploading should be
enabled.
No problem with me, whatever the policy says is OK. When in doubt, I support Commons.
The pertinent policy pages/discussions are https://meta.wikimedia.org/wiki/Requests_for_comment/Disable_local_uploads_on_smaller_wikis and https://meta.wikimedia.org/wiki/Local_uploads_policy, I believe. The policy is still marked as "draft", though.
Change 267886 had a related patch set uploaded (by Alex Monk):
Add ady language to DNS
@jcrespo: fyi, another DB creation happening... Probably not today for obvious reasons, but soon?
Thanks for the CC. Aside from the obvious, no blocker as it would go to the the default s3 shard. Pleas ping me again on IRC when you are going to do it.
Change 268004 had a related patch set uploaded (by Dereckson):
Initial configuration for ady.wikipedia
Do they wish to enable by default the Visual Editor?
What are their desiderata about Flow?
Change 268016 had a related patch set uploaded (by Dereckson):
RESTBase and Labs DNS configuration for ady.wikipedia
We're also not encouraging new wikis to take on Flow as it's not ready for a from-scratch environment.
@greg: So I think we can schedule this for after wmf.13 arrives on wikipedias on Thursday 11th... Unless we want to backport the patches and get it done earlier than that.
I was going to add something like this to the calendar:
{{#invoke:Deployment schedule|row
|when=2016-02-11 14:00 SF
|length=1
|window=[[phabricator:T125501|Adyghe Wikipedia creation]]
|who={{ircnick|Krenair|Alex}}
|what=On terbium, run mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki ady wikipedia adywiki ady.wikipedia.org
{{gerrit|268004}} - make wikiversions rebase, merge
On mira:
* Pull, merge change
* Run sync-dir dblists; sync-wikiversions; sync-file langlist; sync-file wmf-config/InitialiseSettings.php; sync-file w/static/images/project-logos/adywiki.png
* Run mwscript extensions/WikimediaMaintenance/filebackend/setZoneAccess.php adywiki --backend=local-multiwrite
* Run updateinterwikicache
}}|But, I just noticed these steps for new languages which I think we missed:
Make sure that the language code appears in UniversalLanguageSelector's langdb (file data/langdb.yaml).
Add the language code to the ContentTranslation registry - cxserver repository, files config.dev.yaml and config.prod.yaml, in the source and target sections in each.
Not sure where that ULS file is.... @Nikerabbit?
@aude, should this start off as being part of wikidataclient.dblist?
@Krenair langdb is at https://github.com/wikimedia/jquery.uls/blob/master/data/langdb.yaml#L7-L9 - it already contains ady.
Okay. So for future reference, we need to deploy the wikidataclient.dblist change *before* running addWiki.php, we need https://gerrit.wikimedia.org/r/#/c/270150/, and we may need to either:
so that CirrusSearch's updateSearchIndexConfig script doesn't timeout (while trying to connect between elastic nodes) and break everything.
Also, I need to track down that stupid bug in the newprojects list code (part of addWiki.php) that results in "for a in адыгабзэ" (missing "Wikipedia" between "a" and "in"). (Edit: This became T126705, where I decided that the stupid thing may in fact be me.)
Yeah, they changed the way the interwiki cache is stored and didn't leave any way to generate a new one in production.
Change 270327 had a related patch set uploaded (by Alex Monk):
Update interwiki.php for adywiki
So basically, after I'm done deploying the dumpInterwiki patch for it: