Wikitech-l December 2021

wikitech-l@lists.wikimedia.org

28 participants
33 discussions

🚂🌈Summary of 1.38.0-wmf.12 train deployment
by Ahmon Dancy 10 Dec '21

10 Dec '21

- 1.38.0-wmf.12 has been rolled out to all wikis. There are a couple of low frequency errors that are being logged bug they are being worked on. - Conductor: Ahmon Dancy (yours truly) - Backup Conductor: Brennen Bearnes - Blocker Task: T293953 <https://phabricator.wikimedia.org/T293953> - Current Status <https://versions.toolforge.org/> 📊 By the Numbers Sparklines comparing with the last 5 trains. - 231 Patches █▅▁▅▂ - 1 Rollbacks ▁▃█▆▃ - 0 Days of delay ▁▂▆█▁ - 8 Blockers ▃▃▁█▇ ✨ Trainbow Love 🎉Thanks to folks who reported or resolved blockers: - Amir Sarabadani (WMF) - Timo Tijhof - Taavi Väänänen - EBernhardson - Daniel Kinzler - Roan Kattouw - Jon Robson - Zabe - and many more! -

1 0

Looking for new maintainer for packagist-mirror.wmcloud.org
by Kunal Mehta 10 Dec '21

10 Dec '21

Hi, <https://packagist-mirror.wmcloud.org/> is exactly what it sounds like, a mirror of the metadata on packagist.org. It's very simple, just a systemd timer and some Apache config. Since setting it up 2 or 3 years ago I've barely had to touch it. And based on access logs, some people are actually using it (though we never switched CI over to it, as the idea/goal once was). But after being reminded about it by the current Cloud VPS cleanup, I'm not interested in running this anymore. packagist.org is actually open source (*looks at npmjs.com in sadness*) and hasn't had any reliability issues recently AFAIR. There's also a bit of work to do, the VM needs to be upgraded from stretch, and it should be switched over to the new composer/mirror script from upstream. So if someone would like to take it over, comment on <https://phabricator.wikimedia.org/T296968> and I'm happy to add you and explain how it works. Otherwise please consider this notice that I intend to shut it down at the end of the year. -- Legoktm

1 0

Making $wgLegalTitleChars easier to use outside PHP
by Kunal Mehta 10 Dec '21

10 Dec '21

