Hey folks, I'm helping Rebecca Maung (rmaung(a)wikimedia.org) distribute
this request. Her words below:
The Wikimedia Foundation is asking for your feedback in the annual
Community Insights survey. We want to know how well we are supporting
your work on- and off-wiki, and how we can change or improve things in
the future. The opinions you share will directly affect the current
and future work of the Wikimedia Foundation.
If you are a volunteer developer, and have contributed code to any
pieces of MediaWiki, gadgets, or tools, please complete the survey. It
is available in various languages and will take between 15 and 25
minutes to complete.
Follow this link to the survey:
If you have seen a similar message elsewhere and have already taken
the Community Insights survey, please do not take it twice.
You can find more information about this survey on the project page
and see how your feedback helps the Wikimedia Foundation support
contributors like you. This survey is hosted by a third-party service
and governed by this privacy statement. Please visit our frequently
asked questions page to find more information about this survey.
If you need additional help, send an email to surveys(a)wikimedia.org.
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting this week **Wednesday 3-4 pm UTC**
Questions can be asked in English, Persian, Spanish!
The Technical Advice IRC Meeting (TAIM) is a weekly support event for
volunteer developers. Every Wednesday, two full-time developers are
available to help you with all your questions about MediaWiki, gadgets,
tools and more! 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:
Hope to see you there!
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.
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.
(Note: This is only an early heads-up, to be prepared. Google Code-in
has NOT been announced yet, but last year, GCI mentors asked for more
time in advance to identify tasks to mentor. Here you are. :)
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Google Code-in (GCI) is an annual contest for 13-17 year old students.
GCI 2019 has not yet been announced but usually takes place from late
October to December. It is not only about coding: We also need tasks
about design, docs, outreach/research, QA.
Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors , add
your name to the mentors table, and start tagging tasks in Wikimedia
Phabricator by adding the #gci-2019 project tag.
We will need MANY mentors and MANY tasks, otherwise we cannot make it.
Last year, 199 students successfully worked on 765 tasks supported by
39 mentors. For some achievements from the last round, see
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and replace 2 uses of
Linker::link() from the list in T223010" style).
We also have more than 400 unassigned open #good-first-bug tasks:
Can and would you mentor some of these tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
, ask if you have any questions, and add your name to
Thanks (as we will not be able to run this without your help),
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
The current primary master for m1 (db1063), which is mostly for internal
services + etherpad isn't in a great healthy status: it is an old host,
which needs to be decommissioned and which is having disks failing pretty
much every week (plus disks on predictive failure).
We have decided to fail it over one of the newer hosts, db1135:
We have scheduled this switchover for: Tuesday 10th September at 16:00 UTC
This failover should be rather quick and would only take a few seconds
(while we re-load the haproxy) - during those few seconds, the following
services will be on read-only:
Communication will happen at #wikimedia-operations
If you are around at that time and want to help with the monitoring, please
When adding an extension requirement in extension.json, CI would most
probably complain since it does not clone the extension. It has to be
added to the CI configuration:
Add the requirement to the 'dependencies' mapping, then send for review.
Unfortunately one of the CI maintainers would have to approve and deploy it.
As a twist, I wrote a few bits that should make it possible for CI to
automatically process and clone the requirements and thus let us phase
out the central config. But that takes a bit of time to accomplish it
The long story:
MediaWiki extension registration lets one define a requirement upon
other extension/skins. If one writes an extension that extend
VisualEditor, most probably VisualEditor is required, the extension.json
would thus have:
Due to a bug, CI was no more failing when a requirement was not
fulfilled. In fact the extension would not even be enabled when running
That has been fixed via:
From now on, on master branch, CI would fail when a requirement is
missing. Unfortunately, CI does not magically clone the requirements
yet, so you would have to also add them to the CI config (see above).
Antoine "hashar" Musso