April 2022 - Wikitech-l - lists.wikimedia.org

Database dumps
by Byrial Jensen 17 Apr '25

17 Apr '25

Until some weeks ago http://dumps.wikimedia.org/backup-index.html used to show 4 dumps in progress at the same time. That meant that new database dumps normally was available within about 3 weeks for all databases except for enwiki and maybe dewiki where the dump process due to size took longer time. However the 4 dumps processes at one time become 3 some weeks ago. And after massive failures at June 4, only one dump has been in progress at the same time. So at the current speed it will take several months to come thru all dumps. Is it possible to speed up the process again using several dump processes at the same time? Thank you, Byrial

3 2

User-Agent:
by Domas Mituzas 17 Apr '25

17 Apr '25

Hi! from now on specific per-bot/per-software/per-client User-Agent header is mandatory for contacting Wikimedia sites. Domas

19 61

Acquiring list of templates including external links
by Takashi OTA 17 Apr '25

17 Apr '25

Hoi, This is an inquiry from my friend in academia, researching about Wikipedia. He would like to know whether there's a way to acquire a list of templates including external links. Here are some examples including external links. https://ja.wikipedia.org/wiki/Template:JOI/doc https://ja.wikipedia.org/wiki/Template:Twitter/doc Such links are stored in externallinks.sql.gz, in an expanded form. When you want to check increase/decrease of linked domains in chronological order through edit history, you have to check pages-meta-history1.xml etc. In a such case, traditional links and links by templates are mixed, Therefore, the latter ones (links by templates) should be expanded to traditional link forms. Sorry if what I am saying does not make sense. Thanks in advance, --Takashi Ota [[U:Takot]]

13 24

EBNF grammar project status?
by Steve Bennett 01 Apr '25

01 Apr '25

What's the status of the project to create a grammar for Wikitext in EBNF? There are two pages: http://meta.wikimedia.org/wiki/Wikitext_Metasyntax http://www.mediawiki.org/wiki/Markup_spec Nothing seems to have happened since January this year. Also the comments on the latter page seem to indicate a lack of clear goal: is this just a fun project, is it to improve the existing parser, or is it to facilititate a new parser? It's obviously a lot of work, so it needs to be of clear benefit. Brion requested the grammar IIRC (and there's a comment to that effect at http://bugzilla.wikimedia.org/show_bug.cgi?id=7 ), so I'm wondering what became of it. Is there still a goal of replacing the parser? Or is there some alternative plan? Steve

26 217

Phabricator upstream shutdown
by Brian Wolff 21 Mar '25

21 Mar '25

It sounds like phabricator upstream is going away: https://admin.phacility.com/phame/post/view/11/phacility_is_winding_down_op… Just curious, are we planning to continue using it long term or move to something else? -- Brian

10 12

Missing Section Headings
by Marc Riddell 12 Sep '24

12 Sep '24

Hello, I have been a WP editor since 2006. I hope you can help me. For some reason I no longer have Section Heading titles showing in the Articles. This is true of all Headings including the one that carries the Article subject's name. When there is a Table of Contents, it appears fine and, when I click on a particular Section, it goes to that Section, but all that is there is a straight line separating the Sections. There is also no button to edit a Section. If I edit the page and remove the "== ==" markers from the Section Titles, the Title then shows up, but not as a Section Heading. Also, I don't have any Date separators on my Want List. This started 2 days ago. Any thoughts? Thanks, Marc Riddell [[User:Michael David]]

10 11

How to make commits from mirrored Wikimedia repos show up on your GitHub profile
by Bartosz Dziewoński 27 Jun '24

27 Jun '24

I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here. tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.) (Is there a place on mw.org to put this tidbit on?) ------- Forwarded message ------- From: "Brian Levine" <support(a)github.com> (GitHub Staff) To: matma.rex(a)gmail.com Cc: Subject: Re: Commits in mirrored repositories not showing up on my profile Date: Tue, 09 Jul 2013 06:47:19 +0200 Hi Bartosz In order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit. The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits. Cheers Brian -- Matma Rex

3 3

Research FAQ gets a facelift
by Dario Taraborelli 25 Jun '24

25 Jun '24

We just released a new version of Research:FAQ on Meta [1], significantly expanded and updated, to make our processes at WMF more transparent and to meet an explicit FDC request to clarify the role and responsibilities of individual teams involved in research across the organization. The previous version – written from the perspective of the (now inactive) Research:Committee, and mostly obsolete since the release of WMF's open access policy [2] – can still be found here [3]. Comments and bold edits to the new version of the document are welcome. For any question or concern, you can drop me a line or ping my username on-wiki. Thanks, Dario [1] https://meta.wikimedia.org/wiki/Research:FAQ [2] https://wikimediafoundation.org/wiki/Open_access_policy [3] https://meta.wikimedia.org/w/index.php?title=Research:FAQ&oldid=15176953 *Dario Taraborelli *Head of Research, Wikimedia Foundation wikimediafoundation.org • nitens.org • @readermeter <http://twitter.com/readermeter>

2 1

bluejeans
by Jeremy Baron 22 Feb '23

22 Feb '23

Hi, On Tue, Mar 1, 2016 at 3:36 PM, David Strine <dstrine(a)wikimedia.org> wrote: > We will be holding this brownbag in 25 minutes. The Bluejeans link has > changed: > > https://bluejeans.com/396234560 I'm not familiar with bluejeans and maybe have missed a transition because I wasn't paying enough attention. is this some kind of experiment? have all meetings transitioned to this service? anyway, my immediate question at the moment is how do you join without sharing your microphone and camera? am I correct thinking that this is an entirely proprietary stack that's neither gratis nor libre and has no on-premise (not cloud) hosting option? are we paying for this? -Jeremy

9 16

Unsubscribe from mail list
by Arpit Maheshwari 11 Jan '23

