Wikitech-l May 2021

wikitech-l@lists.wikimedia.org

33 participants
55 discussions

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 13 Sep '24

13 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

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

11 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

Line numbering coming soon for syntax highlighting
by Johanna Strodt 22 Sep '21

22 Sep '21

// sorry for cross-posting Hello everyone, Here is another change from WMDE’s Technical Wishes team concerning syntax highlighting: Soon, line numbers will be shown in wikitext editors when you have the syntax highlighting feature (CodeMirror <https://www.mediawiki.org/wiki/Extension:CodeMirror> extension) enabled.[1] The change will make it easier to detect line breaks and to refer to a particular line in discussions. More information can be found on this project page. [2] We plan to deploy this with this week’s Mediawiki train, so it should be on wikis from April 13-15. As a first step, it will be available on the template namespace only. Deployment on other namespaces is planned for the near future. If you have any feedback, please let us know on the project’s talk page. [3] We hope line numbering will be useful to you! Johanna for the Technical Wishes team [1] https://www.mediawiki.org/wiki/Extension:CodeMirror [2] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Line_Numbering [3] https://meta.wikimedia.org/wiki/WMDE_Talk_Technical_Wishes/Line_Numbering -- Johanna Strodt Projektmanagerin Kommunikation Communitys Technische Wunschliste 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 1

Developer Portal content draft: A future central place which links key technical documents
by Andre Klapper 01 Jul '21

01 Jul '21

<tl;dr>: Your feedback is wanted on https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Content_… Hi everyone, last year[1] the Developer Advocacy team started to work on a single, central entry point for developers and tech-minded people for Wikimedia's technical documentation[2]. A central entry point ("developer portal") would cover common technical use cases to allow existing and future technical contributors and developers to find the information they need. Each use case links to its most relevant documentation (i.e. to pages on wikitech or mediawiki.org). This is part of a larger initiative to implement an organization strategy for key technical documents: Understand challenges about finding and maintaining docs, identify key docs, and investigate ways to improve our workflows around documentation. So far we: * Researched and reviewed existing documentation venues and pages * Reviewed developer/documentation portals in the broader industry * Interviewed several engineering teams around technical documentation workflows, audiences, and key technical docs (the key themes from these conversations are available, see the link above) * Created an initial draft for the structure and content of the single entry point Now we would like to improve this initial content draft with your help. 1) Please take a look at the initial draft at https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Content_… 2) Then, please help improve it by sharing your thoughts and feedback until *May 25th* at https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal/Content_… Note that this is only a draft how to structure content. It is not a design or layout proposal and it is not an implementation. For additional future work, see also the Phabricator workboard[3]. Next steps include: * A session at the remote Hackathon (May 22-23; [4]) * Incorporate content improvements, based on your feedback * Check the documents linked from the single entry point proposal for accuracy * Investigate requirements for the technical implementation * Investigate improvements of processes around technical documentation (structure, locations, navigation, stewardship, etc). If you want to learn more about the project, please see https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal Thanks to everybody who has provided their valuable input to get to this stage, and thanks in advance to everyone who will! Cheers, andre [1] https://lists.wikimedia.org/pipermail/wikitech-l/2020-August/093773.html [2] https://www.mediawiki.org/wiki/Developer_Advocacy/Developer_Portal [3] https://phabricator.wikimedia.org/tag/wikimedia-developer-portal/ [4] https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021 -- Andre Klapper (he/him) | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/

1 1

New Code of Conduct committee candidates
by Amir Sarabadani 04 Jun '21

04 Jun '21

Hello, The committee has finished selecting new members and the new committee candidates are (In alphabetical order): - Amir Sarabadani - Kunal Mehta - Martin Urbanec - MusikAnimal - Tony Thomas And auxiliary members will be (Also in alphabetical order): - Ariel Glenn - Effie Mouzeli - Huji - Jayprakash12345 - Nuria Ruiz You can read more about the members in the mediawiki.org page <https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates> . The changes compared to last term are: - Kunal Mehta is joining the main CoC committee - Ariel Glenn is coming back to auxiliary committee - Effie Mouzeli is joining auxiliary committee for the first time - Tonina Zhelyazkova is leaving the committee - Matanya and Tpt are leaving the auxiliary committee - I won't run for the chair this year. This is not the final structure. According to the CoC <https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_m…>, the current committee publishes the new members and calls for public feedback for *six weeks* and after that, the current committee might apply changes to the structure based on public feedback. Please let the committee know if you have any concern regarding the members and its structure until *26 May 2021* and after that, the new committee will be in effect and will serve for a year. Amir, On behalf of the Code of Conduct committee Best

