Jump to content

Mpango wa Mwaka wa Wikimedia Foundation/2025-2026/Malengo na Matokeo Muhimu ya Bidhaa na Teknolojia

Add links
From Meta, a Wikimedia project coordination wiki
This page is a translated version of the page Wikimedia Foundation Annual Plan/2025-2026/Product & Technology OKRs and the translation is 62% complete.
Outdated translations are marked like this.
Other languages:
Wikimedia Foundation Annual Plan 2025–2026

Mwaka Ujao (Machi 2025)

Hata dunia inapobadilika, Shirika la Wikimedia Foundation bado lina uhakika kwamba tunataka dhamira yetu - kutengeneza na kuweka taarifa muhimu kutoka kwenye miradi ya Wikimedia inayopatikana kwenye mtandao bila malipo - kuwa juhudi za vizazi vingi: tunataka maarifa bila malipo yaendelee kupatikana kwa vizazi vingi vijavyo. Ili kufanya hivi, tunahitaji kuhimiza ukuaji wa wafanyakazi wa kujitolea, kuwawezesha wanaojitolea kuunda maudhui ya ensaiklopidia ya kuaminika, kufadhili misheni yetu, na kuboresha utoaji wetu ili kuchagiza mabadiliko ya intaneti. Unaweza kusoma zaidi kuhusu hayo nguzo nne za kimkakati

Mtandao unabadilika haraka. Vizazi vipya vinapata taarifa kupitia video za kijamii na uzoefu wa AI, na, ikilinganishwa na vizazi vya zamani, wachache wao wanafahamu Wikipedia. Tunaona kupungua kwa idadi ya watu wanaokuja kwenye tovuti zetu na idadi ya watu wanaohariri. Wakati huo huo, majukwaa kwenye mtandao yanategemea maudhui ya Wikimedia ili kusisitiza AI zao na matoleo ya utafutaji. Mienendo hii ni changamoto kuu, lakini inaweka wazi kwa nini maarifa ya uhakika ya bure ambayo tunaunda pamoja ni muhimu sana. Ulimwengu unahitaji chanzo cha maarifa cha kutegemewa, kilichopitiwa upya na binadamu zaidi ya hapo awali, na miradi ya Wikimedia inaendelea kuonesha kwamba inaweza kutoa maarifa hayo.

Ili kukabiliana na changamoto hizi kwa mwaka ujao, tutaunda njia za kutumia maudhui ya Wikimedia kwa uendelevu, na tutaleta maudhui ya Wikimedia kwenye nafasi za kijamii za mtandaoni ambako vizazi vipya vinatumia muda wao. Tutaboresha tovuti zetu ili wasomaji watake kurudi, kushiriki kwa kina, na kuchangia kwa njia ambazo ni muhimu kwao. Na tutawekeza katika uwezo wetu wa kujaribu teknolojia mpya haraka, ili kasi yetu ya maendeleo ilingane na kasi ambayo ulimwengu unabadilika.

The infrastructure goal is how the platform and user experience will support addressing these challenges and reaching the majority of the participants in the movement. It is not a list of projects, but instead, a set of directions to fuel volunteer growth, enable volunteers to build trustworthy encyclopedic content, fund our mission, and evolve our offering to shape the changing internet. You can read more about those four strategic pillars.

Kukuza ujitoleaji wa watu

The community of volunteers is the unique engine behind the success of the Wikimedia projects, and we need it to be healthy and growing. But in this past year, we’ve seen continued declines in the number of new and returning editors to the projects. To better understand and more effectively respond to the needs of our current volunteers, the Foundation revamped the Community Wishlist from a once-a-year survey into an always-open intake process where user needs and project ideas can feed into the work of multiple teams at the Foundation. We grouped wishes into "Focus Areas" and have integrated three of those Focus Areas under key results in the annual plan. We also started a pilot Product and Technology Advisory Council to supplement the numerous conversations Foundation teams have with community members on- and off-wiki throughout the year. In addition, we have identified opportunities to bring new generations into our projects, such as the fact that younger people are eagerly participating in other online social spaces where they have easy, mobile-friendly ways to connect over shared topics of interest.

In the coming year, we will fuel volunteer growth by making contribution easier and more appealing to new generations through expanding mobile-first, new ways to edit (“structured tasks”), and adding intelligent workflows that make constructive mobile editing easy for newer contributors (“edit checks”). To more deeply engage and retain existing volunteers, we will offer recommended actions and tasks and surface them in a central hub that makes it easy to organize on-wiki activity.  We will thoughtfully use AI to strengthen volunteers in their work, always keeping humans in the loop and prioritizing transparency. For both new and experienced volunteers, we will build avenues to connect and work together on our sites – inspired by successful campaigns and WikiProjects – allowing them to find liked-minded editors and improve content related to their interests (aligned with this Wishlist focus area).

Kutoa maudhui ya kiensaiklopidia ya kuaminika

As AI-generated material multiplies on the internet, the world needs trustworthy encyclopedic content more than ever. We want to increase the abilities of volunteers to both create new content, ensure that existing content stays trustworthy, and deliver trustworthy content to a new generation of readers with new needs and preferences.

To help volunteers create new content, we'll build on existing guided tools and workflows  (such as the Content Translation Tool), so that large and smaller communities alike can cover vital content. To ensure that existing content stays trustworthy,, we will help experienced volunteers better manage their growing workloads by extending the tools they use to find tasks that need their attention – making it easier for them to update articles and revert unhelpful edits (aligned with this Wishlist focus area).

Pia tutasaidia watendaji kutetea maudhui yetu kwa kuonyesha ishara mpya (zaidi ya anwani za IP) zinazotambua watendaji wabaya, kuruhusu watumiaji kuzuiwa kwa njia ambazo zitapunguza uzuiaji wa kimakosa wa wahariri wenye nia njema.

Ili kuwasilisha maudhui ya ensaiklopidia kwa kizazi kipya, tutaunda vipengele ambavyo vitasaidia aina mpya za wasomaji kuelewa makala kwa urahisi, kuwasaidia kupata taarifa wanazozipenda, na kuwaruhusu kushiriki kikamilifu wanaposoma. Mabadiliko haya yanakusudiwa kuwahimiza wasomaji wapya wa Wikipedia kuwa wasomaji waliojitolea wa Wikipedia, na baadhi yao kuwa wafadhili (kuendana na eneo hili la kuzingatia Orodha ya Matamanio).

Kuwasilisha maudhui ya kuaminika pia kunamaanisha kuunga mkono muundo wa “maarifa kama huduma”, ambapo mtandao mzima unatumia maudhui ya Wikimedia. Katika modeli hii, miundombinu yetu si tu rasilimali muhimu kwa wanadamu wanaokuja kwenye tovuti yetu, lakini pia kwa ajili ya utafutaji na makampuni ya AI, ambayo hufikia maudhui yetu kiotomatiki kama pembejeo ya msingi na matokeo kutoka kwa bidhaa zao. Aina hizi za kampuni zinawakilisha moja tu ya matumizi mengi ambayo yanazidi kuweka mzigo usio endelevu kwenye miundombinu yetu. Kwa mwaka uliopita, ongezeko kubwa la kiasi cha ombi linalotoka kwa zana za kuchakachua na roboti limefanya iwe muhimu zaidi kwetu kusahihisha mtindo huu. Tunahitaji kuanzisha njia endelevu kwa wasanidi programu na watumiaji tena kufikia maudhui ya maarifa ili wanadamu wapewe kipaumbele kuliko roboti.

Kutoa ruzuku kwaajili ya mustakabali wa baadaye wa maudhui ya ‘bure’

Idara ya Bidhaa na Teknolojia ina jukumu muhimu katika kuhakikisha kwamba harakati zetu ni endelevu. Kwa mwaka ujao, tutashirikiana kwa karibu na timu ya Kuchangisha pesa ili wafadhili wetu wapate uzoefu unaozidi kuwa wazi na wenye kuthawabisha. Kwenye tovuti zetu na programu za simu, tutajenga fursa kwa wasomaji kutoa shukrani zao kwa Wikipedia kupitia uchangiaji, na tutajenga njia mpya za wafadhili kujisikia kutambuliwa ili waendeleze michango yao mwaka baada ya mwaka.

Kuunda intaneti inayobadilika

Ili kuleta maarifa ya bure kwa kila mtu ulimwenguni, tunahitaji kukutana nao mahali walipo, na uzoefu unaomsaidia kujifunza. Watu wenye umri wa miaka 18-24 wana ufahamu mdogo na matumizi ya Wikipedia kuliko vizazi vilivyokuja kabla yao. Kwa kiasi kikubwa hujifunza na kuingiliana na majukwaa fupi ya video, watu wanaoaminika mtandaoni, uzoefu wa kijamii wa michezo ya kubahatisha, na, zaidi, programu za AI. Mwaka huu, tutafanya Wikipedia ipatikane kwa watazamaji hao katika maeneo wanayotumia muda mtandaoni, ili wajue Wikipedia kama chanzo cha maarifa cha kuaminika na kilichoundwa na binadamu. Tutakuza uwepo wetu katika mifumo maarufu ya video, tukieneza maudhui ya Wikipedia na kuzalisha jumuiya katika nafasi hizo. Na tutachunguza mawazo ya kuleta maarifa ya Wikipedia kwenye michezo ya kubahatisha na majukwaa ya kijamii.

