Hi! As many of you know, a central global repository for Lua modules and
templates has been a frequent request since the early days of the movement.
(inspired on a previous tool called DiBabel by User:Yurik)
The tool allows to synchronize (that is, automatically copy) Lua modules
across Wikimedia wikis, and provides other features to help developers
update and maintain global modules.
I also re-wrote the documentation at
account for the new tool. It basically describes how to develop a Lua
module that can be copied unchanged to any wiki, by abstracting things like
user-readable strings and config.
Admittedly, this is a "poor man's version" of a proper solution to the
problem, but one I find invaluable while developing and maintaining
modules. Hopefully some of you may find it useful too!
The Technical Decision-Making Forum Retrospective team
<https://www.mediawiki.org/wiki/Technical_decision_making> invites you to
complete a survey about Wikimedia's technical decision-making processes.
While there will be more ways to participate, this is the first and most
important step in our data collection. It aims to gather information about
your experience, thoughts, and needs regarding the process of making
technical decisions across the Wikimedia technical spaces.
This survey will be used for gathering information about the process and
the needs around technical decision-making that touches our production
You can find the survey link here:
Who should take this survey?
People who do technical work that relies on software maintained by the
Wikimedia Foundation (WMF) or affiliates. If you contribute code to
MediaWiki or extensions used by Wikimedia, or you maintain gadgets or tools
that rely on WMF infrastructure, this survey is for you.
What is the deadline?
*August 7th, 2023 *
What will the Retrospective team do with the information?
The retrospective team will synthesize the collected data and publish an
anonymized analysis that will help leadership make decisions about the
future of the process.
We will collect anonymized information that we will analyze in two main
Sentiments based on demographic information: these will tell us whether
there are different needs and desires from different groups of people.
General needs and perceptions about decision-making in our technical
spaces: This will help us understand what kind of decisions happen in
the spaces, who is involved, and how to adjust our processes accordingly.
Is the survey the only way to participate?
The survey is the most important way for us to gather information because
it helps us gather input in a structured manner. But it will not be the
only way you can share your thoughts with us - we will have more
information soon about upcoming listening sessions where you can talk with
us live. In the meantime, you are always welcome to leave feedback on the
Where can I see more information?
There are several places where you can find more information about the
Technical Decision-Making Process Retrospective:
The original announcement about the retrospective from Tajh Taylor:
The Technical Decision-Making Process general information page:
The Technical Decision-Making Process Retrospective on MediaWiki:
Phabricator ticket: https://phabricator.wikimedia.org/T333235
How to contact the retrospective core team:
Write to the core team mailing list: tdf-retro-2023(a)lists.wikimedia.org
The Technical Decision-Making Process Retrospective on MediaWiki talk
Moriel, on behalf of the TDMP Retro Core Group
Moriel Schottlender (chair)
Moriel Schottlender (she/her <https://pronoun.is/she>)
Principal Software Engineer
Wikimedia Foundation https://wikimediafoundation.org/
Please save the date: #SMWCon 2023, December 11-13, Paderborn, Germany
Tickets will be available beginning of September, but you can already announce your participation on the above page and think about possible contributions (talks, tutorials, workshops, etc.).
Hope to see you in Paderborn,
Bernhard and Tobias
I was reading some code today and I suddenly realized that Resources.php
in MediaWiki code is indeed a PHP file, instead of a JSON file, unlike
almost all ResourceLoader module definitions in almost all extensions.
Is there a reason for this, or is it simply because no one has changed
it yet? (It looks like it might be slightly tricky to change, because
the JSON definitions loading is tied to loading extensions…)
The Wikimania Hackathon 2023
<https://wikimania.wikimedia.org/wiki/2023:Hackathon> is coming to Singapore
! This is our first in-person Wikimania Hackathon since 2019. It will take
place August 15–19 at the Suntec Singapore Convention and Exhibition Centre.
Whether you're a newcomer or an experienced technical contributor, there's
a place for you. We have a Newcomer Track with introductory sessions and
workshops, and an Unconference Track with breakout rooms for sessions
identified during the event. A main hacking space will also be available
throughout the event for collaborative work.
Check out our Diff post
for more details about the event, including how to prepare and participate.
Important! If you're registered for Wikimania
<https://wikimania.eventyay.com/> but *didn't opt in for Hackathon updates*,
you may miss out on specific Hackathon emails. To receive these, email
sstefanova(a)wikimedia.org, and we'll add you to the Hackathon mailing list.
If you have any questions, feel free to ask on the Wikimania help desk page
See you in Singapore, or online!
On behalf of the Wikimania Hackathon organizing team
*Tar Lócesilion / Szymon Grabarczuk*
Wikimania 2024 Core Organizing Team
Wikimania 2023 Technology Committee
tld: if you don't use GitLab at the moment, you can skip this message.
We will change the login in GitLab from cas3 to OIDC, to stay compatible
with the upcoming GitLab release. For end-users this change should not be
noticeable. idp.wikimedia.org is still used for single sign-on. Most
changes happened under the hood.
If you have problems logging in, please reach out at
https://phabricator.wikimedia.org/T320390 or on IRC at #wikimedia-gitlab.
Thanks again @John Bond <jbond(a)wikimedia.org> and @Simon Lyngshede
<slyngshede(a)wikimedia.org> for the hard work to make that possible.
In case it's interesting for anyone, the Future Audiences team at the
Wikimedia Foundation will host an office hour to talk among the Wikimedia
Foundation work around generative AI and the ChatGPT plugin experiment
(seeing if we can make sure that people who ask ChatGPT fact questions can
be made aware of when information is coming from us and be given links to
the article), among other things.
Next one is on Thursday, 14:00 UTC. More information:
*Johan Jönsson*Manager, Product Ambassadors
Wikimedia Foundation <https://wikimediafoundation.org/>
The 1.41.0-wmf.19 version of MediaWiki is blocked at group0.
The new version can proceed no further until the following is resolved:
- https://phabricator.wikimedia.org/T342747 -> Special:UserRights in
interwiki mode: Wikimedia\Assert\PreconditionException: Expected
MediaWiki\User\UserIdentityValue to belong to the local wiki, but it
belongs to 'metawiki'
Thank you for your help resolving this issue!
-- Your humble train toiler
Software Engineer III
Wikimedia Foundation <https://wikimediafoundation.org/>
HINT: This is a crossposting from mediawiki-l
With this message I am reaching out to the developers/maintainers of Extension:VisualEditor. I have already tried the mw.org support desk  and IRC without much success.
1. I was wondering if there were any technical reasons for Extension:VisualEditor not inserting a `<br />` element on `SHIFT+ENTER`. This seems to be standard functionality in most other visual HTML editors, plus `<br />` is supported by wikitext.
2. If there was no technical reason, I'd ask for support to implement a Gadget that allows for this behavior. I have already tried a couple of things, but it looks like the `SHIFT+ENTER` event can not be handeled easily. Apparently some core code handles the event and always creates a new paragraph. I did not succeed to stop propagation and override this behavior from my handler.
Maybe I am just missing something here. Any help would be much appreciated.