Based on comments that I received on Wikimedia-l, I would like to invite
people to a casual online meetup one hour before the monthly WMF Metrics
and Activities Meeting.
There will be no set agenda. You can come with questions or ideas that you
would like to discuss. Please be willing to listen to questions and ideas
from other Wikimedians.
I will host the meeting with the Zoom software. You can join with software
or by using your phone. If you join by phone then your phone number will be
visible to other participants.
The primary language of the meeting will be English, but if people would
like to communicate in diverse languages then that is okay too. We can
facilitate translation by text chat. Many Wikimedians, myself included, are
multilingual in varying degrees, so we might try to have live
Here is information about how to connect:
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/136978210
Or iPhone one-tap :
Dial (for higher quality, dial a number based on your current
Argentina: +54 341 512 2188
Australia: +61 (0) 2 8015 2088 or +61 (0) 8 7150 1149
Canada: +1 647 558 0588
Hong Kong, China: +852 5808 6088
France: +33 (0) 1 8288 0188 or +33 (0) 7 5678 4048
Germany: +49 (0) 30 3080 6188 or +49 (0) 30 5679 5800
Israel: +972 (0) 3 978 6688
Italy: +39 069 480 6488
Japan: +81 (0) 3 4578 1488 or +81 524 564 439
Mexico: +52 229 910 0061 or +52 554 161 4288
Spain: +34 84 368 5025 or +34 91 198 0188
Sweden: +46 (0) 7 6692 0434 or +46 (0) 8 4468 2488
Russia: +7 495 283 9788
United Kingdom: +44 (0) 20 3051 2874 or +44 (0) 20 3695 0088
US: +1 408 638 0986 or +1 646 558 8665
Meeting ID: 136 978 210
International numbers available: https://zoom.us/u/ekaPibJIy
The first "Wikimedia Café" meetup will be on 30 August 2018, at 17:00 UTC /
Let me emphasize that the environment won't be like this
so please don't feel intimated if you are nervous about public speaking.
(If a conversation feels to me like it is becoming uncivil or intimidating,
then I will ask the debaters to quiet themselves or to move to somewhere
else.) The meeting will generally have an environment that is more like this
I anticipate that few people will come, which is okay. I hope that if you
come then you will enjoy the environment and conversation.
Until next time,
( https://meta.wikimedia.org/wiki/User:Pine )
I've been meaning to document this for a while.
If you're finding yourself visiting Special:Export/Import often for the
purpose of MediaWiki development there is a much better way to get content
into your local wiki for testing purposes.
This short video explains how MobileFrontend extension provides tooling to
help you debug live on-wiki content via $wgMFContentProviderClass 
Hope it saves someone lots of time!
Senior Software Engineer
One update regarding this.
We enabled using the new table for Special:Tags in several large wikis
which caused a massive improvement in the performance of the page. For
example loading Special:Tags on Wikidata used to take around a minute and
now it takes less than a second. English Wikipedia is down from ten seconds
to less than one and so on.
There is a lot of work needs to be done and maintenance scripts is being
ran to backpopulate the ct_tag_id column in change_tag table (If you want
to follow the progress, see https://phabricator.wikimedia.org/T193873) and
then we need start reading from the new table in mediawiki and finally we
can drop ct_tag column entirely. If you want to help in review, writing
code or anything, just let me know.
On Wed, 27 Jun 2018 at 15:15, Léa Lacroix <lea.lacroix(a)wikimedia.de> wrote:
> Hello all,
> Our team is refactoring some code around the change tags on Recent
> Changes. This can impact people using the database on ToolForge.
> Currently, the tags are stored in the table change_tag in the column
> In the next days, we will add a column ct_tag_id with a unique identifier
> for these tags. A new table change_tag_def that will store the tag id,
> the message, and more information like how many times this tag is used on
> the local wiki.
> On the long term, we plan to drop the column ct_tag since the tag will be
> identified with ct_tag_id.
> This change will happen on:
> - French Wikipedia: Monday July 2nd
> - All other wikis: from July 9th
> If there is any problem (trouble with saving edits, slow down of recent
> changes…) please create a subtask of T185355
> <https://phabricator.wikimedia.org/T185355> or contact Ladsgroup
> Léa Lacroix
> Project Manager Community Communication for Wikidata
> Wikimedia Deutschland e.V.
> Tempelhofer Ufer 23-24
> 10963 Berlin
> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
> unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt
> für Körperschaften I Berlin, Steuernummer 27/029/42207.
> Wikidata-tech mailing list
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
As you may have been aware, we've been working on changing how MediaWiki
stores comments: instead of having them as fields in each revision
(rev_comment), log entry (log_comment), and so on, we're storing the text
in a central "comment" table and referring to them by ID from other tables
(log_comment_id and so on).
We've been writing to the new fields and tables since the end of February
2018, and have back-populated them for old revisions, log entries, and so
on. Now we're starting to look at stopping the writes to the old fields,
starting soon with testing wikis such as test.wikipedia.org and also with
mediawiki.org. Other wikis will follow, likely in October after the DC
For the most part wiki users shouldn't notice any changes, however if you
notice something not displaying a comment or edit summary for new entries,
on these wikis let me know.
For users of the Data Services replicas, such as Toolforge, the views
currently simulate the old columns for you. However this may change in the
future. See https://phabricator.wikimedia.org/T181650#4581384 for details.
MediaWiki developers should make sure code accessing comment fields makes
use of the CommentStore class that was introduced in MediaWiki 1.30.
You can watch https://phabricator.wikimedia.org/T166733 (and any subtasks)
for more information on the deployment process.
Brad Jorsch (Anomie)
Senior Software Engineer
In the next couple weeks I'm planning to start switching our video
transcode output from WebM VP8/Vorbis to the newer WebM VP9/Opus profile,
which saves us about 38% on file size and bandwidth while retaining the
This will not affect what kinds of files you upload; only the scaled
transcoded output files used for playback will change. All modern browsers
that support VP8 support VP9 as well, and our player shim for Safari and IE
will continue to work.
All the details:
Comments and questions welcome!
tl;dr: Please refrain from adding new strings that require translations
to MediaWiki and deployed extensions until further notice.
Due to changes we are making in the way our translation systems process
data we will be temporarily disabling the auto deployment of newly
translated content until further notice. The goal of these changes will
be to improve the evaluation of content submitted to our translation
This means developers should not merge new translatable strings into
MediaWiki Core nor Wikimedia deployed extensions until we re-enable the
system. This is to prevent longer term issues where local wiki admins
overwrite a string and thus prevent updates from new and improved
We apologize for any inconvenience this delay in service may cause and
will alert you as soon as this maintenance is completed.
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
This is to inform you that there will be a datacenter switchover and
switchback on the next few weeks. The timeline's are
Services: Tuesday, September 11th 2018 14:30 UTC
Media storage/Swift: Tuesday, September 11th 2018 15:00 UTC
Traffic: Tuesday, September 11th 2018 19:00 UTC
MediaWiki: Wednesday, September 12th 2018: 14:00 UTC
Traffic: Wednesday, October 10th 2018 09:00 UTC
MediaWiki: Wednesday, October 10th 2018: 14:00 UTC
Services: Thursday, October 11th 2018 14:30 UTC
Media storage/Swift: Thursday, October 11th 2018 15:00 UTC
For the duration of the switchover (1 month), deployers are kindly
requested to refrain from large db schema changes and avoid deploying
any kind of new feature that requires creation of tables.
There will be a train freeze in the week of Sept 10th and Oct 8th.
The net effect of the switchover and switchback for volunteers is
expected to be some minutes of inability to save an edit. For readers,
everything will be as usual.
The tracking task for interested parties is
Alexandros Kosiaris <akosiaris(a)wikimedia.org>
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> will be holding
office hours the first Wednesday of each month, starting next week. Come
ask us anything about Wikimedia search!
We’re particularly interested in:
* Opportunities for collaboration—internally or externally to the Wikimedia
* Challenges you have with on-wiki search, in any of the languages we
But we're happy to talk about anything search-related.
Details for our next meeting:
Date: Wednesday, October 3rd, 2018
Time: 15:00 GMT / 08:00 PDT / 11:00 EDT / 17:00 CEST
Google Meet link: https://meet.google.com/vyc-jvgq-dww
*N.B.:* Google Meet System Requirements
See you there!
Sr. Software Engineer, Search Platform
I'd like to discuss potential improvements to www.mediawiki.org (the
front page itself), both regarding content and presentation, as I see
several issues with the current page.
I propose to discuss this in several stages:
* Defining audiences,
* defining content per group,
* defining presentation and layout.
My main intention are improvements to allow our audiences to better
find the relevant information that they are looking for.
We might not be able to make everything perfect but we can certainly
try to make it better?
If this sounds interesting, please take a look at
and let's discuss on the corresponding discussion page and work on
Andre Klapper | Bugwrangler / Developer Advocate