Within Infrastructure, this is divided into three work portfolios (called "buckets"): Wiki Experiences, Signals and Data Services, and Future Audiences. These buckets are the same as last year and the year before.

Kwa pamoja, tunaamini kwamba mpango huu unakutana na muhimu katika historia ya mtandao, tuliweka sisi ili kulinda kuwa maudhui ya maarifa yasiyolipshwa yanaendelea na kutengenezwa na vizazi vyote. Malengo yetu na matokeo muhimu ya muundo wa muundo na yaliyomo katika mpango huu kwa undani zaidi, na tunatarajia kupokea maswali na mawazo kutoka kwenye jumuiya kwa upana wake.

Building, improving and sustaining the infrastructure for Wikimedia projects and volunteers, rooted in our values

"The Foundation will make and keep useful information from its projects available on the internet free of charge, in perpetuity."

The Product and Technology teams dedicate a permanent, year-round priority to build, improve and maintain the infrastructure that serves the Wikimedia projects. We invest in hosting the Wikimedia projects, developing open-source software and design systems, and maintaining and improving the infrastructure for data products and AI models.

Part of our essential work is focused on the fundamentals of developing and hosting a large popular website. We host our Wikimedia projects in data centers, on servers and hardware we purchase, install and maintain, connected to each other and the rest of the Internet over a high speed network. We monitor and add capacity where needed, and refresh equipment when it gets too old. For example, this year, we anticipate expanding our capacity and refreshing our hardware in our datacenters in Ashburn, Virginia and Carrollton, Texas.

We design and develop open-source software (most notably MediaWiki). We also use and deploy many existing third-party open-source applications, libraries and frameworks. Important bugs in our software get prioritized and fixed. Maintaining open source software requires highly skilled work from people with special expertise in open source software development, site reliability engineering (SRE), product management, program management, design, and more. Our staff work to ensure our software and systems are up to date and adapt to an ever-changing environment. This includes modernizing our code to continue to benefit from security fixes and to work well with new third-party software. For example, MediaWiki is written in PHP, and in the past year we migrated from PHP 7.4 to 8.1, which required changes to both the code and the infrastructure where we host our sites and services. This year, we will build on that effort and migrate to 8.3, using lessons learned and tools developed in the 8.1 upgrade. Updating will make our systems faster for readers, easier to use for staff and volunteers, and more secure for everyone. It will also save future development time thanks to security, performance and support improvements that come with language updates.

To ensure our projects and content remain available on the Internet, both today and in perpetuity, our teams dedicate a significant amount of effort to ensuring high availability of our sites and services. One aspect of this work focuses on disaster recovery from catastrophic or malicious events. For example, we ensure we have backups of important data, and are able to recover from them. Similarly, twice a year we test our ability to switch our sites between our data centers in automated fashion, and fix any issues we find. Another aspect of this work focuses on identifying and adapting to evolving trends in the types and volumes of traffic we receive. For example, with unprecedented growth in automated scrapers, we are prioritizing work to ensure that our sites and services remain accessible for human users, taking a systematic approach to establishing norms around responsible use of our infrastructure.

Not all work is planned far in advance. We also respond to unexpected emerging events and incidents, like site outages, security reports or security incidents, or large scale vandalism attacks on our projects. We monitor our performance and barriers to reachability across the globe (including Internet connectivity problems, or censorship blocks), and investigate any anomalies we find. Some of these unexpected events or repeating patterns of problems result in staff prioritizing short-term follow-up projects that aim to mitigate or completely prevent further negative impact. For example, these kinds of efforts were crucial to enabling our Wikimedia projects to withstand global traffic spikes due to major news events (e.g., high-profile celebrity deaths), through a combination of performance optimization, architectural redesign of bottlenecked areas, and capacity increases. Similarly, recent improvements to the usability of our tools and systems for managing the traffic we receive have enabled us to react more quickly and effectively to changing conditions. This kind of adaptive work is integral to our ability to respond to emerging events, often on short time scales, and ensure our projects and content remain available.

Malengo ya Bidhaa na Teknolojia

Malengo yaliyowasilishwa hapa yako katika muundo wa rasimu na yako wazi kwa maoni na majadiliano.

  • Malengo yanawakilisha mwelekeo wa kiwango cha juu.
  • "Matokeo Muhimu" (KRs) yanawakilisha njia inayoweza kupimika ya kufuatilia mafanikio ya malengo yao.
  • Kimsingi "Nadharia" za kila KR huwakilisha kazi halisi tunayofanya ili kujaribu kufikia matokeo muhimu yanayohusiana. Yatasasishwa katika waraka huu na kwenye mradi husika au kurasa za wiki za timu kadri maarifa yanavyopatikana mwaka mzima.
  • wishlist item ni ya kazi ambayo Shirika linaipa kipaumbele chini ya Orodha ya Matamanio ya Jumuiya.

Uzoefu wa Wiki (WE)

Uzoefu wa Wachangiaji (WE1)

  • Lengo: Michango huongezeka kwa sababu wanaojitolea wanapewa fursa zinazovutia na kuelewa athari zao. Jadili
    • Muktadha: Lengo hili litakuwa msingi wa kuwasilisha mkakati mpya wa wachangiaji wenye nguzo zake 3: 1) kuwapa watu wanaojitolea njia kuu ya kupanga shughuli zao za wiki, 2) kutoa kazi ndogo na za kipekee ili kuleta uwazi zaidi na kuwasaidia wanaojitolea kufikia uwezo wao, na 3) kutoa mchango wenye maana zaidi. Katika mwaka wa 25/26, tunapanga kuwasilisha miundomsingi ya kimsingi ili kuwasaidia wanaojitolea kupanga shughuli zao za mtandaoni kwa njia ya kati, tukianza na hatua zinazolenga wahariri na wasimamizi wazoefu. Katika miaka inayofuata tutaongeza uingiliaji kati katika majukumu yote ya wachangiaji na kujumuisha nafasi zaidi za matatizo. Zaidi ya hayo, tutaendelea kuwekeza katika Kuhariri na Kazi Zilizoundwa, tukijenga msingi wa jinsi ya kutumia AI kwa njia inayoweza kusambazwa, kama mwongozo wakati wa mchakato wa kuhariri na kama njia ya kuwaelekeza wanaojitolea kwenye fursa zinazovutia. Na mwisho, tutawekeza katika kuwafanya wajitoleaji wa athari waonekane zaidi ili kuwaundia matumizi ya maana zaidi.
      • Tokeo kuu la WE1.1: Ongeza mabadiliko ya kujenga [i] kwa X% kwa wahariri walio na au chini ya mabadiliko 100, kama inavyopimwa na majaribio hadi mwisho wa Q2.
        i. "Hariri zenye tija" = mabadiliko ambayo hayajarejeshwa ndani ya masaa 48 baada ya kuchapishwa
        • Wajitoleaji wapya wanatatizika kuanza kuhariri kwa mafanikio. Hasa, watu wanaotumia vifaa vya mkononi ambapo nafasi ya skrini ni ndogo na umakini mara nyingi hugawanyika.
        • Wengine huchoshwa na muktadha, subira, na majaribio na makosa yanayohitajika ili kuchangia kwa njia yenye kujenga. Wengine bado hawajapata fursa ya kuamua kujaribu.
        • WE 1.1 tutashughulikia masuala haya kwa:
          1. Kuonesha mapendekezo ya kuhariri
          2. Kutoa mwongozo wa kuhariri unaoweza kutekelezeka
          3. Kuunda mtiririko wa kazi maalum wa kuhariri
        • Msingi wa juhudi hizi ni hitaji la njia kubwa za kugundua jinsi mabadiliko yanayoendelea na maudhui yaliyopo yanaweza kuboreshwa. Ili kukuza uwezo huu, tutaendelea kufanya majaribio ya kujifunza kwa mashine ili kujifunza jinsi AI inavyoweza kutusaidia kutambua masuala ya sera ya Wikipedia.
      • wishlist item Tokeo kuu WE1.2: Kuongeza idadi ya ushirikiano kwenye wiki kwa X% YoY kufikia mwisho wa Robo mwaka ya 3 (Q3).
        • Wachangiaji mara nyingi hutatizika kupata fursa za kushirikiana wao kwa wao, hasa kuhusu mada na kazi wanazojali. Hii inaweza kusababisha hisia ya kuwa peke yako kwenye wiki kwa wageni, na inaweza kusababisha uchovu kwa wahariri wenye uzoefu. Zaidi ya hayo, athari za shughuli za ushirikiano mara nyingi hazieleweki, ambayo inaweza kusababisha watu wachache kutaka kujiunga, kupanga, au kuunga mkono ushirikiano kwenye Wiki.
        • Tunataka kufanya thamani ya ushirikiano iwe wazi zaidi kwa kufanya yafuatayo:
          1. Kuunda njia mpya za kushirikisha athari za shughuli shirikishi kwenye wiki
          2. Kuanza kukusanya data za harakati kuhusu athari za shughuli za kiushirikiano
          3. Kuweka miundo msingi ya kufuatilia michango shirikishi, ili tuweze kutoa njia mpya za kibunifu za kutambua na kutuza michango katika siku zijazo.
        • Ushirikiano utapimwa kwa shughuli mpya zitakazoundwa kupitia Usajili wa Tukio katika kiendelezi cha Matukio ya Kampeni. Lengo ni kwamba, kufikia mwisho wa KR hii, tutakuwa na watumiaji zaidi wa zana za upanuzi na njia mpya za kupata athari za ushirikiano. Hili litatuweka katika nafasi nzuri ya kuunganisha miundombinu yetu iliyopo kwa njia zingine za kutambua na kuthawabisha kazi kwenye wiki (kama vile moduli ya athari, asante, n.k).
        • Eneo la kuzingatia orodha ya matamanio: Orodha ya Matamanio ya Jumuiya/Maeneo Lengwa/Kuwaunganisha Wachangiaji
      • kipengee cha orodha ya matamanio Tokeo kuu la WE1.3: Hadi mwisho wa Q4, kumekuwa na ongezeko la X% katika hatua za udhibiti zinazofanywa na watu ambao ni wapya kwa aina hiyo ya udhibiti.
        • Kama sehemu ya juhudi zetu za kuleta uwazi zaidi kwa wachangiaji, tunaamini kuwa tunaweza kufanya kazi bora zaidi ya kuibua fursa za michango kwa wanaojitolea. Tutajaribu nadharia hii kwa kuangazia shughuli mahususi za udhibiti (maelezo yatabainishwa) kwa wachangiaji ambao ni wapya kwa aina hiyo ya hatua ya udhibiti, kwa lengo la kupata wachangiaji zaidi kushiriki katika kazi za udhibiti. Tunatazamia hili kuishi katika eneo ambalo ni kitovu cha shughuli za wajitoleaji, na KR hii itatumika kama njia yetu ya kuchunguza dhana hii na kubainisha mahali panapofaa kwa aina hizi za mwingiliano.
        • Lengo letu la jumla kama ilivyoelezwa katika KR si kupanua tu kundi la wasimamizi, lakini kuelekeza juhudi zetu katika kuwashirikisha wahariri wanaofanya kazi kwa sasa na fursa ambazo huenda hawazifahamu. X% ni thamani ya kishikilia nafasi, inayosubiri kipimo cha msingi cha jinsi wahariri amilifu wanavyojihusisha na utiririshaji kazi mpya wa usimamizi.
        • "Wasimamizi" watafuata ufafanuzi ulioanzishwa katika Research:Develop a working definition for moderation activity and moderators, ingawa kazi ya ufuatiliaji ingehitajika ili kupunguza tafsiri ya kiasi.
        • Eneo la kuzingatia orodha ya matamanio: Orodha ya Matamanio ya Jumuiya/Maeneo Lengwa/Utiliaji vipaumbele vya Kazi

