Wikitech-l July 2020

wikitech-l@lists.wikimedia.org

56 participants
70 discussions

[Train] 1.36.0-wmf.1 status update
by Jeena Huneidi 24 Jul '20

24 Jul '20

The 1.36.0-wmf.1 version of MediaWiki is blocked[0]. The new version is deployed to group(s){0,1}[1], but can proceed no further until these issues are resolved: * RevisionAccessException when trying to import files with FileImporter - https://phabricator.wikimedia.org/T258666 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 trawler [0]. <https://phabricator.wikimedia.org/T257969> [1]. <https://versions.toolforge.org/> -- Jeena Huneidi Software Engineer, Release Engineering Wikimedia Foundation

1 0

Production Excellence #22: June 2020
by Krinkle 23 Jul '20

23 Jul '20

📘 Read on Phabricator at https://phabricator.wikimedia.org/phame/post/view/203/ ------- How’d we do in our strive for operational excellence last month? Read on to find out! ## 📈 Month in review * 4 documented incidents in June. [1] * 37 new production errors were filed and 27 were closed. [2] [3] * 72 recent production errors still open (up from 68). * 203 total Wikimedia-prod-error tasks currently open (up from 192). [4] For more about recent incidents and pending actionables see Wikitech and Phabricator, at https://wikitech.wikimedia.org/wiki/Incident_documentation and https://phabricator.wikimedia.org/project/view/4758/ ------- ## 📖 Outstanding errors Breakdown of the errors reported in June that are still open today: * (Needs owner) / Newsletter extension: Unexpected locking SELECT query. https://phabricator.wikimedia.org/T253926 * (Needs owner) / FlaggedRevs extension: Unable to submit review of page due to bad fr_page_id record. https://phabricator.wikimedia.org/T256296 * Editing team / MassMessage extension: Delivery fails due to system user conflict. https://phabricator.wikimedia.org/T171003 * Parsing team / Parsoid: Pagebundle data unavailable due to a bad UTF-8 string. https://phabricator.wikimedia.org/T236866 * Growth team / Recent changes: Update for ActiveUsers data failing due to deadlock. https://phabricator.wikimedia.org/T255059 * Growth team / GrowthExperiments: Issue with question display on personal homepage. https://phabricator.wikimedia.org/T255616 * Language team / Translate extension: Update jobs fail due to invalid function call. https://phabricator.wikimedia.org/T255669 * Language team / ContentTranslation: Save action fails due to duplicate insert query. https://phabricator.wikimedia.org/T256230 * Core Platform team / Content handling: Incompatible content type during content merge/stash. https://phabricator.wikimedia.org/T255700 * Core Platform team / Monolog: API usage logs and error logs sometimes missing due to socket failure. https://phabricator.wikimedia.org/T255578 * Search Platform team / WikibaseCirrus: Elevated error levels from EntitySearchElastic warnings. https://phabricator.wikimedia.org/T255658 * Wikidata / API: Generator query fails due to invalid API result format. https://phabricator.wikimedia.org/T254334 * Wikidata / API: EntityData query emits warning about bad RDF. https://phabricator.wikimedia.org/T255054 * Wikidata / Repo: Entity relation update jobs fail due to deadlock. https://phabricator.wikimedia.org/T255706 ------- ## 📊 Trends Take a look at the workboard and look for tasks that could use your help. → https://phabricator.wikimedia.org/tag/wikimedia-production-error/ Summary over recent months: * July 2019 (5 of 18 tasks left): Two tasks closed. * August (1 of 14 tasks left): Another task closed, only one remaining! 🚀 * September (5 of 12 tasks left): Two tasks closed. * October (6 of 12 tasks left), no change. * November (3 of 5 tasks left): Another task closed. * December (5 of 9 tasks left), no change. * January 2020 (5 of 7 tasks lef), no change. * February (4 of 7 tasks left), no change. * March (2 of 2 tasks left), no change. * April (11 of 14 tasks left): Three tasks closed. * May (11 tasks left): Three tasks closed. * June: 14 new tasks survived the month of June. ⚠️ At the end of May the number of open production errors over recent months was 68. Of those, 10 got closed, but with 14 new tasks from June still open, the total has grown further to 72. The workboard had 192 open tasks last month, which saw another increase, to now 203 open tasks (this includes tasks from 2019 and earlier). ------- ## 🎉 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] Incidents. – https://wikitech.wikimedia.org/wiki/Incident_documentation#2020 [2] Tasks created. – https://phabricator.wikimedia.org/maniphest/query/VTpmvaJLYVL1/#R [3] Tasks closed. – https://phabricator.wikimedia.org/maniphest/query/qn5yeURqyl3D/#R [4] Open tasks. – https://phabricator.wikimedia.org/maniphest/query/Fw3RdXt1Sdxp/#R