11 Jan '23

This is a request to please kindly unsubscribe me from your mailing list

4 4

List related to repositories which haven't mediawiki/mediawiki-codesniffer
by Zoran Dori 10 Jan '23

10 Jan '23

Hello, can someone to update list https://phabricator.wikimedia.org/P10500 which contains repositories which haven't mediawiki/mediawiki-codesniffer. I found in list that much repositories are empty, and repositories which aren't available on Gerrit. So, can someone please update this list of repositories (in mediawiki/extensions) which haven't mediawiki/mediawiki-codesniffer, but at least, contains one PHP file. or to provide me command with which I can update list when I want, so I don't need to request it every time. Best regards, Zoran. P. S.: Happy weekend! :)

4 6

Repository ownership of the Lingo extension
by Zoran Dori 10 Jan '23

10 Jan '23

Hi everyone, I want to notify you that I have, on behalf of the WikiTeq company, made a task https://phabricator.wikimedia.org/T298277 for requesting repository ownership for the Lingo extension. In case that you have any kind of questions, please let me know. :) Best regards, Zoran

3 3

Changes in schema of MediaWiki links tables
by Amir Sarabadani 11 Aug '22

11 Aug '22

(If you don’t work with links tables such as templatelinks, pagelinks and so on, feel free to ignore this message) TLDR: The schema of links tables (starting with templatelinks) will change to have numeric id pointing to linktarget table instead of repeating namespace and title. Hello, The current schema and storage of most links tables are: page id (the source), namespace id of the target link and title of the target. For example, if a page with id of 1 uses Template:Foo, the row in the database would be 1, 6, and Foo (Template namespace has id of 6) Repeating the target’s title is not sustainable, for example more than half of Wikimedia Commons database is just three links tables. The sheer size of these tables makes a considerable portion of all queries slower, backups and dumps taking longer and taking much more space than needed due to unnecessary duplication. In Wikimedia Commons, on average a title is duplicated around 100 times for templatelinks and around 20 times for pagelinks. The numbers for other wikis depend on the usage patterns. Moving forward, these tables will be normalized, meaning a typical row will hold mapping of page id to linktarget id instead. Linktarget is a new table deployed in production and contains immutable records of namespace id and string. The major differences between page and linktarget tables are: 1- linktarget values won’t change (unlike page records that change with page move) 2- linktarget values can point to non-existent pages (=red links). The first table being done is templatelinks, then pagelinks, imagelinks and categorylinks will follow. During the migration phase both values will be accessible but we will turn off writing to the old columns once the values are backfilled and switched to be read from the new schema. We will announce any major changes beforehand but this is to let you know these changes are coming. While the normalization of all links tables will take several years to finish, templatelinks will finish in the next few months and is the most pressing one. So if you: - … rely on the schema of these tables in cloud replicas, you will need to change your tools. - … rely on dumps of these tables, you will need to change your scripts. Currently, templatelinks writes to both data schemes for new rows in most wikis. This week we will start backfilling the data with the new schema but it will take months to finish in large wikis. You can keep track of the general long-term work in https://phabricator.wikimedia.org/T300222 and the specific work for templatelinks in https://phabricator.wikimedia.org/T299417. You can also read more on the reasoning in https://phabricator.wikimedia.org/T222224. Thanks -- *Amir Sarabadani (he/him)* Staff Database Architect Wikimedia Foundation <https://wikimediafoundation.org/>

1 2

Requesting feedback about the future of the LocalisationUpdate extension
by Niklas Laxström 08 May '22

08 May '22

Since the beginning of the year, the Wikimedia Language team has enabled translation backports for MediaWiki core, extensions and skins hosted on Gerrit. On a weekly schedule compatible translations from master branch are backpored to all the supported release branches. Currently supported branches are 1.35–1.38. Translation backports partially replace the purpose of the LocalisationUpdate extension. Wikimedia sites no longer use the extension, and to our knowledge only a few other users of the extension exist, because it needs manual setup to use. We, the Language team, think that maintaining the LocalisationUpdate extension is no longer a good use of our time. We are asking for your feedback about the future of this extension. We are planning to: * Remove LocalisationUpdate from the MediaWiki Language Extension Bundle starting from version 2022.07 * Remove us as maintainers of the extension Additionally, based on the feedback, we are planning to either mark the extension as unmaintained, transfer maintenance to a new maintainer, or request the extension to be archived and removed from the list of extensions bundled with MediaWiki core if there is no indication that anyone uses this extension. We request your feedback and welcome discussion on https://phabricator.wikimedia.org/T300498. Please let us know if you are using this extension and whether you would be interested in maintaining it. *Anticipated questions* Q: What about Wikimedia sites: does this mean they will not get frequent translation updates as they used to have? A: We still think this is important, but we do not think the previous solution can be restored. We would like to collaborate on new solutions. One solution could be more frequent deployments. -Niklas

4 5

Talk to the Search Platform / Query Service Team—May 4th, 2022
by Trey Jones 03 May '22

03 May '22

The Search Platform Team <https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> 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, May 4th, 2022 Time: 15:00-16:00 GMT / 08:00-09:00 PDT / 11:00-12:00 EDT / 16:00-17:00 WAT / 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 Hope to talk to you next week! —Trey Trey Jones Staff Computational Linguist, Search Platform Wikimedia Foundation UTC–4 / EDT

1 1

Make working with templates easier: Several improvements coming to all wikis soon.
by Johanna Strodt 29 Apr '22

29 Apr '22

