Wikitech-l October 2022

wikitech-l@lists.wikimedia.org

49 participants
47 discussions

Re: TDF is looking for community representatives
by Brian Wolff 15 Oct '22

15 Oct '22

So I see that User:Grunny, User:Rtnf and Dessalegn Yehuala were appointed. Respectfully, given the criteria was someone with +2 rights, I would question the decision to appoint Dessalegn Yehuala, who not only has never contributed to MediaWiki, but also appears to have never edited any Wikimedia project, or even have an account. Brian On Thu, Oct 6, 2022 at 1:58 AM Technical Decision Forum Support < TDFsupport(a)wikimedia.org> wrote: > Hi Brian, > > We have our representatives but we are always looking for some more as we > rotate throughout the year. My apologies for the late updates to the > forum. The lists are here > <https://www.mediawiki.org/wiki/Technical_decision_making/Forum>. The > community representatives have completed one feedback to the IP Masking > Proposal and next week we should have "Modern user interfaces for all > users" proposal out to the representatives for their feedback. You can see > it on the TDF <https://phabricator.wikimedia.org/project/board/5179/> > board. > > Thank you, > TDF > > > On Wed, Oct 5, 2022, 5:46 PM Brian Wolff <bawolff(a)gmail.com> wrote: > >> Out of curiosity, what happened? Aug 12 has come and gone. More to the >> point, i was wondering if TDF is even still a thing? >> >> -- >> Brian >> >> On Tuesday, August 2, 2022, Erica Litrenta <elitrenta(a)wikimedia.org> >> wrote: >> >>> Hi everyone. >>> >>> This is a reminder that the search for community representatives for the >>> Technical Decision Forum is still OPEN. >>> >>> There are a few weeks left to apply and/or recommend someone who would >>> be a great fit for the role (learn more at >>> https://www.mediawiki.org/wiki/Technical_decision_making/Community_represen… >>> ). >>> >>> Please let us know if there are any questions we can answer before you >>> submit your application, or a friend's name! Email us at >>> TDFSupport(a)wikimedia.org by Aug 12, 2022. >>> >>> Looking forward to hearing from you soon… >>> >>> The Technical Decision Forum. >>> >>> On Tue, Jul 12, 2022 at 11:17 AM Erica Litrenta <elitrenta(a)wikimedia.org> >>> wrote: >>> >>>> *(This email may not be written in your native language, and/or may be >>>> a crosspost: our apologies.)* >>>> >>>> >>>> Greetings, everyone. >>>> >>>> The Technical Decision Forum, or TDF (1), is seeking community >>>> representatives. Please visit the TDF Community Representation (2) >>>> page for more information, and email TDFSupport(a)wikimedia.org by Aug >>>> 12, 2022 to be considered for selection. >>>> >>>> >>>> Don't worry about the requirements listed on wiki, they are not set in >>>> stone; just provide your name, name of the group you "represent" if any, >>>> and a short sentence or two explaining your interest. >>>> >>>> >>>> For any questions, please post at *MediaWiki.org (3)*, or on the >>>> related Movement Strategy Forum topic (4), or simply email >>>> TDFSupport(a)wikimedia.org. >>>> >>>> Thanks, >>>> >>>> The Technical Decision Forum. >>>> >>>> (1) https://www.mediawiki.org/wiki/Technical_decision_making/Forum >>>> (2) >>>> https://www.mediawiki.org/wiki/Technical_decision_making/Community_represen… >>>> (3) https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Forum >>>> (4) >>>> https://forum.movement-strategy.org/t/technical-decision-forum-tdf-is-looki… >>>> >>>> -- >>>> >>>> ------------------------------ >>>> >>>> >>>> Erica Litrenta (she/her) >>>> >>>> Senior Manager, Community Relations Specialists (Product) >>>> >>>> Wikimedia Foundation >>>> <https://meta.wikimedia.org/wiki/User:Elitre_(WMF)> >>>> >>>> >>> >>> -- >>> >>> ------------------------------ >>> >>> >>> Erica Litrenta (she/her) >>> >>> Senior Manager, Community Relations Specialists (Product) >>> >>> Wikimedia Foundation <https://meta.wikimedia.org/wiki/User:Elitre_(WMF)> >>> >>> >>>

