Making Easy Ways for New Technical Contributors
My Journey as a Speaker at Wikimania 2025
Wikimania 2025 was a landmark moment for me. For the first time, I delivered a technical session in front of a global audience. My talk focused on simplifying the onboarding process for new contributors who struggle to understand Wikimedia’s large and complex codebases. This blog captures the journey that led to the session, the motivation behind it, the challenges I observed, and how the final talk came together.

Where It Started
Understanding the Real Problem for New Developers
When I began contributing to MediaWiki and Wikimedia projects in 2024, I faced the same challenge as many newcomers. The codebases were huge and the architecture was not easy to understand. Moving between APIs, reading old patches, browsing commit histories, and following interconnected tasks often turned into day long rabbit holes.

During cohort training and workshops I hosted as Technical Head of Wiki Club SATI, I observed that many new contributors were confused for days simply trying to understand the structure of the code. The problem was not a lack of skill. The problem was the absence of a clear and visual explanation of how the system actually works.
This gap became the foundation for my Wikimania proposal.
The Idea Behind My Session
A Visual Approach to Understanding Codebases
My talk introduced a solution that focused on generating visual diagrams from Wikimedia codebases. Instead of reading thousands of lines of code or moving between pages of documentation, contributors could instead view the architecture as a set of organized diagrams.
I proposed two key visual formats.
Data Flow Diagrams A structured flow explaining how data moves inside MediaWiki and its components.
Relational Diagrams A map that shows how tasks, modules, files, and contributors are connected across the project.
Visuals help even experienced developers. So for newcomers, the benefit becomes even stronger.
My objective was simple. Reduce the time required to understand a codebase and help contributors make meaningful contributions with confidence.

Preparing for the Session
The Support and Guidance That Shaped the Talk
I prepared the entire session with the same approach I follow while mentoring. Keep the content clear, practical, and focused on solving real developer pain points. During this period I also received feedback from seniors in the community, including guidance that helped me refine the problem statement and align my session with the broader theme of Wikimania.
Elena, who played an important leadership role in the program team, encouraged clarity, accessibility, and impact in technical sessions. That guidance helped shape the tone of the presentation and ensured that the session aligned with inclusivity and sustainability.
This preparation process allowed me to convert my raw idea into a structured talk that would be valuable for both newcomers and experienced developers.
Delivering the Session
From Concept to the Wikimania Stage
When the session began, the focus was not only on the problem but also on demonstrating working ideas. I walked through the challenges of understanding codebases, explained why contributors struggle during their first weeks, and demonstrated how diagrams can transform learning.
I used real examples and showed the tool concept in different levels of detail. The audience was able to see how these diagrams can reduce confusion, cut the onboarding time, and make pull request cycles smoother.
The response was encouraging. Many participants appreciated the practical approach and the fact that this solution directly supports inclusivity and long term sustainability in the contributor pipeline.
How the Session Connects to the Theme of Wikimania
Inclusivity. Impact. Sustainability.
Inclusivity Visual diagrams allow contributors with limited coding experience to understand the architecture. It reduces the fear of entering large projects.
Impact Faster onboarding reduces delays and makes the contributor journey smoother. Contributors start contributing meaningful patches earlier.
Sustainability Better onboarding increases long term contributor retention. A consistent flow of new developers ensures future growth for Wikimedia technology.
This was exactly what the session aimed to strengthen.
After the Talk
How It Changed My Contribution Journey
Delivering at Wikimania gave me a clearer understanding of global needs. Many developers across regions face the same onboarding challenges. The session helped me refine the direction for my upcoming work on contributor tools, including automation, visualizations, and workflows that simplify learning.
It also strengthened my interest in mentoring and supporting new contributors because the impact is immediate and visible.

What Comes Next
Turning the Concept Into a Fully Working Tool
My next focus is to complete the first working version of the diagram generator. This includes data extraction, automated visualization and support for multiple Wikimedia codebases. I plan to collaborate with maintainers and mentors to build a deployable version that the global community can use.
Closing Thoughts
Why This Session Matters
Speaking at Wikimania was more than presenting a topic. It was about contributing to a long term solution that will help hundreds of newcomers start their journey with less confusion and more confidence.
The future of Wikimedia technical contributions depends on how easily new developers can begin contributing. I aim to continue building tools, documentation, and learning pathways that support this goal.
Proposal Link: https://wikimedia.eventyay.com/talk/wikimania2025/talk/QTCMYK/
Presentation Link: https://commons.wikimedia.org/wiki/File:WIKIMANIA_Day_3_Kisumu_-_Making_easy_ways_for_new_technical_contributors.webm
