Wikitech-l October 2023

wikitech-l@lists.wikimedia.org

28 participants
29 discussions

MediaWiki Language Extension Bundle 2023.10
by Kartik Mistry 30 Oct '23

30 Oct '23

We would like to announce the release of MediaWiki Language Extension Bundle 2023.10. This bundle is compatible with '''MediaWiki >= 1.39.0''' and requires '''PHP >= 7.4.0'''. The next MLEB is expected to be released in 3 months. 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-2023.10.tar… * sha256sum: 8b3f356014f1bfdf8c08ec8778c200f1e25567c210d1ee93ba7b7e3f894947ab * Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2023.10.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/postorius/lists/mediawiki-i18n.lists.wikimedia.… * Report bugs to: https://phabricator.wikimedia.org/project/view/1464 Release notes for each extension are below. == Highlights == * Translate extension: Removed <code>mirrors</code> option when providing configuration for translation memory. == Babel == * Localisation and maintenance updates. == CleanChanges == * Localisation and maintenance updates. == cldr == * Localisation and maintenance updates. == Translate == * Removed <code>mirrors</code> option when providing configuration for translation memory. See [[Help:Extension:Translate/Translation_memories#Configuration|related documentation]]. * Translate extension no longer uses jQuery.ui ({{phab|T323332}}). * Added an option to leave a redirect when moving a translatable page ({{phab|T62920}}). * Improve compatibility between syntaxhighlight and translate when using Parsoid ({{phab|T341009}}, {{gerrit|957761}}). * Special:PagePreparation: Improve error handling, and message displayed to the user. ({{phab|T342628}}). * Special:AggregateGroups: Replace previous group selector with a more user-friendly group selection tool. * Made UI tweaks to search translations page to break long words to avoid breaking the layout ({{gerrit|968673}}). * Localisation and maintenance updates. == UniversalLanguageSelector == * Added AwamiNastaliqBold font ({{gerrit|957266}}). * Removed all TTF font files ({{gerrit|957273}}). * Added Tiro Bangla font for Bengali Language ({{phab|T343658}}). * Updated Junicode font to 2.100 ({{phab|T253006}}). * Save preferred languages for named users only ({{phab|T337780}}). * Fixed an error that would cause ULS to not open when clicked if the wiki is configured to allow anonymous users to change their language ({{gerrit|969342}}). * Localisation and maintenance updates. -- Kartik Mistry | કાર્તિક મિસ્ત્રી kartikm.wordpress.com

1 0

SemanticCite
by Sorin Gheorghiu 30 Oct '23

30 Oct '23

Hello folks! does anybody know if this extension is still maintained? The latest commit is from May 16, 2020. There are older tickets about SCI being not compatible with SWM 4.0.0 (and therefore not compatible with MW1.39 which will become EOL end of 2023). Sorin

4 3

Announcing Codex 1.0
by Roan Kattouw 25 Oct '23

25 Oct '23

