[go: nahoru, domu]

Page MenuHomePhabricator

Add Tulu (tcy) to "Primary language community on wiki" list
Closed, ResolvedPublic

Event Timeline

Should this be a part of the new wiki creation procedure ( https://wikitech.wikimedia.org/wiki/Add_a_wiki )?

I suppose it could be, but it's weirdly specific. The Scholarships application keeps a local database table called "language_communities" that is used to present the select list on the application form and then add a community "size" attribute that is used in reporting on the backend. The list we have today came from some spreadsheet that was maintained by WMF staff. Ideally we would get this data by querying some API on a Wikimedia site.

Change 332822 had a related patch set uploaded (by BryanDavis):
Add Tulu (tcy) community

https://gerrit.wikimedia.org/r/332822

Change 332822 merged by jenkins-bot:
Add Tulu (tcy) community

https://gerrit.wikimedia.org/r/332822

Change 332826 had a related patch set uploaded (by BryanDavis):
Add Tulu (tcy) to Communities

https://gerrit.wikimedia.org/r/332826

Change 332826 merged by jenkins-bot:
Add Tulu (tcy) to Communities

https://gerrit.wikimedia.org/r/332826

Mentioned in SAL (#wikimedia-operations) [2017-01-18T21:32:17Z] <bd808> Updated wikimania-scholarships to 29ba0ec "Add Tulu (tcy) to Communities" (T155666)

bd808 claimed this task.

Screen Shot 2017-01-18 at 14.33.18.png (82×689 px, 12 KB)

Should we have a follow-up bug to make this list dynamically generated from action=sitematrix or something?

Should we have a follow-up bug to make this list dynamically generated from action=sitematrix or something?

I wouldn't be against it. We would still need some way to add the "small", "medium", "large" classifications that are used in the reporting however. One thing that could certainly be done would be to get rid of the static class that has duplicate data and instead pull the list from the DB. I don't remember exactly, but I think the PHP class predated the DB table. We could also add a UI for admins to add/change the DB values so things like this don't require a code deployment.