2 2

Reconsidering of eligibility criteria for technical contributions in elections
by Jay prakash 04 Jun '21

04 Jun '21

Hello all, As the 2021 WMF Board elections have been announced, I have proposed to reconsider the eligibility criteria for “developers” and technical contributors, as the previous criteria do not make sense any longer and exclude several groups of contributors. A discussion has been started at https://phabricator.wikimedia.org/T281977 and https://meta.wikimedia.org/wiki/Talk:Wikimedia_Foundation_elections/2021#Re… . Please share your thoughts and feedback. Regards Jay Prakash (he/him) Volunteer Developer, Wikimedia

1 1

Sponsored-by
by Lars Wirzenius 01 Jun '21

01 Jun '21

I figure this might be of interest to some here: we could make sponsorship of contributions more evident by adding a git commit pseudo-header: Sponsored-by: Name Of Sponsoring Entity Obviously this would be optional, and only used by those who want to. Spelled out in a little more detail: https://blog.liw.fi/posts/2021/05/26/sponsored-by/ -- 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."

3 4

Abstract Schema: An Update
by Amir Sarabadani 28 May '21

28 May '21

Hello, If you missed the previous updates, there's the first <https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>and the second <https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>one. This is the last one I'm sending but in a good way. We now finished migrating all 57 core tables to abstract schema. Now tables.sql is empty for MySQL <https://gerrit.wikimedia.org/g/mediawiki/core/+/c60ccf4e6d4932dddc2efd72a8a…>. We will soon remove the tables.sql files and links to them. We have also cleaned more than hundreds of old schema change files. <https://phabricator.wikimedia.org/T272199> That enabled us to actually look for unused sql files and drop tens of unused ones that have not been used since 2002 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/668552>, 2004 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/668761>, or 2005 <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/670176> (and much more) and they got lost in the sheer number of our sql patch files. The next update is exciting for me. With abstraction in place, we can now have a proper tracking of drifts between schema in paper and our production (This is a follow up from a major incident in 2018). Now we have https://drift-tracker.toolforge.org/ that keeps track of these drifts. Our schema has been around for more than twenty years and we have hundreds of database hosts, making sure everything is using the right database schema (and stays correct) is impossible manually and we have been finding and fixing these drifts since 2018, see this comment onwards <https://phabricator.wikimedia.org/T104459#4314828>.). Of course more work in improving the tracker is welcome (here's the list <https://phabricator.wikimedia.org/project/board/5350/>) If you want to enjoy the benefits of abstract schema [1] in extension(s) you or your team maintains, Please abstract the schema of your extension. There's a long list of WMF deployed extensions that are not using abstract schema <https://phabricator.wikimedia.org/T261912> and some even already have a patch that only needs reviewing. Once that's done, we can add that to drift tracking and have a more comprehensive list of potential issues. If you need help with the abstraction work, just ping me. This also helped us resolve several long-standing tickets like T104459 <https://phabricator.wikimedia.org/T104459> (5.5 years old), T62962 <https://phabricator.wikimedia.org/T62962> (7 years old), and T42626 <https://phabricator.wikimedia.org/T42626> (soon reaching its ninth birthday) and will help us to address even more tech debt in future. There is more to be done, improving the abstract schema *change* system, finding a home of schema documentation, improving the drift tracker and making it more automated, so much more. But the biggest chunk of work is now finally done. I really would like to thank Ammarpad for great work on abstracting the tables and handling all sorts of edge cases, James Forrester and Tgr for their reviews which without them this wouldn't be possible and Sam Reed who wrote a script to speed up migration <https://github.com/Ladsgroup/db-analyzor-tools/blob/master/db_abstractor.py>. This was a team work to its core. [1] In more details, by abstracting you will have automated checks for dirfits of the schema of extension(s) you maintain and production. You will have Postgres support for free. Also, you can have automated documentation generation, ability to test the schema itself, and have better consistency of your data types (like one datatype for timestamps). Until the next adventure. -- Amir (he/him)

