How Non-Code Contributors Find Their Place in Open Source Communities. How to Build Trust and Grow Open Source Communities. Q&A with Lahari Chowtoori, and Mila Zhou.

Q1. In the open source world, code contributions take the spotlight. What is the role of non-code contributors and why is it important?

In the open source world, while code contributions are highly visible, non-code contributors play equally vital roles in project success. These non-code contributions include handling documentation, community building, marketing, event organization, governance and strategic planning. They create bridges between technical and non-technical audiences, make projects more accessible, and ensure long-term sustainability. For instance, the Apollo project grew from scratch to over 100,000 members through focused community management, demonstrating how non-technical contributions directly impact project success. 

Q2. You have conducted in-depth interviews with over 10 seasoned open source professionals in documentation, program management, and community building. What was the original motivation of this work?

The motivation behind these interviews was to understand the experiences, challenges, and impact of non-code contributors in open source communities. The work aimed to document their journeys, identify common patterns in inclusion/exclusion, and gather insights about how open source projects can better integrate and value non-technical contributions. 

Q3. What did you discover talking with these professionals? 

The interviews revealed several key findings: 

– Non-technical contributors typically take1-2 years to feel fully included in communities 

-There’s a significant disparity in inclusion difficulty between technica l(rated2/5) and non-technical contributors (rated 4/5) 

-Successful non-technical contributors often combine community-building skills with basic technical knowledge 

-Clear documentation, welcoming spaces, and recognition of diverse contributions are crucial for any project success 

-Non-code contributions are essential for project sustainability but often face challenges in recognition and integration. 

Q4. Is there a real sense of belonging and impact in open source communities for non-code contributors?

Yes, there is a real sense of belonging and impact for non-code contributors, though it typically requires more time and effort to establish compared to technical contributors. Many interviewees eventually reached leadership positions, such as board memberships and program directorships. However, this sense of belonging often comes after overcoming significant challenges, including technical language barriers, occasional dismissal of non-code contributions, and the need to repeatedly demonstrate value in technically-oriented spaces. Success stories like Kattni growing the Circuit Python community from hundreds to 35,000 members demonstrate the significant impact non-code contributors can have. 

Q5. Can you briefly share some of the key stories and insights about their struggles with imposter syndrome, moments of breakthrough, and the factors that kept them engaged despite challenges?

Many community members had nagging self-doubt about whether they truly have valuable contributions to make. Their breakthrough often came when they successfully answered other members’ questions or delivered presentations where participants genuinely learned from their expertise. 
What consistently emerges as a crucial factor in their persistence is the presence of supportive relationships within the community. While self-doubt and external challenges can be discouraging, having allies who validate their contributions and provide encouragement has been transformative. These supportive connections give members the confidence to push through difficulties and continue growing in their roles. 
A particularly striking pattern is how moments of receiving appreciation or acknowledgment from people within the community, especially who has been in the community for a long time and well recognized, helped turn imposter syndrome into a sense of genuine belonging and capability. This highlights how important community support is in helping members recognize and embrace their own value and expertise. 


Q6. In general, how community dynamics, recognition systems, and project structures either foster or hinder the inclusion of non-code contributors? 

community dynamics:

In-person events play a crucial role in fostering inclusion. After people meet face-to-face, their online interactions typically become more friendly and understanding. That’s probably because in person communication allow you to know each other at a personal level, understand what their usual behavior pattern is, and what their common tone is. Also, open source collaboration is global. To many people, English is their second language. However, you often only realize it after after you meet them in person. 

Explicit calls for non-code contributions significantly improve inclusion. When projects clearly communicate their needs for non- technical skills, it becomes easier for potential contributors to step forward. For instance, I organize the PostgreSQL meetup in NYC. In my lightning talk at PGConf, I list on my wishlist – we need people who are good at photograph to help us capture the memorable moments during meetup. On the second day, someone came to me and volunteered to take photo for us. 

A strong support system within the community is vital. One contributor shared how she faced exclusion from certain community members and began doubting herself as a newcomer. However, the encouragement and support from other community members helped her persist and feel included. 

Recognition, even in its simplest form, promotes inclusion of non-code contributors. While some projects are implementing formal systems to document non-code contributions, like CHAOSS’s GitHub reporting system, personal recognition and individual interactions often carry more weight. A simple “thank you” can make a significant difference. 

