TLDR: if browsing a map for French wiki, and a city only has a Russian and
Chinese name, which one should be shown? Should the city name have
different rules from a store or a street name? ...
I have been hacking to add unlimited multilingual support to Wikipedia
maps, and have language fallback question: given a list of arbitrary
languages for each map feature, what is the best choice for a given
I know Mediawiki has language fallbacks, but they are very simple (e.g. for
"ru", if "ru" is not there, try "en").
Some things to consider:
* Unlike Wikipedia, where readers go for "meaning", in maps we mostly need
* Alphabets: Latin alphabet is probably the most universally understood,
followed by...? Per target language?
* Politics: places like Crimea tend to have both Russian and Ukrainian
names defined, but if drawing map in Ukrainian, and some feature has
Russian and English names, but not Ukrainian, should it be shown with the
Russian or Ukrainian name?
* When viewing a map of China in English, should Chinese (local) name be
shown together with the English name? Should it be shown for all types of
features (city name, street name, name of the church, ...?)
Here are the minutes from this week's ArchCom meeting. You can also find the
minutes at <https://www.mediawiki.org/wiki/Architecture_committee/2017-02-08>.
See also the ArchCom status page at
<https://www.mediawiki.org/wiki/Architecture_committee/Status> and the RFC board
Here are the minutes, for your convenience:
* ArchCom plans to take part in Scrum of Scrums in the future
* IRC discussion about database schema improvements next week, pending
confirmation. This is a follow-up to [[phab:T149534]].
* [[phab:T66214]]: Define an official thumb API: Gergö concerned about third
party install efficiency.
* [[phab:T122942]]: Support language variants in the REST API: Current
discussion is primarily about path prefix vs. Accept-Language header.
* [[phab:T155813]]: Decide on storage and delivery method for TemplateStyles
CSS: Lively discussion, pinged Parsing team.
packages was selected for the developer whishlist. There has been some
discussion in the last week, but more input is needed. One open topic is how
this relats to ResourceLoader.
* [[phab:T129842]]: Launch the Wikimedia "Code Review Special Interest Group"
has gained some tracktion. Quim is looking for participants!
* Schema migration for the oldimage table pending implementation: [[phab:T28741]]
Principal Platform Engineer
Gesellschaft zur Förderung Freien Wissens e.V.
We had a short downtime of CI between roughly 3am and 9am UTC that
caused roughly 2/3 of triggered jobs to fail cloning.
The reason is we deployed additional zuul-merger instances (which takes
your patches, merge it on tip of branch and then expose the result to
jobs) but the git-daemon exposing the repositories was not started.
I respawned the git-daemon and it all works properly now. I am doing a
recheck and CR+2 again all patches that got affected.
Antoine "hashar" Musso
We're in progress of deploying a small change to the video scalers,
which should improve availability of newly uploaded video and audio files.
The queue will now be split in two, one which covers low-resolution
conversions for relatively short files, and one which covers long files and
high-resolution conversions. When there's a flood of large uploads, other
new files should still go through the high-priority queue while the large
uploads and HD conversions may back up on the low-priority queue.
The queue-runner side is updated now (done during the 'puppet SWAT'
deployment window), with the MediaWiki side ready to roll around 19:00 UTC
(11am Pacific time, regular SWAT deployment window).
Today I was checking mediawiki/core in github:
And number of contributors is now 400. It might be a little more if we
count SVN era.
To me, it's an important milestone. More important than number of commits
or releases. It's about people not numbers or lines of code.
---------- Forwarded message ----------
From: Victoria Coleman <vcoleman(a)wikimedia.org>
Date: Tue, Feb 7, 2017 at 9:22 PM
Subject: [Wikimedia-l] Wikimedia Cloud Services: new team, new name,
Starting in April 2017, we will be taking a number of projects related to
services we are offering "in the cloud" and creating a new team, Wikimedia
Cloud Services (WMCS), to support a more unified approach to these efforts.
The sub-teams currently managing these efforts - the Labs sub-team within
the Wikimedia Technical Operations team and the Tool Labs support sub-team
from the Community Tech team - will be merged to form this new team.
Wikimedia Cloud Services will be a new team in the Technology Department of
the Wikimedia Foundation reporting to Victoria as the Foundation's Chief
Technology Officer (CTO). This team is being formed based on a proposal
made by the members of the Labs sub-team and the Tool Labs support sub-team.
The new team will be managed by Bryan Davis, who previously managed the
Reading Infrastructure and Community Tech teams before helping found the
Tool Labs support team in 2016. Chase Pettet, formerly manager of the Labs
team, is taking on the new role of Lead Operations Engineer. Andrew Bogott,
Yuvaraj Pandian, and Madhumitha Viswanathan are transferring in their
existing roles from the former Labs team.
The WMCS team will maintain and extend the existing Wikimedia Labs
infrastructure as a service platform, the Tool Labs platform as a service <
https://en.wikipedia.org/wiki/Platform_as_a_service> project, and many
additional supporting technologies used in the cloud environment. The new
team is excited to continue supporting developers who create innovative
solutions to further the free knowledge movement, and will continue to
partner with the larger Wikimedia volunteer community to manage the
physical and virtual resources that power the environment and provide
technical support to volunteer developers and other Wikimedia Cloud
This new team will focus on three areas of ongoing support and improvement:
Providing a stable and efficient hosting platform
Creating and maintaining services that empower the creation and operation
Delivering technical and community support for users of the products
This new team will soon begin working on rebranding efforts intended to
reduce confusion about the products they maintain. <
https://wikitech.wikimedia.org/wiki/Labs_labs_labs> This refocus and
re-branding will take time to execute, but the team is looking forward to
Stay tuned for more announcements, and as always Community members are
encouraged to participate on labs-l(a)lists.wikimedia.org, <
https://phabricator.wikimedia.org/project/profile/832/>Phabricator and the
#wikimedia-labs IRC channel.
Victoria & Wes
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
New messages to: Wikimedia-l(a)lists.wikimedia.org