2 1

Announcing MediaWiki 1.36.0
by Sam Reed 28 May '21

28 May '21

I am happy to announce the availability of the general release of MediaWiki 1.36! Tarballs have already been uploaded, and the git tag has been pushed. Please note that MediaWiki 1.36 now requires the PHP internationalization extension, commonly referred to as Intl, ext-intl, or php-intl. As a reminder, 1.31 (the old LTS) is due to become end of life in June 2021. 1.35 (the new LTS) is supported until September 2023. However, to try and meet our LTS-LTS overlap commitments (1.35 was late due to COVID), 1.31 will get best-efforts extra support until the end of September 2021. Practically, this will mean 1.31 is only tested on PHP 7.2, removing the burden of testing on PHP 7.0 and 7.1 which both became EOL in 2019. It is also noted that the patch from MediaWiki 1.36.0-rc.0 to MediaWiki 1.36.0 (mediawiki-1.36.0.patch.gz/mediawiki-1.36.0.patch.zip) is larger than expected due to an issue with the initial importing of skins and extensions as submodules into the REL1_36 branch. A bug has been filed for this issue, but doesn't cause any practical issues otherwise. MediaWiki 1.36 will be supported until May 2022. MediaWiki 1.37 is due to be released in November 2021. === Changes since MediaWiki 1.36.0-rc.0 === * (T248481) rdbms: Use server time in DatabaseMysqlBase::getLagFromPtHeartbeat(). * (T281549) WebInstaller: Don't show the announce-l subscribe checkbox for now. * (T264214) Follow-ups for UserGroupManager. * (T282280) resourceloader: Fix path-only URLs in wiki modules when script path is docroot. * (T281972) UserIdentityValue: Introduce convenience static factory methods. * (T230428) Make page_is_redirect and page_is_new unsigned. * (T280292) Legacy feature should not load thumbnail style rules (only layout). * (T283247) Freenode -> Libera per wikimedia moving from freenode to libera. * (T280270) composer: Lock Parsoid version to specific 0.13.0 release. * (T142663) Add extension.json merge strategy "provide_default". * (T283540) HookContainer: Fix normalization of callback for static handler. * (T283464) registration: Fix array order for array_replace_recursive merge strategy. * (T283539) Interwiki: Fix calling "onInterwikiLoadPrefix" hook. * (T282594) Timeless: Re-branch to 40eb3dad1for REL1_36. Open Bugs: [1] https://phabricator.wikimedia.org/project/board/4555/ Bug report form: [2] https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tags=MW-1.36-… ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.36/mediawiki-1.36.0.tar.gz https://releases.wikimedia.org/mediawiki/1.36/mediawiki-1.36.0.zip Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.36/mediawiki-core-1.36.0.tar.gz https://releases.wikimedia.org/mediawiki/1.36/mediawiki-core-1.36.0.zip Patch to previous version (1.36.0-rc.0): https://releases.wikimedia.org/mediawiki/1.36/mediawiki-1.36.0.patch.gz https://releases.wikimedia.org/mediawiki/1.36/mediawiki-1.36.0.patch.zip GPG signatures: https://releases.wikimedia.org/mediawiki/1.36/mediawiki-core-1.36.0.tar.gz.… https://releases.wikimedia.org/mediawiki/1.36/mediawiki-core-1.36.0.zip.sig https://releases.wikimedia.org/mediawiki/1.36/mediawiki-1.36.0.zip.sig https://releases.wikimedia.org/mediawiki/1.36/mediawiki-1.36.0.patch.zip.sig Public keys: https://www.mediawiki.org/keys/keys.html Release Notes https://www.mediawiki.org/wiki/Release_notes/1.36

1 0

🌠The More You Know*: Wikimedia’s Kubernetes Pipeline
by Tyler Cipriani 27 May '21

27 May '21