12 16

Re: Request to post on mailing list.
by Asif Rahaman 14 Oct '22

14 Oct '22

Hi. I recently contacted Wikimedia and subscribe for the mailing list. I would like to post on your mailing list. Regards Asif Rahaman Btech second year student (IIT Bhilai) On Fri, Oct 14, 2022, 20:27 Asif Rahaman <asifrahaman162(a)gmail.com> wrote: > Hi. > I recently contacted Wikimedia and subscribe for the mailing list. I would > like to post on your mailing list. > > Regards > Asif Rahaman > Btech second year student (IIT Bhilai) >

3 2

ParserTests updates
by Subramanya Sastry 13 Oct '22

13 Oct '22

Hello everyone, The Content Transform Team <https://www.mediawiki.org/wiki/Content_Transform_Team> finally decided to act on this old task <https://phabricator.wikimedia.org/T111604> to split up the parserTests.txt file in core into a number of smaller files by functionality. We got a first patch merged and there is one more patch in gerrit that will likely merge this week. More patches will follow in the coming weeks and we expect that by the time we are done, we'll have a few 10s of parser test files which will all be significantly smaller than the parserTests.txt file now. So, when some of you write code that needs an update to parser tests,in some cases, you may have to update tests in multiple files. While I have your attention here, a few more parserTests related updates: * Over the last 6 months, we've updated MediaWiki core's parser test runner to run parser tests against Parsoid (both via CLI and in CI via PHPUnit). We call these tests integrated mode Parsoid test runs to contrast it with standalone mode Parsoid test runs (Core's test runner runs in integrated mode with the MediaWiki core code whereas Parsoid's test runner runs in standalone mode without using MediaWiki core code). * I've also been updating the parser tests wiki page <https://www.mediawiki.org/wiki/Parser_tests> to bring the documentation up to date wrt how to write tests for running with Parsoid. We will continue to improve this page and add more details as necessary. Feel free to edit the page or leave questions / comments on the talk page with requests for clarification. * We have also started enabling test runs with Parsoid in extension repositories as well as in core. If you see a 'parsoid-compatible' clause in a test file, that test file is going to be run with Parsoid. We want to make sure as we move further along with the integration of Parsoid with the rendering pipeline, we catch any newly-introduced regressions so they can be fixed. Thanks! Subbu on behalf of the Content Transform Team.

1 0

Request for feedback: Two changes related to databases in MediaWiki
by Amir Sarabadani 12 Oct '22

12 Oct '22

Hello, Two changes is being made on MediaWiki databases: *First:* We are reworking how extensions manage their database schema. The idea is to basically deprecate LoadExtensionSchemaUpdates hook[1] and replace it with structured values in extension.json. This is needed to avoid arbitrary php code execution during database update which can cause problems and was a contributing factor in one of our major outages [2]. The other reason for this change is to be able to wire abstract schema of extensions to core so it can be tested in CI (for example for having a valid json, having prefixes set correctly, etc.) You can see a POC of that in [3] Given that once the change is merged to core, breaking changs to extension registry schema would require a lot of work (updating the maniphest version and so on), it's better to get it right before merge. I have proposed something like [4]. For any feedback on this, please go to https://phabricator.wikimedia.org/T237839, *Second:* We are working to provide a replacement for raw SQL for query conditions. When the query condition is exact equality condition (e.g. rev_id = 123), you don't need to provide raw SQL but for most other cases you need to either provide it or build it via IDatabase methods. For example: 'rev_timestamp > ' . $db->addQuotes( $db->timestamp( $since ) ). You can see an example of this in [5] (being changed to something much better via a newly introduced method). This is not optimal and not very developer friendly, to solve that, we are proposing to have something like ExpressionBuilder::greater( 'rev_timestamp', $db->timestamp( $since ) ) supported in SelectQueryBuilder::where(). You can see the POC in [6]. For any feedback on this please go to https://phabricator.wikimedia.org/T210206 [1] https://www.mediawiki.org/wiki/Manual:Hooks/LoadExtensionSchemaUpdates [2] https://wikitech.wikimedia.org/wiki/Incidents/2020-04-07_Wikidata%27s_wb_it… [3] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/816262/10/tests/phpunit/s… [4] https://phabricator.wikimedia.org/T237839#8268173 [5] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/832625/6/includes/api/Api… [6] https://gerrit.wikimedia.org/r/c/mediawiki/core/+/841940/ Thank you -- *Amir Sarabadani (he/him)* Staff Database Architect Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

