As per the MediaWiki version lifecycle[1], I would like to announce the
formal end of life (EOL) of MediaWiki 1.37 as of today, Wednesday November
30, 2022.
This means that MediaWiki 1.37 will no longer receive maintenance or
security backports. It is therefore strongly discouraged that you continue
to use it.
It is recommended to upgrade either to MediaWiki 1.38, which will be
supported until June 2023 or to 1.39 (released today), the next LTS after
1.35, which will be supported until November 2025.
Thanks!
Sam Reed
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Hello everyone,
As part of the effort to align Parsoid's output with the output of the
legacy parser [1], we're introducing a backwards incompatible change [2] in
the next Parsoid version (0.17.0-a7, to be deployed along with
1.40.0-wmf.12).
This new version modifies the target of the link to add "action=edit" and
"redlink=1" to redlinks (wikilinks that point to a non-existing page).
We missed that this could have an impact on Parsoid clients, but this was
caught by DiscussionTools [3]. Accordingly, we updated the Parsoid HTML
Specification to explicitly add red links to the specification [4][5].
Parsoid clients that rely on wikilink targets should check for URL
parameters and treat them accordingly.
As an advance notice, we will also eventually modify the "title" attribute
of redlinks to add localized information about this state, as is the case
in the legacy parser [1]. Please let us know of any input you may have on
this topic by adding a comment on the corresponding Phabricator ticket so
that we can discuss options [1].
Best regards,
Isabelle, for the Content Transform Team.
[1] https://phabricator.wikimedia.org/T309024
[2] https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/816137/
[3] https://phabricator.wikimedia.org/T324028
[4] https://www.mediawiki.org/wiki/Specs/HTML/2.6.0
[5] This would technically have required a major bump in the specification
version. Since we don't have a well-tested implementation for content
negotiation and the RESTBase sunsetting work is in progress [6], bumping
major versions wasn't an option. We overlooked bumping a minor version as a
signal, because we assumed we had it covered in 2.6.0.
[6] https://phabricator.wikimedia.org/T262315
--
*Isabelle Hurbain-Palatin* (she/her)
Senior Software Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi everyone,
We’re happy to share the November 2022 edition of the Technical Community
Newsletter:
https://www.mediawiki.org/wiki/Technical_Community_Newsletter/2022/November
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. Got something you would like to see or something you
want to highlight in the next quarterly newsletter? Add your suggestion to
the talk page:
https://www.mediawiki.org/wiki/Talk:Technical_Community_Newsletter
If you'd like to keep up with updates and information, subscribe to the
Technical Community Newsletter:
https://www.mediawiki.org/wiki/Newsletter:Technical_Community_Newsletter
Thanks,
Melinda
--
Melinda Seckington
Developer Advocacy Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello all,
*(sorry for cross-posting, and feel free to share this email to other
technical channels)*
On behalf of the Technical Engagement team at the Wikimedia Foundation, I’m
very excited to let you know that after three years of online and hybrid
editions, the Wikimedia Hackathon is about to go back “IRL”, and will take
place on May 19th to 21st in Athens, Greece
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023>.
The Wikimedia Hackathon is an annual event to bring the global technical
community together to connect, hack, and explore new ideas. Technical
contributors from all around the world come together to improve the
technological infrastructure and software that powers and benefits the
Wikimedia projects. The 2023 edition is organized by the Wikimedia
Foundation, in collaboration with the local Wikimedia affiliate, the Wikimedia
Community User Group Greece
<https://meta.wikimedia.org/wiki/Wikimedia_Community_User_Group_Greece>.
This edition of the Wikimedia Hackathon will focus on bringing together
people who already contributed to technical aspects of Mediawiki and the
Wikimedia projects, who know how to find their way on our technical
ecosystem, and who are able to work or collaborate on projects rather
autonomously. People who’d like to get started as technical contributors
are very welcome to look at the list of newcomers-friendly events and
resources
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023/Documentation#Event…>
to start being involved on technical projects.
Most of the Wikimedia Hackathon will take place onsite, but some elements
of the program will be broadcasted online. Local communities are also
welcome to organize pre-hackathon events or meetups. In the upcoming
months, you will find on these pages
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2023> information about
how to attend, the venue, travel, accommodation, and scholarships.
As a next step, registration and scholarship applications will open at the
beginning of December. Updates will be posted regularly on this talk page.
Stay tuned and feel free to share the information to your fellow Wikimedia
technical contributors.
If you have any questions or would like to reach out to the coordination
team, feel free to contact hackathon(a)wikimedia.org or comment on the talk
page <https://www.mediawiki.org/wiki/Talk:Wikimedia_Hackathon_2023>.
We are really looking forward to welcoming you again at the Hackathon
onsite, and we hope that you are also excited to join and hack together!
Best,
--
*Léa Lacroix *(she/her)
Hackathon Event Coordinator
Wikimedia Foundation <https://wikimediafoundation.org/>
On this coming Monday, Nov 22, at 22:00 UTC (14:00 PST) we are
planning to migrate the production Phabricator instance from old
hardware to newer
hardware. (phab1001 -> phab1004)
We are reserving a 30 minute window to switch over but expect actual
user impact to be much shorter.
You should not notice much, it's not a Phabricator version or distro
upgrade, it's all about moving away from old hardware.
We picked a time slot where we expect user traffic to be low.
note: The git-ssh.wikimedia.org service (git over ssh for repos on
Phabricator) has been disabled
a while ago already already and has been deprecated. Please use Gitlab
or Gerrit for all your repo needs.
https://phabricator.wikimedia.org/T280597
--
Daniel Zahn <dzahn(a)wikimedia.org>
Site Reliability Engineer
Hello,
Wikimedia is deprecating and phasing out unencrypted HTTP (T238720
<https://phabricator.wikimedia.org/T238720>), as part of this effort
http://gerrit.wikimedia.org now yields a 403 Forbidden error.
It should not cause any issue since we have always serve Gerrit over
HTTPS and there is a header set to instruct browser to always use that
even when asking for a http:// URL. It might be possible though that a
bot or a local config relied on http:// and those unlikely case will now
be broken.
The change is https://gerrit.wikimedia.org/r/c/operations/puppet/+/859986
If you see any issue, please poke the Phabricator task above.
Antoine Musso && Valentin Gutierrez