Oh, hi there tl;dr: we’re still moving MediaWiki into Kubernetes in Wikimedia Production; there are resources on Wikitech[0] for folks interested in learning more about the specifics of our Kubernetes pipeline. ⏳ Progress Kubernetes is the future deployment platform for most Wikimedia code. The developer and deployment experience under Kubernetes will (hopefully) be easier and safer and developers will have more autonomy. The first Wikimedia production service (Mathoid) moved to Kubernetes in July, 2018. Today there are 25 services using our production Kubernetes infrastructure serving 30,000 requests per second, about 67-ish% of our overall traffic. All services are deployed by their service owners without much oversight. Our Docker registry[1] contains 311 Docker images with 7,690 tags. Our production images are built via Continuous Integration (CI), using our deployment pipeline. Blubber[2] and PipelineLib[3] were introduced in 2018 to allow developers to specify how they wanted their CI to run and when to publish images to our shared registry. Now we’re in the process of applying all we’ve learned from our service migration to the MediaWiki migration to Kubernetes. 🏆 Goal * Open Container Initiative (OCI)-compatible MediaWiki images * Built, tested, and promoted by the image pipeline * Deployed to Kubernetes via Helm * Serving production traffic 🧐 Why * Development - Standard platform for development and production * Deployment - Safer, simpler, industry standard * Production - Increased capacity, redundancy, reliability 👏 Now * We’re building Docker images and Helm charts ** Release Engineering crammed all 184 branched extensions, 4 skins, vendor, and core Mediawiki code into a single image alongside our massive localization of 435 languages ** ServiceOps is working on php-fpm, apache, nutcracker, mcrouter and envoy images and their corresponding helm charts * We’re making our Kubernetes better ** ServiceOps has upgraded our base images and Kubernetes cluster 🔜 Next * Figuring out how deployments work ** Backports, security releases, and train * Figuring out how image upgrades work ** Is a php-fpm upgrade a deployment now? What does that look like? * Figuring out how our Wikimedia configuration changes ** Currently a change to configuration requires a code change, does this code change kick off a whole image build? 🎓 Resources Kubernetes will be very impactful in our production services and we would like to encourage those interested in this change to become familiar with its concepts. Please have a look at our collected Wikitech Kubernetes education resources, tutorials, and guides[0]. Add material if you have had a good experience with a class or tutorial. Otherwise stay tuned and watch that page for additional resources to be added. You will hear from us again as we have additional things to report. – <3 Tyler Cipriani (he/him) (On behalf of all the fine folks working on Kubernetes for MediaWiki) Engineering Manager, Release Engineering Wikimedia Foundation [0]: <https://wikitech.wikimedia.org/wiki/Kubernetes/Kubernetes_Education> [1]: <https://docker-registry.wikimedia.org> [2]: <https://wikitech.wikimedia.org/wiki/Blubber> [3]: <https://wikitech.wikimedia.org/wiki/PipelineLib> *subject line reference: https://en.wikipedia.org/wiki/The_More_You_Know

1 0

Gerrit upgrade to Java 11 - June 1st 7:00 UTC
by Antoine Musso 27 May '21

27 May '21

Hello, On Tuesday June 1st at 7:00 UTC we will switch Gerrit from Java 8 to Java 11. The system will be briefly unavailable has it restarts with the JVM. The window would be roughly half an hour, the service interruption should be just a few minutes. If anything is suspicious we will roll back to Java 8 and restart which would lead another short interruption. The task is: https://phabricator.wikimedia.org/T268225 -- Antoine "hashar" Musso

1 0

2021-05-26 Scrum of Scrums meeting notes
by Grace Gellerman 26 May '21

26 May '21