Maarifa Muhimu (WE2)

  • Lengo: Kufanya maarifa muhimu zaidi yapatikane na kuoneshwa vyema katika lugha na mada mbalimbali. Jadili
    • Muktadha wa lengo: Lengo hili litachochea ukuaji wa maudhui unaozingatia maslahi ya wachangiaji katika mada na lugha mahususi, na hitaji la msomaji la maarifa muhimu ambayo yameonyeshwa vyema. Ujuzi muhimu ni seti ya makala ambayo hutoa upana na undani wa mada zinazohitajika kwa mradi wa lugha ya Wikipedia. Inafafanuliwa na jumuiya kwa kurejelea kujulikana, umuhimu, usomaji uliotabiriwa, na miunganisho kati ya makala.
    • Tutachukua mbinu ya kijamii na kiufundi, kuboresha ufanisi wa vipengele, zana na michakato ya kijamii. Tutatumia vipengele vya bidhaa vyenye athari ya juu kama vile kazi zilizopendekezwa, utafutaji wa maudhui na tafsiri ya maudhui lakini pia kuwezesha uanzishaji na ukuzaji wa Wikipedia za lugha ndogo. Tutawasaidia waandaaji wa Wikimedia ambao huajiri, kutoa mafunzo na kusaidia wachangiaji ili kufanyia kazi malengo ya maudhui shirikishi kupitia usanidi shirikishi kama vile Miradi ya Wiki na kampeni. (Tunakadiria kuwa angalau waandaaji 300 wanashiriki kila robo mwaka.) Pia tutakuza uhusiano na wachapishaji wanaofaa zaidi ili kuondoa vizuizi kwa nyenzo za chanzo. (Kwa sasa tuna ushirikiano na kanzidata zaidi ya 100 maarufu zaidi duniani kwaajili ya kujisajili tu.)
    • Ili kuhakikisha uingiliaji kati wetu una matokeo chanya kwenye maarifa muhimu, tutapima ongezeko la maudhui yaliyopewa kipaumbele na jumuiya na ubora wa maudhui hayo, tukiangalia vipengele kama vile viwango vya ubadilishaji na idadi ya marejeo na picha.
      • Tokeo kuu la WE2.1: Mwishoni mwa Q2, kutekeleza hatua 3 zinazosaidia wachangiaji kuboresha hali ya maudhui muhimu kwenye Wikipedia zao.
        • KR hii itaangazia mapengo ya maudhui ndani ya taratibu za kuhariri, kama vile ugunduzi wa picha kwenye Wikipedia, tafsiri ya maudhui na uundaji wa makala mpya. Pia tutatekeleza na kujaribu uingiliaji kati wa kijamii na kiufundi ili kusaidia shughuli ya kuunda maudhui kwa jumuiya za lugha ndogo. Mafanikio yatapimwa ndani ya kila dhana.
      • Tokeo muhimu WE2.2: Kufikia mwanzoni mwa robo tatu ya mwaka (Q3), Wikifunctions 10 zitakuwa zimeundwa na jumuiya za Wikimedia ili kuunda maudhui kwenye angalau miradi 10 ya Wikimedia.
        • Kwa sasa, zana zinazoweza kuunda maudhui kwa kiasi kikubwa hazipatikani kwa Wikipedia zote. Hii ni pamoja na vigezo na moduli, ambazo zimetumika kwenye Wikipedia kubwa zaidi kuunda na kudumisha maudhui. Wikifunctions inaweza kufanya zana hizi kwa miradi mingi zaidi, na jumuiya mahalia hazitalazimika kuunda au kutuma kudumisha zana hizi wao wenyewe.
        • Uwezo wa awali wa Wikifunctions unaweza kujumuisha:
          • Vitendaji vya ubadilishaji (katika maandishi ya wiki) ili kutoa maudhui ya kina zaidi ambayo vinginevyo yasingekuwepo kwa sababu ya juhudi zinazowekwa.
          • Kufungua sentensi na aya kwa baadhi ya makala (katika maandishi wazi ya wiki), ambayo inaweza kuhakikisha uthabiti na usahihi zaidi katika wiki. Mifano ya hilo ni pamoja na makala za miaka katika wiki nyingi, au wasifu kwenye Wikipedia ya Kiitaliano.
          • Maudhui ambayo yanaweza kutumia Wikidata na kudumisha maudhui kiotomatiki data inaposasishwa, k.m. idadi ya watu wa jiji au umri wa mtu.

