This is a quick note to highlight that in three weeks' time, the REL1_37
branch will be created for MediaWiki core and each of the extensions and
skins in Wikimedia git, with some (the 'tarball') included as sub-modules
of MediaWiki itself. This is the first step in the release process for
MediaWiki 1.37, which should be out in late November 2021, approximately
six months after MediaWiki 1.36.
The branches will reflect the code as of the last 'alpha' branch for the
release, 1.37.0-wmf.23, which will be deployed to Wikimedia wikis in the
week beginning 13 September 2021 for MediaWiki itself and those extensions
and skins available there. (Note that there will not be a 1.37.0-wmf.22
deployment, so there are only two Wikimedia production train deployments
inclusive between now and the branch point.)
After that point, patches that land in the main development branch of
MediaWiki and its bundled extensions and skins will be slated for the
MediaWiki 1.38 release unless specifically backported.
If you are working on a new feature that you wish to land for the release,
you now have three weeks to finish your work and land it in the development
branch; feature changes should not be backported except in an urgent case.
If your work might not be complete in time, and yet should block release
for everyone else, please file a task against the `mw-1.37-release` project
If you have tickets that are already tagged for `mw-1.37-release`, please
finish them, untag them, or reach out to get them resolved in the next few
We hope to issue the first release candidate, 1.37.0-rc.0, two weeks after
the branch point, and if all goes well, to release MediaWiki 1.37.0 a few
weeks after that.
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia is participating in the winter edition of this year's Outreachy <
https://www.outreachy.org/>  (December 2021–February 2022)! The deadline
to submit projects on the Outreachy website is *September 30th, 2021*.
If you would like to share an idea for a project that you would like to
mentor or you are not familiar with the program and want to learn anything
more about it, feel free to reply to this email or leave a note on <
*About the Outreachy program*:
Outreachy offers three-month internships to work remotely in Free and Open
Source Software (FOSS), coding and non-coding projects with experienced
mentors. These internships run twice a year–from May to August and December
to March. Interns are paid a stipend of USD 5,500 for the three months of
work. They also have a USD 500 stipend to travel to conferences and events.
Interns often find employment after their internship with Outreachy
sponsors or jobs that use the skills they learned during their internship.
This program is open to both students and non-students. Outreachy expressly
invites the following people to apply:
- Women (both cis and trans), trans men, and genderqueer people.
- Anyone who faces under-representation, systematic bias, or
discrimination in the technology industry in their country of residence.
- Residents and nationals of the United States of any gender who are
Black/African American, Hispanic/Latinx, Native American/American Indian,
Alaska Native, Native Hawaiian, or Pacific Islander.
See a blog post highlighting experiences and outcomes of interns who
participated in a previous round of Outreachy with Wikimedia <
Some tips for mentors for proposing projects:
- Follow this task description template when you propose a project in
Add #Outreachy (Round 23) tag to it.
- Remember, the project should require an experienced developer ~15 days
to complete and a newcomer ~3 months.
- Each project should have at least two mentors, and one of them should
hold a technical background.
- When it comes to picking a project, you could propose one that is:
- Relevant for your language community or brings impact to the
Wikimedia ecosystem in the future.
- Welcoming and newcomer-friendly and has a moderate learning curve.
- A new idea you are passionate about, there are no deadlines
attached to it; you always wanted to see it happen but couldn't
due to lack
of resources help!
- About developing a standalone tool (possibly hosted on Wikimedia
Toolforge), with fewer dependencies on Wikimedia's core
doesn't necessarily require a specific programming language.
See roles and responsibilities of an Outreachy mentor <
We look forward to your participation!
(On behalf of the organization team)
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
My name is Soham Parekh. I've been working with the foundation both in the
capacities of a volunteer as well as a mentor for Outreachy and Google
Summer of Code since past year and absolutely love being here. I've
recently been exploring a bit of Devops and infrastructure primarily
learning about monitoring, provisioning, Docker and the likes and wanted to
contribute on projects along these lines. I think this would be an amazing
learning experience for me given Wikipedia is capable of handling such huge
chunks of traffic and maintain across all the projects. I wanted some
guidance on which team/group is ideal to reach out to for projects of this
kind? Any help will be awesome!
This email is a summary of the Wikimedia production deployment of
- Train Conductors: dancy, brennen
- Phabricator Task: T281161 <https://phabricator.wikimedia.org/['task']>
- Deployment Status: Live on all wikis <https://versions.toolforge.org/>
- 248 patches
- 0 rollbacks
- 1 day of delays (Group 1 delayed until Thursday)
- 8 blockers (0 remain open)
- 18 tasks mentioned
🚂🌈 Thanks to everyone¹ who helped out with this train. Here are some
names chosen at random:
*¹ yes, even the bots*
- Be sure to tune in next time for another exciting trainwreck.
Myself sourav I am beginner at open source also I want to know your active
project idea list in order to make changes / add more feature into it but
unable to find from where to start , so if you can guide me how to start
contribute in your project it will be helpfull for me
We've released version 0.3.0 of WVUI earlier today.
One of the agreements from Vue.js developer summit  organized by the
Design System team has been to start a new library and repository next with
all other technical decisions made, a.o. being based on Vue 3 or no
support to IE 11. With this email we want to clarify upfront why we've
merged two more component additions (progress-bar and toggle-button)
succeeding the summit.
Reasons was mainly to finalize the already in-flight work by volunteer
Additionally to this, all other components merged since v0.2.0 and before the
summit – checkbox, dropdown and options-menu – are part of this
release. Same goes
for further improvements for the most important in-production use case,
Desktop Improvements project's Typeahead Search feature .
We'll discontinue major additions to WVUI from this release on besides
bug fixes and
will focus our work on the coming library.
Thanks to volunteer DannyS712 for all contributions! And to Nikki
Nikkhoui for the
continued build step support and James Forrester to get release out of the door
during after hours.
Find interactive demos hosted on doc.wikimedia.org  and the additional
improvements since v0.2.0 in the full changelog .
If you have any further questions please reach out to