Hi everyone, In 2019, the German-speaking wikis selected “Make working with templates easier” as the focus area of Wikimedia Deutschland’s Technical Wishes project. Since then, our team has made improvements in different areas, to help template creators as well as users of the wikitext editor and VisualEditor. Our work on this focus area is coming to an end, so I’d like to summarize what happened and lay out the next steps: Two changes from our Templates project have been available on all* wikis for a while already: - A new attribute “suggested values” was introduced to help you clarify what values a parameter may expect. [1] - Line numbers are shown in the “Template” namespace when syntax highlighting (CodeMirror extension) is turned on. [2] A few wikis have these line numbers in _all_ namespaces. If you want this for your wiki as well, please reach out to us. Several other changes were deployed to a small group in the past months. A big thanks to Catalan, Turkish, Greek, Malay, Twi, French, Hungarian, Hebrew, Finnish, Dagbani and German Wikipedia, to English Wikivoyage and Nauruan Wiktionary as well as Wikitech wiki for testing these changes and giving feedback to help us improve these projects. These changes are now coming to more wikis: - Finding and inserting templates will become easier with an improved search (in the TemplateWizard & in the template dialog of VisualEditor and New Wikitext mode). [3] - In VisualEditor, you’ll be able to remove a template from a page via the context menu, just like removing a table or an image. [4] - In VisualEditor, the template dialog will become bigger and descriptions will be more visible. [5] - When using syntax highlighting (CodeMirror extension)*, matching brackets will be highlighted [6] and the color scheme will be updated for better readability [7]. The planned deployment date for all of these changes is March 9 (and March 16 on English Wikipedia). A few weeks later, we’ll be deploying the last improvements from our Templates project: - For syntax highlighting (CodeMirror extension), a colorblind-friendly color scheme will be added. You’ll be able to activate it via a user setting. - A range of fundamental changes to the VisualEditor template dialog will be deployed. They will make it easier to understand what is expected from a template, to navigate the template dialog, and to add parameters to a template. Feedback on all the projects is much appreciated on their respective talk pages. Thanks a lot on behalf of the Technical Wishes team, Johanna, Community Communications Technical Wishes --- * All improvements in the CodeMirror extension, which provides syntax highlighting, only apply to wikis that have the extension installed. This is generally true for left-to-right language wikis, because unfortunately the extension doesn’t work sufficiently for right-to-left languages yet [1] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Suggested_values_for_… [2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Line_Numbering [3] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Finding_and_inserting… [4] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Removing_a_template_f… [5] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/VisualEditor_template… [6] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Bracket_Matching [7] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Improved_Color_Scheme…

1 1

Wikimedia Hackathon: Call for Sessions
by Haley Lepp 28 Apr '22

28 Apr '22

Hello all! Are you planning to attend the Wikimedia Hackathon <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022> from May 20-22 next month? We hope to see you there! The main event will be held online. We have an open call for sessions on our schedule page <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Schedule>. If you'd like to host a session, you can simply pick an open slot in the category which best fits your topic. The developer advocacy team also put together some suggestions <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2022/Schedule/Sessions> for how to create a fun session. You can also add project ideas to the Phabricator Board. <https://phabricator.wikimedia.org/project/view/5802/> We will share more information soon about how to join the online space and where to find local meetups. Take care! Haley and the Hackathon Committee

7 7

MediaWiki Language Extension Bundle 2022.04
by Kartik Mistry 28 Apr '22

28 Apr '22

We would like to announce the release of MediaWiki Language Extension Bundle 2022.04. This bundle is compatible with '''MediaWiki >= 1.36.4 < 1.37 ''' or '''MediaWiki >= 1.37.4''' and requires '''PHP 7.3.19''' or above. The next MLEB is expected to be released in 3 months. If there are very important bug fixes, we will do an intermediate release. Please give us your feedback at [[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]]. * Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.04.tar… * sha256sum: a5ef23339730ec80422d60c31ece1fb696397f6be90fbe9fbf703cc9ddbf5527 * Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2022.04.tar… Quick links: * Installation instructions are at: https://www.mediawiki.org/wiki/MLEB * Announcements of new releases will be posted to a mailing list: https://lists.wikimedia.org/postorius/lists/mediawiki-i18n.lists.wikimedia.… * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ A detailed release note for this release can be found at: https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle/2022.04 -- Kartik Mistry | કાર્તિક મિસ્ત્રી kartikm.wordpress.com

1 0

Re: [Wikimedia-l] Third Pywikibot workshop on Friday, April 29th, 16:00 UTC
by Srishti Sethi 27 Apr '22

27 Apr '22

Hello Handgod, We currently do not have the resources to offer the workshop content in different languages. We are investigating the possibility of taking this up in future projects. One thing, though, is that we are presently exploring Google Meet's live captioning feature, and interestingly, it offers translations in French. As I have not tested this feature myself, particularly for non-English translations, I am unsure how reliable it is, something you might want to try out! Best, Srishti *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/> On Fri, Apr 15, 2022 at 1:31 PM Handgod Abraham <sambayo23(a)gmail.com> wrote: > Thanks ! Is a French translation planned please ? > > Le ven. 15 avr. 2022 à 15:42, Srishti Sethi <ssethi(a)wikimedia.org> a > écrit : > >> Hello everyone, >> >> >> The third workshop on the topic of "Writing Pywikibot scripts" is coming >> up - it will take place on Friday, April 29th at 16:00 UTC. You can find >> more details on the workshop and a link to join here: < >> https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_write_…> >> [1]. >> >> >> This workshop will introduce participants to writing basic scripts via >> the Pywikibot framework. We will be focusing on examples of scripts that >> participants have requested to cover in the workshop (e.g., finding and >> replacing content, archiving discussions, etc.). You can add your ideas to >> the ongoing discussion in the etherpad doc linked from the workshops page. If >> you missed attending the previous two workshops, going through the workshop >> materials beforehand would be beneficial. >> >> >> We look forward to your participation! >> >> >> Best, >> >> Srishti >> >> >> On behalf of the SWT Workshops Organization team >> >> >> [1] >> https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_write_… >> >> >> *Srishti Sethi* >> Senior Developer Advocate >> Wikimedia Foundation <https://wikimediafoundation.org/> >> >> _______________________________________________ >> 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 > >

1 1

Gerrit upgrade April 28th - 08:00 UTC
by Antoine Musso 27 Apr '22

27 Apr '22

Hello, I will upgrade our Gerrit from 3.3.10 to [version 3.4.4] this Thursday April 28th at 8:00 UTC. I will first upgrade the [Gerrit replica] then the primary server. The service will thus be unavailable for a few minutes while I restart the service. Upstream release notes highlights three new features: 1) Checks UI: we do not plan to use this feature 2) Unresolved Comments ported to latest patchset Unresolved comments that were left on older patchsets will now also be shown on newer patchsets. 3) Comment Chips and Context Comment state (resolved, unresolved, draft) is summarized by chips below the commit message. The Comments Tab and the Change Log will not just show the comment thread, but also the snippet of code (where the comment was made) as context. And various small UI changes, see [version 3.4.4] for a full list. [version 3.4.4] https://www.gerritcodereview.com/3.4.html [Gerrit replica] https://wikitech.wikimedia.org/wiki/Gerrit-replica.wikimedia.org Upgrade task: https://phabricator.wikimedia.org/T292759 -- Antoine "hashar" Musso Wikimedia Release Engineering