Today the Design Systems Team <https://www.mediawiki.org/wiki/Design_Systems_Team> is announcing the release of Codex 1.0! What is Codex? Codex <https://doc.wikimedia.org/codex/latest/> is the new design system for Wikimedia. Over the past 2 years, the Design Systems Team and contributors from the Wikimedia Foundation, Wikimedia Deutschland, and the volunteer communities have collaborated to create a centralized design system to serve Wikimedia projects. Codex provides more equitable experiences for all Wikimedia movement participants, and makes it easier and faster to design and build consistent user interfaces. With Codex, we aim to enable more people to contribute to the mission. Codex provides a library of design tokens <https://doc.wikimedia.org/codex/latest/design-tokens/overview.html>, user interface components <https://doc.wikimedia.org/codex/latest/components/overview.html>, and catalog of icons <https://doc.wikimedia.org/codex/latest/icons/overview.html> to use with these components. Through the Codex Figma libraries, designers can reuse these shared components <https://www.figma.com/file/KoDuJMadWBXtsOtzGS4134/%E2%9D%96-Codex-component…> , tokens <https://www.figma.com/file/mRvSsFD2Kwh8AZNjlx7rIl/%E2%9C%A8-Design-tokens?t…>, and assets <https://www.figma.com/file/1lT9LKOK6wiHLnpraMjP3E/%E2%9D%96-Assets-(Icons%2…> in their designs. For developers, Codex provides components built with Vue.js, as well as some CSS-only components that do not require JavaScript to use. Codex is already being used for Wikifunctions <https://www.mediawiki.org/wiki/Extension:WikiLambda>, Vector 2022 <https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements/Features/Se…>, the Growth Mentor Dashboard <https://www.mediawiki.org/wiki/Growth/Mentor_dashboard> and Impact Module <https://www.mediawiki.org/wiki/Growth/Positive_reinforcement>, the New Pages Feed <https://en.wikipedia.org/wiki/Wikipedia:Page_Curation/2023_Moderator_Tools_…> , MediaSearch <https://www.mediawiki.org/wiki/Extension:MediaSearch>, NearbyPages <https://www.mediawiki.org/wiki/Extension:NearbyPages>, QuickSurveys <https://www.mediawiki.org/wiki/Extension:QuickSurveys>, and ReadingLists <https://www.mediawiki.org/wiki/Extension:ReadingLists>. Projects currently under development using Codex include Accessibility for reading <https://www.mediawiki.org/wiki/Reading/Web/Accessibility_for_reading> and the Incident Reporting System <https://meta.wikimedia.org/wiki/Private_Incident_Reporting_System>. Codex provides a set of core components <https://www.mediawiki.org/wiki/Design_Systems_Team/Codex_Planned_Components> that cover a wide range of Wikimedia user interface needs, but does not necessarily provide equivalents of all components in OOUI <https://www.mediawiki.org/wiki/OOUI>. If you find that a component you were expecting to use is missing, please talk to the Design Systems Team <https://www.mediawiki.org/wiki/Design_Systems_Team/Working_with_us> and we'd be happy to help you. We strongly encourage contribution to Codex <https://doc.wikimedia.org/codex/latest/contributing/overview.html>, in line with our vision of being a collaborative project guided by stewardship. Why 1.0 now? The Design Systems Team has been working towards this milestone for a number of months now. Based on early feedback, we’ve already made improvements to the developer experience of using Codex, like providing ready-to-go example repos <https://gitlab.wikimedia.org/repos/design-systems/CodexExample> of using Codex in a MediaWiki extension and changing our code snippets in the doc site for easier copy-paste into non-TypeScript and MediaWiki-specific projects. We also dedicated significant time and effort ensuring accessibility of Codex components and assets conform to WCAG 2.1 AA and other standards, and plan to engage with groups like the American Foundation for the Blind for further improvements. We’ve been consolidating various design resources (like the design style guide <https://design.wikimedia.org/style-guide/>) into Codex so there is a single source of truth for Wikimedia front-end development and design standards. This is to clarify Codex’s role not just as a UI library, but as the design system for Wikimedia. Who should use Codex? Everyone! Some foundational elements like design tokens can and should be used in all Wikimedia software going forward. Most of the MediaWiki code that uses the older pre-token variables from mediawiki.ui has already been migrated to use the Codex tokens instead. The Codex wiki documentation <https://www.mediawiki.org/wiki/Codex#Using_Codex_design_tokens> has more information about using design tokens (and other elements) in MediaWiki. At this time, Codex components are most suitable for client-side features that don't have complex requirements for non-JavaScript support, or for server-rendered interfaces that don't need much interactivity. Features requiring both high interactivity and the need to support users without JavaScript will need to create separate implementations of the feature using CSS-only components and using Vue components. The Design Systems Team has explored solutions that would allow a single Vue implementation to support both non-JavaScript and JavaScript users in the future. Gadget and user script developers who would like to use JavaScript for interactivity cannot reliably use Codex at this time. However, this is something the Design System Team is looking to provide a solution for in the future. Further details and feedback is welcome on Phabricator <https://phabricator.wikimedia.org/T313945>. Eventually, we intend for Codex to mostly replace other user interface libraries in the Wikimedia ecosystem, like OOUI and jquery.ui. Over time, we hope this will make the design of features and the developer experience less fragmented across the projects. We encourage people who want to make their code more maintainable and use modern tools now and in the future to consider migrating existing projects to Codex. For new projects, we strongly recommend building with Codex from the beginning. This will ensure you get the best and latest in design and engineering resources and tools, accessibility compliance, and multilingual and internationalization support. Next steps The Design Systems Team is here to assist you in evaluating whether Codex is suitable for your project and can help you put together a migration plan for existing codebases. Those who wish to get started with Codex can visit the documentation site <https://doc.wikimedia.org/codex/latest/>. To get more detailed information about using Codex in MediaWiki, you can visit the project wiki page <https://www.mediawiki.org/wiki/Codex>. For a general list of resources, you can visit our team wiki page <https://www.mediawiki.org/wiki/Design_Systems_Team/Resources>. Again, if you have any questions, feedback, or would like assistance from the Design Systems Team, come talk to us <https://www.mediawiki.org/wiki/Design_Systems_Team/Working_with_us>!

