Jump to content

Language Onboarding and Development/Status Updates/Q1 2025-26

From mediawiki.org

Q1 2025-26 July to Sep

[edit]

Summary

[edit]
  • Experimented inviting native speakers through targeted regional and language outreach through a CentralNotice banner on a high-traffic Wikipedia in their region and engaging them in simple edits.
  • Resolved 15 tickets in total on Localisation and Internationalisation support ; 5 Languages onboarded,  4 tickets on messages , 6 tickets on technical volunteer engagement on plural support, fall back, namespaces, date and time format etc . Additionally, engaged at 3 collaboration and engagement spaces; Wikimania, Language community meting and published a newsletter

Hypothesis work; Engage native speakers  to improve vital content in small language wikis

[edit]

Objective; Make more vital knowledge available and well illustrated across languages and topics( link ) Key Result: By the end of Q2, implement 3 interventions that help contributors to improve the state of vital content on their Wikipedia

Hypothesis WE2.1.1: If we invite native speakers of small wikis through a CentralNotice banner on a high-traffic Wikipedia in their region to contribute to SuggestedEdits and other Growth features, we can assess whether this approach attracts new native speakers and if they use these editing tools to improve vital content. More here T399011

First draft of the WE 2.1.1 report has been published link. This report focuses on short-term measurements; longer-term effects will be measured three months later. For a short summary, see the comment in the Phabricator task here: link.

  • Across both scenarios, there were a total of 19,076,386 banner impressions, 10,766 clicks, 233 accounts created, 128 users engaged with growth features, and 55 edits made by new editors.
  • Overall, Scenario 2 (user → newcomer homepage) had a higher growth engagement rate of 1.80% compared to Scenario 1 (user → event registration → newcomer homepage), which had an engagement rate of 0.99%.
  • While Scenario 2 shows a higher growth engagement rate, Scenario 1 shows more account creations and edits. This might relate to the regions targeted and the larger population of speakers in Scenario 1, whereas Scenario 2’s higher engagement rate could result from the user experience of being taken directly to the newcomer homepage rather than via the event registration page.
  • Medium activity language & size comparison (minwiki & astwiki): minwiki had an engagement rate of 0.36%, while astwiki had an engagement rate of 4.18%. The difference is statistically significant. Scenario 2 shows higher growth feature homepage engagement than Scenario 1 for this group. This is particularly interesting because Minangkabau is spoken by far more people than Asturian, yet Asturian shows higher growth feature homepage engagement in Scenario 2.
  • Looking at how these results compare with previous campaigns, we can reference a similar report: link.
    • For impressions, 0.001% led to account creations (compared to 0.006% in that campaign).
    • In that campaign, 3.7% of users who clicked the banner on the landing page created accounts. In our campaign, Scenario 1 saw 2.9% of landing page users create accounts, and Scenario 2 saw 2.6%.

Essential work: Communities particularly new & smaller ones are supported with internationalization and localisation workflows and features to help them move towards their goals.

[edit]

[edit]

Key Result; Respond to internationalisation and localisation requests through timely interventions and engagements to support Language communities to move towards their goals.

This area includes technical efforts to enable newly introduced or  smaller languages  to be accessible, usable and sustainable on Wikimedia environments. This has entailed resolving internationalization, and localization needs of these language communities including onboarding new languages,  UI localisation, Plural support, Keyboard support, Fall back among other areas categorised into various focus areas depending on prioritization per quarter.

2-3 splits to allows for translators to easily select highly-visible/high functionality messages as priority translations in their native language. Splitting Mediawiki core subgroups into different categories provides the opportunity to allow for translators to easily select highly-visible/high functionality messages as priority translations in their native language T404633

4 completed tickets

  • Respond to language onboarding requests through timely interventions and engagements to support Language communities to move towards their goals. Additionally, 1-2 exploratory steps to the process of onboarding a new language, reducing highly manual and repetitive steps and making it more efficient to make configuration changes, see more T404643

5 completed tickets. ( Also Implemented a work in progress patch that has majority of the functionalities required to automate the onboarding process to MediaWiki core completed)

Resolve at least 10 internationalisation and localisation requests per quarter through timely interventions and engagements to support Language communities requesting technical assistance. T399682

6 tasks completed with 5 volunteers engaged.

Additionally, engaged at 3 collaboration and engagement spaces; Wikimania, Language community meting and published a newsletter