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.6
- 1.36.4
- 1.37.2
This will resolve four issues in MediaWiki core and also includes some
fixes previously committed to git, including minor security and hardening
patches along with bug fixes included for maintenance reasons. One issue
does not affect MediaWiki 1.35 and 1.36.
In addition to those, these releases will resolve other issues in MediaWiki
core and also include some fixes previously committed to git, including
minor security and hardening patches along with bug fixes included for
maintenance reasons.
We will make the fixes available in the respective release branches 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.36 is due to become end of life (EOL) in May 2022. 1.36.4
is expected to be the last release for this branch. It is recommended to
upgrade to 1.37, or to 1.38 due to be released in May 2022.
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Hi all,
(If you don't write code for Wikipedia-deployed skins/extensions you can skip this message.)
Last month, we (Growth team) reached a milestone where GrowthExperiments features[0] are now deployed to 100% of newly created accounts[1] on nearly all Wikipedias. These features were built over the last four years[2] to increase the retention of new editors by giving them clear places to get started with editing and to get support.
As a core/skin/extension developer, here are some changes to the new user account experience that you should know about:
* after a user account is created, a user is redirected to Special:WelcomeSurvey[3]. From there we invite the user to visit Special:Homepage[4]. In addition the username in personal tools is linked to Special:Homepage
* On Special:Homepage, the user is guided through editing with suggested edits[5], and can talk to a mentor via the mentorship tools[6]
* When editing any page in the main namespace or selected other namespaces, users will see a help panel button[7] that offers in-context help and ways to contact mentors
* After an edit is saved, we use the mw.postEdit hook (desktop & mobile) to display a dialog with suggested tasks to the user
If you have ideas for building with any of these features (e.g. adding new functionality to Special:Homepage; adding your own in-context help to the help panel; developing new types of tasks for newcomers to work on) we would be happy to hear from you! Also, if you'd like to try the features yourself, you can read about how to enable them here[8].
Cheers,
Kosta for the Growth Team
[0] https://www.mediawiki.org/wiki/Growth/Feature_summary
[1] We have retained a few wikis where we experiment with a control group that does not get Growth features. Also, newcomers who are opted-in to the features can turn them off in their preferences.
[2] Thank you to the ~50 contributors who have made this possible! https://github.com/wikimedia/mediawiki-extensions-GrowthExperiments/graphs/…
[3] https://www.mediawiki.org/wiki/Growth/Personalized_first_day/Welcome_survey
[4] https://www.mediawiki.org/wiki/Growth/Feature_summary#Newcomer_homepage
[5] https://www.mediawiki.org/wiki/Growth/Feature_summary#Newcomer_tasks
[6] https://www.mediawiki.org/wiki/Growth/Mentor_dashboard
[7] https://www.mediawiki.org/wiki/Growth/Feature_summary/en#Help_panel
[8] https://www.mediawiki.org/wiki/Help:Growth/Tools/Enable_the_Homepage
Hello everyone!
Your friendly neighborhood Hackathon committee is thrilled to announce the
2022 Global Wikimedia Hackathon! We invite you to join us for three days of
collaborating, interactive sessions, and social fun from May 20-May 22. The
Hackathon will be held online and there will be grants available to support
local in-person meetups around the world. You can find more information
about this on our MediaWiki.org page
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022>, which will
continue to grow over the next few weeks. For more details, read below.
Who: The Hackathon is for anyone who contributes (or wants to contribute
to) to Wikimedia’s technical areas - as code creators, maintainers,
translators, designers, technical writers and other technical roles. You
can come with a project in mind, join an existing project, or create
something new with others. The choice is yours! Newcomers are welcome.
We will send out more information on how to schedule a session in the
program soon. You can also add yourself to the participants list
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Participants>, and
mention if you would like to help with tasks such as facilitation or
welcoming newcomers. There will be scholarship stipends available- please
stay tuned for more information.
What: A Wikimedia Hackathon <https://www.mediawiki.org/wiki/Hackathons> is
a space for the technical community to come together and work together on
technical projects, learn from each other, and make new friends.
When: May 20-May 22. The schedule will be announced shortly. We are trying
to plan events so that people in all time zones can participate
comfortably. There will be core hours several times a day when most events
will occur, and online social and hacking spaces open 24 hours a day
throughout the three days.
Where: The Hackathon will primarily be held online. However, very soon we
will share an application for local affiliates to apply for grants to host
in-person local meetups. Meetups can be anything from social gatherings
with food, to a party for watching the opening or closing ceremony, to a
pre-event workshop, to renting a venue where people can participate
together in the online event. Grants can range from 500-5000 USD. Stay
tuned for more information!
How (can you help)?:
1.
We are seeking another committee member! The commitment is around 3
hours per week. If you are interested, please contact hlepp(a)wikimedia.org
2.
We have an ideas page.
<https://www.mediawiki.org/wiki/Talk:Wikimedia_Hackathon_2022>What are
you interested in? What would you like to see or do in this year’s
hackathon? Please share your ideas with everyone! This is a community
Hackathon and we will work together to put on a great event.
3.
Do you have any accessibility or translation requests? Please contact
hlepp(a)wikimedia.org
Cheers,
Your Hackathon Committee
Andre <https://www.mediawiki.org/wiki/User:AKlapper_(WMF)>
Haley <https://www.mediawiki.org/wiki/User:HLepp_(WMF)>
Jay <https://www.mediawiki.org/wiki/User:Jayprakash12345>
Lucas <https://www.mediawiki.org/wiki/User:Lucas_Werkmeister>
Marios <https://www.mediawiki.org/wiki/User:Magioladitis>
Neslihan <https://www.mediawiki.org/wiki/User:Flanoz>
Selene
<https://www.mediawiki.org/w/index.php?title=User:SYang_(WMF)&action=edit&re…>
Hello everyone,
The second workshop on the topic of "Running Pywikibot scripts" is coming
up - it will take place on Friday, March 25th at 16:00 UTC. You can find
more details on the workshop and a link to join here: <
https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_run_a_…>
[1].
This workshop will introduce participants to the bot scripts available via
the Pywikibot framework and how to use them. If you missed attending the
first one, it would be beneficial to have Pywikibot installed on your
computer before the workshop.
We look forward to your participation!
Best,
Srishti
On behalf of the SWT Workshops Organization team
[1]
https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_run_a_…
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
I'd like to draw some attention to the current outstanding release blockers.
From https://phabricator.wikimedia.org/tag/mw-1.38-release/,
8 tasks as queried from https://phabricator.wikimedia.org/maniphest/query/2YXgSfsvECyO/#R
1. T261329 Prepare Parsoid for MW 1.38 (ideally) <https://phabricator.wikimedia.org/T261329>
2. T265518 Move Parsoid ServiceWorker.php and extension/src/Config into core <https://phabricator.wikimedia.org/T265518>
3. T302117 ZeroConf VE for MW 1.38 <https://phabricator.wikimedia.org/T302117>
> Component: Parsoid.
> Assigned to: WMF Content Transformation, formerly known as Parsing team.
If this is finished in master, it may be worth checking that relevant docs are up-to-date, and that relevant changes have made it to the branch in time (or are backported).
4. T275246 Populate rev_actor and rev_comment_id <https://phabricator.wikimedia.org/T275246>
> Component: MediaWiki-Revision-backend.
> Assigned to: WMF Platform Engineering (@tstarling).
Originally planned for MW 1.36. Last year, change 684142 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/684142> implemented the migration.
I moved it to the MW 1.39 milestone as this isn't something we can (nor should) rush through code changes alone. Per Tim's comment <https://phabricator.wikimedia.org/T275246#7512017>, we should add this to the installer/updater after we've succesfully migrated WMF's.
5. T288686 WVUI's TypeaheadSearch should work with a non-default `$wgScriptPath` <https://phabricator.wikimedia.org/T288686>
> Component: Vector 22.
> Assigned to: Readers Web.
The new Vector 22 skin isn't yet used by default, but it currently hardcodes WMF-specific configuration and is bundled the release. There is an open patch pending review.
6. T294612 Raw HTML from Language Converters' title conversion displayed <https://phabricator.wikimedia.org/T294612>
> Component: MediaWiki-Parser, MediaWiki-Language-converter.
> Assigned to: WMF Content Transformation, formerly known as Parsing team.
A regression reported October, that appears unsolved in prod (the linked example still displays raw HTML) and currently set to block the release.
7. T295187 Chinese conversion no longer work in the table of content <https://phabricator.wikimedia.org/T295187>
> Component: MediaWiki-Parser, MediaWiki-Language-converter.
> Assigned to: WMF Content Transformation (@cscott).
This appears to be resolved from my very rudimentary testing.
8. T303029 Revert ParsoidSiteConfigInit hook creation <https://phabricator.wikimedia.org/T303029>
> Component: Parsoid.
> Assigned to: WMF Content Transformation, formerly known as Parsing team.
Best,
-- Timo
Hello, all!
This is a follow-up on our earlier announcement[0] of the above.
Thanks to those who have already migrated their tool(s) from Debian Stretch
grid or are
in the process of doing this.
At the start of this process, there were 867 tools running on Stretch grid.
The current number is 821.
=== Recap ===
We are migrating away from Debian Stretch[1] to Debian Buster for all of
Toolforge servers,
and the most affected piece is the Grid Engine backend in particular.
We need to shut down all Stretch hosts before the end of support date to
ensure that
Toolforge remains a secure platform. This migration will take several
months because many people still use the Stretch hosts and our users
are working on tools in their spare time.
== What should I do? ==
You should migrate your Toolforge tool to a newer environment.
You have two options:
* migrate from Toolforge Stretch Grid Engine to Toolforge Kubernetes[2].
* migrate from Toolforge Stretch Grid Engine to Toolforge Buster Grid
Engine.[3]
== Timeline ==
* 2022-02-15: Availability of Debian Buster grid announced to community -
DONE
* 2022-03-21: Weekly reminders via email to tool maintainers for tools
still running on Stretch - IN PROGRESS
* Week of 2022-04-21:
** Daily reminders via email to tool maintainers for tools still running on
Stretch
** Switch login.toolforge.org to point to Buster bastion
* Week of 2022-05-02: Evaluate migration status and formulate plan for
final shutdown of Stretch grid
* Week of 2022-05-21: Shutdown Stretch grid
We thank all of you for your support during this migration process.
You can always reach out via any of our communication channels[4]
[0]
https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.…
[1] https://wikitech.wikimedia.org/wiki/News/Toolforge_Stretch_deprecation
[2]
https://wikitech.wikimedia.org/wiki/Help:Toolforge/Jobs_framework#Grid_Engi…
[3]
https://wikitech.wikimedia.org/wiki/News/Toolforge_Stretch_deprecation#Move…
[4]
https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Commun…
Thanks.
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
🚂🌈Summary of 1.38.0-wmf.26 train deployment
This email is a summary of the Wikimedia production deployment of
1.38.0-wmf.26
- Conductor: Jeena Huneidi
- Backup Conductor: Ahmon Dancy
- Blocker Task: T300202 <https://phabricator.wikimedia.org/T300202>
- Current Status <https://versions.toolforge.org>
📊 Numbers
Sparklines comparing with the last 5 trains.
- 314 Patches ▅▁▄█▅
- 0 Rollbacks ▁▁▁█▁
- 1 Days of delay ▁▁▁▁█
- 6 Blockers ▁▁▂█▄
🥰 Trainbow Love 🌈 Thanks to folks who reported or resolved blockers:
- Antoine "hashar" Musso
- Amir Sarabadani
- Timo Tijhof
- Zabe
- Kosta Harlan
- Jon Robson
--
Jeena Huneidi
Software Engineer, Release Engineering
Wikimedia Foundation
The 1.39.0-wmf.1 version of MediaWiki is blocked[0].
The new version is deployed to testwikis, but can proceed no
further until these issues are resolved:
* Wikimedia\Rdbms\DBTransactionError: Transaction round stage must be
'cursory' (not 'within-rollback-callbacks') -
https://phabricator.wikimedia.org/T281451
* Wikimedia\Timestamp\TimestampException:
Wikimedia\Timestamp\ConvertibleTimestamp::getTimestamp: The timestamp
cannot be represented in the specified format -
https://phabricator.wikimedia.org/T304307
Once these issues are resolved train can resume. If these issues are
resolved on a Friday the train will resume Monday.
Thank you for your help resolving these issues!
-- Your humble train toiler
[0]. https://phabricator.wikimedia.org/T300203
[1]. <https://versions.toolforge.org/>
--
Jaime Nuche
Software Engineer III
Wikimedia Foundation <https://wikimediafoundation.org/>
<https://wikimediafoundation.org/>