🌱 Fresh 22.09 released!
by Krinkle 11 Oct '22

11 Oct '22

This release promotes Node.js 16 to be the default runtime in fresh-node. Get started by installing, updating, or learning more, at: https://gerrit.wikimedia.org/g/fresh#fresh-environment Changelog: https://gerrit.wikimedia.org/g/fresh/+/22.09.1/CHANGELOG.md Node.js 16 is now the default environment for the fresh-node command. This addresses an issue with Vue.js development using Vite 3, which did not work well under Node.js 14. (Thanks Lucas Werkmeister, T314051 <https://phabricator.wikimedia.org/T314051>). Note that most projects still test on Node.js 14 in WMF CI. [1] If you find that some of your tests don't yet pass under Node.js 16, fret not! Node.js 14 and 12 remain available via the bundled fresh-node14 and fresh-node12 commands. If you encounter problems in Fresh with Node.js 16 or experience other issues, let us know on Phabricator at https://phabricator.wikimedia.org/tag/fresh/. This is also where you can browse previous tasks. Fresh is a fast way to create isolated environments from your terminal. These can be used to work more responsibly with 'npm' developer tools such as ESLint, QUnit, Grunt, Selenium, and more. Example guide: https://www.mediawiki.org/wiki/Manual:JavaScript_unit_testing -- Timo Tijhof [1] https://phabricator.wikimedia.org/T314470

1 0

Cookie-based CSS toggles for logged-out readers?
by Samuel Klein 11 Oct '22

11 Oct '22

Dear WT, The perennial discussion about ways to provide logged-out users with persistent customization of their reading experience in the browser has cropped up again in the context of the pending deployment of Vector 2022. Can a cookie-based width toggle <https://en.wikipedia.org/wiki/Wikipedia:Requests_for_comment/Deployment_of_…> be offered without splitting the cache or otherwise making the toggler regret their tog? The answers currently range from "*shouldn't be very complicated or hacky, just toggling a class*..." and "*can be delivered to logged-out users on top of the cached parser output*.." to "*impossible*". Could someone clarify the challenges and costs of trying to toggle css classes in this way? Warmly, SJ -- Samuel Klein @metasj w:user:sj +1 617 529 4266

2 3

Subject: [REMINDER] Coolest Tool Award 2022: Call for nominations!
by Seyram Komla Sapaty 11 Oct '22

11 Oct '22

Hello! Last reminder, there are 2 days left (today and tomorrow) to submit your Coolest Tool Award <https://meta.wikimedia.org/wiki/Coolest_Tool_Award> nominations. Please recommend your favorite tools! Thanks! Komla, for the Coolest Tool Academy 2022 -- Seyram Komla Sapaty Developer Advocate Wikimedia Cloud Services

1 0

MediaWiki 1.39.0-rc.1 is ready for testing
by Sam Reed 08 Oct '22

08 Oct '22