Hi, Myself and Erutuon are working on writing a Rust library[1] that validates and normalizes MediaWiki page titles, initially for use in bots and tools, but it has other potential use cases too. There is some prior art for this, a mediawiki-title npm package[2] is used by various nodejs services, and there's a mediawiki.Title ResourceLoader module in core too, all of which reimplement MediaWiki's title parsing, validation and normalization routines...basically MediaWikiTitleCodec and what it calls. One problem area is $wgLegalTitleChars. It's part of a PHP regex that gets used to check if any invalid characters are present by inverting it, basically [^{legalchars}]. It's also exposed via the meta=siteinfo API, which suggests that it's useful for external callers, but in its current form it's really not. The current value is: $wgLegalTitleChars = " %!\"$&'()*,\\-.\\/0-9:;=?@A-Z\\\\^_`a-z~\\x80-\\xFF+"; It's is a mix of literal characters, some escaped and some not, and various ranges. Specifically, it's tuned for PHP regexes, like / is escaped because it delimits regexes (an unnecessary escape and therefore problematic in Rust), and it uses syntax like \x80-\xFF, while in JavaScript we want \u0080-\uFFFF. We'd also like to use the Unicode escape class syntax in Rust, but for now have worked around it to use the byte class. In fact, we have functions that parse the byte class and turn it into a unicode class, Title::convertByteClassToUnicodeClass() in PHP and a JavaScript version too[3]. This seems entirely unnecessary to me, given that we could just write this sequence in a more regex-neutral manner to make it more portable: $wgLegalTitleCharacters = [ 'characters' => " %!\"$&'()*,-./:;=?@\\\\^_`~", // + 'plus' => true, // A-Z, a-z, 0-9 'alphanumeric' => true, // \x80-\xFF 'non-ascii' => true, ]; Characters are literal characters to run through preg_quote or mw.util.escapeRegExp, and the ranges are to be specified in whatever format the specific regex engine would like. But this also opens up the question - is there a valid use case for customizing $wgLegalTitleChars anymore? We already have a comment that says "Don't change this unless you know what you're doing". There's also one that says "In some rare cases you may wish to remove + for compatibility with old links." - is that still a consideration today? I would think that for easy importing/exporting across various MediaWiki wikis we want the set of legal title characters to be rather static. And if someone wants to ban some character from being used, Extension:TitleBlacklist (bundled) provides a much less invasive way to do so. So to recap: 1. Can we get rid of the ability to customize legal title characters? 2. If #1 is no, any objections to the breaking change of swapping out $wgLegalTitleChars (string) for $wgLegalTitleCharacters (array)? Note that extensions can still read from the old global, just it can't be overridden in LocalSettings anymore. The actual patch to review is <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/745386>. [1] https://gitlab.com/mwbot-rs/mwbot/-/tree/master/mwtitle [2] https://github.com/wikimedia/mediawiki-title/ [3] https://github.com/wikimedia/mediawiki-title/blob/master/lib/utils.js

1 0

MediaWiki Language Extension Bundle 2021.12 (Bug fix release)
by Kartik Mistry 03 Dec '21

03 Dec '21

Hello all, I would like to announce the release of MediaWiki Language Extension Bundle 2021.12. This is a bug-fix release. Previous release was [ https://lists.wikimedia.org/hyperkitty/list/mediawiki-i18n@lists.wikimedia.… MLEB 2021.11]. This bundle is compatible with '''MediaWiki 1.35.3''' or above and requires '''PHP 7.3.19''' or above. Next MLEB is expected to be released next month. 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-2021.11.tar… * sha256sum: 61c9c7a700c9f98c6b3c59adf2f0fc7d1919fc87e0c3584308d313536dd81f37 * Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.11.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/mailman/listinfo/mediawiki-i18n * Report bugs to: https://phabricator.wikimedia.org/project/view/1464/ Release notes for each extension are below. -- Kartik Mistry == Babel, cldr, LocalisationUpdate, CleanChanges and UniversalLanguageSelector == * No changes. == Translate == * Fix broken SpecialMovePage on MediaWiki 1.35 ([[phab:T294605|Phab:T296450]]) -- Kartik Mistry | કાર્તિક મિસ્ત્રી kartikm.wordpress.com

1 0

Nomination for Zabe to have +2 in mediawiki/
by Kunal Mehta 03 Dec '21

03 Dec '21

Hi, I've nominated Zabe for +2 rights in all mediawiki/* repositories: <https://phabricator.wikimedia.org/T296165>. -- Legoktm

1 1

Cloud VPS users, please claim your projects (and, introducing Komla)
by Andrew Bogott 02 Dec '21

02 Dec '21

Hello cloud-vps users! It's time for our annual cleanup of unused projects and resources. Our new developer advocate Komla Sapaty will be guiding this process; please respond promptly to his emails and do your best to make him feel welcome! Every year or so the Cloud Services team tries to identify and clean up unused projects and VMs. We do this via an opt-in process: anyone can mark a project as 'in use,' and that project will be preserved for another year. I've created a wiki page that lists all existing projects, here: https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2021_Purge If you are a VPS user, please visit that page and mark any projects that you use as {{Used}}. Note that it's not necessary for you to be a project admin to mark something -- if you know that you're currently using a resource and want to keep using it, go ahead and mark it accordingly. If you /are/ a project admin, please take a moment to mark which VMs are or aren't used in your projects. When February arrives, I will shut down and begin the process of reclaiming resources from unused projects. If you think you use a VPS project but aren't sure which, I encourage you to poke around on https://tools.wmflabs.org/openstack-browser/ to see what looks familiar. Worst case, just email cloud(a)lists.wikimedia.org with a description of your use case and we'll sort it out there. Exclusive toolforge users are free to ignore this email and future related things. Thank you! -Andrew and the WMCS team

1 0

Contributing to Wikimedia Foundation (Where Can I find the projects?)
by Sai Teja Anantha 02 Dec '21

02 Dec '21

Hey, I am Sai Teja Anantha, an Undergraduate student from IIT Kharagpur. I am a newbie to open source contributions, and I am looking forward to contributing to the Wikimedia foundation Organization. I am looking for projects in this Organization. Where can I find the projects currently that are active in this Organization, please let me know. Thanks in Advance

2 1

Apply for or raise awareness about the Wikimedia Research Fund
by Leila Zia 02 Dec '21

02 Dec '21

[Apologies for cross-posting] Hi all, We're excited to announce the launch of the Wikimedia Research Fund [1] with the goal of diversifying the network of Wikimedia researchers globally and supporting the Wikimedia Movement in deeper understanding of the projects, decision making, and building new technologies. The reason we're reaching out to you, as the developer community, is that we believe one of the ways research can be impactful is through its use in tools/code and as developers, you have knowledge of what research can support you in your work. (Examples, OCR for specific languages, better NLP models in your local language, other ML models for specific tasks that you want your tools to offer, and more.) The deadline to apply is January 3, 2022. We intend to give funds of value USD 2k-50k. More info at https://meta.wikimedia.org/wiki/Grants:Programs/Wikimedia_Research_%26_Tech… . Big thanks to Emily Lescak for all her behind-the-scenes work to make the launch of the Research Fund possible, and to the Community Resources team at the Wikimedia Foundation for giving us the opportunity and the funds. If you have questions, please reach out to us at research_fund(a)wikimedia.org, meta [2], here, or in one of our upcoming office hours [3]! :) Best, the Research Fund committee chairs Benjamin Mako Hill (University of Washington) Leila Zia (Wikimedia Foundation) [1] https://meta.wikimedia.org/wiki/Grants:Programs/Wikimedia_Research_%26_Tech… [2] https://meta.wikimedia.org/wiki/Grants_talk:Start [3] https://meta.wikimedia.org/wiki/Grants:Programs/Wikimedia_Research_%26_Tech…

1 0

Train is cancelled this week
by Tyler Cipriani 01 Dec '21

01 Dec '21

Hi all! I know this is a past-due notice considering it's Wednesday. But I'm cancelling the train for this week. We are distracted by some internal changes, and I don't feel that we have the capacity to devote attention to these internal changes and do the train as well. Sorry all :( Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation

1 0

Small breaking change to WikiPage
by Thomas Chin 01 Dec '21

01 Dec '21

Hello, There is currently a patch <https://gerrit.wikimedia.org/r/c/mediawiki/core/+/732429/> in the works that will introduce a slight breaking change to WikiPage. It removes three public functions that weren't intended to be public to begin with: WikiPage::insertNullProtectionRevision, ::protectDescription, and ::protectDescriptionLog. The only known external usage of these methods have a patch <https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Translate/+/734727> up, but please be on the lookout if any of your code happens to use them. Cheers, -- *Thomas Chin <https://meta.wikimedia.org/wiki/User:TChin_(WMF)>* (he/him) Software Engineer - Platform Engineering Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

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