Hi,
I am currently working on designing a bot to support open-source software
development: the idea is that the bot can analyze code review comments,
detect those related to explaining the reasons behind the implementation
choices and suggest these reasons as source code comments. As the first
step of this design process we would like to ask developers involved in
code reviews to answer a survey (we expect it to take not more than 25
minutes): https://forms.office.com/r/9nD4HtNbTK
Thanks in advance,
--
Felipe Ebert
Eindhoven University of Technology, The Netherlands
Hi,
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?
Thanks,
Dhaval
Hi,
(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
https://grafana.wikimedia.org/d/000000037/mw-js-deprecate?orgId=1&refresh=1…
Thank you and sorry for the inconvenience.
--
Amir (he/him)
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.
----
Hi all,
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
timelines, here:
https://www.mediawiki.org/wiki/GitLab/Roadmap
As ever, you can follow work on this project on Phabricator:
https://phabricator.wikimedia.org/project/board/5057/
Feel free to reach out with any questions via mail, Phabricator, or
#wikimedia-releng on Libera Chat IRC.
--
Brennen Bearnes
Release Engineering
Wikimedia Foundation
Hello,
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:
http://gerrit-documentation.storage.googleapis.com/Documentation/3.3.1/user…
Ahmon, Antoine, Brennen
Release Engineering
[version 3.3] https://www.gerritcodereview.com/3.3.html
[Gerrit replica]
https://wikitech.wikimedia.org/wiki/Gerrit-replica.wikimedia.org
Upgrade task: https://phabricator.wikimedia.org/T262241
Hello all,
We invite you all to sign up for Toolhub's Quality Signal sessions!
Toolhub <https://meta.wikimedia.org/wiki/Toolhub> [1] is a
community-authored catalog of Wikimedia tools. On Toolhub, you will be able
to discover new tools in the Wikimedia ecosystem, promote their use in your
wiki community, and help improve them by contributing data. Toolhub's first
release is planned around Wikimania 2021.
The Toolhub team is currently working on identifying quality indicators
through conversations with tool users and developers. As a tool user, how
do you know which tool is reliable, useful, and safe to use? As a tool
maintainer, what makes it attractive to you to contribute to an existing
tool? What information are you looking for to decide whether to join a tool
project? We hope that these sessions will help gather quality indicators
for tools and provide valuable insight toward developing new features to
convey the quality.
Want to organize a quality signal session in your community in August/early
September? Please get in touch on the talk page or sign-up for an already
planned session by adding your name below it: <
https://meta.wikimedia.org/wiki/Toolhub/The_Quality_Signal_Sessions> [2].
Your feedback, thoughts, ideas would be valuable!
If you are attending Wikimania, we are running a few introductions and a
feedback session as part of the unconference. Learn more here: <
https://wikimania.wikimedia.org/wiki/2021:Unconference/Toolhub> [3].
Cheers,
Srishti
On behalf of the Toolhub team
[1] https://meta.wikimedia.org/wiki/Toolhub
[2] https://meta.wikimedia.org/wiki/Toolhub/The_Quality_Signal_Sessions
[3] https://wikimania.wikimedia.org/wiki/2021:Unconference/Toolhub
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello all,
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: <
https://wikimania.wikimedia.org/wiki/2021:Hackathon#Propose_a_project_or_a_…>
[1].
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:
<https://t.me/wikimaniachat> [2].
We look forward to your participation!
Cheers,
Srishti
On behalf of the Wikimania Hackathon organizing team
[1]
https://wikimania.wikimedia.org/wiki/2021:Hackathon#Propose_a_project_or_a_…
[2] https://t.me/wikimaniachat
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds
office hours the first Wednesday of each month. Come talk to us about
anything related to Wikimedia search, Wikidata Query Service, Wikimedia
Commons Query Service, etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, August 4th, 2021
Time: 15:00-16:00 GMT / 08:00-09:00 PDT / 11:00-12:00 EDT / 17:00-18:00 CEST
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vgj-bbeb-uyi
Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927
*NOTE: We have a new Google Meet link as of August 2021, which offers
international calling options.*
Trey Jones
Sr. Computational Linguist, Search Platform
Wikimedia Foundation
UTC–4 / EDT
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).
Questions:
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)?
Thanks!
Steve Baskauf
--
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
https://my.vanderbilt.edu/baskauf/
This email is a summary of the Wikimedia production deployment of
1.37.0-wmf.16.
Mukunda Modell was the train conductor last week. Antoine Musso (hashar)
was the backup conductor.
Blocker task: https://phabricator.wikimedia.org/T281157
The new version is live on all sites: https://versions.toolforge.org/
== 📊 Stats ==
* 365 patches ↑
* 1 risky patch ↑
* 1 rollback (for ~2hours) ↑
* 0 days of delay ↓
* 2 blockers added, 0 resolved, 2 removed — same as last week
** OPEN: https://phabricator.wikimedia.org/T287704 by @mmodell
** RESOLVED: https://phabricator.wikimedia.org/T286490 by @dancy
== 🚂🌈 ==
A couple of tasks were mentioned but not added as blockers:
* OPEN: https://phabricator.wikimedia.org/T287642 by @brennen
* RESOLVED: https://phabricator.wikimedia.org/T287649 by @IKhitron
* RESOLVED: https://phabricator.wikimedia.org/T191021 by @Trizek-WMF
Thank you to everyone who filed tasks, triaged bugs, talked publicly, added
risky patch notifications, and braved yet another production deployment. To
quote Winnie the Pooh: "You are braver than you believe, stronger than you
seem, and smarter than you think"
Much thanks goes to:
* Addshore
* alexhollender
* daniel
* DannyS712
* Etonkovidova
* IKhitron
* Jdlrobson
* Krinkle
* Ladsgroup
* Legoktm
* Majavah
* ovasileva
* Pchelolo
* Zabe
– The Trainbow Bunch