On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote:
> We will be holding this brownbag in 25 minutes. The Bluejeans link has
I'm not familiar with bluejeans and maybe have missed a transition
because I wasn't paying enough attention. is this some kind of
experiment? have all meetings transitioned to this service?
anyway, my immediate question at the moment is how do you join without
sharing your microphone and camera?
am I correct thinking that this is an entirely proprietary stack
that's neither gratis nor libre and has no on-premise (not cloud)
hosting option? are we paying for this?
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
Following the recent outage, we've had a new series of complaints
about the lack of improvements in CX, especially related to
server-side activities like saving/publishing pages.
Now, I know the team is involved in a long-term effort to merge the
editor with the VE, but is there an end in sight for that effort? Can
I tell people who ask "look, 6 more months then we'll have a much
better translation tool"?
Is there a publicly available roadmap for this project and more
generally, for CX?
Running all tests for MediaWiki and matching what CI/Jenkins is running
has been a constant challenge for everyone, myself included. Today I am
introducing Quibble, a python script that clone MediaWiki, set it up and
run test commands.
It is a follow up to the Vienna Hackathon in 2017. We had a lot of
discussion to make the CI jobs reproducible on a local machine and to
unify the logic at a single place. Today, I have added a few jobs to
An immediate advantage is that they run in Docker containers and will
start running as soon as an execution slot is available. That will be
faster than the old jobs (suffixed with -jessie) that had to wait for a
virtual machine to be made available.
A second advantage, is one can exactly reproduce the build on a local
computer and even hack code for a fix up.
The setup guide is available from the source repository
The minimal example would be:
git clone https://gerrit.wikimedia.org/r/p/integration/quibble
python3 -m pip install -e .
A few more details are available in this post on the QA list:
Please give it a try and send issues, support requests to Phabricator:
Next week I will polish up support for MediaWiki extensions and skins
and eventually Quibble will take over most of the CI jobs running for
MediaWiki related projects.
Antoine "hashar" Musso
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting again **the day after tomorrow,
Wednesday 3-4 pm UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki.org/wiki/Technical_
Hope to see you there!
Michi (for WMDE’s tech team)
Michael F. Schönitzer
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/681/51985.