Wikitech-l March 2021

wikitech-l@lists.wikimedia.org

58 participants
63 discussions

Joining Trusted-Contributors
by Klaas Skelte van der Werf 23 Mar '21

23 Mar '21

I just noticed that I can no longer amend other peoples patch sets. I used to have this ability, but it appears that it was moved to Trusted-Contributors. [1] Can someone in that group add me? Thanks in advance. Mainframe98 [1] https://phabricator.wikimedia.org/T238651

2 2

Gerrit authentication fails
by Swathi Kasikala 22 Mar '21

22 Mar '21

Hello, This is Swathi new to this MediaWiki environment and really excited to contribute to it for which I already created a Wikimedia developer account using this https://wikitech.wikimedia.org/wiki/Special:CreateAccount and now when I am trying to login to Gerrit (https://gerrit.wikimedia.org/) using the same credentials the message is been displayed that the authentication failed. Can someone help me out to solve this issue, please-- Regards, Swathi Kasikala. amFOSS <https://amfoss.in/@swathi>

2 1

Production Excellence #29: February 2021
by Krinkle 22 Mar '21

22 Mar '21

How’d we do in our strive for operational excellence last month? Read on to find out! Read on Phabricator at https://phabricator.wikimedia.org/phame/post/view/228 📈 Incidents 3 documented incidents last month, [1] which is average for the time of year. [2] Learn about these incidents at Incident status <https://wikitech.wikimedia.org/wiki/Incident_status> on Wikitech, and their Preventive measures <https://phabricator.wikimedia.org/project/view/4758/> in Phabricator. For those with NDA-restricted access, there may be additional private incident reports <https://drive.google.com/drive/u/0/folders/1d2hlER4s_GPe0TWDqNfa2RQcYFuOdhOo> available. 💡 *Did you know: Our Incident reports have switched to using the ISO date format in their titles and listings, for improved readability and edit-ability (esp. when publishing on a later date). So long 202010221, and hello 2021-02-21!* ------- 📊 Trends In February we saw a continuation of the new downward trend that began this January <https://phabricator.wikimedia.org/phame/post/view/227/production_excellence…>, which came after twelve months of continued rising. Let's make sure this trend sticks with us as we work our way through the debt, whilst also learning to have a healthy week-to-week iteration where we monitor and follow-up on any new developments such that they don't introduce lasting regressions. The recent tally (issues filed since we started reporting in March 2019) is down to 138 unresolved errors, from 152 last month. The old backlog (pre-2019 issues) also continued its 5-month streak and is down to 148, from 160 last month. If this progress continues we'll soon have fewer "Old" issues than "Recent" issues, and possibly by the start of 2022 we may be able to report and focus only on our rotation through recent issues as hopefully we are then balancing our work such that issues reported this month are addressed mostly in the same month or otherwise later that quarter within 2-3 months. Visually that would manifest as the colored chunks having a short life on the chart with each drawn at a sharp downwards angle – instead of dragged out where it was building up an ever-taller shortcake. I do like cake, but I prefer the kind I can eat. 🍰 Month-over-month plots based on spreadsheet data <https://docs.google.com/spreadsheets/d/e/2PACX-1vTrUCAI10hIroYDU-i5_8s7pony…>. [3] [4] Figure 1, Figure 2: Unresolved error reports stacked by month. <https://phabricator.wikimedia.org/phame/post/view/228/production_excellence…> ------- 📖 Outstanding errors Summary over recent months: - ⚠️ July 2019 (2 of 18 issues left): *no change*. - ⚠️ August 2019 (1 of 14 issues): *no change*. - ⚠️ October 2019 (4 of 12 issues): *no change*. - ⚠️ November 2019 (1 of 5 issues): *no change*. - ⚠️ December 2019 (1 of 9 issues): One task resolved (-1). - ⚠️ January 2020 (2 of 7 issues): *no change*. - ⚠️ February 2020 (1 of 7 issues): *no change*. - ⚠️ March 2020 (2 of 2 issues): *no change*. - April 2020 (9 of 14 issues left): *no change*. - May 2020 (6 of 14 issues left): *no change*. - June 2020 (7 of 14 issues left): *no change*. - July 2020 (9 of 24 new issues <https://phabricator.wikimedia.org/maniphest/query/s__D8Kd0xuQH/#R>): *no change*. - August 2020 (20 of 53 new issues <https://phabricator.wikimedia.org/maniphest/query/hu1yhWu4sXkP/#R>): Two tasks resolved (-2). - September 2020 (9 of 33 new issues <https://phabricator.wikimedia.org/maniphest/query/CGFQViLShnOY/#R>): Five tasks resolved (-5). - October 2020 (26 of 69 new issues <https://phabricator.wikimedia.org/maniphest/query/MYnnBybPTYpd/#R>): Five tasks resolved (-5). - November 2020 (11 of 38 new issues <https://phabricator.wikimedia.org/maniphest/query/CkC_VqQq5VC0/#R>): Three tasks resolved (-3). - December 2020 (12 of 33 new issues <https://phabricator.wikimedia.org/maniphest/query/10NQy74iKaZJ/#R>): Seven tasks resolved (-7). - January 2021 (5 of 50 new issues <https://phabricator.wikimedia.org/maniphest/query/WIP9W8q54HB6/#R>): Two tasks resolved (-2). - *February 2021*: 11 of 20 new issues <https://phabricator.wikimedia.org/maniphest/query/5MzPJAb5oJgv/#R> survived the month and remained unresolved (+20; -9) Recent tally 152 issues open, as of Excellence #28 <https://phabricator.wikimedia.org/phame/post/view/227/production_excellence…> (16 Feb 2021). -25 issues closed since, of the previous 152 open issues. +11 new issues that survived Feb 2021. 138 issues open, as of today 5 Mar 2021. For the on-going month of March 2021, we've got 12 new issues <https://phabricator.wikimedia.org/maniphest/query/aDItN1Nm0ron/#R> so far. Take a look at the workboard <https://phabricator.wikimedia.org/tag/wikimedia-production-error/> and look for tasks that could use your help! ------- 🎉 Thanks! Thank you to everyone else who helped by reporting, investigating, or resolving problems in Wikimedia production. Thanks! Until next time, – Timo Tijhof ------- Footnotes: [1] Incident status Wikitech <https://wikitech.wikimedia.org/wiki/Incident_status>. [2] Wikimedia incident stats by Krinkle, CodePen <https://codepen.io/Krinkle/full/wbYMZK>. [3] Month-over-month, Production Excellence spreadsheet <https://docs.google.com/spreadsheets/d/e/2PACX-1vTrUCAI10hIroYDU-i5_8s7pony…> . [4] Open tasks, Wikimedia-prod-error, Phabricator <https://phabricator.wikimedia.org/maniphest/query/Fw3RdXt1Sdxp/#R>.