Uzoefu wa Mtumiaji (WE3)

  • Lengo: Wasomaji kutoka vizazi vingi hujishughulisha, na wanaendelea kujishughulisha, na Wikipedia, na kusababisha ongezeko linalopimika la uhifadhi na shughuli ya uchangiaji. Jadili
    • Muktadha wa lengo: Lengo hili litalenga kuhifadhi wasomaji wapya kupitia miundo bunifu ya maudhui, hadhira kuu kupitia kuimarisha uzoefu unaofahamika wa usomaji, na kuhakikisha uendelevu wa muda mrefu kwa kuimarisha miunganisho ya wasomaji na kutoa michango mbalimbali. Itajumuisha muendelezo wa kazi yetu ili kurahisisha ugunduzi wa maudhui kupitia vipengele vipya na vya majaribio zaidi kama vile muhtasari wa AI au maeneo tata yaliyobinafsishwa. Pia itajumuisha kazi ya kubakiza na kuboresha ubora wa uzoefu wa kusoma kwa kina zaidi katika faneli ya kusoma na kuchunguza uratibu wa usomaji kupitia orodha za usomaji na ushiriki mwingine usio wa kuhariri. Kwa wafadhili, kazi hii itaendelea kulenga utofautishaji wa vyanzo vya mapato kutoka ndani ya jukwaa.
      • kipengee cha orodha ya matamanio Tokeo kuu la WE3.1: Kuongeza uhifadhi wa wasomaji ambao wametoka kwenye akaunti kwa 5% kwenye programu na 3% kwenye wavuti, kama inavyopimwa kupitia majaribio ya A/B, kwa kujaribu njia za kujifunza na kujihusisha kufikia mwisho wa robo mwaka ya 4( Q4)
        • KR hii italenga kuendelea kuwekeza katika matumizi ambayo yanaboresha njia mpya za kuvinjari na kujifunza maudhui, mara nyingi kwa kutumia teknolojia na miundo mipya - kuwasilisha maudhui yaliyopo kwa njia mpya na zinazovutia. Katika mwaka huu wa fedha, tungependa kuendelea kujaribu vipengele vipya huku tukizingatia kuongeza majaribio yaliyofaulu kwenye wiki na mifumo. Kazi katika KR itaenea kwenye tovuti ya simu na eneo-kazi, pamoja na programu za iOS na Android na kulenga ugunduzi wa maudhui (maelekezo ya kuvinjari na mapendekezo) na miundo ya kujifunza inayoweza kubadilika (muhtasari unaosaidiwa na mashine, uchanganyaji wa maudhui).
        • Eneo la kuzingatia orodha ya matamanio: Matukio mapya ya watumiaji
      • 'Tokeo muhimu WE3.2: Ongeza idadi ya michango kupitia njia zisizo za mabango au barua pepe kwa 5% Mwaka baada ya mwaka (YoY) kupitia mwingiliano wa bidhaa zinazokuza miunganisho ya kina na kupunguza msuguano kwa wafadhili kufikia mwisho wa robo mwaka ya 2 (Q2)
        • KR hii itatuona tukiendelea kuchunguza maeneo mapya ya michango na fursa nyingine za kubadilisha wasomaji kuwa wafadhili na kuwafanya waendelee kuwa nasi kwa kuimarisha miunganisho yao kwenye Wiki, ikijumuisha maudhui yaliyobinafsishwa zaidi. KR itaangazia kutambulisha pointi mpya za kuingia na kurudia maeneo yaliyopo kwenye programu na wavuti, kwa ushirikiano na timu ya kuchangisha pesa.
      • Tokeo muhimu WE3.3: Kuongeza ubakishaji wa wasomaji wanaomiliki akaunti kwenye programu na wavuti kwa 5% kufikia mwisho wa robo mwaka ya 4 ( Q4), kama inavyopimwa kupitia majaribio ya A/B
        • KR hii italenga kuboresha hali ya usomaji na ujifunzaji kwa wasomaji waliopo na wenye uzoefu, kwa lengo la kuhifadhi hadhira yetu ya sasa na kuimarisha muunganisho wao kwenye tovuti ili wapate kujifunza zaidi, na pia kuwa tayari na kuwa wazi kuchukua njia kuelekea mchango na uhariri. Kazi kwa eneo hili hapa italenga kuboresha hali ya usomaji kwenye wavuti na programu (maboresho ya usomaji, usogezaji bora na ugunduzi), pamoja na kuendeleza na kusisitiza kuhusu uratibu na matoleo yetu ya kuweka mapendeleo (Orodha za kusoma, mapendekezo yaliyobinafsishwa, historia ya mtumiaji na makala, n.k.)
      • Tokeo muhimu WE3.4: Kufikia mwisho wa robo tatu ya mwaka (Q3), tutasimika tovuti moja ya kache ndogo ambayo inakidhi ubora wetu wa sasa wa huduma na viwango vya usalama kulingana na uwekaji wetu wa sasa wa tovuti ya kache
        • KR hii italenga kuthibitisha dhana kwamba tunaweza kuboresha utendakazi wa tovuti na kupunguza muda wa kusubiri kwa wasomaji wetu kwa kurahisisha miundombinu yetu ya akiba na kuboresha michakato ya uwekaji wa tovuti ya kache kwa kupunguza muda wa awali wa utumaji kutoka takriban mwaka mmoja kwa wastani hadi robo kabisa. Lengo hapa litakuwa kukamilisha kurahisisha, kupeleka PoC, kufanya ukaguzi wa usalama na kukamilisha muhtasari wa uamuzi kuhusu kama kuendelea na kupeleka akiba zetu za kache kwa umma. Kupungua kwa muda wa kusubiri kunaweza kusababisha ongezeko lililothibitishwa la utazamaji wa kurasa na msingi wa wasomaji wa kijiografia zaidi.
      • Key result WE3.5: Improve donor identification —ensuring that all consenting logged-in readers can be identified by donor status for a personalized experience—by the end of Q4.
        • We will implement donor identification strategies to ensure that all consenting logged-in readers can be identified by donor status, enabling a more tailored and engaging experience. Donor identification efforts will be prioritized through Q4 to support more effective personalization and activation initiatives in the future.

Uaminifu & Usalama (WE4)

  • Lengo: Kukuza uwezo ulioimarishwa wa kuzuia matumizi mabaya ili kulinda miradi yetu dhidi ya vitisho vilivyoenea na vinavyolengwa huku tukiimarisha ulinzi wa faragha na usalama kwa watumiaji wetu. Jadili
    • Muktadha wa lengo: Baadhi ya vipengele vya uwezo wetu wa kupambana na matumizi mabaya vinahitaji kuboreshwa. Udhibiti wa unyanyasaji unaotegemea IP unapungua ufanisi wake, zana kadhaa za wasimamizi zinahitaji uboreshaji wa ufanisi, na tunahitaji kuweka pamoja mkakati mmoja unaotusaidia kukabiliana na matumizi mabaya yaliyokithiri kwa kutumia mawimbi mbalimbali na mbinu za kupunguza (captcha, blocks, n.k) kwa kukubaliana. Katika mwaka huu, tutaanza kufanya maendeleo juu ya shida kubwa zaidi katika nafasi hii. Zaidi ya hayo, uwekezaji huu katika ulinzi wa unyanyasaji unapaswa kusawazishwa na uwekezaji katika kuelewa na kuboresha afya ya jamii, vipengele kadhaa ambavyo vimejumuishwa katika mahitaji mbalimbali ya udhibiti.
      • Tokeo kuu la WE4.1: Kufikia Q4, tutakuwa na mfumo unaoweza kugundulika kwa urahisi, wa kuripoti matukio ya ndani ya muktadha uliowekwa kwenye miradi yetu yote.
        • Kuhakikisha usalama na ustawi wa mtumiaji ni jukumu la msingi la mfumo wetu. Mamlaka nyingi zina kanuni zinazohitaji mifumo ya mtandaoni kama yetu kufuatilia na kuchukua hatua dhidi ya unyanyasaji, unyanyasaji wa mtandaoni na maudhui mengine hatari kwenye mifumo yao. Kukosa kushughulikia haya kunaweza kuweka mifumo kwenye dhima ya kisheria na vikwazo vya udhibiti.
        • Tunataka kuwawezesha watumiaji wetu kuweza kuripoti vitisho mara moja vyenye madhara kupitia utaratibu wa kuripoti unaoweza kugundulika kwa urahisi na angavu ili kuhakikisha kuwa tunaweza kujifunza kuhusu matukio kama haya na kuchukua hatua za haraka inapobidi. Hii ni hatua ya kuwafanya watumiaji wetu kujisikia salama wanapochangia kwenye mfumo wetu. Tunafanya hivi kwa kutekeleza Mfumo wa Kuripoti Matukio kwenye wiki zetu.
      • Tokeo kuu la WE4.2: Kuboresha usahihi wa zana za kupinga matumizi mabaya, kama inavyopimwa kwa punguzo la X% la mwingiliano wa wito wa kuchukua hatua katika notisi ya zuio uhariri wa simu.
        • Tunataka kuboresha uwezo uliopo na kutoa zana mpya zinazowezesha uzuiaji sahihi zaidi na bora kwa watendaji wabaya. Njia moja ya kupima ufanisi wetu ni kwa kuangalia mwingiliano na kiungo cha "wito wa kuchukua hatua" ambacho kipo kwenye kiolesura cha kuhariri cha simu wakati mtumiaji amezuiwa. Dhana ni kwamba watumiaji wanaotumia kiungo hiki wana uwezekano mkubwa wa kujihusisha na kiungo kutokana na uharibifu wa dhamana kutoka kwenye vizuizi vya anuani ya IP. Ikiwa tutaona kupungua kwa idadi ya mwingiliano na kiunga cha wito wa kuchukua hatua, kuna uwezekano kuwa tunapunguza pia uharibifu wa dhamana kutoka kwa vizuizi vya IP. Kazi katika KR hii inahusisha mawimbi mapya/yaliyoboreshwa katika AbuseFilters, ugunduzi na upunguzaji wa mbinu za watu kujificha utambulisho wao na kupiga marufuku ukwepaji, kutoa taarifa kuhusu uwezekano wa uharibifu wa dhamana, kuimarisha ugunduzi wa roboti na ufanisi zaidi katika violesura vya zana za kuzuia matumizi mabaya.
      • Tokeo muhimu WE4.3: Kupunguza idadi ya mashambulizi makubwa ambayo yanahitaji uingiliaji wa binadamu wa SRE kwa 50% (ikilinganishwa na FY-na-FY)
        • Mabadiliko ya mandhari ya mtandao, ikiwa ni pamoja na kuongezeka kwa roboti za kiwango kikubwa na mashambulizi ya mara kwa mara zaidi yamefanya mbinu zetu za kijadi za kuzuia matumizi mabaya ya kiwango kikubwa kuwa za kizamani. Mashambulizi kama haya yanaweza kufanya tovuti zetu zisipatikane kwa kujaza miundombinu yetu na maombi, au kuzidi uwezo wa jumuiya yetu kupambana na uharibifu mkubwa. Hili pia linaleta doa lisilo na sababu kwa wahariri wetu wa mapendeleo ya juu na jumuiya yetu ya kiufundi.
        • Tunahitaji kwa haraka kuboresha uwezo wetu wa kugundua, kustahimili, na kupunguza au kukomesha mashambulizi kama hayo kiotomatiki.
        • Mwaka huu tutaangazia zaidi ugunduzi wa kiotomatiki wa anwani za IP na mitandao ambayo hujihusisha na mashambulizi ya mara kwa mara dhidi yetu, na kupunguza kiasi cha mzigo wa maingizo hatari ya mara kwa mara yanayowekwa kwenye mifumo yetu.
      • Tokeo kuu la WE4.4: Kufikia Q2, Akaunti za Muda zitakuwa zimewekwa kwa 100% ya miradi yetu ili uwazi wa taarifa zinazotambulika kibinafsi za wahariri wetu ambao hawajasajiliwa zinapatikana kwa chini ya 0.1% ya watumiaji waliojiandikisha.
        • Akaunti za muda zinalenga kuboresha faragha na hivyo basi, usalama wa wahariri wetu ambao hawajasajiliwa kwa kulinda taarifa zao za kibinafsi zinazoweza kuwatambulisha (anwani ya IP) ili zisionekane na umma na kuwawekea vikwazo wale wanaozihitaji kwa madhumuni ya doria pekee. Licha ya kuwa uboreshaji mkubwa wa usalama wa watumiaji, mradi huu pia ni muhimu kwa kuzingatia mahitaji mbalimbali ya udhibiti.
      • Tokeo Muhimu WE4.5: Kufanya na kuchapisha tathmini ya hatari na fursa ya AI kwa Uaminifu na Usalama, kubainisha vitisho na fursa zinazoweza kutokea, pamoja na mikakati inayopendekezwa ya kupunguza au kupitishwa kwa miradi ya Wikimedia.
        • AI inafanya maendeleo ya haraka kote kwenye Mtandao. Kuna fursa nyingi pamoja na vitisho vinavyoibuka na AI kuwa kila mahali. Kwa mfano, maudhui ni rahisi na ya bei nafuu kuzalisha, lakini kiasi ni ngumu zaidi. Vile vile, utafiti unaweza kufanywa kwa bidii kidogo lakini maono ya AI ni ngumu kutambua. Watu hubakia katikati ya AI kama chanzo cha habari lakini AI mara nyingi hukosa hatua kali za usalama.
        • Mradi huu unalenga kufanya tathmini ya athari za AI kwenye vipengele vya Uaminifu na Usalama vya mfumo ikolojia wa Wikimedia. Hii inaweza kujumuisha:
          • Kuchapisha tathmini ya athari ya AI
          • Utambuzi wa fursa za bidhaa
          • Kubainisha miundo tunayoweza kutumia na kutengeneza mpango wa kuziunganisha

