*TL;DR*: As part of the annual plan, we are moving Wikimedia Services to be
run in an orchestrated platform driven by a new build pipeline (yes, that
means containers). All new services for Wikimedia production must now start
using this platform. By the end of June 2019, we will have started
converting most remaining services. If you're responsible for an existing
or new service, please talk to us.
Some Wikimedia functionality is provided by services which operate
alongside MediaWiki, complimenting or supporting important features for
users. They currently mostly run directly on the "bare metal" shared
service clusters. The Deployment Pipeline "TEC3" annual plan involves
modernising production platforms, and we have a goal to move all of these
to the new platform we've been building.
There are many benefits of changing to use this platform:
* Adding/removing capacity is easy as easy as a deployment; consequently,
overall our clusters will be more scalable, and used more efficiently;
* Rolling deployments are the default, reducing disruption and increasing
dependability for readers, editors, and other end-users of our services;
* Deployments are automatically versioned, rather than relying on a manual
process from deployers;
* There is increased testing before the deployment, by means of a staging
* Developers no longer need to create and use deploy repos manually, the
pipeline does this.
If you are an owner, developer, or deployer of a current or forthcoming
Wikimedia production service, we need to hear from you.
Some services have already moved to this new platform, and others are
moving to it. We are building and improving the features as we discover
needs, so while we are confident now that services can run on this platform
run reliably, we still lack comprehensive documentation for this platform.
We are already in the process of creating it but we would like your input
to make sure that we are supporting all our stakeholders.
Please peruse the page about the deployment pipeline on wikitech and
poke around. What documentation do you actually want? How can we make your
work simpler and more straight-forward? Please file a task in
Phabricator or comment on the talk page.
 - https://phabricator.wikimedia.org/T198901
 - https://wikitech.wikimedia.org/wiki/Deployment_pipeline
 - https://phabricator.wikimedia.org/project/profile/2453/
 - https://wikitech.wikimedia.org/wiki/Talk:Deployment_pipeline
