We have communicated
this change in August 2022 but here is a reminder that if you query
externallinks table in wikireplicas, you will need to rework your queries.
Changes are: el_to, el_index and el_index_60 fields will be dropped and you
need to query el_to_domain_index and el_to_path fields instead.
The data has been migrated in all wikis except English Wikipedia, Wikimedia
Commons and Wikidata, you can keep track of the data migration in T326314
In late June, we will stop updating the old fields and will start dropping
This is done to optimize storage of external links (drastically reducing
its size by removing duplication) and enabling user requested features such
as resolving two <https://phabricator.wikimedia.org/T14810> fifteen-year-old
tickets <https://phabricator.wikimedia.org/T17218> or easier aggregating of
external links domain , something that wasn’t possible until now.
 For example, If you want to get list of the top-linked websites, you
can query `SELECT el_to_domain_index, count(*) from externallinks group by
el_to_domain_index order by count(*) desc limit 50;`
Thank you and sorry for the inconvenience.
*Amir Sarabadani (he/him)*
Staff Database Architect
Wikimedia Foundation <https://wikimediafoundation.org/>
After nearly a decade of mishap and delay, we have updated the WMCS
can be found here:
There is one significant change in these terms: Cloud-vps projects which
for their projects. This is section 7.3. For other WMCS users and admins
these documents do not represent any significant change in policy, but
do clarify and finalize many things that were poorly-worded in the
previous TOU, or policies that we have enforced informally without
Please feel free to reach out to WMCS staff if you find any part of
these documents concerning or disruptive to your work on our platforms.
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
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
What's a good way of rotating logs on Toolforge? I haven't found anything
in the documentation on Wikitech. For context, in this case I'm looking to
use it for logs from Celery workers. I figured I can create a scheduled job
that runs logrotate in the tools home directory. Is there any other,
recommended or better way to do this?
Wikimedia Sverige (WMSE)
Telefon/*Phone*: (+46) 0707 - 92 03 84
Tool developers may be interested to know that Codex , the design
system for Wikimedia, is now available on the Toolforge CDNjs Mirror 
(and on upstream CDNjs , but you should prefer the Toolforge mirror
:P). This means you can relatively easily use the Codex components,
icons, and/or design tokens in your tools if you want, just like e.g.
Bootstrap. See  for an example in one of my tools. (The most
important technical bits are the importmap, import statements, createApp
call, and `components: codex` and `...codexIcons`, if you want to search
for those parts in particular.)
The Codex maintainers would probably like me to remind you that Codex
has not reached version 1.0 yet ;) I gather that it’s coming up (and
not, like, years away), but until then you should probably be ready for
breaking changes to happen. Once version 1.0 is out, CDNjs and the
Toolforge mirror should pick it up automatically, but you’ll need to
adjust the URLs in your tools like for any version upgrade (since the
version number is part of the URL – CDNjs doesn’t offer auto-updating
The Phabricator task for Codex being available on CDNjs is T338834 ;
if you experience any issues, you can bring them up there.