Responsible Use of Infrastructure (WE5)

  • Objective: Developers and reusers access knowledge content in curated pathways, ensuring the sustainability of our infrastructure and responsible content reuse. Jadili
    • Objective context: This objective will focus on establishing pathways for responsible content reuse.
    • Wikimedia hosts the largest collection of human-curated knowledge on the web. This has made our knowledge infrastructure an invaluable destination not just for humans, but also for automatic data consumers. Our content feeds into search engines, social media platforms, ecommerce, and ever since the rise of AI, is used to train large machine learning models. Consumers source data by scraping pages, using the APIs, and downloading content – commonly without attribution. In the world of unauthenticated traffic we can’t reliably differentiate one user from another, which greatly limits our ability to enable and enforce responsible use of our infrastructure: How can we continue to enable our community, while also putting boundaries around automatic content consumption? How might we funnel users into preferred, supported channels? What guidance do we need to incentivise responsible content reuse? How can we drive towards a cohesive developer experience, and build products that meet the needs of volunteer developers, staff and reusers alike? While these questions are not all new, the urgency of addressing these has grown exponentially: Since 2024 we’re observing a dramatic rise in request volume, with most of the increase coming from scraping bots collecting training data for AI-powered workflows and products. The load on our infrastructure is not sustainable and puts human access to knowledge at risk: We need to act now to re-establish a healthy balance, so we can effectively support the Wikimedia projects and enable the sustained success of our mission.
      • Key result WE5.1: By the end of Q4, 50% of requests to programmatic access channels can be attributed to a known developer or application, enabling us to increase the sustainability of our infrastructure and prevent abuse.
        • We currently have limited ways to identify who is responsible for automated traffic and, unlike on-wiki, limited ways to contact users or regulate their access. We have seen a significant increase in the volume of external automated traffic, which is not sustainable for us and puts human access to knowledge at risk. We aim to increase the percentage of automated traffic that is attributed to a known account, by requiring authentication and authorization based on tiered levels of access for high volume scraping and API use. This will help us to identify who is reusing content at scale, enabling us to protect our infrastructure and improve governance around fair use, whilst more effectively meeting their needs. We will also explore how to better support the technical community with a more cohesive developer experience that protects preferential access for community members and enables new functionality for developers.
      • Key result WE5.2: By the end of Q4 2025, 70% of Wikimedia web API endpoints will be supported by common infrastructure that enables us to provide a more consistent developer experience, reduce developer burden, and improve approachability of Wikimedia web API experiences.
        • We aim to improve the experience and sustainability of our developer pathways by offering more consistent, stable, and discoverable web APIs for all Wikimedia developers. We will simplify our API offerings by introducing more centralized infrastructure for core API capabilities, allowing us to have consistent pathways and governance for: OpenAPI specs and documentation, developer identification and access controls, API policy enforcement, routing, versioning, and error handling. By streamlining our API offerings, we will make it faster, easier, and more delightful to build tools, bots, research projects, and features that serve the Wikimedia mission. This approach supports the multi-generational future of the mission by reducing API infrastructure maintenance costs, increasing visibility and access control for combating bad actors, and fostering a stronger developer community.
      • Key result WE5.3: By the end of Q4, new attribution guidelines for web, apps, voice assistants, and LLMs will be published and linked across Wikimedia sites, with at least two reuse demos deployed that drive measurable engagement (e.g., X% clickthrough rate to guidance), and at least one external reuse partner adopting best-practice attribution.
        • To increase proper attribution of Wikimedia content, we will provide clear best-practice guidance that promotes responsible reuse. This includes creating attribution guidelines for key platforms (web, apps, voice, multimedia) and showcasing at least two practical examples highlighting exemplary applications of Wikimedia content. Examples of outputs include encouraging media organisations to credit Wikimedia Commons images, search engines to surface relevant Wikimedia data more effectively, or AI assistants to integrate Wikipedia knowledge in transparent and responsible ways that increases trust in their reliability. Strengthening attribution practices not only increases public awareness and drives engagement back to Wikimedia projects, but also helps establish responsible and novel ways of remixing knowledge, and deterring misuse.
      • Key result WE5.4: Reduce the amount of traffic generated by scrapers by 20% when measured in terms of request rate, and by 30% in terms of bandwidth
        • Scraping has always been here: the search engines have relied on Wikipedia to provide information to their users for decades; however lately there’s another big motivation to scrape our data: it’s the largest curated, multilingual set of knowledge content you can find on the internet and it’s a fundamental tool to train large language models. This is true both for our encyclopedic content and our multimedia repository, Wikimedia Commons, which is invaluable for machine learning models that generate images.
        • As a consequence, over the past year, we saw a significant increase in the amount of scraper traffic, and also of related site-stability incidents: Site Reliability Engineers have had to enforce on a case-by-case basis rate limiting or banning of crawlers repeatedly to protect our infrastructure. Scraping has become so prominent that our outgoing bandwidth has increased by 50% in 2024. What's more, a recent analysis showed that at least 65% of our most expensive requests (the ones that we can’t serve from our caching servers and which are served from the main databases instead) are performed by bots.
        • Our computing resources are extremely limited compared to the amount of traffic we make, so we have to prioritize who we serve with those resources, and we want to favour human consumption, and prioritize supporting the Wikimedia projects and contributors with our scarce resources.

