I had imported gadget AJQuickDelete from commons to gu.wiki a few years
back, which worked perfectly well until I updated it last month. Not it has
disappeared from the navigation bar.
Can someone please help me by looking in to it?
(If you don't use jQuery in your code or gadgets, you can ignore this email)
in 2017 jQuery 3 got deployed to production and a backward compatibility
layer was introduced to prevent old codes from breaking. Since then it has
been emitting warnings in your console. All start with "JQMIGRATE". Some of
these old jquery breaking changes have been deprecated in versions released
in 2006 or 2007.
We are slowly pulling the plug and removing that compatibility layer (which
would reduce the default payload and make Wikipedia faster for everyone).
Yesterday, that layer was removed from mediawiki CI, tests in gated
extensions have passed but there is a chance that your extension might be
broken in CI now if it's not part of gated extensions. In that case, please
fix the errors.
We will move forward to deploy this in Wikimedia wikis soon meaning really
old gadgets will also break if they don't fix their code. Please check your
console and if you see jquery migration deprecation warnings, attend to
them because they will break soon. Firefox doesn't give trace to warnings
anymore but in Chrome (and using ?debug=1) you can easily find the source
of deprecation warnings.
We already fixed many usages in code and gadgets and we will make sure to
fix heavily used gadgets and user scripts but we can't possibly fix
everything and it's the maintainers' responsibility to fix deprecation
warnings that is being emitted for years.
Another aspect is that if you use jquery.ui, this library has been
deprecated as well and I recommend moving away from it but if you still use
it and migration can be hard, we patched our jquery.ui fork to make sure it
doesn't break. Still, if you find a part of jquery.ui that has not been
fixed, let me know.
You can track the work in https://phabricator.wikimedia.org/T280944 and the
metrics of deprecations can be found in
Thank you and sorry for the inconvenience.
tl;dr: https://gitlab.wikimedia.org/ exists now and individuals can host
projects there; at the team level we're moving some RelEng projects over
and will be in touch with early adopters soon; you can find a roadmap
for this work at https://www.mediawiki.org/wiki/GitLab/Roadmap - read on
for more details.
It's been a while since my last update on WMF's implementation of
GitLab, so here's another one.
When I last wrote, we were hoping to have a minimum-viable installation
of GitLab by the end of June. That mostly worked out.
gitlab.wikimedia.org is now live, and seeing (limited) real usage.
So can you use it? Yes, with caveats.
* Once T288162 - https://phabricator.wikimedia.org/T288162 - is resolved
in the near future, everyone with a Wikimedia developer account should
be able to sign in. Until then, use is limited to members of the WMF,
WMDE, and NDA groups.
* No shared CI job runners are provided yet
* No teams just yet, only individual projects, getting ACL right is hard :)
* Your data will not be obliterated from here forward, *probably*
* We have backups even!
Can teams use it? Soon! RelEng is porting a few projects over, and then
we'll get in touch with teams on the early adopter list.
Things we're thinking about:
* Shared CI runners: https://phabricator.wikimedia.org/T287279
* ACL groups and membership: https://phabricator.wikimedia.org/T282842
* Early adopters: https://phabricator.wikimedia.org/T282842
The WMF has also hired two full-time serviceops folks with a GitLab focus.
Lastly, I'll note that we have a roadmap for this work, with rough
As ever, you can follow work on this project on Phabricator:
Feel free to reach out with any questions via mail, Phabricator, or
#wikimedia-releng on Libera Chat IRC.
We will upgrade our Gerrit to [version 3.3]. We have scheduled it on
Tuesday, August 3rd at 16:00 UTC. We will first upgrade the [Gerrit
replica] then the primary server. The service will thus be unavailable for
a few minutes while we conduct the operation and restart the service.
The July 19th upgrade took a bit longer than expected since we were trying
our runbook for the first time. We have since improved our documentation
and addressed a few configuration glitches we had.
This upgrade comes with a new feature: "Attention Set". It replaces change
*assignees* with a list of people that are expected to act on the change.
It helps better differentiate changes you have already reviewed from the
one you have to review or amend. The feature is nicely explained on
upstream documentation page:
Ahmon, Antoine, Brennen
[version 3.3] https://www.gerritcodereview.com/3.3.html
Upgrade task: https://phabricator.wikimedia.org/T262241
This email is a reminder to start proposing projects and sessions for this
year’s Wikimania hackathon, taking place on August 13th (the first day of
Wikimania). You may have already seen the announcement email last week with
all the details.
This year’s hackathon will take place in a 24 hrs format covering all time
zones. You can start proposing a session or a project by following the
guidelines here: <
We also encourage folks to reuse the video of a previously recorded session
(in lecture format) to organize a watch party-style session. And, you can
pause during or after for questions and discussions. That way, you have to
do less prep, and one can watch your session at any time during the event.
There isn't a specific focus area proposed this time, so your session or
project needn't fit under a theme. Anything that involves MediaWiki
development or covers a technical area in the Wikimedia ecosystem. Plus, we
welcome sessions that would be helpful to newcomers–new to the event, our
technical spaces, or projects.
If you have any questions, feel free to use the related talk page to
contact the organizing team or join the community conversation on Telegram:
We look forward to your participation!
On behalf of the Wikimania Hackathon organizing team
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
I have a script for writing to the Wikidata API that respects the rate limit of 50 edits per minute for bots without a bot flag. However, when that script was used by somebody else, she received the error "As an anti-abuse measure, you are limited from performing this action too many times in a short space of time, and you have exceeded this limit.\nPlease try again in a few minutes". I think it is because she is a "newbie" who is subjected to a slower rate (i.e. as in https://www.mediawiki.org/wiki/Manual:$wgRateLimits).
1. Is there a newbie rate limit that is slower than the rate for "normal" registered users?
2. If so, what is that limit?
3. How many edits must a newbie user make before they are no longer considered a "newbie" (or is number of edits not the criterion for being considered a newbie)?
Steven J. Baskauf, Ph.D. he/him/his
Data Science and Data Curation Specialist / Librarian III
Jean & Alexander Heard Libraries, Vanderbilt University
Nashville, TN 37235, USA
Office: Eskind Biomedical Library, EMB 111
Phone: (615) 343-4582
With excitement we're sharing today that Vue.js is Wikimedia
framework for use with MediaWiki.
The evaluation of front-end frameworks officially started mid 2019, as
part of the Platform Evolution program’s goal to evolve our technology
platform and development processes to empower the Wikimedia
The corresponding Technical RFC was successfully resolved in March
2020. As this framework selection is a wide-ranging, long-term
decision, a dedicated group, the Front-end Architecture Working
Group, was established to drive the technology comparison and the
final recommendation. Besides the resolved RFC the outcome was to
build and test developer experience in a pilot project.
The selected pilot was within the Desktop Improvements project with
its new Vue.js-based TypeaheadSearch feature that allows for providing
additional context while searching. Since its introduction in March
2021 the new TypeaheadSearch component has been the default across
15 wikis of varying sizes and has received positive user feedback.
A final developer satisfaction survey was completed to gain further
information on the developer experience. The survey results emphasized
“a positive light on the future of working with Vue.js”. And “[t]he
engineers felt optimistic about the future and confident in
recommending it for adoption across all our teams.”
The pilot gave us confidence in the recommendation to adopt Vue.js and
we are moving into further implementation of Vue.js tooling and
product migration planning.
To support further efforts, the Wikimedia Foundation has established
the Wikimedia Design System team, which I'm proudly part of. Our
continued work and upcoming priorities include:
- Preparing a shared Vue.js user-interface components library
- Deciding on Vue 2 or Vue 3 including transition path
- Figuring out how the components library will be built and
distributed in and beyond MediaWiki
You can find more of the ongoing work on Phabricator.
For full transparency, we've carried that knowledge with us for some
time already, but were prioritizing progressing integration, annual
planning and our internal All-hands conference to finally arrive at
this announcement today.
I'd like to thank a number of folks involved in leading to this, all
Front-end Architecture Working Group members, especially colleagues
Eric Gardner & Roan Kattouw for driving the RFC, the Readers Web team
for undergoing as pilot implementers and especially our former
colleague Stephen Niedzielski who was central to making it a success,
Wikimedia Deutschland for numerous insights through their Vue.js
experience, current Design System team members responsible for further
progress, all Movement volunteers involved in both providing feedback
to the pilot and contributing to development and Product & Tech
department leadership for their strong support of this wide-reaching
Wikimedia Design System
1 Montgomery Street
San Francisco, CA 94104