Hej hej everyone,
The January 2023 edition of the Technical Community Newsletter is
available:
https://www.mediawiki.org/wiki/Technical_Community_Newsletter/2023/January
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,
andre
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
Hello
*Gerrit's CI (Jenkins and Zuul) will be down for 30 minutes tomorrow
between 14:00–16:00 UTC* due to network switch upgrades[0].
Gerrit will still work. And (after maintenance), you can run CI on any
patch you submit during this window. Either by leaving a Gerrit comment
beginning with the word "recheck" or rebasing your patch[1].
Apologies for the inconvenience :(
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://phabricator.wikimedia.org/T327925>
[1]: <https://www.mediawiki.org/wiki/Continuous_integration/Jenkins>
The *deadline* for applying for a Scholarship to attend Wikimania 2023 in
Singapore on August 16-19 is:
** Sunday, 5 February 2023 23:59 AoE
<https://iw.toolforge.org/zonestamp/1675684740> **
Please spread the word to anyone you know who might qualify.
A full scholarship covers travel, accommodation, and registration. There
are also partial scholarships. To learn more:
https://wikimania.wikimedia.org/wiki/2023:Scholarships
To apply for a scholarship, fill out the application form on:
https://wikimediafoundation.limesurvey.net/799477
** Special call for technical contributors **
If you are a tool creator, maintainer, user, or otherwise contribute to our
movement’s technical ecosystem and are willing to teach and mentor others,
collaborate on technical projects, and help onboard tech folks new to our
technical communities – please do apply and make sure you elaborate on what
technical mentorship you could contribute in your application. This will
greatly increase your chances to be selected.
If you have any questions, please contact:
wikimania-scholarships(a)wikimedia.org or leave a message at: 2023
talk:Scholarships
<https://wikimania.wikimedia.org/wiki/2023_talk:Scholarships>Thank you,
Slavina, on behalf of the Wikimania Scholarship Committee
--
Slavina Stefanova (she/her)
Software Engineer - Technical Engagement
Wikimedia Foundation
TLDR: Any ResourceLoader module will now run on mobile or desktop site by
default. Previously they would only load on the desktop site.
Hopefully this goes without disruption, but to be safe, if you maintain
code used in Wikimedia production, please:
1) check your experiences over the course of this week in mobile/desktop
site for JS errors/obvious UI errors (the former will be detected and
monitored via logstash)
2) check that your repository doesn't fail the core
testUnsatisfiableDependencies PHPUnit test. 3) Please check out the
following Phabricator tickets to see if you are impacted on the long term
[4][5].
# Background
Back in the early days of MobileFrontend, most of the JavaScript we had was
not mobile friendly. To avoid this we created an allow-list system, where
JavaScript was disabled by default and extensions/skins had to explicitly
enable it by adding a "targets" property to their ResourceLoaderModule
definition.
This was meant as a short term solution, but as with many things, attention
got pulled elsewhere, and almost ten years later it was still there.
There have been many complaints about this over those years. Mainly:
1) It means we have split the ResourceLoader cache further
2) It's not intuitive - new code was getting shipped to desktop only
experiences by default.
It also featured on the Developer Wishlist of 2017 at #34 [1].
3) Many older features don't work for community members for no credible
reason.
# Recent developments
As one of the few remaining people responsible for doing this in the first
time, I felt obliged to spend some time over December trying to pay off
this technical debt. I audited code that was being removed by the targets
system [2] and made the target explicit. Where modules were problematic on
mobile, we marked them in such a way that it was clear that they should
only run in a certain mode. This was only possible thanks to attention from
Amir, Santosh, Thiemo, Lucas W, Tpt, Sohom D, Bartosz - thank you all.
Today, Roan merged a change that makes ResourceLoader modules default to
the desktop AND mobile sites. This should be a harmless change, but may be
unintentionally triggering failures in testUnsatisfiableDependencies tests
as it seems some extension/skins are not included in the MediaWiki core
PHPUnit test run. If you encounter this issue, the fix is relatively simple
- you must define targets explicitly (see this example [6] and apologies in
advance for any annoyance this may cause)
# For action
Please take extra care with your code that you test on both mobile/desktop
sites and at mobile/desktop breakpoints. It's still possible to ship code
to mobile/desktop and see these guidelines [3] if you need to do that or
reply to this email with any questions you have.
# Next steps
This change will help with limiting the targets system to existing known
cases. This has been a long term request of the performance team. Please
see the follow up tickets to see if there is any action from you at your
leisure [4][5].
[1] https://www.mediawiki.org/wiki/Developer_Wishlist/2017/results
[2] in https://phabricator.wikimedia.org/T324723
[3]
https://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_for_extension…
[4] https://phabricator.wikimedia.org/T328497
[5] https://phabricator.wikimedia.org/T328498
[6]
https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PropertySuggester/+/8…
This is info about the changes in
https://archive.org/details/2022-daily_user_pageviews.
The following 17 files have been updated (Reason for change: Bad conversion):
2022-azb.wikipedia-daily_user_pageviews.dkmf.gz
2022-bxr.wikipedia-daily_user_pageviews.dkmf.gz
2022-cy.wiktionary-daily_user_pageviews.dkmf.gz
2022-ext.wikipedia-daily_user_pageviews.dkmf.gz
2022-hz.wikipedia-daily_user_pageviews.dkmf.gz
2022-jv.wiktionary-daily_user_pageviews.dkmf.gz
2022-ky.wiktionary-daily_user_pageviews.dkmf.gz
2022-lv.wiktionary-daily_user_pageviews.dkmf.gz
2022-mzn.wikipedia-daily_user_pageviews.dkmf.gz
2022-nz.wikimedia-daily_user_pageviews.dkmf.gz
2022-pwn.wikipedia-daily_user_pageviews.dkmf.gz
2022-qu.wiktionary-daily_user_pageviews.dkmf.gz
2022-szy.wikipedia-daily_user_pageviews.dkmf.gz
2022-tyv.wikipedia-daily_user_pageviews.dkmf.gz
2022-uz.wiktionary-daily_user_pageviews.dkmf.gz
2022-vo.wiktionary-daily_user_pageviews.dkmf.gz
2022-xmf.wikipedia-daily_user_pageviews.dkmf.gz
Dušan Kreheľ
Hello all!
The Search Platform Team usually holds an open meeting on the first
Wednesday of each month. Come talk to us about anything related to
Wikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons Query
Service (WCQS), etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, February 1st, 2023
Time: 16:00-17:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CET
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
Have fun and see you soon!
Guillaume
--
*Guillaume Lederrey* (he/him)
Engineering Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2023-01): 342
Active Maniphest users (any activity) in (2023-01): 1155
Task authors in (2023-01): 605
Users who have closed tasks in (2023-01): 325
Projects which had at least one task moved from one column to another on
their workboard in (2023-01): 323
Tasks created in (2023-01): 2457
Tasks closed in (2023-01): 2281
Open and stalled tasks in total: 52737
* Only open tasks in total: 51824
* Only stalled tasks in total: 913
Median age in days of open tasks by priority:
Unbreak now: 135
Needs Triage: 818
High: 1075
Normal: 1803
Low: 2485
Lowest: 2617
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2023-01): 4
To see the names of the most active task authors:
* Go to https://wikimedia.biterg.io/
* Choose "Phabricator > Overview" from the top bar
* Adjust the time frame in the upper right corner to your needs
* See the author names in the "Submitters" panel
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on phab1004 at Wed 01 Feb 2023 12:01:16 AM UTC)