Accelerate Path to Product Outcomes (WE6)

  • Objective: Wikimedia developers quickly and confidently get their products out to end users. Jadili
    • Objective context: To be effective in achieving the 4 strategic pillars, Wikimedia developers need to be spending their time and effort on high-leverage activities that result in delivering quality products as early as possible. Overly complicated workflows, lack of standard tooling, and unsustainable system components get in the way of those outcomes.
    • This work builds on the momentum we've picked up the last 2 annual plans evolving MediaWiki as a platform and the software supporting its development and deployment. The work for this year will focus on providing more reliable developer environments, simplifying pre-production workflows, and reducing platform and infrastructure risks.
      • Key result WE6.1: By the end of Q4, the number of train-blocking bugs that make it beyond test wikis is reduced by 10%
        • In 2024, there were 144 times developers had to revisit work because there was an emergency preventing the deployment of MediaWiki. In many of those cases, the bugs were caught after deploying to testwikis, meaning the issue reached a potential audience of billions of users. We can't control the fact that bugs will exist, but catching them earlier would mean less hero work is needed. It would also build up confidence in developers that when something goes to real production, there won't be a fire.
        • We will catch these bugs earlier by providing environments needed by developers to confidently deliver and test their code throughout the development and deployment lifecycle. We also need to ensure that these improvements do not come at the cost of developer velocity.
      • Key result WE6.2: By end of Q4, 4 steps from the production readiness review checklist can be executed without SRE intervention
        • Getting a new service or feature deployed in production currently depends on a list of 24 steps for which each step typically needs support from SREs. We established the SRE ambassador program to intervene earlier in the development cycle and build up capacity within the development teams themselves, but many of the tasks should be entirely self-serviceable. Currently, this amounts to work that is manual, repetitive, automatable, and that scales linearly with the number of development teams. This is not sustainable for the SRE team in the long run.
        • In the past, much of this work was abstracted from development teams by maintaining a set of shared common libraries and best practices to interact with our platform. These were abandoned when we moved to our new Kubernetes infrastructure and do not have a direct replacement. By providing similar libraries, documentation, and training that apply to the way we build and deploy things today, we believe we can reduce the amount of involvement needed from SRE before deploying a new service or feature to production.
      • Key result WE6.3: By end of Q4, 100% of Wikipedia page views are served through Parsoid
        • Parsoid offers enhanced capabilities for wikitext evolution and future-proofing the platform. Maintaining two parsers concurrently is not sustainable in the long term, as it increases technical debt and complexity. Additionally, the success of some new projects like Wikifunctions depends on Parsoid being widely available.
        • We have been scaling up the rollout to smaller projects and this year we will be ready for the Wikipedias. Serving all Wikipedia page view reads through Parsoid is the most important next milestone. In addition to the rollout itself, this work also includes resolving performance issues and communicating effectively about the impact to readers and editors.
      • Key result WE6.4: By end of Q2, at least two identified risks that threaten our ability to continue deploying or scaling the wikis have been mitigated or reduced to an acceptable level
        • Through a few targeted initiatives, we will reduce or mitigate several scalability, reliability, or security risks that we have identified as a likely potential threat to the growth and sustainability of our platform and our public projects.
        • For example, we will be refactoring the structure of the core databases of Commons to ensure its growth will not be limited by the capacity of available server hardware within the next few years. We will also be upgrading PHP, the programming language powering MediaWiki and related services, to a more modern version. Other risks identified will likely require implementing additional security measures to protect and harden of our infrastructure.

Ishara na Huduma za Data (SDS)

Vipimo (SDS1)

  • Lengo:Watoa maamuzi hutumia zaidi inayoaminika na data ya trafiki ya binadamu na roboti kwa wakati ili kufahamisha bidhaa na maamuzi ya kimkakati. Jadili
    • Muktadha wa lengo: Kuongezeka kwa trafiki otomatiki katika miaka michache iliyopita kumeshusha imani yetu katika vipimo vya trafiki. Kwa kuongeza, masuala mengi ya data yamejitokeza, na muda wa kutambua na kutatua ni mkubwa sana. Masuala haya hupunguza kasi na kupunguza uwezo wetu wa kutathmini mifumo ya trafiki ya binadamu na roboti, ambayo ni nyenzo muhimu kwa kupanga na maamuzi ya bidhaa.
    • Kwa mwaka wa fedha FY25-26, tutaangazia vipimo vyetu vya trafiki kama mfano wa kusuluhisha mapengo ya ubora wa data katika mabomba yetu ya sasa, kuweka miundombinu na michakato ya ufuatiliaji na kutatua masuala ya ubora wa data, na kutoa zana zinazowawezesha watoa maamuzi kuelewa mitindo kuhusu trafiki ya binadamu na otomatiki.
    • One use case is about how we measure human and bot traffic. The rise of automated traffic in the past couple of years has made it harder to understand the extent to which humans are interacting with and contributing to Wikimedia projects. We aim to improve our ability to evaluate human and bot traffic patterns, which are critical inputs for planning and product decisions.
      • Tokeo kuu la SDS1.1: Kufikia mwisho wa Q1, wachambuzi wanaotumia vipimo vya mwonekano wa ukurasa wanaweza kufikia hatua za kimsingi za ubora wa data na utambuzi wa trafiki kiotomatiki
        • Kupitia dhana zilizogunduliwa katika KR hii, tunalenga kutambua mapungufu katika mbinu zetu za sasa za ugunduzi wa kiotomatiki wa trafiki na kuelewa pale zinaposhindwa kuainisha vizuri trafiki ya kutazama ukurasa. Maarifa haya yataarifu uboreshaji wa njia zinazozalisha na kuainisha vipimo vya mwonekano wa kurasa. Zaidi ya hayo, tutafafanua vipimo vya ubora wa data ili kufuatilia na kupima uboreshaji wa usahihi wa data.
        • KR hii itaweka msingi wa ufuatiliaji wa KR (KR2) unaolenga kutekeleza uboreshaji wa mambo yaliyobainishwa hapa. Vipimo vya ubora wa data vilivyoanzishwa katika awamu hii vitatumika kama vigezo vya kutathmini ufanisi wa maboresho hayo ya siku zijazo.
      • Key result SDS1.2: By the end of Q2, all 6 data pipelines dependent on the wikitext history data set will have weekly delivery guarantees (SLOs) for the wikitext history input sources.
        • The goal of FY24/25 KR 1.4 has been to remove the dependency on the monthly updated mediawiki_wikitext_history and mediawiki_wikitext_history_current data sets for the 3 most relevant downstream pipelines and to provide an alternative data set with guaranteed weekly SLOs.
        • While FY24/25 KR 1.4 helped mitigate the reliability issues for the most relevant dependent pipelines, there are remaining pipelines left with the unreliable legacy input source. These should be migrated too as well as the file based input source to the wikitext history data set itself.

Jukwaa la Majaribio (SDS2)

  • Lengo: Wasimamizi wa bidhaa wanaweza kutathmini kwa haraka, kwa urahisi na kwa uhakika athari za mabadiliko ya kipengele cha bidhaa katika Wikipedia. Jadili
    • Muktadha wa lengo: Ili kuwezesha na kuharakisha kufanya maamuzi kwa ufahamu wa data kuhusu uundaji wa vipengele vya bidhaa, wasimamizi wa bidhaa wanahitaji jukwaa la majaribio ambapo wanaweza kufafanua vipengele, kuchagua hadhira ya kimatibabu ya watumiaji, na kuona vipimo vya athari. Kuharakisha muda kutoka kwenye uzinduzi hadi uchanganuzi ni muhimu, kwani kufupisha ratiba ya kujifunza kutaharakisha majaribio, na hatimaye, uvumbuzi. Kazi za mwongozo na mbinu zilizopangwa za kipimo zimetambuliwa kama vizuizi vya kasi. Hali inayofaa ni kwamba wasimamizi wa bidhaa wanaweza kupata kutoka kwa uzinduzi wa majaribio hadi ugunduzi kwa uingiliaji mdogo au bila uingiliaji wa mikono kutoka kwa wahandisi na wachambuzi.
    • Tunaangazia Wikipedia kwa mwaka ujao wa fedha kwa sababu hapo ndipo Uzoefu wa Msingi una nia ya majaribio (mkakati wa shirika unatufanya tuongezeke maradufu kwenye Wikipedia), na kwa sababu huturuhusu kuangazia na kuashiria kwa uwazi zaidi timu na miradi gani tunashirikiana nayo. Timu nyingine zimetumia vipengele vya mfumo wa majaribio na huenda zikaendelea kufanya hivyo, lakini matumizi hayo hayatakuwa kipaumbele katika lengo hili.
      • Tokeo kuu la SDS2.1: Kufikia mwisho wa Q2, kupunguza muda unaomchukua meneja wa bidhaa kufanya jaribio la A/B la aina mbili kwa kipengele cha msomaji kwenye Wikipedia hadi chini ya wiki 6 (bila kujumuisha muda wa ukusanyaji wa data).
        • Kwa sasa, wasimamizi wa bidhaa wanakabiliwa na mzunguko wa majaribio wa wiki 10+ - kutoka kwa dhana hadi matokeo, bila kujumuisha muda wa majaribio - kwa sababu ya utegemezi wa wachanganuzi na wahandisi, michakato inayofanyika kwa mikono na masuala ya uaminifu wa data. Vitegemezi hivi huchelewesha kujifunza, kurudia, na uvumbuzi. Msimamizi wa bidhaa aliyeimarishwa na kuelimishwa kuhusu uwezo wa kujihudumia wa jukwaa letu ataweza kufanya uamuzi wa bidhaa kwa ujasiri kutokana na data inayoaminika katika muda wa chini ya wiki 6 (bila kujumuisha utekelezaji wa matibabu na muda wa kukusanya data).

