(If you don’t work with links tables such as templatelinks, pagelinks and
so on, feel free to ignore this message)
TLDR: The schema of links tables (starting with templatelinks) will change
to have numeric id pointing to linktarget table instead of repeating
namespace and title.
The current schema and storage of most links tables are: page id (the
source), namespace id of the target link and title of the target. For
example, if a page with id of 1 uses Template:Foo, the row in the database
would be 1, 6, and Foo (Template namespace has id of 6)
Repeating the target’s title is not sustainable, for example more than half
of Wikimedia Commons database is just three links tables. The sheer size of
these tables makes a considerable portion of all queries slower, backups
and dumps taking longer and taking much more space than needed due to
unnecessary duplication. In Wikimedia Commons, on average a title is
duplicated around 100 times for templatelinks and around 20 times for
pagelinks. The numbers for other wikis depend on the usage patterns.
Moving forward, these tables will be normalized, meaning a typical row will
hold mapping of page id to linktarget id instead. Linktarget is a new table
deployed in production and contains immutable records of namespace id and
string. The major differences between page and linktarget tables are: 1-
linktarget values won’t change (unlike page records that change with page
move) 2- linktarget values can point to non-existent pages (=red links).
The first table being done is templatelinks, then pagelinks, imagelinks and
categorylinks will follow. During the migration phase both values will be
accessible but we will turn off writing to the old columns once the values
are backfilled and switched to be read from the new schema. We will
announce any major changes beforehand but this is to let you know these
changes are coming.
While the normalization of all links tables will take several years to
finish, templatelinks will finish in the next few months and is the most
So if you:
… rely on the schema of these tables in cloud replicas, you will need to
change your tools.
… rely on dumps of these tables, you will need to change your scripts.
Currently, templatelinks writes to both data schemes for new rows in most
wikis. This week we will start backfilling the data with the new schema but
it will take months to finish in large wikis.
You can keep track of the general long-term work in
https://phabricator.wikimedia.org/T300222 and the specific work for
templatelinks in https://phabricator.wikimedia.org/T299417. You can also
read more on the reasoning in https://phabricator.wikimedia.org/T222224.
*Amir Sarabadani (he/him)*
Staff Database Architect
Wikimedia Foundation <https://wikimediafoundation.org/>
Since the beginning of the year, the Wikimedia Language team has enabled
translation backports for MediaWiki core, extensions and skins hosted on
Gerrit. On a weekly schedule compatible translations from master branch are
backpored to all the supported release branches. Currently supported
branches are 1.35–1.38.
Translation backports partially replace the purpose of the
LocalisationUpdate extension. Wikimedia sites no longer use the extension,
and to our knowledge only a few other users of the extension exist, because
it needs manual setup to use.
We, the Language team, think that maintaining the LocalisationUpdate
extension is no longer a good use of our time. We are asking for your
feedback about the future of this extension.
We are planning to:
* Remove LocalisationUpdate from the MediaWiki Language Extension Bundle
starting from version 2022.07
* Remove us as maintainers of the extension
Additionally, based on the feedback, we are planning to either mark the
extension as unmaintained, transfer maintenance to a new maintainer, or
request the extension to be archived and removed from the list of
extensions bundled with MediaWiki core if there is no indication that
anyone uses this extension.
We request your feedback and welcome discussion on
https://phabricator.wikimedia.org/T300498. Please let us know if you are
using this extension and whether you would be interested in maintaining it.
Q: What about Wikimedia sites: does this mean they will not get frequent
translation updates as they used to have?
A: We still think this is important, but we do not think the previous
solution can be restored. We would like to collaborate on new solutions.
One solution could be more frequent deployments.
In 2019, the German-speaking wikis selected “Make working with templates
easier” as the focus area of Wikimedia Deutschland’s Technical Wishes
project. Since then, our team has made improvements in different areas, to
help template creators as well as users of the wikitext editor and
VisualEditor. Our work on this focus area is coming to an end, so I’d like
to summarize what happened and lay out the next steps:
Two changes from our Templates project have been available on all* wikis
for a while already:
A new attribute “suggested values” was introduced to help you clarify
what values a parameter may expect. 
Line numbers are shown in the “Template” namespace when syntax
highlighting (CodeMirror extension) is turned on.  A few wikis have
these line numbers in _all_ namespaces. If you want this for your wiki as
well, please reach out to us.
Several other changes were deployed to a small group in the past months. A
big thanks to Catalan, Turkish, Greek, Malay, Twi, French, Hungarian,
Hebrew, Finnish, Dagbani and German Wikipedia, to English Wikivoyage and
Nauruan Wiktionary as well as Wikitech wiki for testing these changes and
giving feedback to help us improve these projects. These changes are now
coming to more wikis:
Finding and inserting templates will become easier with an improved
search (in the TemplateWizard & in the template dialog of VisualEditor and
New Wikitext mode). 
In VisualEditor, you’ll be able to remove a template from a page via the
context menu, just like removing a table or an image. 
In VisualEditor, the template dialog will become bigger and descriptions
will be more visible. 
When using syntax highlighting (CodeMirror extension)*, matching
brackets will be highlighted  and the color scheme will be updated
for better readability .
The planned deployment date for all of these changes is March 9 (and March
16 on English Wikipedia).
A few weeks later, we’ll be deploying the last improvements from our
For syntax highlighting (CodeMirror extension), a colorblind-friendly
color scheme will be added. You’ll be able to activate it via a user
A range of fundamental changes to the VisualEditor template dialog will
be deployed. They will make it easier to understand what is expected from a
template, to navigate the template dialog, and to add parameters to a
Feedback on all the projects is much appreciated on their respective talk
pages. Thanks a lot on behalf of the Technical Wishes team,
Johanna, Community Communications Technical Wishes
* All improvements in the CodeMirror extension, which provides syntax
highlighting, only apply to wikis that have the extension installed. This
is generally true for left-to-right language wikis, because unfortunately
the extension doesn’t work sufficiently for right-to-left languages yet
We currently do not have the resources to offer the workshop content in
different languages. We are investigating the possibility of taking this up
in future projects. One thing, though, is that we are presently exploring
Google Meet's live captioning feature, and interestingly, it offers
translations in French. As I have not tested this feature myself,
particularly for non-English translations, I am unsure how reliable it is,
something you might want to try out!
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
On Fri, Apr 15, 2022 at 1:31 PM Handgod Abraham <sambayo23(a)gmail.com> wrote:
> Thanks ! Is a French translation planned please ?
> Le ven. 15 avr. 2022 à 15:42, Srishti Sethi <ssethi(a)wikimedia.org> a
> écrit :
>> Hello everyone,
>> The third workshop on the topic of "Writing Pywikibot scripts" is coming
>> up - it will take place on Friday, April 29th at 16:00 UTC. You can find
>> more details on the workshop and a link to join here: <
>> This workshop will introduce participants to writing basic scripts via
>> the Pywikibot framework. We will be focusing on examples of scripts that
>> participants have requested to cover in the workshop (e.g., finding and
>> replacing content, archiving discussions, etc.). You can add your ideas to
>> the ongoing discussion in the etherpad doc linked from the workshops page. If
>> you missed attending the previous two workshops, going through the workshop
>> materials beforehand would be beneficial.
>> We look forward to your participation!
>> On behalf of the SWT Workshops Organization team
>> *Srishti Sethi*
>> Senior Developer Advocate
>> Wikimedia Foundation <https://wikimediafoundation.org/>
>> Wikimedia-l mailing list -- wikimedia-l(a)lists.wikimedia.org, guidelines
>> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
>> Public archives at
>> To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org
I will upgrade our Gerrit from 3.3.10 to [version 3.4.4] this Thursday
April 28th at 8:00 UTC. I will first upgrade the [Gerrit replica] then
the primary server. The service will thus be unavailable for a few
minutes while I restart the service.
Upstream release notes highlights three new features:
1) Checks UI: we do not plan to use this feature
2) Unresolved Comments ported to latest patchset
Unresolved comments that were left on older patchsets will now also be
shown on newer patchsets.
3) Comment Chips and Context
Comment state (resolved, unresolved, draft) is summarized by chips below
the commit message. The Comments Tab and the Change Log will not just
show the comment thread, but also the snippet of code (where the comment
was made) as context.
And various small UI changes, see [version 3.4.4] for a full list.
[version 3.4.4] https://www.gerritcodereview.com/3.4.html
Upgrade task: https://phabricator.wikimedia.org/T292759
Antoine "hashar" Musso
Wikimedia Release Engineering
We’re happy to announce the April 2022 edition of the Technical Community
The newsletter is compiled by the Wikimedia Developer Advocacy Team. It
aims to share highlights, news, and information of interest from and about
the Wikimedia technical community.
The Wikimedia Technical Community is large and diverse, and we know we
can't capture everything perfectly. We would love to hear your ideas for
future newsletters. Let us know what you would like to see or highlights
you would like us to include.
If you'd like to keep up with updates and information, subscribe to the
Technical Community Newsletter:
Developer Advocacy Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
We are updating composer in the CI images from 2.1.8 to 2.3.3 which
update most jobs relying on PHP.
The "Quibble" jobs have not been upgraded due to prerequisites tasks
that have not been completed yet.
If you find something suspiciously related to the composer upgrade,
please report on the upgrade task or as a subtask:
James Forrester & Antoine Musso