This email is a summary of the Wikimedia production deployment of
1.38.0-wmf.5 which has been successfully completed last week.
* Conductor: Antoine "hashar" Musso
* Backup Conductor: Ahmon Dancy
* Blocker Task: T281169 <https://phabricator.wikimedia.org/T281169>
* Current Status <https://versions.toolforge.org>
🔢 Numbers
Sparklines comparing with the last 5 trains.
* 351 Patches ██▁▂█
* 0 Rollbacks ▁▃█▁▁
* 0 Days of delay ▁▁█▁▁
* 3 Blockers ▄█▇█▁
✨ Traintastic Folks 😻
Thanks to folks who reported or resolved blockers:
* Jon Robson, remembered me about JavaScript client side errors to be
taken of
* Elena and Joseph Seddon, flagged a blocker for group 1 ahead of time
and got it fixed with Simone Cuomo.
* Subramanya Sastry, who has noiticed a missed class in Parsoid
* C. Scott, Lucas Werkmeister who promptly addressed deprecation errors
* Ahmon Dancy for being the backup conductor and closely watching
error logs
Antoine "hashar" Musso
We are happy to announce that Umherirrender has received this quarter's Web
Perf Hero award.
Umherirrender has initiated and carried out significant improvements to the
performance of MediaWiki user preferences (T278650
<https://www.mediawiki.org/wiki/Phab:T278650>, T58633
<https://www.mediawiki.org/wiki/Phab:T58633> , and T291748
<https://www.mediawiki.org/wiki/Phab:T291748>). The impact is felt widely
and throughout Wikimedia sites. For example, when switching languages via
the ULS selector, or exploring Beta Features and Gadgets, or switching
skins. These are all powered by the MediaWiki "Preferences" component.
The work included implementing support for deferred message parsing in more
HTMLForm classes, and applying this to the Echo and Gadgets extensions.
This cut API latency by over 50%, from 0.7s to 0.3s at the median, and 1.2s
to 0.5s at p95. (See graphs at T278650#7130951
<https://www.mediawiki.org/wiki/Phab:T278650#7130951>).
This ward is given to individuals who have gone above and beyond to improve
the performance of Wikimedia Foundation sites. It's awarded once a quarter,
and takes the form of a Phabricator badge
More information and past recipients:
https://www.mediawiki.org/wiki/Wikimedia_Performance_Team/Web_Perf_Hero_awa…
Phabricator badge:
https://phabricator.wikimedia.org/badges/view/17/
-- Timo Tijhof, on behalf of Wikimedia Performance Team.
Hi everyone!
Just a reminder that there is one week left to submit your Coolest Tool
Award nominations. It only takes a few minutes to fill the form in!
Please recommend your favorite tools by October 27nd:
https://meta.wikimedia.org/wiki/Coolest_Tool_Award
Thanks!
andre, for the Coolest Tool Academy 2021
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
This email is a summary of last week's Wikimedia production deployment
of 1.38.0-wmf.4:
Conductor: Ahmon Dancy
Backup Conductor: Brennen Bearnes
Blocker Task: https://phabricator.wikimedia.org/T281168
Current Status: https://versions.toolforge.org/
📈 Numbers
Sparklines comparing with the last 5 trains.
273 Patches ▇██▁▂
0 Rollbacks ▃▁▃█▁
0 Days of delay ▃▁▁█▁
8 Blockers ▃▁█▆█
✨ Traintastic Folks 😻
Thanks to folks who reported/resolved blockers, and otherwise assisted
with this train:
Jon Robson
Bartosz Dziewoński
Zabe
xSavitar
Tim Starling
Majavah
James D. Forrester
DannyS712
ppelberg
EAkinloose
Krinkle
--
Brennen Bearnes
Release Engineering
Wikimedia Foundation
= tl;dr =
Users with Wikimedia developer accounts can now log in to
https://gitlab.wikimedia.org/ and create projects under their user
namespaces, regardless of institutional affiliation.
= The longer version =
Hey all,
This is an update on the Wikimedia GitLab project[0].
GitLab access was formerly restricted to WMF/WMDE/NDA users. We've
lifted that restriction.[1]
With that out of the way, we're working to sort out open questions about
use of shared CI runners[2] and what Docker images they're allowed to
run[3], along with shoring up various aspects of our infrastructure,
cleaning up some lingering authentication bugs, and integrating with
other development services and communication channels.
In general, you can follow this project as a whole on Phabricator, on
the GitLab workboard.[4] As ever, questions are welcome on Phab, in
#wikimedia-releng on libera.chat, or directly in e-mail.
[0]. https://www.mediawiki.org/wiki/GitLab/Roadmap
[1]. https://phabricator.wikimedia.org/T288162
[2]. https://phabricator.wikimedia.org/T292094
[3]. https://phabricator.wikimedia.org/T291978
[4]. https://phabricator.wikimedia.org/tag/gitlab/
Best,
--
Brennen Bearnes
Release Engineering
Wikimedia Foundation
= tl;dr =
Users with Wikimedia developer accounts can now log in to
https://gitlab.wikimedia.org/ and create projects under their user
namespaces, regardless of institutional affiliation.
= The longer version =
Hey all,
This is an update on the Wikimedia GitLab project[0].
GitLab access was formerly restricted to WMF/WMDE/NDA users. We've
lifted that restriction.[1]
With that out of the way, we're working to sort out open questions about
use of shared CI runners[2] and what Docker images they're allowed to
run[3], along with shoring up various aspects of our infrastructure,
cleaning up some lingering authentication bugs, and integrating with
other development services and communication channels.
In general, you can follow this project as a whole on Phabricator, on
the GitLab workboard.[4] As ever, questions are welcome on Phab, in
#wikimedia-releng on libera.chat, or directly in e-mail.
[0]. https://www.mediawiki.org/wiki/GitLab/Roadmap
[1]. https://phabricator.wikimedia.org/T288162
[2]. https://phabricator.wikimedia.org/T292094
[3]. https://phabricator.wikimedia.org/T291978
[4]. https://phabricator.wikimedia.org/tag/gitlab/
Best,
--
Brennen Bearnes
Release Engineering
Wikimedia Foundation
Hi Bodhisattwa,
See below.
On Fri, Oct 15, 2021 at 1:41 PM Bodhisattwa Mandal
<bodhisattwa.rgkmc(a)gmail.com> wrote:
>
> Also, is there any way to add info on existing tools?
I learned from Bryan yesterday that this is possible via toolsadmin
(Bryan helped with one of our tools yesterday via
https://toolsadmin.wikimedia.org/tools/id/wikinav for that particular
tool). Toolhub then updates the list of tools every hour and you
should see your tool in toolhub. I hope this helps.
And congratulations to all of you who have been involved in making
this launch and product happen. :)
Leila
>
> Regards,
> Bodhisattwa
>
> On Fri, 15 Oct 2021 at 19:53, Birgit Müller <bmueller(a)wikimedia.org> wrote:
>>
>> Thanks Galder :-) - answers are below:
>>
>> On Thu, Oct 14, 2021 at 9:38 PM Galder Gonzalez Larrañaga <galder158(a)hotmail.com> wrote:
>>>
>>> Thanks, Brigit, for this hub, it is great to have it! I have tried and can't find any way to look for tools that are not nominated as "Coolest Tool Award" besides looking for name. Is there a way for searching by categories?
>>
>>
>> Today you can try searching for various keywords to find tools in the catalog (i.e. "Wikidata", "image", "editor", "template" ...). We're interested in adding support for the community to organize tools in categories/based on use cases in the future. There are some notes from past Design Research on that in the Data Model documentation. [0]
>>
>> Please feel welcome to comment on the talk page if you have further questions or ideas! [1]
>>
>> Birgit
>>
>> [0] https://meta.wikimedia.org/wiki/Toolhub/Data_model#Tool_use_cases
>> [1] https://meta.wikimedia.org/wiki/Talk:Toolhub
>>
>>
>>>
>>>
>>> Thanks
>>> Galder
>>> ________________________________
>>> From: Birgit Müller <bmueller(a)wikimedia.org>
>>> Sent: Thursday, October 14, 2021 4:58 PM
>>> To: wikitech-l <wikitech-l(a)lists.wikimedia.org>; wikimedia-l(a)lists.wikimedia.org <wikimedia-l(a)lists.wikimedia.org>; Wikimedia Cloud Services general discussion and support <cloud(a)lists.wikimedia.org>; wikidata(a)lists.wikimedia.org <wikidata(a)lists.wikimedia.org>; wikitech-ambassadors(a)lists.wikimedia.org <wikitech-ambassadors(a)lists.wikimedia.org>
>>> Subject: [Wikimedia-l] Toolhub 1.0 is launched! Discover software tools used at Wikimedia
>>>
>>>
>>> Hi All,
>>>
>>> We are happy to announce the launch of Toolhub – a community-authored catalogue that aims to make software tools used in the Wikimedia movement discoverable to everyone.
>>>
>>>
>>> Community developed tools – including web applications, bots, gadgets, user scripts, lua modules, and more – play a significant role in the Wikimedia projects. These software applications address a wide range of use cases including finding bad faith edits and other content curation, bulk editing, collecting statistical information, creating special citations, and much more. About ⅓ of all edits are made by bots and tools. In addition, semi-automated edits are helped by user scripts, gadgets, and other editing assistance tools that run from the user's local computer or directly inside the wikis. There are thousands of tools available, but how can you find them?
>>>
>>>
>>> With Toolhub, you can document and find tools, promote their use in your wiki community, and help improve them by contributing data. You can create and share lists of tools relevant to your work - for example, for GLAM tools, or for wiki projects such as Women in Red.
>>>
>>>
>>> This first release provides a core set of functionalities, and contains an initial data set of about 1500 tools. Most of the initial tools in the catalog are imported from the same data files developers have created for Hay's Directory which has been a major inspiration for Toolhub.
>>>
>>>
>>> Toolhub serves developers and users of tools alike. It is part of our efforts to improve the infrastructure and services for technical contributors, captured under one of Technology’s top level objectives in the FY 2020-2021 and 2021-2022 annual plans: Tech Community Building. We hope to continue conversations with developers and users of tools, plan to improve Toolhub, and to further expand the functionality.
>>>
>>>
>>> A collaborative system and open developer platform
>>>
>>> Toolhub is built as an API driven platform that makes it possible to extend and remix the catalogue, and to make collecting and reusing information about tools as open and collaborative as we can. Everything that can be done interactively with the Toolhub website can also be done remotely through the API. We would love to hear from technical contributors interested in using the Toolhub API to build new tools that make new ways to add or consume information from Toolhub's catalog.
>>>
>>>
>>> Our decision record and weekly progress reports on Meta provide more insights in technical implementation details and decisions made throughout the development process. The Toolhub/About page provides information on project origin, research, use cases, data model, and roadmap. This recording from a lightning talk at ‘21 Wikimania gives an overview of the main aspects in 10 minutes.
>>>
>>>
>>> Thank you <3
>>>
>>> This project wouldn’t have been possible without the support, knowledge, ideas and prior work of many. One of the nicest side-effects of a release is that it’s a great opportunity to thank folks for their time and contributions :-)
>>>
>>>
>>> Husky, whose Hay's Directory provided the foundation for the data model used by Toolhub and inspired some of its features.
>>>
>>> Harej, for his invaluable contributions in the early stages of the Toolhub project.
>>>
>>> Our 'advisory board' - Giuseppe (SRE), Risker (editor, admin), Reedy (Security), Keegan (Community Relations), and Eran (volunteer developer & RTL expert) for providing their perspectives on key questions throughout the development process.
>>>
>>> Giuseppe, Kunal, Manuel, Effie, Cole and Emanuele from SRE and Majavah for their help on finding and resolving deployment issues.
>>>
>>> Dan and Jeena from Release Engineering for help with build tooling.
>>>
>>> Guillaume and the rest of the Search Platform team for supporting our search index needs.
>>>
>>> Manuel for supporting our database needs.
>>>
>>> Niklas and the whole translatewiki.net community for help with localization and internationalization.
>>>
>>> Rita, Olga, Alex, and Matthew from the Product Design team for their feedback on the Toolhub user interface.
>>>
>>> Scott from the Security team for our security readiness review.
>>>
>>> Amire, Kunal, Eran, Reedy, and Dan for contributing code to the project.
>>>
>>> Ricordisamoa, Quim, and the people participating in conversations on wikitech-l for T115650 which inspired this whole project.
>>>
>>> Finally, a huge thanks to all the folks who gave input and feedback on the talk page, in Phabricator, and at sessions - this is really appreciated!
>>>
>>>
>>> We hope that this new resource will be fun to explore, inspire you with new ideas, and ultimately be useful for your work.
>>>
>>>
>>> Feedback, bug reports, ideas and questions are more than welcome on the talk page of the project, or in Phabricator. Bryan (tech lead) & Seve (our new Product Manager) will be there to chat with interested folks and help with any questions. We are looking forward to evolving this project step-by-step and jointly with everyone!
>>>
>>>
>>> Birgit – on behalf of Technical Engagement & our Toolhub project team
>>>
>>>
>>>
>>> --
>>> Birgit Müller (she/her)
>>> Director of Technical Engagement
>>>
>>> Wikimedia Foundation
>>> _______________________________________________
>>> Wikimedia-l mailing list -- wikimedia-l(a)lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
>>> Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org…
>>> To unsubscribe send an email to wikimedia-l-leave(a)lists.wikimedia.org
>>
>>
>>
>> --
>> Birgit Müller (she/her)
>> Director of Technical Engagement
>>
>> Wikimedia Foundation
>> _______________________________________________
>> Wikidata mailing list -- wikidata(a)lists.wikimedia.org
>> To unsubscribe send an email to wikidata-leave(a)lists.wikimedia.org
>
> _______________________________________________
> Wikidata mailing list -- wikidata(a)lists.wikimedia.org
> To unsubscribe send an email to wikidata-leave(a)lists.wikimedia.org