= 2021-05-26= == Callouts == * The Structured Data team will be removing MediaSearch UI code from WikibaseMediaInfo soon. If you want to look at or use our reusable Vue components, you can find them in the new MediaSearch extension: https://gerrit.wikimedia.org/r/admin/repos/mediawiki/extensions/MediaSearch * No train week of 2021-05-31 == Gerrit patches or GitHub Pull Requests for reviews or feedback == * === No updates === CommTech, AHT, Editing, iOS, Android, Prod Infra, Parsing, Library, Analytics, Cloud Services, Security, WMDE Technical Wishes == SoS Meeting Bookkeeping == * Updates: today is the last instance of this meeting in its current form == Product == === Growth === * Blocked by: * Blocking: * Thank yous: * Updates: ** Continuing work on Add Link https://wikitech.wikimedia.org/wiki/Add_Link *** planning to enable for 50% of new users on pilot wikis (arwiki, bnwiki, cswiki, viwiki) this week ** Continuing work on on-wiki configuration https://www.mediawiki.org/wiki/Growth/Community_configuration *** planning to enable on pilot wikis this week === Web === * Blocked by: * Blocking: * Thank yous: ** Huge thanks to Trey Jones for their help with the highlighting of query highlighting in the WVUI typeahead-search component: https://phabricator.wikimedia.org/T281797 * Updates: ** Instrument QA for the language switcher treatment A/B test: https://phabricator.wikimedia.org/T280770 ** Continuing work on on the new user links (personal tools) treatment: https://phabricator.wikimedia.org/T266536 === Structured Data === * Blocked by: * Blocking: * Thank yous: * Updates: ** New MediaSearch extension is on production, will disable WBMI version of the UI this week ** We will soon remove our Vue code from WBMI, so if you want to look at or use our reusable components, you can find them in the MediaSearch extension: https://gerrit.wikimedia.org/r/admin/repos/mediawiki/extensions/MediaSearch === Abstract Wikipedia === * Blocked by: ** None. * Blocking: ** None known. * Thank yous: ** Thanks to Jen Wright for help with the TDMP process alignment. * Updates: ** Close to finishing Phase ε (epsilon): https://meta.wikimedia.org/wiki/Abstract_Wikipedia/Phases ** Security & Performance reviews scheduled to end this Phase; our thanks to them! === Language === * Blocked by: * Blocking: * Thank yous: ** Big thanks to the DBAs (Jaime and Manuel) for helping to find the cause for https://phabricator.wikimedia.org/T282905 ** To Antoine "hashar" Musso for quickly fixing: https://phabricator.wikimedia.org/T283665 that was failing ULS patches from being merged * Updates: ** No major updates === Inuka === * Blocked by: * Blocking: * Thank yous: * Updates: ** Icon / Banner for Wikipedia Preview Wordpress Plugin: https://phabricator.wikimedia.org/T283623 ** High memory consume issue for KaiOS v1.5.0 on Jio phone: https://phabricator.wikimedia.org/T283725 === Vue.js === * Blocked by: * Blocking: * Thank yous: * Updates: ** Revewing feedback from the Technical Desicion Making forum on adding a build step to mediawiki, working on an additional proof of concept ** Radio component is now available in WVUI: https://doc.wikimedia.org/wvui/master/ui/?path=/story/components-radio--rad… ** Evaluating WVUI icon system: https://phabricator.wikimedia.org/T282625 ** Evaluating the use of TypeScript in WVUI: https://phabricator.wikimedia.org/T282835 ** Preparing to cut a new release of WVUI == Technology == === Fundraising Tech === [From last week.] * Blocked by: * Blocking: * Thank yous: * Updates: ** Working on new API integration for backup card processor ** Moving lots of CiviCRM code off drupal 7 === Engineering Productivity === ==== Quality and Test Engineering ==== [From last week.] * Blocked by: * Blocking: * Thank yous: * Updates: ** Blog post by Željko Filipin: macOS vs Ubuntu Linux - `npm ci` & `npm run selenium-test` with and without Fresh https://phabricator.wikimedia.org/phame/post/view/241/macos_vs_ubuntu_linux/ ==== Release Engineering ==== * Blocked by: ** * Blocking: ** * Thank yous: ** Thank you to Zabe for lots of quick fixes for train blockers. ** Thank you to James Forrester for code reviews. * Updates: ** [All] Deployments/Covid-19 https://wikitech.wikimedia.org/wiki/Deployments/Covid-19 ** Train Health *** Last week: 1.37.0-wmf.6 [[phab:T281147]]  *** This week: 1.37.0-wmf.7 [[phab:T281148]]  *** Next week: no train https://www.mediawiki.org/wiki/Scrum_of_scrums/2021-05-26 === Search Platform === [From last week.] * Blocked by: * Blocking: * Thank yous: ** Alex, Effie and Janis for helping navigate deploying Flink to k8s and for being flexible and finding creating solutions! * Updates: ** Service implementation for relforge100[34] - https://phabricator.wikimedia.org/T262211 ** Generate SSL certification for relforge1003.eqiad.wmnet and relforge1004.eqiad.wmnet - https://phabricator.wikimedia.org/T275885 ** Expose wdqs1009 to wdqs users and gather feedback - https://phabricator.wikimedia.org/T266470 ** Reboot elasticsearch* and relforge* to apply kernel security updates - https://phabricator.wikimedia.org/T280563 ** Unpack Spanish Elasticsearch Analyzer - https://phabricator.wikimedia.org/T277699 ** Cleanup duplicate indices in cloudelastic - https://phabricator.wikimedia.org/T279009 ** SonarQube should analyze all Search Platform projects - https://phabricator.wikimedia.org/T264877 ** Transfer one codfw wdqs-internal host over to codfw wdqs (public) - https://phabricator.wikimedia.org/T281498 === Site Reliability Engineering === [From last week.] * Blocked by: ** None * Blocking: ** None * Thank yous: * Updates: ** Shellbox deployment ongoing ** new caching PoP (point of presence - 2nd EMEA site) named drmrs buildout to begin, puppet patches started trickling in == Cross-cutting == * Blocked by: ** [long term] Search Platform: PHP 8.0 work is long-term blocked on the migration to ElasticSearch 7.0 https://phabricator.wikimedia.org/T263142 (or at least 6.7). * Blocking: ** None known. * Thank yous: ** Special thanks to bd808 and legoktm for their work helping with the freenode crisis. * Updates: ** Lots of energy spent on the freenode -> Libera migration; disruption not ideal. :( ** REL1_36 release process: *** 1.36.0 should be released soon. Thanks to all who have helped. ** CI tools: *** mediawiki-codesniffer v36 upgrade completed. Thanks to everyone who has made this happen, especially Umherirrender. *** CI tools' upgrade status: https://libraryupgrader2.wmcloud.org/status?branch=master ** PHP 8.0: *** No changes this week. *** Our target remains REL1_35 (and thus also REL1_36), as well as master. *** Upstream libraries: Elastica-related PHP code is theoretically the last one. *** Core: Some unit and integration tests still fail; thank you to everyone working on fixing them. [[Category:Scrum of scrums{{#translation:}}|*]]