Deployment Pipeline team
*James D. Forrester* (he/him <http://pronoun.is/he> or they/themself
Wikimedia Foundation <https://wikimediafoundation.org/>
(A few days late, or a day early.)
Thank to Ebe123 and Daimona Eaytoy for their work on the Score and
AbuseFilter extensions. For years they've been working on these code bases
and consistently very responsive to bug reports, maintenance inquiries, and
offering help to other interested contributors.
Thanks for being awesome!
A change was deployed to the Wikitech config 2019-04-15T23:16 UTC
which prevents users from logging into the wiki with a username that
differs in case from the 'cn' value for their developer account.
This change is not expected to cause problems for most users, but
there may be some people who have historically entered a username with
mismatched case (for example "bryandavis" instead of "BryanDavis") and
relied on MediaWiki and the LdapAuthentication plugin figuring things
out. This will no longer happen automatically. These users will need
to update their password managers (or brains if they are not using a
password manager) to supply the username with correct casing.
The "wrongpassword" error message on Wikitech has been updated with a
local override to help people discover this problem. See
<https://phabricator.wikimedia.org/T165795> for more details.
Bryan, on behalf of the Cloud Services team
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Manager, Technical Engagement Boise, ID USA
irc: bd808 v:415.839.6885 x6855
While I am waiting for my other OOUI-related question to be answered, I
want to ask a brand new one!
Please see the code here: https://meta.wikimedia.org/wiki/User:Huji/OOUI2.js
Once you enable this script, you will be shown a dialog with two sets of
buttons. The first set has "Show Emotions" pre-selected, and you see two
buttons (Happy and Sad) in the second button group. You can click on those
buttons and you will see they get highlighted as you select them.
Next, you can click on "Show Animals" and that will swap the second row
with a new ButtonSelectWidget which has two choices (Cat and Dog). Again,
you can click on Cat or Dog and they will get highlighted and function
*Now the problem:* Click on "Show Emotions" again; it will bring back the
other ButtonSelectWidget, the one with Happy and Sad buttons; but these
buttons do not work anymore. If you click on the they won't get selected,
and indeed, the 'choose' even is not triggered for that ButtonSelectWidget
I also tried a different implementation in which instead of swapping the
contents of the panel, I recreate the ButtonSelectWidget each time, but
that also had the same problem.
Am I doing something wrong, or have I uncovered a bug in OOUI?
Is your organization interested in hosting and co-organizing the 2020
Wikimedia Hackathon? We are looking for co-organizers!
Details about the decision process can be found here:
Details about what it takes to organize a hackathon can be found here:
CHANGES FOR 2019
Because of changes to the Wikimedia Foundation budgeting process, we are
still working on confirming exact budgeting and requirements for this
event. Generally we expect similar size and budget to previous years, but
this is not finalized.
We are open & encouraging to bids from anywhere, but locations outside
of Europe and the USA will be given extra weight.
Focus areas will be defined much further in advance, however
participants can work on whatever they like related to Wikimedia Technology
We are continuing to work on changes around our newcomer support and
onboarding as well as our mentoring programs - this will continue to
develop until the event. At the same time we are still maintaining
additional focus on providing a well-facilitated and organized meeting
space for groups and the most active volunteers in the developer community
to collaborate face to face, with appropriate representation of Foundation,
affiliates, and volunteers, to discuss the future of Wikimedia technologies
We hope to expand our scholarship program to include more participants
from outside of the USA and Europe.
Ideally we will announce the host for 2020 by the Prague Hackathon in May.
If multiple chapters or organizations are interested, we hope to work
together to figure out the the best solution.
Any organizations interested in hosting should please create a Phabricator
ticket and associate it with the #Developer-Relations project, or email
rfarrand(a)wikimedia.org with a proposal or questions. Srishti and I are
happy to assist in creating the ticket if needed.
Please include as much information as possible from: Proposing a hackathon
Additionally if you are interested in working together on a smaller
technical event focused around newcomers in your region please also let me
know! We are in the initial stages of building a program around this.
Please email me at rfarrand(a)wikimedia.org with any questions or concerns. I
am not on the chapters@ list, so if there is anything that I should respond
to, make sure to keep me on CC. Also please forward this email anywhere
you think it might be useful.
Looking forward to hearing from you!
Events Program Manager
Technical Collaboration Team
It's coming close to time for annual appointments of community members to
serve on the Code of Conduct (CoC) committee. The Code of Conduct Committee
is a team of five trusted individuals plus five auxiliary members with
diverse affiliations responsible for general enforcement of the Code of
conduct for Wikimedia technical spaces. Committee members are in charge of
processing complaints, discussing with the parties affected, agreeing on
resolutions, and following up on their enforcement. For more on their
duties and roles, see
This is a call for community members interested in volunteering for
appointment to this committee. Volunteers serving in this role should be
experienced Wikimedians or have had experience serving in a similar
The current committee is doing the selection and will research and discuss
candidates. Six weeks before the beginning of the next Committee term,
meaning 23th of April 2019, they will publish their candidate slate (a list
of candidates) on-wiki. The community can provide feedback on these
candidates, via private email to the group choosing the next Committee. The
feedback period will be two weeks. The current Committee will then either
finalize the slate, or update the candidate slate in response to concerns
raised. If the candidate slate changes, there will be another two week
feedback period covering the newly proposed members. After the selections
are finalized, there will be a training period, after which the new
Committee is appointed. The current Committee continues to serve until the
feedback, selection, and training process is complete.
If you are interested in serving on this committee or like to nominate a
candidate, please write an email to techconductcandidates AT wikimedia.org
with details of your experience on the projects, your thoughts on the code
of conduct and the committee and what you hope to bring to the role and
whether you have a preference in being auxiliary or constant member of the
committee. The committee consists of five members plus five auxiliary
members and they will serve for a year; all applications are appreciated
and will be carefully considered. The deadline for applications is end of
day on 20th of April, 2019.
Please feel free to pass this invitation along to any users who you think
may be qualified and interested.
Amir on behalf of the CoC committee
Am 12.04.19 um 05:18 schrieb David Sharpe:
> I think there was an extra text paste affecting this portion of the document:
> “Motivation: Motivation: These principles aim at the /equity/ goal set by
> the /Movement Strategy Outcomes/ and reflected in the Wikimedia
> Foundation's /Goals and Priorities/: /"Modernize our product experience/",
> particularly by /"integrating content from Commons, Wikidata, Wikisource and
> other projects into Wikipedia”/."
Double motivation :)
fixed, thank you.
Principal Software Engineer, Core Platform
We are happy to announce that the 13th DBpedia Community Meeting will be
held in Leipzig, Germany on 23rd of May, 2019. DBpedia will be part of
the Language, Data and Knowledge conference (LDK). This new biennial
conference series aims at bringing together researchers from across
disciplines. Further information on the conference program and its
associated events can be found here: http://2019.ldk-conf.org/.
* Highlights *
- Keynote #1: Making Linked Data Fun with DBpedia by Peter Haase, metaphacts
- Keynote #2: From Wikipedia to Thousands of Wikis – The DBkWik
Knowledge Graph by Heiko Paulheim, University of Mannheim
- DBpedia Association hour
- DBpedia Showcase Session
* Quick Facts *
- Web URL: http://wiki.dbpedia.org/meetings/Leipzig2019
- When: May 23rd, 2019
- Where: Mediencampus Villa Ida, Poetenweg 28, 04155 Leipzig
- Call for Contribution: Submit your proposal in our form
- Registration: You need to buy a ticket via
* Side Event *
The Thinktank and Hackathon “Artificial Intelligence for Smart
Agriculture” is part of the DBpedia meeting. The activity is supported
by the projects DataBio, Bridge2Era as well as CIAOTECH/PNO. The goal of
the thinktank & hackathon is to build new ideas and small tools, which
are able to demonstrate the use auf AI within the agricultural domain
and a sustainable bioeconomy. Especially, the use and impact of linked
data for AI components will be one part of the event. Further
discussions about future collaborations and ideas of the future of
AI-based Smart Agriculture will be held. Please submit your ideas and
We are looking forward to meeting you in Leipzig!
Your DBpedia Association