2 1

Upcoming change to the Wikimedia Maps Terms of Use
by Stephen LaPorte 22 Mar '21

22 Mar '21

Hi all, On April 5, 2020, we will update the Wikimedia Maps Terms of Use. Following the access limits announced in August 2020 [0] and implemented in October 2020 [1], the Wikimedia Maps service no longer supports third-party usage of Wikimedia map tiles. We are now updating the terms to reflect this policy. This change will not affect support for Wikimedia Maps on the Wikimedia projects, tools hosted on Wikimedia Cloud Services, or other allowed Wikimedia-affiliated domains. [2] The updated Maps Terms of Use is available here: https://meta.wikimedia.org/wiki/Revised_Maps_Terms_of_Use_(March_2021) If you have any suggestions, you can add them to the talk page: https://meta.wikimedia.org/wiki/Talk:Revised_Maps_Terms_of_Use_(March_2021) Under our Maps Terms of Use, we've committed to providing 14 days notice before changes are made to the policy. Best, Stephen [0] https://lists.wikimedia.org/pipermail/maps-l/2020-August/001729.html [1] https://phabricator.wikimedia.org/T261424 [2] https://phabricator.wikimedia.org/T261694 -- Stephen LaPorte (he/him/his) Legal Director Wikimedia Foundation *NOTICE: This message may be confidential or legally privileged. If you have received it by accident, please delete it and let us know about the mistake. As an attorney for the Wikimedia Foundation, for legal and ethical reasons, I cannot give legal advice to, or serve as a lawyer for, community members, volunteers, or staff members in their personal capacity. For more on what this means, please see our legal disclaimer <https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer>.*

1 0

Coming soon: Improved colors for syntax highlighting
by Johanna Strodt 22 Mar '21

22 Mar '21