1 0

April 2022 Edition of the Technical Community Newsletter
by Melinda Seckington 27 Apr '22

27 Apr '22

Hi everyone, We’re happy to announce the April 2022 edition of the Technical Community Newsletter: https://www.mediawiki.org/wiki/Technical_Community_Newsletter/2022/April 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. Let us know what you would like to see or highlights you would like us to include. 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, Melinda -- Melinda Seckington Developer Advocacy Manager Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

CI composer update from 2.1.8 to 2.3.3
by Antoine Musso 27 Apr '22

27 Apr '22

Hello, We are updating composer in the CI images from 2.1.8 to 2.3.3 which update most jobs relying on PHP. The "Quibble" jobs have not been upgraded due to prerequisites tasks that have not been completed yet. If you find something suspiciously related to the composer upgrade, please report on the upgrade task or as a subtask: https://phabricator.wikimedia.org/T303867 Thank you! -- James Forrester & Antoine Musso

1 0

Code of Conduct Committee – call for new members
by Martin Urbanec 24 Apr '22

24 Apr '22

Hello all, It's coming close to the time for annual appointments of community members to serve on the Code of Conduct committee (CoCC). The Code of Conduct Committee is a team of five trusted individuals (plus five auxiliary members) with diverse affiliations responsible for general enforcement of the Code of conduct for Wikimedia technical spaces. Committee members are in charge of processing complaints, discussing with the parties affected, agreeing on resolutions, and following up on their enforcement. For more on their duties and roles, see https://www.mediawiki.org/wiki/Code_of_Conduct/Committee. This is a call for community members interested in volunteering for appointment to this committee. Volunteers serving in this role should be experienced Wikimedians or have had experience serving in a similar position before. The current committee is doing the selection and will research and discuss candidates. Six weeks before the beginning of the next Committee term, meaning 07 May 2022, they will publish their candidate slate (a list of candidates) on-wiki. The community can provide feedback on these candidates, via private email to the group choosing the next Committee. The feedback period will be two weeks. The current Committee will then either finalize the slate, or update the candidate slate in response to concerns raised. If the candidate slate changes, there will be another two week feedback period covering the newly proposed members. After the selections are finalized, there will be a training period, after which the new Committee is appointed. The current Committee continues to serve until the feedback, selection, and training process is complete. If you are interested in serving on this committee or like to nominate a candidate, please write an email to techconductcandidates AT wikimedia.org with details of your experience on the projects, your thoughts on the code of conduct and the committee and what you hope to bring to the role and whether you have a preference in being auxiliary or main member of the committee. The committee consists of five main members plus five auxiliary members and they will serve for a year; all applications are appreciated and will be carefully considered. The deadline for applications is *the end of day on 30 April 2022*. Please feel free to pass this invitation along to any users who you think may be qualified and interested. Best, Martin Urbanec, on behalf of the Code of Conduct Committee

1 1

Production Excellence #42: April 2022
by Krinkle 21 Apr '22

21 Apr '22