I'm pleased to announce the immediate availability of MediaWiki 1.39.0-rc.1, the second release candidate for 1.39.0, the next LTS after MediaWiki 1.35. Download links are at the end of the e-mail. The tag has been signed and pushed to Git. This is not a final release, and should not be used for production websites. Known issues are tracked in Phabricator on the release workboard [1]. As with every release of MediaWiki, a large number of changes have landed in the last six months (over 1850 commits since 1.38.0 was cut), and you should read over the preliminary release notes as part of assuring yourself of areas that may have issues with your configuration, your skins, and/or your extensions. As always, please try out the release candidate in a test environment and do report any issues that you discover. Please use the #MW-1.39-Release [2] tag in Phabricator when reporting issues specific to this release, to make sure that we find them as quickly as possible. It is expected that MediaWiki 1.39 will become final in November 2022, though the date may slip if blockers are identified. Changes since MediaWiki 1.39.0-rc.0: * Localisation updates. * (T318481) composer: Drop symfony/php73-polyfill. * (T318460) SpecialChangeEmail: Set default for returntoquery. * (T318307) HTMLFormField::validate(): Update docs to permit all data types * (T306802) docker: update to latest published images. * (T318754) WebInstallerOptions::addPersonalizationOptions(): Close fieldset. * (T227047) Soft-deprecate the remainder of ActorMigration. * (T316304, CVE-2022-41767) SECURITY: reassignEdits doesn't update results in an IP range check on Special:Contributions. * (T309894, CVE-2022-41765) SECURITY: HTMLUserTextField exposes existence of hidden users. * (T307278, CVE-2022-41766) SECURITY: On action=rollback the message "alreadyrolled" can leak revision deleted user name. * (T319186) .phan/config.php: Update minimum_target_php_version. * Tests: Explicit cast to int in RandomImageGenerator test (php8 warnings). * (T319186) .phan/config.php: Update minimum_target_php_version. * (T310243) Deprecate use of 'wvui-search' package. * utils: Fix return doc about false/null for UrlUtils::expand. * (T319000) WebInstaller: Don't try and run trim() on null. * In the event of preg failure in MagicWordArray throw exception. * (T318753) Installer: Disable logo dropper for now. Preliminary release notes: https://gerrit.wikimedia.org/g/mediawiki/core/+/REL1_39/RELEASE-NOTES-1.39 https://www.mediawiki.org/wiki/Release_notes/1.39 Open Bugs: [1] https://phabricator.wikimedia.org/tag/mw-1.39-release/ Bug report form: [2] https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tags=MW-1.39-… ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.39/mediawiki-1.39.0-rc.1.tar.gz https://releases.wikimedia.org/mediawiki/1.39/mediawiki-1.39.0-rc.1.zip Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.39/mediawiki-core-1.39.0-rc.1.ta… https://releases.wikimedia.org/mediawiki/1.39/mediawiki-core-1.39.0-rc.1.zip Patch to previous version (1.39.0-rc.0): https://releases.wikimedia.org/mediawiki/1.39/mediawiki-1.39.0-rc.1.patch.gz https://releases.wikimedia.org/mediawiki/1.39/mediawiki-1.39.0-rc.1.patch.z… GPG signatures: https://releases.wikimedia.org/mediawiki/1.39/mediawiki-core-1.39.0-rc.1.ta… https://releases.wikimedia.org/mediawiki/1.39/mediawiki-core-1.39.0-rc.1.zi… https://releases.wikimedia.org/mediawiki/1.39/mediawiki-1.39.0-rc.1.tar.gz.… https://releases.wikimedia.org/mediawiki/1.39/mediawiki-1.39.0-rc.1.zip.sig https://releases.wikimedia.org/mediawiki/1.39/mediawiki-1.39.0-rc.1.patch.g… https://releases.wikimedia.org/mediawiki/1.39/mediawiki-1.39.0-rc.1.patch.z… Public keys: https://www.mediawiki.org/keys/keys.html