1 0

Scrum of scrums/2020-07-22
by Željko Filipin 22 Jul '20

22 Jul '20

Hi, for HTML version see https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-07-22 Željko -- = 2020-07-22 = == Callouts == * Release Engineering ** [All] Review guidance at [[wikitech:Deployments/Covid-19]] and Code Deployment Office Hour at 17:00UTC in #wikimedia-office ** "scap sync" will be renamed to "scap sync-world" in the next release. If you use "scap sync" non-interactively, please add a note to: [[phab:T250302]] (and also, explain why you're using it) ** scap sync now has option --canary-wait-time; [[phab:T217924]] == SoS Meeting Bookkeeping == * Updates: ** Update the wiki page instead of the etherpad page (https://etherpad.wikimedia.org/p/Scrum-of-Scrums) == Product == === Web === * Updates: ** '''Summary''': deploying Desktop Improvements Project (DIP) to select wikis, starting WVUI Vector integration and network client. ** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector / DIP)]]: *** [[phab:T177108|<nowiki>TypeError: $.collapsibleTabs.getSettings(...) is undefined from Vector skin</nowiki>]] *** [[phab:T257518|<nowiki>[Bug] Max-Width Layout: Sidebar overlaps footer when its height is longer than the content height</nowiki>]] *** [[phab:T255727|<nowiki>Make collapsible sidebar persistent for logged-in users</nowiki>]] *** [[phab:T254851|<nowiki>Current checkbox hack doesn't provide <Enter> or <Space> as toggle action</nowiki>]] *** [[phab:T254228|<nowiki>Deploy new version of vector skin to all wikis as a user preference</nowiki>]] *** [[phab:T254227|<nowiki>Switch test wikis to new version of vector by default</nowiki>]] *** [[phab:T253842|<nowiki>Fix the printable versions of modern Vector</nowiki>]] *** [[phab:T249363|<nowiki>Move the existing search to the header in preparation for Vue.js search development</nowiki>]] *** [[phab:T246420|<nowiki>Limit content width, and refine alignment & styling of relevant elements</nowiki>]] *** [[phab:T167956|<nowiki>Deprecate and remove printable version mode</nowiki>]] *** [[phab:T251212|<nowiki>[Dev] Drop VectorTemplate usage in Vector</nowiki>]] *** [[phab:T244392|Vue.js search case study]]: **** See [[Reading/Web/Desktop Improvements/Vue.js case study/Status log|weekly status updates]]. ** Mobile website (MinervaNeue / MobileFrontend): *** [[phab:T237036|<nowiki>ext.uls.interface should set targets and explicitly not target the Minerva skin</nowiki>]] *** [[phab:T235712|<nowiki>Fix the most common "Module not loadable on target mobile" warnings (Oct 2019)</nowiki>]] *** [[phab:T257953|<nowiki>[Technical debt payoff] Drop MFSpecialCaseMainPage, from MobileFrontend</nowiki>]] *** [[phab:T254287|<nowiki>Final warning: Mobile main page special casing will be disabled July </nowiki>]] *** [[phab:T240622|<nowiki>[Technical debt payoff] Remove InlineDiffFormatter and InlineDifferenceEngine from MobileFrontend</nowiki>]] *** [[phab:T32405|<nowiki>[EPIC] MobileFrontend extension should stop special-casing main page</nowiki>]] ** Standardization *** [[phab:T232903|<nowiki>Standardise `.mw-infobox` by relying on `.warningbox`</nowiki>]] ** Portals *** [[phab:T128546|<nowiki>[Recurring Task] Update Wikipedia and sister projects portals statistics</nowiki>]] ** QuickSurveys *** [[phab:T246977|<nowiki>Run baseline quicksurvey on test wikis</nowiki>]] ** Miscellaneous *** [[phab:T138401|<nowiki>Replace jsduck with JSDoc3 across all Wikimedia code bases</nowiki>]] === Structured Data === * Updates: ** working on adding schema.org licensing data to article pages ** ongoing work on mediasearch == Technology == === Fundraising Tech === * Updates: ** Investigating American Express card failures in India ** Fixing how we set up one-time card donations to make them possible to convert to monthly recurring ** Refining sync process for employer matching gift policies ** Investigating seemingly unintended duplicate donations ** Updating custom CiviCRM report used to track fraud. === Engineering Productivity === ==== Release Engineering ==== * Updates: ** [All] Deployments/Covid-19 [[wikitech:Deployments/Covid-19]] ** Train Health *** Last week: 1.35.0-wmf.41 - [[phab:T256669]] *** This week: 1.36.0-wmf.1 - [[phab:T257969]] *** Next week: 1.36.0-wmf.2 - [[phab:T257970]] === Site Reliability Engineering === * Updates: ** mobileapps traffic is being migrated to kubernetes.