5 4

Seeking Guidance for Open Source Contribution
by Makwana Nikunj 25 Oct '23

25 Oct '23

Dear Learning Equality Team, My name is Nikunj Makwana, and I am currently a third-year computer science undergraduate at Government Engineering College, Dahod. I have some experience in programming languages like html, css , js, react, java. My primary skills lie in js, I am passionate about open-source and have recently participated in Hacktoberfest 2023. I am now seeking mentorship to improve my skills in open-source development. I am keen to contribute to your projects and would appreciate your guidance on how to get started. Your mentorship would be valuable to me, and I look forward to hearing from you soon. Thank you for your time. Best regards, Nikunj Makwana

2 1

Celebrating the Success of Our Interns and GSoC Mentor Summit Recap
by Vasanth Gopa 21 Oct '23

21 Oct '23

Hello everyone, We are delighted to share the fantastic news of our interns' accomplishments during GSoC 2023 and Outreachy Round 26, under the guidance of their mentors. Please join us in congratulating these remarkable individuals for their unwavering commitment and hard work: *GSoC’ Interns*: 1. Ahmed Amine Hassou (Morocco) Project: Wiki Education Dashboard - Refactoring and upgrading React Mentors: Sage Ross, Will Kent 2. Chenhao Liu (United States of America) Project: Wiki Farm Support for Canasta Mentors: Yaron Koren, Jeffrey Wang 3. Nikhil Mahajan (India) Project: End-to-end test coverage for Abstract Wikipedia's Wikifunctions Mentors: Stef Dunlap, James Forrester, Cory Massaro, Denny Vrandečić 4. Zexi Gong (China) Project: Wikidocumentaries to import images from the web to Structured Data on Commons Mentors: TuukkaH, Susannaanas 5. Shashwat Khanna (India) Project: Improve Programs & Events Dashboard UX for Article Scoped Programs Mentor: Sage Ross 6. Saurabh Jamadagni (India) Project: Adding a menu to Scribe-iOS application and expanding keyboard languages Mentor: Andrew McAllister 7. Ritika Pahwa (India) Project: Commons Android app - Make upload more reliable Mentors: Nicolas Raoul, Kaartic Sivaraam 8. Punith Nayak (India) Project: Improve the functionality of VideoCutTool - New features Mentors: Gopa Vasanth, Sohom Datta 9. Varun Shrivastava (India) Project: Improve the functionality of VideoCutTool - Code Quality/Code Health Mentors: Gopa Vasanth, Sohom Datta Additionally, we have the following *Outreachy interns*: 1. Abhishek Bhardwaj (India) Project: Research imbalances in translation between languages on Wikipedia Mentors: Adam Wight, Simulo, Kavitha A 2. Nathaly Toledo (Venezuela) Project: Research imbalances in translation between languages on Wikipedia Mentors: Adam Wight, Simulo, Kavitha A 3. Sulagna Saha (Bangladesh) Project: Write a Ruby gem for analyzing Wikidata edits Mentors: Sage Ross, Will Kent These diligent interns have made significant contributions to our community, and we encourage you to explore their reports and blogs to learn more about their exceptional work. You can find additional information about these projects on the following pages: - https://www.mediawiki.org/wiki/Google_Summer_of_Code/2023 - https://m.mediawiki.org/wiki/Outreachy/Round_26 Furthermore, we are thrilled to inform you that Srishti Sethi and I (Gopa) recently attended the Google Summer of Code Mentor Summit held at Google Headquarters in Sunnyvale, California. We represented the outstanding work of our nine GSoC 2023 interns on Wikimedia projects and had the privilege of learning from peers in various open-source software fields, including arts, education, music, robotics, and more. This event, conducted in an unconference, participant-driven style, provided a platform for attendees to discuss the challenges of running open-source projects and share valuable tips and advice for mentoring interns. It's worth noting that Wikimedia has been an active participant in Google Summer of Code since 2006. Once again, we extend our heartfelt congratulations to all our interns, mentors, and everyone who supported them throughout this journey. We eagerly anticipate their continued contributions to Wikimedia projects. Cheers, Wikimedia Organization Administrators (Srishti Sethi, Soham Datta, Sheila and Gopa) -- Regards, Gopa Vasanth <https://gopavasanth.github.io/> Twitter <https://twitter.com/gopavasanth1999> | LinkedIn <https://www.linkedin.com/in/gopa-vasanth/> | GitHub <https://github.com/gopavasanth> | Gerrit <https://gerrit.wikimedia.org/r/#/q/gopavasanth> “Yesterday is not ours to recover, but tomorrow is ours to win or lose.”