Project structures can either enhance or hinder inclusion. Some projects give non-code contributors PMC role, like Airflow. Or in the example of Django, it has created specific roles for designer, such as the Design czar position. While this approach acknowledges non-code contributions and ensures quality work, it has sparked debates about appropriate access levels. That’s an area needing further research into how different projects handle non-code contributor roles and what mechanisms prove most effective. Having clear advancement paths for non-code contributors is essential for sustainable inclusion. 

Q7. What are the main lessons learned? How to create welcoming spaces for diverse talents, build inclusive contribution pathways, and maintain long-term engagement with non-code contributors?

Main lessons learned: 

    To projects: it’s crucial to actively acknowledge and appreciate non-code contributions.That represents a fundamentals mindset shift. A vibrant community and a successful project need a lot of nurture that’s beyond code, and project leaders should consistently communicate this value. Regular recognition of non-code contributions should become standard practice within the community. Projects should also create clear entry points for non-technical contributors, similar to how they provide “good first issues” for developers. This could include maintaining a dedicated page listing non-code opportunities or ongoing activities seeking volunteers, making the path to contribution straightforward and accessible 


    To non code contributors: while technical expertise isn’t necessary, maintaining a genuine interest in technology is essential. Non-code contributors should demonstrate enthusiasm for learning about the technical aspects of the project, as this understanding helps them perform their roles more effectively. This technological curiosity enables them to bridge the gap between technical and non-technical aspects of the project, ultimately leading to more meaningful contributions 


Q8. Behind every successful open source project is a strong content strategy that builds trust, amplifies community voices, and drives meaningful engagement. What are your recommendations? 

At its core, content is what initially draws people to your community – you need to offer something valuable that solves real problems or addresses genuine needs. Think of it like planting seeds – good content attracts initial interest, but it’s the community experience that helps those seeds grow and flourish.
I believe consistency is essential. When you regularly share high-quality content, whether it’s documentation, tutorials, or thought leadership pieces, you build trust and reliability. Community members know they can count on you for valuable insights and updates. This consistent presence encourages them to stay engaged and contribute back to the community. 


What’s particularly important, in my experience, is fostering a culture of volunteerism. The heart of any open source project beats through its volunteers and actively encouraging community participation is essential. This means not just creating content, but actively giving shoutout to volunteers, inviting people to contribute their own expertise and perspectives. When community members feel empowered to share their knowledge and experiences, it creates a richer, more diverse knowledge base that benefits everyone. 

Q9. Could you mention the top 3 most successful open source projects you are aware of? And why are they successful?

Let me share my perspective on successful open source projects, focusing on Python as a standout example. While there are many successful open source projects, Python particularly stands out to me for its remarkable community dynamics. Python’s success isn’t just about its technical merits – it’s about how the community has cultivated an exceptionally inclusive environment. What makes Python truly special is its diverse participation, where traditionally underrepresented groups in tech have found a welcoming home. From my direct interactions with the Python community, I’ve witnessed how they consciously prioritize inclusion. For instance, community members actively facilitate connections, with established members taking the initiative to introduce newcomers to others. These seemingly small gestures create a powerful ripple effect, making Python not just a programming language but a thriving, welcoming ecosystem. This intentional focus on inclusion has contributed significantly to Python’s enduring success and widespread adoption across various domains. 

…………………………………………………………

Lahari Chowtoori, Technical Program Manager, AWS

Lahari Chowtoori is a Technical Program Manager at Amazon Web Services (AWS), focusing on open source, machine learning, and artificial intelligence initiatives. With a background in Data Science and Machine Learning, she explores ways to bridge AI technology with open source solutions. Lahari is passionate about learning from the open source community and sharing knowledge to help others in their technical journey. She believes in the power of combining AI innovation with open source principles to create more accessible and impactful technology solutions.

Miaolai Zhou, Program Manager, AWS

Mila is a passionate program manager at AWS, spearheading funding programs that provide vital resources to open source projects. Her unwavering commitment to empowering and supporting these communities fosters sustainability, drives innovation, and enables collaboration. Mila’s leadership extends to strategic initiatives enhancing open source supply chain security, aligning with key investment streams to safeguard critical infrastructure. Beyond her professional role, Mila actively engages with the open source community, attending conferences and contributing to discussions on sustainability, security, and best practices. Her expertise shapes discourse around these critical issues, positioning her as an influential figure in the open source ecosystem. I am the operation committee member of PGCONF NYC and a core member of Alpha Omega.

Sponsored by AWS