*tl;dr*: use `scap backport <gerrit url>` to deploy MediaWiki backports
____
There’s now a *single step* to deploy changes to Wikimedia’s production
MediaWiki.
🤯 An 85% reduction in command remembering!
On the deployment host run:
scap backport <gerrit url>
This works for any change to a live branch for mediawiki/core, extensions,
skins, or operations/mediawiki-config.
____
More details (and a demo) inside Jeena Huneidi’s excellent write up
<https://phabricator.wikimedia.org/phame/post/view/297/scap_backport_makes_d…>
.
<3
– Tyler Cipriani (on behalf of the RelEngers <https://releng.team> who really
do make dreams come true)
Engineering Manager, Release Engineering
Wikimedia Foundation
Hi all,
Now that Wikimedia production is fully on PHP 7.4[0], I propose dropping
support for PHP 7.2 and 7.3 from the master branch (which currently
means it'd apply to MW 1.40). PHP 7.2 is already not supported on the
release branches since MW 1.35.
PHP 7.3 went end-of-life in late 2021, and both the latest Debian stable
release (bullseye) and the latest Ubuntu LTS release (jammy) ship with
newer versions (7.4 and 8.1, respectively).
Please consider this the policy-required[1] notice. These changes can be
implemented in two weeks if there aren't any major objections here or in
the relevant Phabricator task[2].
[0]: https://phabricator.wikimedia.org/T271736
[1]: https://www.mediawiki.org/wiki/Support_policy_for_PHP#Process
[2]: https://phabricator.wikimedia.org/T261872
-- Taavi
Hi all,
On Thursday we will be issuing a security and maintenance release to all
supported branches of MediaWiki.
The new releases will be:
- 1.35.8
- 1.37.5
- 1.38.3
This will resolve three low priority issues in MediaWiki core along with
bug fixes included for maintenance reasons. This includes various patches
for PHP 8.0 and PHP 8.1 support.
We will make the fixes available in the respective release branches (plus
1.39 which is currently in release candidate status) and master in git.
Tarballs will be available for the above mentioned point releases as well.
A summary of some of the security fixes that have gone into non-bundled
MediaWiki extensions will also follow later.
As a reminder, 1.37 is due to become end of life (EOL) in November 2022.
1.37.5 is expected to be the last release for this branch. It is
recommended to upgrade to 1.38, or to 1.39 (the next LTS after 1.35) due to
be released in November 2022.
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Hi
We're currently in the final phase of planning for the IDM project (now
named Charon <https://en.wikipedia.org/wiki/Charon>, at least internally),
but before we start development we would like to hear feedback from you.
Briefly: The identity management portal is a project in the Infrastructure
Foundations team. The goal is to provide a self service portal, for
requesting, granting and revoking access to various systems and platforms.
This will also impact clinic duty, hopefully making it less of a chore on
SRE, once completed.
One of the initial goals will be to replace the account creation in the
WikiTech wiki, getting us closer to being able to resolve:
https://phabricator.wikimedia.org/T161859 (Make Wikitech an SUL wiki.
SUL = Standard
Unified Login) and https://phabricator.wikimedia.org/T161553 (Remove
OpenStackManager from Wikitech).
As currently planned we'll implement the portal in Python and Django
<https://www.djangoproject.com/>, keeping it in line with other SRE
projects, such as Striker and Debmonitor.
The initial implementation steps are described on WikiTech:
https://wikitech.wikimedia.org/wiki/Wikitech_IDM. A more detailed roadmap
does exist, but for now what we would like your feedback on is the four Major
use cases for the wikitech IDM
<https://wikitech.wikimedia.org/wiki/Wikitech_IDM#Major_use_cases_for_the_wi…>
.
Please use the Talk page on the wiki for feedback and comments. If you feel
a real time conversation is more conducive please catch me (slyngs) or
Moritz (moritzm) on the #wikimedia-sre-foundation IRC channel.
Let us know if you have any questions, use cases you like us to support in
the long term, if there are road blocks you believe we missed or just
feedback in general.
Thanks.
--
Simon
Hi all-
It’s time for the fourth edition of the Coolest Tool Award!
Tools play an essential role at Wikimedia, and so do the many volunteer
developers who experiment with new ideas, develop & maintain local & global
solutions and enhance the experience for Wikimedia communities.
We’d like to invite you all to nominate your favorite & most used tools and
help us celebrate the people who create them!
Please go to: https://meta.wikimedia.org/wiki/Coolest_Tool_Award
to recommend tools by October 12, 2022. You can nominate as many tools as
you want by filling out the form multiple times.
Thanks a lot for your ideas and recommendation(s)!
The award is organized & selected by the Coolest Tool Academy 2022
<https://meta.wikimedia.org/wiki/Coolest_Tool_Award/2022>[0]. We plan to
award the coolest tools in a variety of categories (see last year’s
categories <https://meta.wikimedia.org/wiki/Coolest_Tool_Award/2021>[1] for
an example). The award ceremony will take place virtually again this year
and we will provide more details about the specific logistics and dates
when we get closer to the event :-)
We’ll continue to spread the word over the next days and weeks, but any
help sharing this information with others is much appreciated :-)
[0]: https://meta.wikimedia.org/wiki/Coolest_Tool_Award/2022
[1]: https://meta.wikimedia.org/wiki/Coolest_Tool_Award/2021
Thanks-
Komla, for the Coolest Tool Academy 2022
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
Today, someone asked to see if I could get MediaWiki 1.35 to work with
ElasticSearch 7.x because they already had a licensed instance running
that they wanted to piggy back onto.
It wasn't too difficult to get CirrusSearch for 1.39 backported so that
I can at least get results from the search. I haven't tested it too
much and I the unit tests aren't working, but this WORKSFORME, so far.
Is there anyone else interested in this?
--
Mark A. Hershberger
NicheWork LLC
717-271-1084
Hello everyone,
Join us in congratulating 11 interns who successfully completed a project
via GSoC 2022 & Outreachy Round 24 with support and guidance from 20
mentors:
- Wikidata infobox rewrite in Lua for Commons by Lennard Hofmann.
Mentors: Mike Peel
- Edit request wizard by Ankit Gupta. Mentors: Enterprisey, SD0001
- Javascript build process and dependencies modernization for Wiki
Education Dashboard by Shashwat Khanna. Mentors: Sage Ross, Dhruvdutt Jadhav
- Custom picture selector improvements for Commons Android app by Ayan
Sarkar. Mentors: Nicolas Raoul, Aditya Srivastav
- Canasta CLI and Kubernetes template stack by Amal Paul. Mentors:
Jeffrey Wang, Yaron Koren
- WikidataComplete plugin extension for enabling data donations,
recommendations, and gamification by Lalit Suthar. Mentors: Andreas Both,
Dennis Diefenbach, Aleksandr Perevalov, Kunpeng GUO.
- Campaigns retention metrics dashboard by Nivas Ramisetty. Mentors: Jay
Prakash, Krishna Chaitanya Velaga, Alex Stinson
- Tracking support for specific namespaces for Programs & Events
Dashboard by Vaidehi Atpadkar. Mentors: Sage Ross
- Python library to work with html-dumps by Nazia Tasnim. Mentors:
Martin Gerlach, Isaac Johnson
- Bots for automatically identifying first and last author names for
Wikicite and Wikidata by Feliciss & Luis Roberto. Mentors: Mike Peel, Andy
Mabbett
You can learn more about these projects here:
<https://www.mediawiki.org/wiki/Google_Summer_of_Code/Past_projects#2022>
[1],
<https://www.mediawiki.org/wiki/Outreachy/Past_projects#Round_24> [2].
Cheers,
Wikimedia organization administrators (Srishti, Aisha, and Gopa)
[1] https://www.mediawiki.org/wiki/Google_Summer_of_Code/Past_projects#2022
[2] https://www.mediawiki.org/wiki/Outreachy/Past_projects#Round_24
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>