1 0

[Wikimedia Technical Talks] Beyond Wikipedia - Knowledge that even a computer can understand
by Sarah R 22 Jul '20

22 Jul '20

Hi Everyone, It's time for Wikimedia Tech Talks 2020 Episode 5! *This talk will take place next Wednesday on 22 July 2020 at 17:00 UTC.* *Title:* Beyond Wikipedia - Knowledge that even a computer can understand *Speaker*: Zbyszko Papierski, Senior Software Engineer <https://wikimediafoundation.org/profile/zbyszko-papierski/> *Summary:* Everybody knows what Wikipedia is, right? This magnificent source of knowledge has been helping countless people with their everyday lives for nearly two decades. Whether you want to know how to calculate the circumference of the circle, whether hyenas are pack animals or what really happened to the Ottoman Empire - Wikipedia’s got your back. Well, unless you happen to be a computer. One issue with Wikipedia is that knowledge there isn’t very well structured. There are links to other pages, sure - but unless you actually understand the text, you won’t understand what the link actually is. This is, of course, a field day for AI/ML experts - and there are a lot of people already scavenging Wikipedia for any meaningful relations. Fortunately, this is not the only way. Enter Wikidata - Wikipedia’s younger sister. Wikidata is also a source of knowledge curated and provided by a community of volunteers but presented in a relational graph format. Structuring the knowledge has huge ramifications - it not only makes it easier to digest by software but also allows you to infer new knowledge. There are different ways for developers to interact with Wikidata, but we’ll focus on Wikidata Query Service - a service my team is responsible for. It provides a queryable interface - using an RDF graph language called SPARQL (not to be confused with a hundred other things in IT with “spark” in the name). Let’s do some discovery! *The link to the Youtube Livestream can be found here: * https://www.youtube.com/watch?v=jNNy8ALGjaE During the live talk, you are invited to join the discussion on IRC at #wikimedia-office You can browse past Tech Talks here: https://www.mediawiki.org/wiki/Tech_talks If you are interested in giving your own tech talk, you can learn more here: https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te… Note: This is a public talk. Feel free to distribute through appropriate email and social channels! Kindly, Sarah R. Rodlund Senior Technical Writer, Developer Advocacy <https://meta.wikimedia.org/wiki/Developer_Advocacy> srodlund(a)wikimedia.org

1 1

Welcome to Wikimedia development! (Summer of 2020)
by Timo Tijhof 22 Jul '20

22 Jul '20

