Hello everyone,
As part of the RESTBase Sunset effort, some endpoints are being phased out
in favor of better, more stable alternatives or completely removed.
The /page/talk <https://en.wikipedia.org/api/rest_v1/#/Talk%20pages>
endpoint is now ready for deprecation. This endpoint is marked as
experimental and its usage has been exclusively by the Android and iOS
apps which
teams signed off on the deprecation readiness
<https://phabricator.wikimedia.org/T392491>. This endpoint has no
alternatives.
Next steps: because this is an experimental endpoint, we decided to apply
the existing policy for REST endpoints
<https://www.mediawiki.org/wiki/API_versioning#Experimental> and turn it
off as soon as possible while still respecting Android and iOS old
versions' deprecation timeline. Traffic to this endpoint can be blocked
starting Today, Sep 29th 2025 (09/29/2025) and code will be removed after
that. Details about the deprecation can be found in this phabricator task,
T401895 <https://phabricator.wikimedia.org/T401895>.
Don't hesitate in getting in touch in case you have any questions or
concerns.
Best regards,
--
Mateus Santos
Product Manager - MediaWiki Engineering Group
Wikimedia Foundation
Hello,
The deadline to submit projects on the Outreachy website is fast
approaching! If you're interested in mentoring a project through Outreachy,
share them here as a subtask of this Phabricator task:
https://phabricator.wikimedia.org/T403210 *before September 26th*. We're
looking forward to receiving your projects!
Best,
Sheila & Lani (Wikimedia Org Admins for Outreachy Round 31)
---------- Forwarded message ---------
From: Sheila Wangari <swangari-ctr(a)wikimedia.org>
Date: Thu, Sep 18, 2025 at 4:14 PM
Subject: [Wikitech-l] Call for Projects and mentors for Outreachy Round 31!
To: <wikitech-l(a)lists.wikimedia.org>, <wikimedia-l(a)lists.wikimedia.org>, <
wikidata(a)lists.wikimedia.org>
Cc: Amanda Bittaker <abittaker(a)wikimedia.org>, Onyinyechi Onifade <
oonifade(a)wikimedia.org>
Hello Everyone,
TLDR: Wikimedia is participating in the Outreachy Round 31 internship
program <https://www.mediawiki.org/wiki/Outreachy/Round_31> [1].
Outreachy's goal is to support people from groups underrepresented in the
technology industry. Interns will work remotely with mentors from our
community. We are seeking mentors to propose projects that Outreachy
interns can work on during their internship. If you have some ideas for coding
or non-coding (design, documentation, translation, outreach, research)
projects, share them by Sept. 26, 2025, at 4 pm UTC <
https://phabricator.wikimedia.org/T403210 > [2]
Program Timeline
As a mentor, you engage potential candidates in the application period
between October–November (winter round) and help them make small
contributions to your project. You work more closely with the accepted
candidates (interns) during the internship period between December–March
(winter round).
Important dates are:
- September 26th, 2025, at 4 pm UTC - Project submission deadline
<https://www.outreachy.org/communities/cfp/wikimedia/>
- October 8, 2025 - Contribution period begins.
- November 3, 2025 - Contribution period ends.
*Guidelines for crafting project proposals *
-
Follow this task description template when you propose a project in
Phabricator: <
https://phabricator.wikimedia.org/tag/outreach-programs-projects/> Add
#Outreachy (Round 31) tag.
-
The project should require an experienced developer~15 days, and a
newcomer, 3 months to complete.
-
Each project should have at least two mentors, including one with a
technical background.
-
Ideally, the project has no tight deadlines, a moderate learning curve,
and fewer dependencies on Wikimedia's core infrastructure. Projects
addressing the needs of a language community are most welcome.
Learn more about the roles and responsibilities of mentors on
MediaWiki.org: <https://www.mediawiki.org/wiki/Outreachy/Mentors> [4][5]
Cheers,
Sheila & Lani (Wikimedia Org Admins for Outreachy Round 31)
[1] https://www.mediawiki.org/wiki/Outreachy/Round_31
[2] https://phabricator.wikimedia.org/T403210
[3] https://phabricator.wikimedia.org/tag/outreach-programs-projects/
[4] https://www.mediawiki.org/wiki/Outreachy/Mentors
[5] https://www.outreachy.org/mentor/mentor-faq/
Hello Everyone,
TLDR: Wikimedia is participating in the Outreachy Round 31 internship
program <https://www.mediawiki.org/wiki/Outreachy/Round_31> [1].
Outreachy's goal is to support people from groups underrepresented in the
technology industry. Interns will work remotely with mentors from our
community. We are seeking mentors to propose projects that Outreachy
interns can work on during their internship. If you have some ideas for coding
or non-coding (design, documentation, translation, outreach, research)
projects, share them by Sept. 26, 2025, at 4 pm UTC <
https://phabricator.wikimedia.org/T403210 > [2]
Program Timeline
As a mentor, you engage potential candidates in the application period
between October–November (winter round) and help them make small
contributions to your project. You work more closely with the accepted
candidates (interns) during the internship period between December–March
(winter round).
Important dates are:
- September 26th, 2025, at 4 pm UTC - Project submission deadline
<https://www.outreachy.org/communities/cfp/wikimedia/>
- October 8, 2025 - Contribution period begins.
- November 3, 2025 - Contribution period ends.
*Guidelines for crafting project proposals*
-
Follow this task description template when you propose a project in
Phabricator: <
https://phabricator.wikimedia.org/tag/outreach-programs-projects/> Add
#Outreachy (Round 31) tag.
-
The project should require an experienced developer~15 days, and a
newcomer, 3 months to complete.
-
Each project should have at least two mentors, including one with a
technical background.
-
Ideally, the project has no tight deadlines, a moderate learning curve,
and fewer dependencies on Wikimedia's core infrastructure. Projects
addressing the needs of a language community are most welcome.
Learn more about the roles and responsibilities of mentors on
MediaWiki.org: <https://www.mediawiki.org/wiki/Outreachy/Mentors> [4][5]
Cheers,
Sheila & Lani (Wikimedia Org Admins for Outreachy Round 31)
[1] https://www.mediawiki.org/wiki/Outreachy/Round_31
[2] https://phabricator.wikimedia.org/T403210
[3] https://phabricator.wikimedia.org/tag/outreach-programs-projects/
[4] https://www.mediawiki.org/wiki/Outreachy/Mentors
[5] https://www.outreachy.org/mentor/mentor-faq/
Hello everyone,
Apologies for cross-posting.
Gentle reminder that the Fall 2025 MediaWiki Users & Developers Conference<https://www.semantic-mediawiki.org/wiki/MediaWiki_Users_and_Developers_Conf…> will be held on October 28-30th, and hosted by the TIB Leibniz Centre in Hanover, Germany.
On behalf of the Program Committee with this email we want to extend an invitation for tutorial proposals on any topic related to MediaWiki usage, deployment or development, including the MediaWiki extension ecosystem (Wikibase, Semantic MediaWiki, etc). Tutorials can be up to 90 mins long and held in hybrid format.
The call for contributions<https://www.semantic-mediawiki.org/wiki/MediaWiki_Users_and_Developers_Conf…> remains open until September 5th. To propose a tutorial or any other form of contribution talk for this conference, just fill out this form<https://www.semantic-mediawiki.org/wiki/Special:FormEdit/Talk?Talk%5BConfer…>.
Everyone is encouraged to attend, to meet and discuss MediaWiki-related topics relating to both the Wikimedia world and uses within companies, organizations, etc.
Thank you, and I hope to see many of you in Hanover!
Lozana Rossenova, on behalf of the conference team
Hello Wikimedia developers! I am writing to update on a small change just
in case it impacts you. If you don't write MediaWiki extensions on
Wikimedia's Gerrit you can disregard this message.
# TLDR
If you see a PHPUnit failure with the text "The following modules have not
declared budgets", instructions on how to address this issue can be found
in this email. The fix involves a small modification to
bundlesize.config.json file that should already exist in your impacted
repository.
# Longer version
In the Wikimedia ecosystem, adding significant JavaScript and CSS to page
load can impact user experience, sometimes increasing the time it takes for
a page to load or become responsive.
This is particularly a concern for readers who may be using slower
connections or need to get information as quickly as possible.
A while back we introduced a test that required codebases to register
ResourceLoader modules that they add to anonymous page views in a
bundlesize.config.json file. This essential acts an audit to easily
identify how code ends up on a page [1]. This only applies to code added by
extensions and the Vector skin (not gadgets). When the test fails it points
to a page on mediawiki.org that documents how to address problems with the
test [2].
Recently we had several incidents where Vue.js and OOUI were loaded on page
load for all anonymous users. For certain users this would have resulted in
the page feeling unresponsive (e.g. frozen). This was because the test did
not take into account the fact that JavaScript modules themselves can load
additional dependencies. As a result of this the test has been updated to
also consider such modules.
IF you experience issues with tests following this change, the
documentation contains all the information you should need to resolve it.
If you have any further problems or the documentation isn't helping you,
please ping me on the talk page, or Gerrit patch you are experiencing the
issue, or on the Phabricator ticket [3] and we'll get it addressed ASAP
(provided I'm not sleeping :-)).
[1]
https://codesearch.wmcloud.org/search/?q=maxSize&files=bundlesize.config.js…
[2] https://www.mediawiki.org/wiki/Performance_budgeting
[3] https://phabricator.wikimedia.org/T395698
Howdy bot builders, tool tinkerers, researchers, and all other Wikimedia
web API users –
We need your help! The MediaWiki Interfaces team is partnering with
design (Sarai
Sanchez <ssanchez(a)wikimedia.org>) to redesign the Wikimedia REST API Sandbox
using Codex. If you have opinions about API documentation and what makes
developer experiences good or bad, we would love to have you participate in
an API sandbox discovery session!
— What to expect —
A ~45 minute video call session to ask questions about your Wikimedia API
experience with a focus on pain points related to documentation. In
addition to high level questions, we will ask you to perform a task or two
to find information using the existing API docs, followed by reviewing
mocks for the new experience to compare the experiences.
If you’d like to participate, please either respond to this message or grab
time directly on Sarai’s calendar
<https://calendar.app.google/TAwmwy145SatRc5D7>.
NOTE: Although the conversation will predominantly focus on building a
better experience for the REST APIs, no experience with using them is
necessary. In fact, we want some folks who have never used the REST APIs to
see what the first use experience is like!
— More Context —
Earlier this year, we launched a limited release
<https://www.mediawiki.org/wiki/MediaWiki_Interfaces_Team/Feature_Feedback/R…>
of a new REST Sandbox built using SwaggerUI
<https://test.wikipedia.org/wiki/Special:RestSandbox>. While this
experience will be made available on all Wikimedia projects soon, we are
also in the process of redesigning the experience from the ground up using
Codex. The shift is motivated by better translation and
internationalization support, and better compliance with open source
standards <https://phabricator.wikimedia.org/T382086>. We also hope that by
designing the documentation from the ground up, we can learn from a variety
of best practices from APIs around the internet to create the best possible
experience for Wikimedia developers.
— Asynchronous feedback —
We are still in an early phase of discovery, where live (and sometimes
unexpected or meandering) conversations lead to the best learnings. We will
provide an asynchronous feedback mechanism for the new experience as we get
farther into the design refinement process, where users like you will be
able to review screenshots and provide feedback on your own time. Even if
you don’t have time to talk to us now, keep an eye out for future calls for
feedback on this topic!
In the meantime, we do have a few other options for asynchronous feedback:
-
For feedback on the existing, SwaggerUI REST sandbox, please review and
respond to the open feedback prompts
<https://www.mediawiki.org/wiki/MediaWiki_Interfaces_Team/Feature_Feedback/R…>or
start a new conversation on the discussion page.
-
For broader API feedback, feel free to respond to the developer
discovery prompts
<https://www.mediawiki.org/wiki/MediaWiki_Interfaces_Team/Developer_Feedback…>
we have about Wikimedia Web APIs or raise a new topic on the discussion
page.
— What’s next? —
We are currently in the design stage for the redesign, with a plan to start
implementation in a near future quarter. Because we have the opportunity to
completely customize the experience, we would love to get feedback early
and often from the community to make sure it fits your needs and creates a
delightful experience for all Wikimedia developers!
Please feel free to reach out with any questions, comments, or concerns you
might have. We look forward to hearing from you, and can’t wait to shape
the future of the Wikimedia APIs together!
Thanks,
Halley & Sarai
*Halley Coplin* (she/her)
Sr. Product Manager, MediaWiki Interfaces
Wikimedia Foundation <https://wikimediafoundation.org/>