Hadhira za Baadaye (FA)

Hadhira za Baadaye (FA1)

  • Lengo: Shirika la Wikimedia Foundation limetayarishwa na mapendekezo kuhusu uwekezaji wa kimkakati wa kufuata ili kusaidia harakati zetu kuhudumia hadhira mpya katika mtandao unaobadilika. Jadili
    • Muktadha wa lengo: Kutokana na mabadiliko yanayoendelea katika teknolojia na tabia ya mtumiaji mtandaoni (k.m., kuongeza kwa upendeleo wa kupata ujuzi kupitia programu za kijamii, umaarufu wa uboreshaji wa video fupi, kuongezeka kwa AI ya uzalishaji), harakati za Wikimedia zinakabiliwa na changamoto katika kuvutia na kuhifadhi wasomaji na wachangiaji. Mabadiliko haya pia huleta fursa za kuhudumia hadhira mpya kwa kuunda na kutoa taarifa kwa njia mpya. Hata hivyo, sisi kama harakati hatuna picha wazi iliyo na data ya manufaa na mabadiliko ya mikakati tofauti tunayoweza kufuata ili kushinda changamoto au kuchangamkia fursa mpya. Kwa mfano, tunapaswa...
      • Je, ungependa kuwekeza katika vipengele vipya vikubwa kama vile vikaragosi(chatbots?)
      • Je, ungependa kupeleka maarifa na njia za Wikimedia za kuchangia kwenye majukwaa maarufu ya watu wengine?
      • Kitu kingine?
    • Ili kuhakikisha kuwa Wikimedia inakuwa mradi wa vizazi vingi, tutajaribu dhahania ili kuelewa vyema na kupendekeza mikakati yenye mwelekeo chanya - kwa Shirika la Wikimedia Foundation na harakati za Wikimedia - kufuata ili kuvutia na kuhifadhi hadhira ya siku zijazo.
      • Tokeo muhimu FA1.1: Kutokana na maarifa na mapendekezo ya majaribio ya Hadhira ya Baadaye, kufikia mwisho wa Q3 angalau lengo moja au tokeo moja kuu linalomilikiwa na timu ya Wasio na mtazamo wa siku zijazo litakuwepo katika rasimu ya mpango wa mwaka unaofuata.
        • Tangu 2020, Shirika la Wikimedia Foundation limekuwa likifuatilia mitindo ya nje ambayo inaweza kuathiri uwezo wetu wa kuhudumia vizazi vijavyo vya watumiaji-maarifa na wachangiaji-maarifa na kubaki kuwa harakati ya maarifa bila malipo kwa vizazi vijavyo. Hadhira ya baadaye, timu ndogo ya R&D, ita:
          • Kufanya majaribio ya haraka na ya muda (yakilenga angalau majaribio 3 kwa mwaka wa fedha) ili kuchunguza njia za kushughulikia mienendo hii.
          • Kulingana na maarifa kutoka kwenye majaribio, toa mapendekezo kwa uwekezaji mpya usio wa majaribio ambao WMF inapaswa kufuata - yaani, bidhaa au programu mpya zinazohitaji kutekelezwa na timu kamili au timu - katika kipindi chetu cha kawaida cha kupanga kila mwaka.
        • Matokeo haya muhimu yatatimizwa ikiwa angalau lengo moja au matokeo muhimu ambayo yanamilikiwa na timu nje ya Hadhira ya Baadaye na yanaendeshwa na pendekezo la Hadhira ya Baadaye yataonekana katika rasimu ya mpango wa kila mwaka wa mwaka wa fedha unaofuata.

Video ya kijamii (FA2)

  • Lengo: Vijana (<25-umri wa miaka) watu wanapenda, kujifunza kutoka kwenye majukwaa, kujihusisha na, na kushirikisha maudhui ya Wikipedia kwenye majukwaa ambapo wanapenda kutumia muda mtandaoni. Jadili
    • Muktadha wa Malengo: Majaribio ya Hadhira ya Baadaye ya video fupi mwaka huu wa fedha yameonyesha kuwa tunaweza kufikia hadhira changa kwa kiwango kikubwa kwenye mifumo hii, lakini data yetu ya Afya ya Biashara inaonyesha kuwa uwekezaji wetu wa sasa hautoshi kukabiliana na kupungua kwa ufahamu na uhusiano na Wikipedia kati ya hadhira ya Gen-Z.
    • Ili kuhakikisha kwamba tunakifikia na kushirikisha kizazi hiki ipasavyo, tunaamini kwamba tutahitaji kujihusisha katika mbinu mbalimbali, na kuongeza kwa kiasi kikubwa ushiriki wetu katika maeneo kama vile masoko na ushawishi wa kulipia, kampeni za ubunifu, kuitikia mitindo na kuongeza kiwango chetu cha majaribio kwenye njia hizi.
    • Tunatarajia kuwa changamoto tunazokabiliana nazo zitahitaji uwekezaji mkubwa zaidi ili kutusaidia kuzishinda, hasa katika juhudi za Mawasiliano na Masoko ili kuanzisha ushirikiano, pamoja na ushirikiano wa idara mbalimbali katika kuunda bidhaa na uzoefu mpya unaolenga kuongeza uwepo wa chapa na maudhui ya Wikipedia kwenye mifumo hii.
      • Key result FA2.1: Generate 5,000,000 views from short-form video content across all owned channels by the end of H1.
        • This year, we achieved a reach of approximately 1 million views within 3 months of launching short videos on the @Wikipedia channels on TikTok, Instagram, and YouTube. By the start of next fiscal year, we expect more followers on our owned channels and more insights into effective/engaging content that we can put into practice to reach even more viewers.
        • By setting an ambitious goal in the first half of the year, we hope to drive toward more significant impact, allow for the creation of new strategies/processes to facilitate the work, and be able to advocate for additional resources to meet this goal.
      • Key result FA2.2: Iterating on actual views baseline achieved at the end of H1, by the end of H2 achieve a 10% increase on views achieved in H1.
        • While we are aiming for 5 million views in the first half of the year, we may land significantly above or below this initial goal. In the second half of the year, we will have an actual (vs the projected goal of 5 million) baseline, more learning about effective strategies/resourcing needs, so we expect to be able to improve on this initial baseline.
      • Key result FA2.3: Launch a product off-platform aimed at future audiences' new methods of learning/media consumption and bring it to market through a collaborated product branding and marketing campaign.
        • Future Audiences typically works on small-scale experiments with minimal/organic marketing. This year, we would like to reserve time for a more scaled-up new product + marketing campaign targeting younger audiences off-platform.

Bidhaa & Usaidizi wa Kiuhandisi (PES)

Bidhaa & Uhandisi wa Bidhaa(PES1)

  • Objective: WMF Product and Engineering teams are more effective due to improved processes, fostering a positive shift in our culture. Jadili
    • Objective context: This objective is about making The Wikimedia Foundation’s ways of work faster, smarter, and better. It’s all about how we work. This means less friction and obstacles (inefficiencies and errors) in processes, and achieving impact quicker. This Objective is also about learning ways of work that can be adopted across the department and organization.
      • Key result PES1.1: By end of Q2, define SLOs for 6 production services based on a prioritization rubric that aims to maximise our learning of how to define and use SLOs to make informed decisions regarding prioritization of reliability related work by stakeholder teams.
        • A Service Level Objective (SLO) is an agreement between stakeholder teams on a target level of service (reliability/performance) that teams collaborate to meet (and not greatly exceed). For example, it helps determine when reliability or performance work should to be prioritized or deprioritized by a development team, or what constitutes a problem. Teams need to care about identifying what is immediate (alerting/incident response/critical bugs) versus what isn’t. The goal is to reduce friction across functions by negotiating targets and informing shared and clear prioritization.
      • Key result PES1.2: 80% of Wishlist-based requests submitted during Q1 and Q2 receive an initial response within 14 days, resulting in a status change.
        • We learned in FY2024-5 that wishes can inform strategic work (via focus areas), and that processing and evaluating wishes is a collaborative effort. We also learned we can streamline how we process wishes as a foundation, and that we need to better communicate the status and foundation's position on any given wish.
        • In this KR, we will run experiments to improve the speed and efficiency of processing wishes, increase the number of foundation staff evaluating and commenting on wishes (with less effort), and experiment with frameworks to evaluate wishes against agreed-upon product goals. Additionally, we want to experiment with targeted wishlist brainstorming, where community-led ideas align to team and product goals. Finally, we will evaluate and measure community sentiment of the wishlist.
      • Key result PES1.3: Two early-stage cross-departmental experiments, validated by our external consumer, donor, and contributor audiences, are incorporated by the Foundation into the annual plan.
        • This work is about creating experiments and experimentation processes for adoption across our organization.
        • The Foundation strengthens a culture of cross-departmental experimentation by incorporating two validated, early-stage experiments into its annual planning. This initiative fosters collaboration beyond the Product & Technology department feature teams, encouraging more innovation with other departments in the organization (such as Communications and Advancement). By seeding untested newer ideas and streamlining processes for experimentation, teams enhance productivity and scale impact. Success is measured by completing two cross-departmental experiments per year, integrating them into future OKR work, and increasing adoption of experimentation practices. Examples of outputs are new prototypes to increase new editors’ growth and productivity, to experimental features that deepen reader and donor connection to Wikipedia. One specific opportunity identified is connecting small feature explorations to celebrate Wikipedia’s 25th birthday.