2 1

First edition of the Language & Internationalization newsletter
by Srishti Sethi 16 Oct '23

16 Oct '23

Hello everyone, We are thrilled to introduce the first edition of the Language & Internationalization newsletter, available at this link: < https://www.mediawiki.org/wiki/Wikimedia_Language_engineering/Newsletter/20…> [1]. This newsletter is compiled by the Wikimedia Language team. It provides updates from July–September quarter on new feature development, improvements in various language-related technical projects and support efforts, details about community meetings, and contributions ideas to get involved in projects. To stay updated, you can subscribe to the newsletter on its wiki page. If you have any feedback or ideas for topics to feature in the newsletter, please share them on the discussion page, accessible here: < https://www.mediawiki.org/w/index.php?title=Talk:Wikimedia_Language_enginee…> [2]. Cheers, Srishti [1] https://www.mediawiki.org/wiki/Wikimedia_Language_engineering/Newsletter/20… [2] https://www.mediawiki.org/w/index.php?title=Talk:Wikimedia_Language_enginee… *Srishti Sethi* Senior Developer Advocate Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

[Train] 1.41.0-wmf.30 blocked
by Antoine Musso 12 Oct '23

12 Oct '23

Hello, The 1.41.0-wmf.30 version of MediaWiki is blocked. The new version deployed to group 1 but can proceed no further until the issue is resolved: Error: Typed property GrowthExperiments\NewcomerTasks\AddLink\LinkRecommendationUpdater::$linkRecommendationTaskType must not be accessed before initialization https://phabricator.wikimedia.org/T348719 Once the issue is resolved, the train can resume. cheers, -- Antoine Musso & Andre Klapper

1 1

MediaWiki Extensions and Skins Security Release Supplement (1.35.12/1.39.5/1.40.1)
by Maryum Styles 10 Oct '23

10 Oct '23

Greetings- With the security/maintenance release of MediaWiki 1.35.12/1.39.5/1.40.1, we would also like to provide this supplementary announcement of MediaWiki extensions and skins with now-public Phabricator tasks, security patches and backports [1]: EntitySchema + (T339016, CVE-2023-45368) - EntitySchema edits don't run through AbuseFilter https://gerrit.wikimedia.org/r/q/Id71ece831c929fadb1710634de9a7be5f02e0b0e Wikibase + (T333980, CVE-2023-45366) - FederatedPropertiesError shows label as unescaped HTML https://gerrit.wikimedia.org/r/q/I76b953be86d6465ee7355c0a189c68cf20457786 Citoid + (T340200, CVE-2023-45365) - i18n XSS in Citoid Wikibase module https://gerrit.wikimedia.org/r/q/I570e00e45f8a36fbf2b26db9610fa0a702a28f67 CheckUser + (T344923, CVE-2023-45367) - User can store arbitrary number of rows in cu_useragent_clienthints https://gerrit.wikimedia.org/r/c/mediawiki/extensions/CheckUser/+/952482/ SportsTeams + (T345040, CVE-2023-45374) - SportsTeams: no anti-CSRF check in Special:SportsTeamsManager and Special:UpdateFavoriteTeams https://gerrit.wikimedia.org/r/c/mediawiki/extensions/SportsTeams/+/952552 Wikibase + (T345064, CVE-2023-45371) - Merging items is not rate limited and only partially protected by AbuseFilter https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wikibase/+/961264/ ProofreadPage + (T345693, CVE-2023-45373) - ProofreadPage Security-XSS errors in CI https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ProofreadPage/+/96126… PageTriage + (T344359, CVE-2023-45369) - pagetriagelist API leaks suppressed usernames https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PageTriage/+/960676/ SportsTeam + (T345680, CVE-2023-45370) - SportsTeams: Special:SportsManagerLogo and Special:SportsTeamsManagerLogo should check for the "sportsteamsmanager" user right https://gerrit.wikimedia.org/r/c/mediawiki/extensions/SportsTeams/+/959699/ 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]. [1] https://phabricator.wikimedia.org/T340874 [2] https://www.mediawiki.org/wiki/Version_lifecycle [3] https://www.mediawiki.org/wiki/Reporting_security_bugs