// sorry for cross-posting Hi! Another improvement for the syntax highlighting (CodeMirror) is coming soon: The Technical Wishes team at Wikimedia Deutschland will update the colors in the syntax highlighting feature to add more contrast, improving accessibility and readability. The changes ensure that the syntax highlighting color scheme is compliant with the Web Content Accessibility Guidelines (WCAG 1.4.3 AA).[1] This not only helps people with reduced vision, but can also be helpful when editing in glaring daylight. Examples can be found on the project page.[2] As usual, we deploy in batches, and plan to start with a German, Catalan and Turkish Wikipedia on March 24.[3] Feedback is, as always, welcome on the talk page of the project.[4] Best, Johanna for the Technical Wishes team [1] https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines [2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Improved_Color_Scheme… [3] https://phabricator.wikimedia.org/T276346 [4] https://meta.wikimedia.org/wiki/Talk:WMDE_Technical_Wishes/Improved_Color_S… -- Johanna Strodt Project manager Community Communications Technical Wishes Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Tel. (030) 219 158 26-0 https://wikimedia.de Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit teilhaben, es nutzen und mehren können. Helfen Sie uns dabei! https://spenden.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

appy as gsoc participant
by Mohammad Shahansha 21 Mar '21

21 Mar '21

Hi! I'm Shahansha, a student at Heritage Institute of technology. I have experince from last more than 1 year in my journey as a developer and have worked with HTML, CSS, JS,java, Bootstrap 4, Python3, C/C++,mongoDB, MySQL to enchance MY creativity. Im interested to enchance develops, enhances, tests and web content applications with an end goal of creating engaging and user-friendly site layout and function, I'm much fascinated to be a part of the community, learn and contribute In wikimedia Gsoc. Thank You!!

2 1

Introduction
by Rohit Purkait 20 Mar '21

20 Mar '21

Hi Wikitech-I Team, I am Rohit Purkait, 1st year B.Tech undergraduate at Techno India Main. I would like to contribute to Wikitech-I*.* I have working experience in HTML, CSS, SASS, JavaScript and Node.js This is one of the responsive websites created by me in the Front-End Mentor Challenge: My created website <https://loop-studios-chi.vercel.app/> Here is the GitHub repo link for the above: Github Repo Link <https://github.com/codeswithroh/loop-studios> Thanks and Regards, Rohit Purkait

2 1

Summary of this week's deploymentt of 1.36.0-wmf.35
by Lars Wirzenius 19 Mar '21

19 Mar '21

This is a summary of this week's deployment of the 1.36.0-wmf.35 branch of MediaWiki and its extensions. The primary person doing this was Ahmon Dancy, with Brennen Bearnes as backup, both from the Release Engineering team. Overall this week was not entirely smooth, but not too bad. The branch was created automatically early on Tuesday, UTC time, as usual. Ahmon deployed it to group0, but had to roll back due to T277362. All wikis are now on 1.36.0-wmf.35. Next week is a new train. There were several problems found that blocked the train from progressing to the next group: - T277056: TypeError: Argument 1 passed to Wikimedia\Rdbms\TransactionProfiler::recordConnection() must be of the type string, null given https://phabricator.wikimedia.org/T277056 - T277061: Many WikibaseLexeme tests suddenly failing in quibble-vendor-mysql-php72-{selenium,noselenium}-docker https://phabricator.wikimedia.org/T277061 - T277094: Bug in client error logging stops any errors from being logged in group 0 wikis https://phabricator.wikimedia.org/T277094 - T277161: Minify v2.2.0 incorrectly minifies vue.js (faulty line break resulting in early return) https://phabricator.wikimedia.org/T277161 - T277795: User not found by actor ID: [id] https://phabricator.wikimedia.org/T277795 - an attempt at fixing was made, but the fix is stiill being assessed - T277302: Hatnote and ambox recognition is poor and essentially only works for enwiki https://phabricator.wikimedia.org/T277302 - T277362: Deprecation warning client-repo wikitext link https://phabricator.wikimedia.org/T277362 - T277593: ErrorException: Invalid cross-wiki page Q[id]. Expected: wikidatawiki, got local (duplicate of T277593) https://phabricator.wikimedia.org/T277593 Several people helped to find, triage, analyze, or fix of problems during this week. Release Engineering thanks everyone, without help we wouldn't be able to deploy MediaWiki. - Aaron Schulz - Addshore - Amir Sarabadani - Antoine Musso - Bartosz Dziewoński - Daimona - Daniel Kinzler - Ed Sanders - FriedhelmW - Gergő Tisza - James D. Forrester - Jon Robson - Legoktm - Leszek Manicki - Lucas Werkmeister - PerfektesChaos - RhinosF1 - Roan Kattouw - Sam Smith - Tarrow - Timo Tijhof - Tobias Andersson - XanonymusX There may have been other people, and if so, we apologize for not including them on the list above. For more information, please see: - https://phabricator.wikimedia.org/T274939 - https://wikitech.wikimedia.org/wiki/Heterogeneous_deployment/Train_deploys -- WMF release engineering team | he/him or they/them "Imagine a world in which every single human being can freely share in the sum of all knowledge."