1 0

No train the week of 2021-05-31
by Tyler Cipriani 26 May '21

26 May '21

Hi All There will be no train 2021-05-31 (2021-05-31–2021-06-04) — having our Engineering Productivity offsite. There is a long-term calendar of upcoming known deployment disruptions available on Wikitech: https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar Thanks! Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation

1 1

Change to how we build the wikimedia base container images.
by Giuseppe Lavagetto 26 May '21

26 May '21

[X-posting from ops-l] Hi all, Starting today, we are building our base container images using debuerreotype instead than bootstrap-vz, which is unmaintained [1]. This is the same tool that is used for the dockerhub debian images, and our images are now completely equivalent to the debian base images, plus our own apt configuration[2]. With this change, we're also introducing a simpler nomenclature for our base images: we will tag our images with "$codename" instead than with "wikimedia-$codename". Thus: - the base stretch image is now docker-registry.wikimedia.org/stretch - the base buster image is now docker-registry.wikimedia.org/buster We have also added a new image based on the (yet unreleased, caveat emptor) debian bullseye. We will keep tagging the latest version of those images as "wikimedia-stretch" and "wikimedia-buster" for the time being, in order to allow for backwards compatibility, but we encourage everyone to migrate eventually to the new naming. Cheers, Giuseppe [1] https://phabricator.wikimedia.org/T281984 [2] Our very simple build script is here: https://gerrit.wikimedia.org/r/plugins/gitiles/operations/puppet/+/refs/hea… -- Giuseppe Lavagetto Principal Site Reliability Engineer, Wikimedia Foundation

1 0

IRC channels are moving to Libera Chat
by Kunal Mehta 26 May '21

26 May '21