Kupanga Pamoja (Januari 2025)

January 2025 update.

Portrait of Selena

Mpango wa Mwaka ni maelezo ya Wikimedia Foundation ya kile tunachotarajia kufikia katika mwaka ujao.Tunafanya kazi kwa bidii ili kufanya mpango kuwa shirikishi, wenye matamanio na kufanikishwa. Kila mwaka, tunawaomba wachangiaji kutoa mitazamo yao, matumaini na maombi mahususi tunapounda mpango. Baadhi ya njia tunazotafuta maoni ni kupitia mazungumzo ya timu ya bidhaa na jumuiya, Orodha ya Matamanio ya Jumuiya, mazungumzo ya jumuiya kama vile mfululizo wa mazungumzo ya Commons, kwenye mikutano, na kupitia kurasa za wiki kama huu.

Kwa mpango wetu ujao wa mwaka, kuanzia Julai 2025 hadi Juni 2026, tunafikiria jinsi tunavyoweza kutumikia vyema maono ya vizazi vingi, ukizingatia mabadiliko ya haraka katika dunia na mtandao na jinsi hiyo inavyoathiri dhamira yetu ya maarifa huria.

Kama nilivyosema mwaka jana, tunahitaji kuangazia kile kinachotutofautisha: uwezo wetu wa kutoa maudhui ya kuaminika hata kama taarifa potofu na mbaya zinapoenea kwenye mtandao na kwenye majukwaa yanayoshindania umakini wa vizazi vipya. Hii ni pamoja na kuhakikisha tunafanikisha dhamira ya kukusanya na kutoa jumla ya maarifa yote ya binadamu kwa ulimwengu kwa kupanua wigo wetu wa taarifa zinazokosekana, ambazo zinaweza kusababishwa na ukosefu wa usawa, ubaguzi na upendeleo. Maudhui yetu yanahitaji pia kutumika na kubaki kuwa muhimu katika mabadiliko ya intaneti yanayoendeshwa na akili mnemba na uzoefu tele. Na hatimaye, tunahitaji kutafuta njia za kufadhili harakati zetu kwa uendelevu kwa kujenga mkakati wa pamoja wa bidhaa zetu na kukusanya pesa ili tuweze kusaidia kazi hii kwa muda mrefu.

Ili kufanya chaguo na maelewano kuhusu mahali pa kuelekeza juhudi zetu katika mwaka ujao, tulikusanya maswali pamoja na kufikiria jinsi ya kutenga rasilimali zetu zenye kikomo ili kupata matokeo makubwa zaidi.

Ikiwa una nia mahususi katika sifa au huduma ambazo idara ya Bidhaa na Teknolojia itaunda kulingana na vipaumbele vilivyowekwa hapa, kutakuwa na wakati Machi wa kutoa maoni kuhusu malengo mahususi na matokeo muhimu. (Haya hapa ni malengo na matokeo muhimu ya mpango wa sasa wa mwaka, kwa marejeo.)

Iwapo ungependa kufikiria kuhusu changamoto na fursa katika mazingira yetu ya kiufundi na mwelekeo tunaopaswa kuweka katika mpango ujao wa mwaka, tafadhali zingatia maswali yaliyo hapa chini pamoja nasi.

Tunaendelea kupokea taarifa kuhusu maswali haya kwa njia nyingi -- kutoka mazungumzo ya jumuiya, data tunazokusanya, mahojiano ya utafiti tunayofanya, na zaidi. Hii si mara ya kwanza tunauliza na kujifunza kuhusu mengi ya mambo haya–na tayari tumekuwa tukifanya kazi karibu na wengi wao! Tunataka kuwauliza tena sasa na kuendelea kujifunza, kwasababu ni wa umuhimu kwetu katika hatua hii ya upangaji wetu.

Maswali:

  • Vipimo na data
    • Ni njia zipi ambazo data na vipimo vinaweza kusaidia vyema kazi yenu kama wahariri? Unaweza kufikiria data kuhusu kuhariri, kusoma, au kupanga ambazo zingeweza kukusaidia kuchagua jinsi ya kutumia wakati wako, au wakati jambo fulani linahitaji kushughulikiwa? Hii inaweza kuwa data kuhusu shughuli yako mwenyewe au shughuli za wengine.
  • Uhariri
    • Ni wakati gani ambapo kuhariri kunakufaa zaidi na kukufurahisha? Ni wakati gani inakatisha tamaa na ngumu zaidi?
    • Tunataka wachangiaji wapokee maoni zaidi na kutambuliwa kwa kazi zao, ili isionekane kama hakuna mtu anayetambua juhudi wanazotumia kwenye wiki. Ni aina gani ya maoni na utambuzi yanayokupa hamasa? Ni nini kinachokugusa uendelee kuhariri?
    • Kwa sababu wiki ni kubwa sana, inaweza kuwa vigumu kwa wahariri kuamua ni kazi gani ya wiki ni muhimu zaidi kwao kutumia muda wao kila siku. Ni habari au zana gani zinaweza kukusaidia kuchagua jinsi ya kutumia wakati wako? Je, ingeweza saidia kuwa na sehemu kuu, ya binafsi ambayo inakuruhusu kupata fursa mpya, kudhibiti kazi zako na kuelewa matokeo yako?
    • Tunataka kuboresha uzoefu wa ushirikiano kwenye wiki, ili iwe rahisi kwa wachangiaji kutafutana na kufanya miradi pamoja, iwe ni kupitia hifadhi rudufu, warsha za hariri, Miradi ya Wiki, au hata wahariri wawili wanaofanya kazi pamoja. Unafikiri tunaweza kuwasaidia vipi wachangiaji zaidi kutafutana, kuunganika na kufanya kazi pamoja?
  • Kusoma/Kujifunza
    • Wiki hupakia haraka au polepole kulingana na mahali ambapo watu wanaishi ulimwenguni. Je, kuna sehemu yoyote duniani ambapo unafikiri kwamba utendakazi ulioboreshwa unahitajika zaidi?
    • Tunawezaje kusaidia vizazi vipya vya wasomaji kupata maudhui ya Wikipedia ya kuvutia na shirikishi? Tumejadili mawazo kuhusu maudhui na video zenye mwingiliano hapo awali, na katika mwaka huu tumeangazia kwenye chati na kwenye kujaribu njia mpya za kuibua yaliyomo kwenye Wikipedia. Je, tunawezaje kuendelea na mwendo huu ili kutumia maudhui yetu yaliyopo kwa njia mpya ambazo ni za kipekee kwa Wikimedia?
  • Wasimamizi
    • Ni nini kinachoweza kuhitaji kubadilishwa kuhusu Wikipedia ili watu wengi zaidi watake kujihusisha katika majukumu ya juu ya kujitolea, kama vile wafanya doria au wakabidhi?
    • Ni taarifa au muktadha gani kuhusu hariri au watumiaji unaweza kukusaidia kufanya doria au maamuzi ya mkabidhi kwa haraka au kwa urahisi zaidi?
  • Mitindo ya Nje
    • Ni mabadiliko gani muhimu zaidi unayoona duniani nje ya Wikimedia? Hizi zinaweza kuwa mitindo ya teknolojia, elimu, au jinsi watu wanavyojifunza.
    • Nje ya harakati za Wikimedia, ni jumuiya gani nyingine za mtandaoni unazoshiriki? Tunaweza kujifunza nini kutoka kwenye zana na michakato kwenye majukwaa mengine ya jumuiya?
    • Unatumia vipi zana za AI ndani na nje ya kazi yako ya Wikimedia? Je, unaona AI inakufaa kwa nini?
  • Commons
    • Ni maamuzi gani tunaweza kufanya na jumuiya ya Commons ili kuunda mradi endelevu unaosaidia kuunda maarifa ya ensaiklopidia?
  • Wikidata
    • Ungependa kuona Wikidata inakua vipi katika siku zijazo? Je, inawezaje kuwa muhimu zaidi kwa ajili ya kujenga maudhui ya ensaiklopidia ya kuaminika?

–– Selena Deckelmann

Retrieved from "https://meta.wikimedia.org/w/index.php?title=Wikimedia_Foundation_Annual_Plan/2025-2026/Product_%26_Technology_OKRs/sw&oldid=28604962"