How’d we do in our strive for operational excellence last month? Read on to find out! Incidents We've had quite the month, with 8 documented incidents. That's more than double the two-year median of three a month (Incident graphs <https://codepen.io/Krinkle/full/wbYMZK>). 2022-03-01 ulsfo network <https://wikitech.wikimedia.org/wiki/Incidents/2022-03-01_ulsfo_network> Impact: For 20 minutes, clients normally routed to Ulsfo were unable to reach our projects. This includes New Zealand, parts of Canada, and the United States west coast. 2022-03-04 esams availability banner sampling <https://wikitech.wikimedia.org/wiki/Incidents/2022-03-04_esams_availability…> Impact: For 1.5 hours, all wikis were largely unreachable from Europe (via Esams), with more limited impact across the globe via other data centers as well. 2022-03-06 wdqs-categories <https://wikitech.wikimedia.org/wiki/Incidents/2022-03-06_wdqs-categories> Impact: For 1.5 hours, some requests to the public Wikidata Query Service API were sporadically blocked. 2022-03-10 site availability <https://wikitech.wikimedia.org/wiki/Incidents/2022-03-10_MediaWiki_availabi…> Impact: For 12 min, all wikis were unreachable to logged-in users, and to unregistered users trying to access uncached content. 2022-03-27 api <https://wikitech.wikimedia.org/wiki/Incidents/2022-03-27_api> Impact: For ~4 hours, in three segments of 1-2 hours each over two days, there were higher levels of failed or slow MediaWiki API requests. 2022-03-27 wdqs outage <https://wikitech.wikimedia.org/wiki/Incidents/2022-03-27_wdqs_outage> Impact: For 30 minutes, all WDQS queries failed due to an internal deadlock. 2022-03-29 network <https://wikitech.wikimedia.org/wiki/Incidents/2022-03-29_network> Impact: For approximately 5 minutes, Wikipedia and other Wikimedia sites were slow or inaccessible for many users, mostly in Europe/Africa/Asia. (Details not public at this time.) 2022-03-31 api errors <https://wikitech.wikimedia.org/wiki/Incidents/2022-03-31_api_errors> Impact: For 22 minutes, API server and app server availability were slightly decreased (~0.1% errors, all for s7-hosted wikis such as Spanish Wikipedia), and the latency of API servers was elevated as well. Incident follow-up Remember to review and schedule Incident Follow-up (Sustainability) <https://phabricator.wikimedia.org/project/view/4758/> in Phabricator, which are preventive measures and tech debt mitigations written down after an incident is concluded. Read more about past incidents at Incident status <https://wikitech.wikimedia.org/wiki/Incident_status> on Wikitech. Some recently completed sustainability work: Add linecard diversity to router-to-router interconnect at Codfw <https://phabricator.wikimedia.org/T248506> Filed by Chris (SRE Infra) in 2020 after an incident where all hosts in the Codfw data center lost connectivity at once. Completed by Arzhel and Cathal (SRE Infra), and Papaul (DC Ops); including in Esams where the same issue existed. Expand parser tests to cover language conversation variants in table-of-contents output <https://phabricator.wikimedia.org/T295187> Suggested and carried out by CScott (Parsoid) after reviewing an incident in November. The TOC on wikis that rely on the LanguageConverter service (such as Chinese Wikipedia) were no longer localized Fix unquoted URL parameters in Icgina health checks <https://phabricator.wikimedia.org/T304323> Suggested by Riccardo (SRE Infra) in response to an early warning signal for TLS certificate expiry. He realized that automated checks for a related cluster were still claiming to be in good health, when they in fact should have been firing a similar warning. Carried out by Filippo and Dzahn. Provide automation to quickly show replication status when primary is down <https://phabricator.wikimedia.org/T281249> Filed in April by Jaime (SRE Data Persistence), carried out by John and Ladsgroup. Trends Since the last edition, we resolved 24 of the 301 unresolved errors that carried over from previous months. In March, we created 54 new production errors <https://phabricator.wikimedia.org/maniphest/query/ryOkF_JP6cV1/#R>. That's quite high compared to the twenty-odd reports we find most months. Of these, 17 remain open today a month later. In the month of April, so far, we reported 20 new errors <https://phabricator.wikimedia.org/maniphest/query/1LEA6jQzf7iU/#R> of which also 17 remain open today. The production error workboard once again adds up to exactly 298 open tasks (spreadsheet <https://docs.google.com/spreadsheets/d/e/2PACX-1vTrUCAI10hIroYDU-i5_8s7pony…>). Take a look at the workboard and look for tasks that could use your help. → https://phabricator.wikimedia.org/tag/wikimedia-production-error/ Thanks! Thank you to everyone who helped by reporting, investigating, or resolving problems in Wikimedia production. Thanks! Until next time, – Timo Tijhof 🔗 Share or read later via https://phabricator.wikimedia.org/phame/post/view/283/

1 0

🚂🧪Trainsperiment Survey Results
by Tyler Cipriani 21 Apr '22

21 Apr '22

*tl;dr: *What We Learned from Trainsperiment Week <https://phabricator.wikimedia.org/phame/post/view/281/what_we_learned_from_…> Release Engineering took the feedback from the Trainsperiment survey and posted it on our blog <https://phabricator.wikimedia.org/phame/post/view/281/what_we_learned_from_…>—there are a lot of cool charts to see! Trainsperiment week happened the week of March 21st when we deployed MediaWiki versions 1.39.0-wmf.1–1.39.0-wmf.4 in a single week. Thank you to everyone who took the time to give us feedback, and worked with us while we tried something new. <3 Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation

1 0

MediaWiki 1.38.0-rc.0 is ready for testing
by Sam Reed 20 Apr '22

20 Apr '22

I'm pleased to announce the immediate availability of MediaWiki 1.38.0-rc.0, the first release candidate for 1.38.0. Download links are at the end of the e-mail. The tag has been signed and pushed to Git. This is not a final release, and should not be used for production websites. Known issues are tracked in Phabricator on the release workboard [1]. As with every release of MediaWiki, a large number of changes have landed in the last six months (over 1500 commits since 1.37.0 was cut), and you should read over the preliminary release notes as part of assuring yourself of areas that may have issues with your configuration, your skins, and/or your extensions. As always, please try out the release candidate in a test environment and do report any issues that you discover. Please use the #MW-1.38-Release [2] tag in Phabricator when reporting issues specific to this release, to make sure that we find them as quickly as possible. It is expected that MediaWiki 1.38 will become final in May 2022, though the date may slip if blockers are identified. Preliminary release notes: https://gerrit.wikimedia.org/g/mediawiki/core/+/REL1_38/RELEASE-NOTES-1.38 https://www.mediawiki.org/wiki/Release_notes/1.38 Open Bugs: [1] https://phabricator.wikimedia.org/tag/mw-1.38-release/ Bug report form: [2] https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tags=MW-1.38-… ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.38/mediawiki-1.38.0-rc.0.tar.gz https://releases.wikimedia.org/mediawiki/1.38/mediawiki-1.38.0-rc.0.zip Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.38/mediawiki-core-1.38.0-rc.0.ta… https://releases.wikimedia.org/mediawiki/1.38/mediawiki-core-1.38.0-rc.0.zip GPG signatures: https://releases.wikimedia.org/mediawiki/1.38/mediawiki-core-1.38.0-rc.0.ta… https://releases.wikimedia.org/mediawiki/1.38/mediawiki-core-1.38.0-rc.0.zi… https://releases.wikimedia.org/mediawiki/1.38/mediawiki-1.38.0-rc.0.tar.gz.… https://releases.wikimedia.org/mediawiki/1.38/mediawiki-1.38.0-rc.0.zip.sig Public keys: https://www.mediawiki.org/keys/keys.html

1 0

Removal of revision_actor_temp table
by Amir Sarabadani 20 Apr '22

20 Apr '22

Hello, (If you don't query revision_actor_temp table, feel free to ignore this email) We will remove revision_actor_temp in two weeks, this table was only built for temporary use inside mediawiki. Cloud replicas provide a view that you can query the revision table directly and instead of joining the revision table with revision_actor_temp, you can simply get the value of rev_actor field. We have finally backfilled the value of rev_actor in production and that can be used directly (thus we will remove the view soon). If you query this table in your tools, reports, etc. You need to change it ASAP. Hopefully this should make your queries much simpler. Keep in mind a similar work will happen on revision_comment_temp table in the future. You can follow the work in https://phabricator.wikimedia.org/T275246 Best -- *Amir Sarabadani (he/him)* Staff Database Architect Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

Fwd: Message from the Code of Conduct Committee
by MZMcBride 19 Apr '22

19 Apr '22

2 1

[Train] 1.39.0-wmf.8 status update
by Jeena Huneidi 19 Apr '22

19 Apr '22

The 1.39.0-wmf.8 version of MediaWiki is blocked[0]. The new version is deployed to testwikis[1], but can proceed no further until these issues are resolved: * Fatal exception of type "UnexpectedValueException" when attempting to block - https://phabricator.wikimedia.org/T305786 * Templates get transcluded in (un)delete reason for associated talk \ page - https://phabricator.wikimedia.org/T306431 Once these issues are resolved, train can resume. If these issues are resolved on a Friday the train will resume Monday. Thank you for your help resolving these issues! -- Your humble train toiler [0]. <https://phabricator.wikimedia.org/T305214> [1]. <https://versions.toolforge.org/> -- Jeena Huneidi Software Engineer, Release Engineering Wikimedia Foundation

1 0

Third Pywikibot workshop on Friday, April 29th, 16:00 UTC
by Srishti Sethi 15 Apr '22

15 Apr '22

Hello everyone, The third workshop on the topic of "Writing Pywikibot scripts" is coming up - it will take place on Friday, April 29th at 16:00 UTC. You can find more details on the workshop and a link to join here: < https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_write_…> [1]. This workshop will introduce participants to writing basic scripts via the Pywikibot framework. We will be focusing on examples of scripts that participants have requested to cover in the workshop (e.g., finding and replacing content, archiving discussions, etc.). You can add your ideas to the ongoing discussion in the etherpad doc linked from the workshops page. If you missed attending the previous two workshops, going through the workshop materials beforehand would be beneficial. We look forward to your participation! Best, Srishti On behalf of the SWT Workshops Organization team [1] https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_write_… *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

🚂🌈Summary of 1.39.0-wmf.7 train deployment
by Ahmon Dancy 15 Apr '22

15 Apr '22

This email is a summary of the Wikimedia production deployment of 1.39.0-wmf.7 - Conductor: Ahmon Dancy (yours truly) - Backup Conductor: Jaime Nuche - Blocker Task: T305213 <https://phabricator.wikimedia.org/T305213> - Current Status <https://versions.toolforge.org> 📊 According to our calculations Sparklines comparing with the last 5 trains. - 273 Patches ▁▁▅█▆ - 0 Rollbacks ▁█▁█▁ - 0 Days of delay ▄▄▄▄▄ - 4 Blockers ▅█▁▂▃ 🌈 Traintastic Folks 😻 Thanks to folks who reported or resolved blockers: - Samuel - Timo Tijhof - Zabe - Antoine "hashar" Musso

1 0

Removal of the mw.eventLog.Schema class without deprecation
by Sam Smith 14 Apr '22

14 Apr '22

Hello, I've proposed the removal of the mw.eventLog.Schema class without deprecation. Patch: https://gerrit.wikimedia.org/r/780882 Phab task: https://phabricator.wikimedia.org/T305491 Uses: - https://codesearch.wmcloud.org/search/?q=%5C.Schema%5C(&files=js - https://global-search.toolforge.org/?q=%5C.Schema%5C%28&regex=1&namespaces=… The EventLogging extension provides the mw.eventLog.Schema class as part of its JavaScript API. The class was introduced circa 2015 and was used in a handful of extensions maintained by the Readers Web team around that time. As of writing, however, it is not used in any Wikimedia-hosted codebase, user script, or gadget. Thanks, -Sam

3 3

Different cache invalidation rules for similar users?
by Strainu 13 Apr '22

13 Apr '22

Hi, I've recently seen some complaints from 2 users located in the same country that it takes about half a day for the Javascript changes to propagate. Users from different countries but similar user rights don't seem to have this problem. Is it possible to have different cache invalidation rules for different countries? If not, what else could cause this behavior? Thanks, Strainu

4 6

Announcing www.wikimediastatus.net
by Chris Danis 11 Apr '22

11 Apr '22

Hi, The Wikimedia Site Reliability Engineering team is pleased to announce the launch of a new public-facing status page at https://www.wikimediastatus.net/ This site shows five automated high-level metrics where you can see the overall health and performance of our wikis' technical environment. It also contains manually-written updates for widespread outages, which are written as quickly as the engineers are able to do so while also working to fix the actual problems. The site is separated from our production infrastructure and hosted by an external service, so that it can be accessed even if the wikis are briefly unavailable, or if something is wrong with Wikimedia's connectivity to the Internet. You can read more about this project on Diff[1] and on Wikitech[2]. Feedback is welcome on the Wikitech talk page[3], on Phab[4], or on the #wikimedia-sre IRC channel[5]. Thanks! [1]: https://diff.wikimedia.org/2022/03/31/announcing-www-wikimediastatus-net/ [2]: https://wikitech.wikimedia.org/wiki/Wikimediastatus.net [3]: https://wikitech.wikimedia.org/wiki/Talk:Wikimediastatus.net [4]: https://phabricator.wikimedia.org/T202061 [5]: #wikimedia-sre on Libera.chat, or, webchat at https://web.libera.chat/#wikimedia-sre -- Chris Danis (they/he) Staff Site Reliability Engineer Wikimedia Foundation

1 0

Swag program for technical contributors
by Srishti Sethi 11 Apr '22

11 Apr '22

Hello everyone, We want to let you know about a new swag program for technical contributors that the Wikimedia Foundation's Technical Engagement < https://www.mediawiki.org/wiki/Wikimedia_Technical_Engagement> [1] team has developed in collaboration with the Fundraising Operations < https://meta.wikimedia.org/wiki/Fundraising> [2] team. This program will reward technical contributors for their active participation in outreach programs, events, and software projects by giving swag. This is a small token of appreciation for the countless efforts of our technical contributors! In the first year of its operation, the swag program considers 85 individuals with significant contributions as developers, mentors, and organizers in 2021 for each of the following areas. - Google Summer of Code & Outreachy - Small wiki toolkits - Gerrit code contributions - Wikimedia & Wikimania Hackathon To learn more about each of these areas and the overall program, visit < https://www.mediawiki.org/wiki/Wikimedia_tech_swag_program> [3]. If you have any feedback or questions, or have suggestions around which areas to cover, please share on the talk page. Best, Srishti On behalf of Technical Engagement team [1] https://www.mediawiki.org/wiki/Wikimedia_Technical_Engagement [2] https://meta.wikimedia.org/wiki/Fundraising [3] https://www.mediawiki.org/wiki/Wikimedia_tech_swag_program *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

2 2

Subject: MediaWiki Extensions and Skins Security Release Supplement (1.35.6/1.36.4/1.37.2)
by Maryum Styles 07 Apr '22

07 Apr '22

Greetings- With the security/maintenance release of MediaWiki 1.35.6/1.36.4/1.37.2 [0], we would also like to provide this supplementary announcement of MediaWiki extensions and skins with now-public Phabricator tasks, security patches and backports [1]: == Echo == + (T285116, CVE-2022-28324) - Echo does not set X-Forwarded-For for internal API requests, some of which get logged to CU https://gerrit.wikimedia.org/r/q/I0551fe64042676f8a2b35afb82a3b4e9c09ea673 == GrowthExperiments == + (T298019, CVE-2022-28326) - i18n XSS in GrowthExperiments suggested edits pager https://gerrit.wikimedia.org/r/q/Iadc224a038ef0cec072cc1d6b84277355648f9f9 == MobileFrontend == + (T298581, CVE-2022-28325) - Mobile version of Special:Contributions leaks existence of globally suppressed users https://gerrit.wikimedia.org/r/q/I4dbb315226af267d43154d1a5a5c4635d68d1038 == SecurePoll == + (T298434, CVE-2022-28323) - SecurePoll leaks voter's exact vote timestamp https://gerrit.wikimedia.org/r/q/I4dbb315226af267d43154d1a5a5c4635d68d1038 == FileImporter == + (T294256, CVE-2022-28206) - FileImporter allows imports to cascade protected files when the importer does not have administrator permissions https://gerrit.wikimedia.org/r/c/mediawiki/extensions/FileImporter/+/757022 == GrowthExperiments == + (T298312, CVE-2022-28207) - Special:Impact leaks suppressed usernames https://gerrit.wikimedia.org/r/q/mediawiki/extensions/GrowthExperiments/+/7… == CentralAuth == + (T302248, CVE-2022-28205) - CentralAuth expiring global groups do not expire https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CentralAuth/+/765336 https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CentralAuth/+/765335 == Wikibase == + (T302215, CVE-2022-28208) - HTML injection / XSS from i18n message in WikibaseClient edit hook https://gerrit.wikimedia.org/r/q/Ife8620d65577e53b03ef4674f54d1684e2f5a773 == JsonConfig == + (T302192, CVE-2021-28210) - Data fields in Commons tabular datasets allow running arbitrary JS https://gerrit.wikimedia.org/r/q/Ifa2f6ec9ccce3b781e83a9905392e70d6a7340ad == TimedMediaHandler == + (T160800, CVE-2022-28211) - TimedMediaHandler doesn't prevent blocked users from restarting transcodes https://gerrit.wikimedia.org/r/q/I285c7c189af350be22f5de7b1c6757ad7479a20c == AntiSpoof == + (T304126, CVE-2022-28209) - One of the checks for 'override-antispoof' permission is inverted https://gerrit.wikimedia.org/r/q/Id8c4e2e336695ce70ccdf8a51ad729bf4a99f8f7 == FlaggedRevs == + (T304354, CVE-2022-28212) - It is impossible to oversight who has reviewed a revision via FlaggedRevs https://gerrit.wikimedia.org/r/q/I563bc73829d3a7c6349d364287ba42df78f3c91a == CentralAuth == + (T226212, CVE-2022-28322) - Global rename log shows timestamp of suppressed action https://gerrit.wikimedia.org/r/q/Ica7fedf10a4a8cca3d4b811ff05bfd5553753603 The Wikimedia Security Team recommends updating these extensions and/or skins to the current master branch or relevant, supported release branch [2] as soon as possible. Some of the referenced Phabricator tasks above _may_ still be private. Unfortunately, when security issues are reported, sometimes sensitive information is exposed and since Phabricator is historical, we cannot make these tasks public without exposing this sensitive information. If you have any additional questions or concerns regarding this update, please feel free to contact security(a)wikimedia.org or file a security task within Phabricator [3]. [0] https://w.wiki/52Am [1] https://phabricator.wikimedia.org/T297839 [2] https://www.mediawiki.org/wiki/Version_lifecycle [3] https://www.mediawiki.org/wiki/Reporting_security_bugs

1 0

Gerrit & CI maintenance April 7th at 7:00 UTC
by Antoine Musso 07 Apr '22

07 Apr '22

Hello, I will restart the Gerrit and CI services tomorrow Thursday April 7th at 7:00 UTC. The services will be unavailable for up to half an hour while the maintenance is being conducted. I have shifted the morning UTC backport and config window by half an hour. The MediaWiki train for 1.39.0-wmf.36 scheduled for 8:00 UTC might be delayed a bit depending on how many config and backports we have to process. Synchronization will be on Libera.chat IRC channel #wikimedia-operations cheers, -- Antoine "hashar" Musso

1 1

🚂🧪Trainsperiment Survey (Due April 8th)
by Tyler Cipriani 05 Apr '22

05 Apr '22

The Trainsperiment is complete! Thank you to all the folks who commented and helped solve blockers— *together* *we deployed four trains in one week!* We have another favor to ask: we want to hear what you thought of the experiment. _____ *Trainsperiment survey* If you have the mental space to take a survey, we'd appreciate it. - Link: https://forms.gle/8P8BDuUrT1JKtCu36 - Deadline: We'll leave the survey open until *Friday, April 8th* We'll share what we learn (anonymously) shortly after that! ___ Thanks all! Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation

1 1

Talk to the Search Platform / Query Service Team—April 6th, 2022
by Trey Jones 05 Apr '22

05 Apr '22

The Search Platform Team <https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> 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, April 6th, 2022 Time: 15:00-16:00 GMT / 08:00-09:00 PDT / 11:00-12:00 EDT / 16:00-17:00 WAT / 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 Hope to talk to you next week! —Trey Trey Jones Staff Computational Linguist, Search Platform Wikimedia Foundation UTC–4 / EDT

1 1

Give WMF Feedback on Model Cards
by Hal Triedman 04 Apr '22

04 Apr '22

Hi all, The WMF Privacy and Machine Learning Platform teams are developing model cards to increase visibility, transparency, and accountability of algorithmic decision-making on WMF platforms. A model card <https://arxiv.org/abs/1810.03993> is a document about a machine learning model that seeks to answer basic questions about the model in a clear and concise manner. The broad goal of this project is for every ML model hosted by WMF to have a model card for the community and public to understand, discuss, and govern that model. We would love for you to give some feedback on the talk page of our prototype: https://meta.wikimedia.org/wiki/User:HTriedman_(WMF)/Language_Agnostic_Link… We're specifically looking to answer the following questions: - What aspects of the model card are useful, informative, or helpful? - What aspects of the model card are confusing or unhelpful? - Are there any features or sections that aren't on the model card that you would like to see? Thanks so much! Hal

1 0

Requesting ownership for the HidePrefix extension
by Zoran Dori 02 Apr '22

02 Apr '22

Hi all, I made a task on the Phabricator[0], where I've requested ownership for the HidePrefix extension. Be free to place comments, and any questions for me if you have. [0] https://phabricator.wikimedia.org/T305317 Best regards, Zoran

1 0

🚀 SD0001 receives Web Perf Hero award!
by Krinkle 01 Apr '22

01 Apr '22

I'm happy to share that the next Web Perf Hero award goes to SD0001, in recognition of their many contributions and positive impact on the performance of Wikimedia software. I'll share two major examples. SD0001 implemented Package files <https://www.mediawiki.org/wiki/ResourceLoader/Package_files> for Gadgets <https://www.mediawiki.org/wiki/Extension:Gadgets> (T198758 <https://phabricator.wikimedia.org/T198758>). This enables gadget maintainers to bundle JSON files, unpacked via `require()`. This improves performance by avoiding delays from extra web requests. It also improves security by allowing safe contributions to JSON pages, as pure data with validated syntax on-edit. Previously, admins on Wikimedia wikis for example, would need script editing access for this and rely on copy-paste instructions from another person via the talk page. SD0001 also introduced `Module::getSkins` in ResourceLoader, and used it in the startup module <https://www.mediawiki.org/wiki/ResourceLoader/Architecture#Front-end> to optimise away unneeded module registrations <https://techblog.wikimedia.org/2019/09/19/wikipedias-javascript-initialisat…>. We just shipped the first adoption of this for Gadgets (T236603 <https://phabricator.wikimedia.org/T236603>). In the future, we'll use this to optimise MediaWiki's own skin modules as well. This award is given once a quarter, and manifests as 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 WMF Performance Team.

2 1

Phabricator monthly statistics - 2022-03
by aklapper＠wikimedia.org 31 Mar '22

31 Mar '22

Hi Community Metrics team, This is your automatic monthly Phabricator statistics mail. Accounts created in (2022-03): 375 Active Maniphest users (any activity) in (2022-03): 1069 Task authors in (2022-03): 557 Users who have closed tasks in (2022-03): 277 Projects which had at least one task moved from one column to another on their workboard in (2022-03): 330 Tasks created in (2022-03): 2456 Tasks closed in (2022-03): 2265 Open and stalled tasks in total: 49125 * Only open tasks in total: 48227 * Only stalled tasks in total: 898 Median age in days of open tasks by priority: Unbreak now: 12 Needs Triage: 758 High: 1155 Normal: 1648 Low: 2306 Lowest: 2376 (How long tasks have been open, not how long they have had that priority) Active Differential users (any activity) in (2022-03): 13 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 phab1001 at Fri 01 Apr 2022 12:00:21 AM UTC)

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l April 2022