The committee has finished selecting new members and the new committee
candidates are (In alphabetical order):
- Amir Sarabadani
- Kunal Mehta
- Martin Urbanec
- Tony Thomas
And auxiliary members will be (Also in alphabetical order):
- Ariel Glenn
- Effie Mouzeli
- Nuria Ruiz
You can read more about the members in the mediawiki.org page
The changes compared to last term are:
- Kunal Mehta is joining the main CoC committee
- Ariel Glenn is coming back to auxiliary committee
- Effie Mouzeli is joining auxiliary committee for the first time
- Tonina Zhelyazkova is leaving the committee
- Matanya and Tpt are leaving the auxiliary committee
- I won't run for the chair this year.
This is not the final structure. According to the CoC
the current committee publishes the new members and calls for public
feedback for *six weeks* and after that, the current committee might apply
changes to the structure based on public feedback.
Please let the committee know if you have any concern regarding the members
and its structure until *26 May 2021* and after that, the new committee
will be in effect and will serve for a year.
Amir, On behalf of the Code of Conduct committee
I figure this might be of interest to some here: we could make
sponsorship of contributions more evident by adding a git commit
Sponsored-by: Name Of Sponsoring Entity
Obviously this would be optional, and only used by those who want to.
Spelled out in a little more detail:
WMF release engineering team | he/him or they/them
"Imagine a world in which every single human being can freely share in
the sum of all knowledge."
Oh, hi there
tl;dr: we’re still moving MediaWiki into Kubernetes in Wikimedia
Production; there are resources on Wikitech for folks interested in
learning more about the specifics of our Kubernetes pipeline.
Kubernetes is the future deployment platform for most Wikimedia code.
The developer and deployment experience under Kubernetes will
(hopefully) be easier and safer and developers will have more
The first Wikimedia production service (Mathoid) moved to Kubernetes
in July, 2018. Today there are 25 services using our production
Kubernetes infrastructure serving 30,000 requests per second, about
67-ish% of our overall traffic. All services are deployed by their
service owners without much oversight.
Our Docker registry contains 311 Docker images with 7,690 tags. Our
production images are built via Continuous Integration (CI), using our
deployment pipeline. Blubber and PipelineLib were introduced in
2018 to allow developers to specify how they wanted their CI to run
and when to publish images to our shared registry.
Now we’re in the process of applying all we’ve learned from our
service migration to the MediaWiki migration to Kubernetes.
* Open Container Initiative (OCI)-compatible MediaWiki images
* Built, tested, and promoted by the image pipeline
* Deployed to Kubernetes via Helm
* Serving production traffic
* Development - Standard platform for development and production
* Deployment - Safer, simpler, industry standard
* Production - Increased capacity, redundancy, reliability
* We’re building Docker images and Helm charts
** Release Engineering crammed all 184 branched extensions, 4 skins,
vendor, and core Mediawiki code into a single image alongside our
massive localization of 435 languages
** ServiceOps is working on php-fpm, apache, nutcracker, mcrouter and
envoy images and their corresponding helm charts
* We’re making our Kubernetes better
** ServiceOps has upgraded our base images and Kubernetes cluster
* Figuring out how deployments work
** Backports, security releases, and train
* Figuring out how image upgrades work
** Is a php-fpm upgrade a deployment now? What does that look like?
* Figuring out how our Wikimedia configuration changes
** Currently a change to configuration requires a code change, does
this code change kick off a whole image build?
Kubernetes will be very impactful in our production services and we
would like to encourage those interested in this change to become
familiar with its concepts.
Please have a look at our collected Wikitech Kubernetes education
resources, tutorials, and guides. Add material if you have had a
good experience with a class or tutorial.
Otherwise stay tuned and watch that page for additional resources to
be added. You will hear from us again as we have additional things to
Tyler Cipriani (he/him) (On behalf of all the fine folks working on
Kubernetes for MediaWiki)
Engineering Manager, Release Engineering
*subject line reference: https://en.wikipedia.org/wiki/The_More_You_Know
On Tuesday June 1st at 7:00 UTC we will switch Gerrit from Java 8 to
Java 11. The system will be briefly unavailable has it restarts with the
The window would be roughly half an hour, the service interruption
should be just a few minutes. If anything is suspicious we will roll
back to Java 8 and restart which would lead another short interruption.
The task is: https://phabricator.wikimedia.org/T268225
Antoine "hashar" Musso