Hello fellow contributors, developers, and colleagues, This is a semiannual refresher on Wikimedia development policies. Whether you joined last week, or have been here for a decade, I hope this helps you navigate our current practices. (See changelog below.) Feel free to use this thread to ask or answer questions about any of these! TL;DR: * The Code of Conduct applies to how all of us behave. https://mediawiki.org/wiki/Code_of_Conduct * If you can merge code changes, please familiarize yourself with the Privilege policy. https://mediawiki.org/wiki/Gerrit/Privilege_policy * The Support policy for PHP describes what we support and for how long. It allows site operators and developers to plan ahead (incl WMF). https://mediawiki.org/wiki/Support_policy_for_PHP * The Stable interface is about code that should stay compatible, and is safe to use in an extension. https://mediawiki.org/wiki/Stable_interface_policy * Ask for help! Either here onlist, or on IRC chat. https://mediawiki.org/wiki/MediaWiki_on_IRC ### Gerrit privilege policy As maintainer you take final responsibility over code before it ships to the servers and the personal devices of a billion people. No pressure! :-) https://mediawiki.org/wiki/Gerrit/Privilege_policy ### MediaWiki stability and PHP support Before you use internal code or extend core in an undocumented way, it’s best to start a conversation on Phabricator first. Explain your use case and decide together how to proceed. Also involve the maintainers or code stewards of the component in question. https://mediawiki.org/wiki/Developers/Maintainers ### Data access and privacy Wikimedia takes pride in its commitment to protecting user privacy. If you build feature instrumentation or store personal data, think about how the data will be removed or aggregated. https://meta.wikimedia.org/wiki/Data_retention_guidelines If you have shell access, see also the Server Access and Data Access responsibilities. https://phabricator.wikimedia.org/L3 https://wikitech.wikimedia.org/wiki/Data_access#Responsibilities ### Best practices and ask for help You can find pages about coding style, security, performance, localisation, and more; on https://mediawiki.org/wiki/Development_guidelines Use these pages to your advantage, and feel free to ask questions here on Wikitech-l, or chat in #mediawiki on Freenode IRC. https://mediawiki.org/wiki/MediaWiki_on_IRC ### Changes since 2019 For those of you who know most of this already, here’s what’s changed: * February 2019: The "+2 policy" was updated and is now the Gerrit privilege policy. – https://mediawiki.org/wiki/Gerrit/Privilege_policy, https://phabricator.wikimedia.org/T216295 * March 2019: Established principles around the creation of new services. The idea for this started at Wikimedia Technical Conference in Portland (2018). – https://mediawiki.org/wiki/Wikimedia_services_guideline, https://phabricator.wikimedia.org/T208524 * September 2019: There is a new general policy for PHP support changes. We no longer need dedicated RFCs, such when MediaWiki required PHP 5.5+ in 2016, or PHP 7 in 2017. The policy was first used to require PHP 7.2+ for MediaWiki 1.34. – https://mediawiki.org/wiki/Support_policy_for_PHP, https://phabricator.wikimedia.org/T228342 * March 2020: The “Deprecation policy” was updated and is now the Stable interface policy. – https://mediawiki.org/wiki/Stable_interface_policy, https://phabricator.wikimedia.org/T193613 * April 2020: We added some structure, boilerplate, and documented common stakeholder questions. These changes enable RFC authors to go through the process quicker, and to steer more of it on their own. – https://mediawiki.org/wiki/Requests_for_comment, https://phabricator.wikimedia.org/T216308 -- Timo Tijhof Principal Engineer Wikimedia Foundation

1 0

Should we cancel Scrum of scrums meeting?
by Željko Filipin 21 Jul '20

21 Jul '20

Hi, TLDR: reply to me (off-list) if you would think Scrum of scrums is still useful. I've been sending Scrum of scrums[0] mails to wikitech-l list since 2019-03-20[1]. The meeting has existed since 2013. I haven't done any proper research, but a quick look says the number of participating teams is decreasing significantly. Quick sample, the first meeting of July in years 2014-2020. 2014-07-09 14 2015-07-01 12 2016-07-06 18 2017-07-05 16 2018-07-11 18 2019-07-03 16 2020-07-01 8 Željko -- 0: https://www.mediawiki.org/wiki/Scrum_of_scrums 1: https://lists.wikimedia.org/pipermail/wikitech-l/2019-March/091817.html