1 0

MediaWiki 1.41-beta has been branched
by James Forrester 10 Oct '23

10 Oct '23

Hey all, This is a quick note to highlight that I've created the REL1_41 branch for MediaWiki core and each of the extensions and skins in Wikimedia git[0]. This is the first step in the release process for MediaWiki 1.41.0, which should be out in November 2023, approximately six months after MediaWiki 1.40.0. The branches reflect the code as of the last 'alpha' branch for the release, 1.41.0-wmf.30, which is being deployed to Wikimedia wikis this week for MediaWiki itself and those extensions and skins available there. From now on, patches that land in the main development branch of MediaWiki and its bundled extensions and skins will be slated for the MediaWiki 1.42 release, unless specifically backported[1]. If you are working on a critical bug fix that will affect the code in the release, once the patch has been merged into the development branch, you should propose it for backporting by cherry-picking to the REL1_41 branch. If you are working on a new feature, that should now not be backported. If you have an urgent case where the work should block release for everyone else, please file a task against the `mw 1.41-release` project on Phabricator.[2] If you have tickets that are tagged for `mw-1.41-release`, please finish them, untag them, or reach out to get them resolved in the next few days. We hope to issue the first release candidate, 1.41.0-rc.0, in two weeks' time, and if all goes well, to then release MediaWiki 1.41.0 a few weeks after that. [0]: https://www.mediawiki.org/wiki/Bundled_extensions_and_skins [1]: https://www.mediawiki.org/wiki/Backporting_fixes [2]: https://phabricator.wikimedia.org/tag/mw-1.41-release/ Yours, -- *James D. Forrester* (he/him <http://pronoun.is/he> or they/themself <http://pronoun.is/they/.../themself>) Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

October 2023 - Technical Community Newsletter!
by Onyinyechi Onifade 10 Oct '23

10 Oct '23

Hello Tech Enthusiasts, Welcome to the October’23 <https://www.mediawiki.org/wiki/Technical_Community_Newsletter/2023/October> edition of our Tech Community Newsletter! We're excited to bring you a roundup of highlights, news, and information of interest from and about the Wikimedia Technical Community. The newsletter is compiled by staff(s) working on developer outreach. 🥁 Here’s a sneak peek of what to expect from this newsletter edition: Technical Community Spotlight: African Wikimedia Technical Community (AWTC) Get inspired by the journey of the African Wikimedia Technical Community. Learn about their experiences, Upcoming Projects and Events, and areas you can support! Highlight from the Wikimania Hackathon Catch a glimpse of the innovation, creativity, and collaboration that unfolded at the Wikimania hackathon in Singapore! *Read the full October’23 newsletter edition here ➡️https://www.mediawiki.org/wiki/Technical_Community_Newsletter/2023/October <https://www.mediawiki.org/wiki/Technical_Community_Newsletter/2023/October>! * The Wikimedia Technical Community is large and diverse - it's hard to capture everything. We would love to hear your ideas. Have a topic you'd like us to cover or a story to share? Ideas for future newsletter editions? Would like to have your community featured in the next edition? Please add your suggestion to the talk page <https://www.mediawiki.org/wiki/Talk:Technical_Community_Newsletter> or send an email to oonifade(a)wikimedia.org. We'd love to hear from you! If you'd like to keep up with updates and information, subscribe to the Technical Community Newsletter: https://www.mediawiki.org/wiki/Newsletter:Technical_Community_Newsletter Until the next edition, -- *Onyinyechi Onifade * Technical Community Program Manager 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 October 2023