Hey all,
This is a quick note to highlight that in six weeks' time, the REL1_41
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[0]. This is the first step in the release process for
MediaWiki 1.41, which should be out in May 2023, approximately six months
after MediaWiki 1.40.
The branches will reflect the code as of the last 'alpha' branch for the
release, 1.41.0-wmf.30, which will be deployed to Wikimedia wikis in the
week beginning 10 October 2023 for MediaWiki itself and those extensions
and skins available there.
After that point, patches that land in the main development branch of
MediaWiki and its bundled extensions and skins will be instead be slated
for the MediaWiki 1.42 release unless specifically backported[1].
If you are working on a new feature that you wish to land for the release,
you now have a few days 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.41-release` project
on Phabricator.[2]
If you have tickets that are already tagged for `mw-1.41-release`, please
finish them, untag them, or reach out to get them resolved in the next few
weeks.
We hope to issue the first release candidate, 1.41.0-rc.0, two weeks after
the branch point, and if all goes well, to release MediaWiki 1.41.0 a few
weeks after that.
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://www.mediawiki.org/wiki/Bundled_extensions_and_skins>
[1]: <https://www.mediawiki.org/wiki/Backporting_fixes>
[2]: <https://phabricator.wikimedia.org/tag/mw-1.41-release/>
Hello!
We're excited to invite you to our Mobile Apps Team online meeting. This is
a great opportunity to learn about the latest developments in Wikipedia's
mobile apps and engage with the team.
Date: 27th October
Time: 5 p.m. UTC
Meeting Link: https://wikimedia.zoom.us/j/83695206107
Our host, Jazmin Tanner <https://meta.wikimedia.org/wiki/User:JTanner_(WMF)>,
Product Manager of the Apps Team
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team>, and our software
engineers will be there to provide updates, answer your questions, and hear
your suggestions.
Agenda:
Mobile app updates
Q&A session
Share your thoughts
Contribute by posting your questions and insights about Wikipedia’s mobile
apps on the Wikimedia Apps/Office Hours page on mediawiki.org
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Office_Hours#:~:text=edit%20s…>.
The deadline for input is 24th October at 12:00 UTC.
We can provide Arabic and French interpretations if we get +7 sign-ups for
each language by 3rd October on the same link.
Also, for a one-day reminder before the meeting, add your username.
Please help us spread the word to interested developers in Android, iOS
Wikipedia mobile apps, and Commons. We value your contribution to the
Wikimedia community and look forward to your active participation in this
meeting!
Respectfully,
*Amal Ramadan* (She\Her)
Sr. Community Relations Specialist
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi all,
For your information, as part of the September 2023 datacenter switchover
<https://wikitech.wikimedia.org/wiki/Switch_Datacenter>, the primary
maintenance server is now mwmaint2002.codfw.wmnet.
If you use the alias maintenance.eqiad.wmnet, please note that the host key
has changed.You may want to run wmf-update-known-hosts-production.
Please reach out if you encounter any issue, either by responding to this
email, or by filing a sub-task to https://phabricator.wikimedia.org/T346474.
Thanks,
Kamila Součková (they/them)
Senior SRE
Wikimedia Foundation
Hello everyone,
TLDR; Wikimedia is participating in the Outreachy Round 27 internship
program <https://www.mediawiki.org/wiki/Outreachy/Round_27 > [1].
Outreachy's goal is to support people from groups underrepresented in the
technology industry. Interns will work remotely with mentors from our
community. We are seeking mentors to propose projects that Outreachy
interns can work on during their internship. If you have some ideas for coding
or non-coding (design, documentation, translation, outreach, research)
projects, share them by Sept. 29, 2023 at 4 pm UTC here as a subtask of
this parent task: <https://phabricator.wikimedia.org/T343871 > [2]
Program Timeline
As a mentor, you engage potential candidates in the application period
between October–November (winter round) and help them make small
contributions to your project. You work more closely with the accepted
candidates during the internship period between December–March (winter
round).
Important dates are:
-
Aug. 22, 2023 at 4pm UTC - Live Q&A for Outreachy mentors
<https://www.youtube.com/@outreachyinternships>
-
September 29, 2023 at 4pm UTC - Project submission deadline
<https://www.outreachy.org/communities/cfp/wikimedia/>
Guidelines for Crafting Project Proposals
* Follow this task description template when you propose a project in
Phabricator: <
https://phabricator.wikimedia.org/tag/outreach-programs-projects> [3]. You
can also use this workboard to pick an idea if you don't have one already.
Add #Outreachy (Round 27) tag.
* Project should require an experienced developer ~15 days and a newcomer
~3 months to complete.
* Each project should have at least two mentors, including one with a
technical background.
* Ideally, the project has no tight deadlines, a moderate learning curve,
and fewer dependencies on Wikimedia's core infrastructure. Projects
addressing the needs of a language community are most welcome.
Learn more about the roles and responsibilities of mentors on
MediaWiki.org: <https://www.mediawiki.org/wiki/Outreachy/Mentors> [4][5]
Cheers,
Onyinye & Sheila (Wikimedia Org Admins for Outreachy Round 27)
[1] https://www.mediawiki.org/wiki/Outreachy/Round_27
[2] https://phabricator.wikimedia.org/T343871
[3] https://phabricator.wikimedia.org/tag/outreach-programs-projects/
[4] https://www.mediawiki.org/wiki/Outreachy/Mentors
[ 5] https://www.outreachy.org/mentor/mentor-faq
The 1.41.0-wmf.27 version of MediaWiki is blocked[0].
The new version is currently deployed to testwikis, but can proceed no
further until this issue is resolved:
* T346800 - startupregistrystats-testwiki periodic job fails
- https://phabricator.wikimedia.org/T346800
Once this issue is resolved train can resume.
Thank you for any help resolving these issues!
-- Your relatively calm train operator
[0]. https://phabricator.wikimedia.org/T345888
[1]. https://versions.toolforge.org/
Hi all,
For your information, part of the September 2023 datacenter switchover
<https://wikitech.wikimedia.org/wiki/Switch_Datacenter>, the primary
deployment server is now deploy2002.codfw.wmnet.
If you use the alias deployment.eqiad.wmnet, please note that the host key
has changed.You may want to run
wmf-update-known-hosts-production.
Please reach out if you encounter any issue, either by responding to this
email, or by filing a sub-task to https://phabricator.wikimedia.org/T345263.
Thanks,
Kamila Součková (they/them)
Senior SRE
Wikimedia Foundation
The QTE, Cloud Services, and Release Engineering team (collectively known
as DevEx, Developer Experience) are kicking off a new project to create an
advanced prototype of an on-demand test environment provisioner called
Catalyst. This tool is a logical successor to Patch Demo
<https://patchdemo.wmflabs.org/>, which could deploy MediaWikis for testing
but not services, and DUCT
<https://people.wikimedia.org/~kindrobot/duct/presentation.html>, which
could deploy Mediawikis and services for testing in Wikifunctions
<http://wikifunctions.org>, but was not scalable to other teams/projects.
We expect the MVP (minimum viable prototype) to be ready in approximately
two months and would be very interested in input/help from the community,
both with the prototype and with where a generally available product might
look like thereafter. More information on the project, its technology
stack, and how to get involved is at
https://wikitech.wikimedia.org/wiki/Catalyst.
--
*Stef Dunlap* (she/her)
Staff Software Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi everybody,
In https://phabricator.wikimedia.org/T342116 the Machine Learning team
announces its intention to deprecate the mediawiki.revision-score stream.
For external users, the stream is consumable via the
https://stream.wikimedia.org API and it currently has very few users.
Our idea is to create smaller streams, one for each model type, instead of
having a big aggregator. For example, revision 123456 for enwiki ends up
with several scores from various models in the current revision-score
stream, that is convenient but very hard to manage and maintain for us
(since it is not clear if users are interested in all the data or only a
subset of it). The revision-score stream is also very tightly coupled with
the ORES' architecture, which we are trying to deprecate. In the future we
plan to have smaller streams, in which every revision will get associated
with a single score, from a specific model server:
mediawiki.revision-score-goodfaith
mediawiki.revision-score-damaging
...
...
[ and also new models that will be deployed. ]
To avoid creating unnecessary streams, we'll create the ones that WMF teams
and the community will need and ask during the next months. If you have any
requirement, please follow up with us:
- Email: ml(a)wikimedia.org
- Phabricator: #Machine-Learning-Team tag
- IRC (Libera): #wikimedia-ml
If you are a user of the Mediawiki revision-score stream please follow up
on the task above explaining your use case, we'll try to do our best to
find a good solution for you!
Thanks in advance,
Regards,
Luca
Dear fellow developers! If you don't work on gadgets or Wikimedia code,
feel free to ignore this email!
For some time we've had the Stable interface policy which has been super
helpful for backend-development. I would love us to have an equivalent for
frontend code.
For the past 3 years we have been building one with feedback and
suggestions from gadget developers, WMF staff and Wikimedia volunteers. The
current draft can be found at:
https://www.mediawiki.org/wiki/User:Jdlrobson/Stable_interface_policy/front…
I would like to make this policy official so that we can get the benefits
of having a document and continue to evolve it in a more official capacity.
If anyone wants to veto this, I'd like to hear from you on the talk page or
by a reply to this email (either privately or publicly). When making a veto
please make that explicit and include the text you find problematic and
details about why.
If there is no active veto after one month, this policy will be made
official and moved to
https://www.mediawiki.org/wiki/Stable_interface_policy/frontend.
Thanks in advance for all your help with this important matter!
Jon Robson
PS. This note has also been sent to tech news.