1 0

FlaggedRevs (Pending changes) extension and its future
by Amir Sarabadani 19 Mar '21

19 Mar '21

Hello, This extension is one of the oldest extensions we still have in production and currently does not have a maintainer. FlaggedRevs has been the cause of several incidents and visible regressions specially since software decays and our environment constantly changes. Another problem with this extension is its scope, while most of its functionalities are not enabled in WMF production or enabled in a very small set of wikis (e.g. multiple dimensions was enabled only in Hebrew Wikisource but they agreed to disable it). This has made maintaining the extension a tall order (more of a nightmare). In other words, this extension does too many things and does none well. To move forward, we are removing barely used functionalities of this extension. Including support for multiple dimensions, multiple tiers, several one of its special pages and more to make it less of a burden to maintain and improve. It would simplify its logic drastically and will enable us to rework its old interface, fix several deprecated code that this extension is the last to block their removal (like action=ajax), reduce the number of issues/incidents/regressions caused by this extension and much more. Users in most wikis that have this extension enabled (including English Wikipedia and German Wikipedia) won't see a difference but for example, users won't be able to mark a revision as "good quality" or "average quality" anymore in English Wikibooks or Finnish Wikipedia. The "checked/stable" status will stay though. This is also to notify third party installations of this extension that this will happen from release 1.36 so if you need to have some of its features we are removing, please fork. To see the discussion around this, take a look at https://phabricator.wikimedia.org/T185664 Thank you for understanding and sorry for any inconvenience. -- Amir (he/him)

1 0

MediaWiki now supports ES6
by Roan Kattouw 18 Mar '21

18 Mar '21

The Vue migration team is pleased to announce that MediaWiki finally has built-in support for writing modern JavaScript with ES6. Up until now, all JavaScript code in MediaWiki has been written in ES5 (a version of JavaScript standardized in 2009), because MediaWiki maintains support for some browsers that don't support ES6. Over the years this has become increasingly frustrating for developers, because ES6 (standardized in 2015) adds new language features that make writing code easier and more pleasant, but these features couldn't be used in MediaWiki. A lot of modern code and tools are now written in ES6, and browsers that don't support ES6 have become obsolete. At this point, the only significant non-ES6 browser that MediaWiki continues to support is Internet Explorer 11, whose usage is relatively low, but not yet quite low enough for us to drop support for it. In keeping with the IE11 announcement[1] from earlier this month, we will continue to support IE11, but some new features will not support it. What this means for developers is that you can now use ES6 code in MediaWiki core, extensions, and skins, as long as it's in a feature that doesn't need to support IE11. ResourceLoader modules that use ES6 code have to be flagged as such, and you will need to put ES6 code in a separate directory so that different eslint rules can be applied. For detailed instructions on how to start using ES6 in your code, see https://www.mediawiki.org/wiki/ResourceLoader/ES6 . Unfortunately, ES6 code is not yet supported in on-wiki JavaScript (Gadgets, user scripts, and site scripts), because we need to check that these scripts are syntactically valid, and our current validator only understands ES5 [2]. To make this possible, we added functionality[3] to ResourceLoader to allow modules to mark themselves as ES6-only, and prevent those modules from being loaded in browsers that don't support ES6. We also made significant changes[4] to our JavaScript minifier[5] to support the minification of ES6 code, which previously generated invalid output[6] when confronted with ES6 syntax. And we updated our eslint ruleset[7] to add a linter configuration for ES6 code[8]. Thank you to Timo Tijhof (Krinkle) and DannyS712 for code reviewing the ResourceLoader and minifier changes, to Lucas Werkmeister for finding a critical bug[9] in the minifier change, and to James Forrester and Ed Sanders for code reviewing the linter changes and releasing new versions of all these packages. Roan Kattouw On behalf of the Vue migration team (Anne Tomasevich, Eric Gardner, Volker Eckl, and myself) [1] https://www.mediawiki.org/wiki/Compatibility/IE11 [2] https://phabricator.wikimedia.org/T75714 [3] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/657953 [4] https://gerrit.wikimedia.org/r/c/mediawiki/libs/Minify/+/664700 [5] https://github.com/wikimedia/Minify/ [6] https://phabricator.wikimedia.org/T255556 [7] https://github.com/wikimedia/eslint-config-wikimedia [8] https://github.com/wikimedia/eslint-config-wikimedia/pull/358 [9] https://phabricator.wikimedia.org/T277161

2 1

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 March 2021