Technical spaces within the Wikimedia movement remain heavily skewed toward male contributors, with the 2025 Developer Survey reporting that 74% of respondents identify as men compared to just 7% as women. To address this, facilitators Silvia Gutiérrez, Carla Toro, and Giovanna Fontenelle recently synthesized insights from a 2026 Wikimedia Hackathon session to identify specific barriers preventing women+ from participating in technical development and outlined actionable strategies to foster a more inclusive environment.
Barriers to Entry: Moving Beyond the “Genius” Myth
The primary challenge identified by participants in the “Sharing Journeys” unconference session is the “performance burden.” In technical Wikimedia spaces, contributors often feel they cannot be “average” or show a learning process. According to the session findings, the current culture prioritizes final products over the messy, iterative nature of development. This creates a high-pressure environment where asking basic questions is often perceived as a sign of weakness.
Furthermore, the tendency for well-meaning mentors to label difficult technical tasks as “easy” serves to discourage newcomers. When a contributor struggles with a task that is dismissed as simple, it reinforces impostor syndrome and suggests they are unfit for the role. To mitigate this, the organizers recommend that tech leads and mentors replace dismissive language with shared experiences, explicitly stating where they have previously encountered similar obstacles.
Pro Tip: Shift the culture of your technical team by hosting “failure sessions” where members present code that didn’t work or scripts that hit a wall. Normalizing the struggle is a key step in retaining new contributors.
Strategies for Building Inclusive Technical Communities
Evidence-based recognition is a powerful enabler for retention. Participants noted that receiving credit for incremental contributions—not just finished tools—helps combat feelings of exclusion. The report suggests that technical leads should actively track and celebrate individual contributions to provide the tangible proof of impact that many women+ require to feel they truly belong in the space.
The creation of dedicated spaces for women+ has also proven effective. Drawing inspiration from organizations like RLadies, the guide argues that feminist-aligned environments lower the “activation energy” required for participation. These spaces allow contributors to ask questions without the pressure of the “male gaze,” fostering a safer environment for skill development. Key recommendations include:
- Formalizing Entry Points: Publish clear glossaries for technical jargon like “Gerrit” or “backport” to remove linguistic gatekeeping.
- Diversifying Contributions: Actively invite participation in non-code areas such as documentation, testing, and design.
- Facilitator Training: Ensure that women+ spaces are led by individuals with intersectional awareness to maintain a supportive atmosphere.
The Future of Wikimedia Technical Contributions
The path forward requires moving away from the assumption that women+ must be “ready” to join technical spaces. The “Sharing Journeys” guide emphasizes that community leaders must lower the barriers they control. This includes shifting from a “demonstration-first” culture, which is often adversarial, to a “collaboration-first” model. By adopting a code of conduct that prioritizes non-violent communication, technical moderators can ensure that questions are met with curiosity rather than criticism.
Did you know? The 2025 Developer Survey, which informed the recent hackathon discussions, included 152 men, 14 women, and 15 nonbinary, genderqueer, or transgender individuals, highlighting the significant gender gap that persists in open-source technical contribution.
Frequently Asked Questions
How can organizers improve diversity at future hackathons?
Organizers can start by creating multiple, low-threshold entry points for non-coders, providing clear glossaries for technical terms, and protecting time during core hours for women+ only sessions.
What is the “performance burden” in tech spaces?
It is the feeling that contributors must demonstrate constant expertise and perfection, preventing them from asking questions or sharing work-in-progress for fear of being judged harshly.
What is the most effective way to help someone with impostor syndrome?
Rather than offering generic encouragement, provide concrete evidence of their past successes and contributions. Helping them see a list of their merged patches or cited work is more effective than telling them they are “great.”
Are you working to make your technical community more inclusive? Share your experiences in the comments or participate in the Wikimedia Foundation’s ongoing research to help shape future development policies.
Worth a look