tl;dr: * Wikimedia IRC channels are moving from Freenode to Libera.Chat. * Register an account on Libera.Chat and join us there! There has been a lot of activity over the past week related to staffing changes on the Freenode IRC network [0]. The Wikimedia IRC Group Contacts (GCs) [1] evaluated the situation and decided that moving the Wikimedia IRC channels from Freenode to the brand new Libera.Chat IRC network [2] would be the best course of action [3]. So, we are moving! There is a new subpage on Meta-Wiki [4] for information on how to create a new account for yourself on Libera.Chat and other related information. Earlier we had planned on supporting the Freenode channels for longer with bridges across the networks, but supposedly "draft" changes to Freenode policies and recent actions by their new staff have pushed us to close our channels and fully leave their network. We need help with updating all references to point to the Libera Chat channels instead - this work is being tracked as [5]. [0]: https://www.kline.sh/ [1]: https://meta.wikimedia.org/wiki/IRC/Group_Contacts [2]: https://libera.chat/ [3]: https://meta.wikimedia.org/w/index.php?diff=21476411 [4]: https://meta.wikimedia.org/wiki/IRC/Migrating_to_Libera_Chat [5]: https://phabricator.wikimedia.org/T283247 -- Legoktm

2 1

Join the Wikimedia Hackathon online venue
by Léa Lacroix 22 May '21

22 May '21

Hello all, The Wikimedia Hackathon <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021> is taking place right now, and you can still join us spontaneously! First of all, we are happy to present our online venue, a spatialized chat where you can walk around, spontaneously interact with other participants, and discover the various surprises or the map that we designed specially for the hackathon. You can find more information here <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/Discussions#Online_…>, and join us at any time to work on your projects or just socialize with other Wikimedians. During the hackathon, we have a schedule of sessions <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/Schedule> running: the second day is now over, and you can watch the main track in replay here <https://www.youtube.com/watch?v=VujfdGnUnp0&ab_channel=MediaWiki>. On Sunday, more sessions will take place in the hacking rooms, you can still join or even schedule your own discussions. If you would like to work on a project, have a look at the Phabricator board <https://phabricator.wikimedia.org/project/board/5303/>, where you can create new tasks or join existing projects. Finally, a showcase will take place Sunday at 14:00 UTC <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/Showcase>. If you are working on a project, feel free to add it in the related Etherpad. You are also welcome to watch the presentations. As usual, for questions, feel free to use the talk page <https://www.mediawiki.org/wiki/Talk:Wikimedia_Hackathon_2021> or our social channels <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/Discussions>. Have a great time at the hackathon, For the coordination team, -- Léa Lacroix Community Engagement Coordinator Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

Summary of this week's deployment of 1.37.0-wmf.6: all good!
by Jeena Huneidi 22 May '21

22 May '21

This is a summary of this week's deployment of the 1.37.0-wmf.6 branch of MediaWiki and its extensions (also known as "the train"). The primary person in charge this week is Antoine Musso, with Ahmon Dancy as backup, both from the Release Engineering team. The summary task for this week is https://phabricator.wikimedia.org/T281147 The new version is running all sites. There were a total of four blockers reported and resolved: - T282825 - PHP Deprecated: Use of RevisionListBase::$title was deprecated in MediaWiki 1.37. [Called from RevDelRevisionItem::getHTML] https://phabricator.wikimedia.org/T282825 - T283167 - InvalidArgumentException: Unable to normalize the provided actor name x.y.z.v/16 https://phabricator.wikimedia.org/T283167 - T283170 - Special:RecentChanges in it.wikiversity dies with an internal error https://phabricator.wikimedia.org/T283170 - T283196 - TypeError: Argument 2 passed to UploadStash::__construct() must implement interface MediaWiki\User\UserIdentity or be null, boolean given, called in /srv/mediawiki/php-1.37.0-wmf.6/includes/upload/UploadFromStash.php on line 66 https://phabricator.wikimedia.org/T283196 As usual, a whole bunch of people helped to find, triage, analyze, fix, or work around problems this. Release Engineering thanks everyone, without help we wouldn't be able to deploy MediaWiki. - Zabe - Tim Starling - James Forrester - DannyS712 - Petr Pchelko - Valerio Bozzolan - Giacomo Alessandroni - Sam Reed - Daniel Kinzler - Amir Sarabadani - Bartosz Dziewoński - Timo Tijhif There may have been other people, and if so, I apologize for not including them on the list above. Have a good weekend. Be well. Be safe. For more information, please see: - https://phabricator.wikimedia.org/T281147 - https://wikitech.wikimedia.org/wiki/Heterogeneous_deployment/Train_deploys - https://versions.toolforge.org/ -- Jeena Huneidi Software Engineer, Release Engineering Wikimedia Foundation

1 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 May 2021