3 3

NEW: Lists of technical resources and recommendations for smaller language wikis!
by Srishti Sethi 21 Jul '20

21 Jul '20

Hello everyone, As part of the Small wiki toolkits <https://meta.wikimedia.org/wiki/Small_wiki_toolkits> initiative, a Starter kit <https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Starter_kit> has been developed for smaller language Wikimedia wikis! This Starter kit lists resources, tools, and recommendations in technical areas (e.g., templates, bots, gadgets, etc.) relevant to smaller wikis that are just getting started. Small wiki contributors can use it to make their community's workflow easier. You can now use and promote the Starter kit in your wiki community, and start translating the landing page and its subpages in a language you want. If you have any questions, ideas for venues where it should be shared or wiki pages where it should be linked, or any other suggestions for improving it further, please share on this talk page <https://meta.wikimedia.org/wiki/Talk:Small_wiki_toolkits/Starter_kit>. If you are interested in helping with the Small Wiki Toolkits initiative and can offer help with running workshops, developing toolkits, or exchanging problems and challenges in smaller wiki communities, add yourself as a member here: https://meta.wikimedia.org/wiki/Small_wiki_toolkits#Members Cheers, Srishti *Srishti Sethi* Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

2 1

Change of translation for "attribution" in CC licenses
by Strainu 20 Jul '20

20 Jul '20

Hi folks, Sorry for cross-posting, not sure which list is the best venue for my problem. I have an issue with regards to the translation of the word "attribution" in "Creative Commons Attribution-Share-Alike". For reasons (explained in [1]) which are not interesting for Wikimedia, the CC-sanctioned Romanian translation has changed from "distribuire" to "partajare" in the translation for version 4.0 *only*. This becomes a problem for multilingual wikis (mw, m, c), which use meta-templates and MediaWiki messages to translate the {{cc-by-sa-*}} templates. What would be the easiest way to solve the problem without affecting other languages? Thanks, Strainu [1] (in Romanian) https://www.cyberculture.ro/2020/07/20/licente-creative-commons-versiunea-4…

1 0

TechCom Radar 2020-07-15
by Kate Chapman 20 Jul '20

20 Jul '20

Hi All, Here are the minutes from this week's TechCom meeting: * Last call ending 22 July 2020 RFC: HTML element for inline media from wikitext <https://phabricator.wikimedia.org/T251641> * No IRC meeting next week You can also find our meeting minutes at < https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board < https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. If you prefer you can subscribe to our newsletter here < https://www.mediawiki.org/wiki/Newsletter:TechCom_Radar> Thanks, Kate -- Kate Chapman (she/her/hers) Director of Architecture, Architecture Team Wikimedia Foundation kchapman(a)wikimedia.org

1 0

Contribute to the Wikimedia Technical Blog!
by Sarah R 18 Jul '20

18 Jul '20

Hi all, Are you interested in writing a post for the Wikimedia Technical Blog <https://techblog.wikimedia.org/>? We're currently seeking contributions! Writing a post is a great opportunity to reflect on and share your work with a wide audience of people who are curious about Wikimedia technology and the Open Source community. This venue provides a central place for people to share stories about the technical work that they do. Posts cover a range of topics <https://www.mediawiki.org/wiki/Wikimedia_technical_blog_editorial_guideline…> from how-tos, to community outreach, to deep dives into processes and technology, and much more. If you're interested in writing a blog post, read the editorial guidelines <https://www.mediawiki.org/wiki/Wikimedia_technical_blog_editorial_guidelines> to learn about what would make a good story and how to get published! We manage the process of reviewing and publishing posts here: https://phabricator.wikimedia.org/tag/Technical-blog-posts Looking forward to reading your stories! Sarah R. Rodlund Senior Technical Writer, Developer Advocacy <https://meta.wikimedia.org/wiki/Developer_Advocacy> srodlund(a)wikimedia.org *“*

4 6

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 July 2020