1 0

[Small wiki toolkits] Upcoming "How to interact with Wikidata via Pywikibot" workshop on Friday, October 7th, 16:00 UTC
by Srishti Sethi 07 Oct '22

07 Oct '22

Hello everyone, The eighth workshop on the topic of "How to interact with Wikidata via Pywikibot" is coming up - it will take place on Friday, October 7th at 16:00 UTC. You can find more details on the workshop and a link to join here: < https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_intera…> [1]. This workshop will summarise how to access and save information to Wikidata, including through page generators and queries*, using Pywikibot. It will also cover the Wikidata conventions about the bot editing, including the bot approvals process (*queries not included, please bring your own!). This session will be run by Mike Peel. To participate in this workshop, you would need basic familiarity with Wikidata and Pywikibot installation. We look forward to your participation! Best, Srishti On behalf of the SWT Workshops Organization team [1] https://meta.wikimedia.org/wiki/Small_wiki_toolkits/Workshops#How_to_intera… *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

2 2

MediaWiki Extensions and Skins Security Release Supplement (1.35.8/1.37.5/1.38.3)
by Maryum Styles 06 Oct '22

06 Oct '22

Greetings- With the security/maintenance release of MediaWiki 1.35.8/1.37.5/1.38.3, we would also like to provide this supplementary announcement of MediaWiki extensions and skins with now-public Phabricator tasks, security patches and backports [1]: OAuth + (T308861 <https://phabricator.wikimedia.org/T308861>, CVE-2022-39191) - OAuth debug log includes consumer secrets https://gerrit.wikimedia.org/r/c/mediawiki/extensions/OAuth/+/839460/ GrowthExperiments + (T313205 <https://phabricator.wikimedia.org/T313205>, CVE-2022-39194) - Growth's Community configuration makes it possible for rogue admin to take down a site https://gerrit.wikimedia.org/r/q/I9b3766a71ee403b3a72c8af995e70c3017abe12e IPInfo + (T310763 <https://phabricator.wikimedia.org/T310763>, CVE-2022-39192) - IP Info tool shows whether an IP is autoblocked, potentially allowing unmasking of users by correlation https://gerrit.wikimedia.org/r/q/Ib1fdac6b2db70fc33f6d9e9f3e9108b6d65961b4 PageTriage + (T314245 <https://phabricator.wikimedia.org/T314245>, CVE-2022-41344) - Someone with patrol user right can mark own article as reviewed if they use api.php?action=pagetriageaction https://gerrit.wikimedia.org/r/q/I9a3c9dafc634c59d7dbf1d6d62da389046a0e22e OAuth + (T312820 <https://phabricator.wikimedia.org/T312820>, CVE-2022-41346) - Special:OAuth/rest_redirect does unrestricted redirects https://gerrit.wikimedia.org/r/q/I789fb7384d89fbf42df22dc7b1953fb9087d95b1 Translate + (T302479 <https://phabricator.wikimedia.org/T302479>, CVE-2022-41345) - Blocked users with "translation administrator" right are able to mark pages for translation https://gerrit.wikimedia.org/r/q/Ic206021 The Wikimedia Security Team recommends updating these extensions and/or skins to the current master branch or relevant, supported release branch [2] as soon as possible. Some of the referenced Phabricator tasks above _may_ still be private. Unfortunately, when security issues are reported, sometimes sensitive information is exposed and since Phabricator is historical, we cannot make these tasks public without exposing this sensitive information. If you have any additional questions or concerns regarding this update, please feel free to contact security(a)wikimedia.org or file a security task within Phabricator [3]. [0] https://w.wiki/5nN3 [1] https://phabricator.wikimedia.org/T311785 [2] https://www.mediawiki.org/wiki/Version_lifecycle [3] https://www.mediawiki.org/wiki/Reporting_security_bugs

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l October 2022