In theory, I'm not sure that open source should work. Think about it: Companies usually keep their best ideas secret. But in open source, everyone shares their code openly. You'd expect most people to just use the free software without giving anything back. Not to mention trying to organize thousands of volunteers from all over the world to build something complex. But despite all these reasons why it shouldn't work, open source not only survives – it thrives. It's powering a huge part of the technology we use every day. But for many people, the idea of actually contributing to open source still feels pretty scary. Why? And more importantly, how can we change that?
Let's start with a personal story. When I first thought of contributing to an open source project, I was afraid. The fear of making a mistake in front of the entire internet was overwhelming. Sound familiar? If so, you're not alone. Research shows that this fear of public failure is a significant barrier to open source participation.
But here's the interesting part: studies also show that the most effective way to overcome this fear is through community support. When we're part of a group, our fear of failure decreases, and our willingness to take risks increases. This is where the magic happens.
#100DaysOfOSS Challenge
Our #100DaysOfOSS Challenge, isn't about coding for 100 days. It's about leveraging the power of community to transform hesitation into action.
Here's why I think this approach works:
Structured Progress: The challenge provides a clear pathway, breaking down contributing to open source into manageable weekly tasks.
Community Support: By connecting participants, the challenge creates a supportive peer group. This not only can reduce anxiety but also increase accountability and motivation.
Learning by Doing: The challenge emphasizes practical contributions, aligning with the principles of experiential learning - you don't have to know how to code to contribute.
Flexibility: Participants can tailor the challenge to their interests, which research shows increases intrinsic motivation and long-term engagement.
This year, we have support from GitHub Education to enhance the challenge and we're introducing weekly structured posts and increased community engagement opportunities. It's an experiment in scaling the benefits of community-supported learning.
So, here's my call to action: If you've ever been curious about open source but hesitated to jump in, join us for #100DaysOfOSS with your intro today - we already have over 100 people!
If you'd like to start exploring, check out my Beginner Friendly Workspace and let me know what repositories should add!
P.S. If you're participating, you can also sign up for the OpenSauced newsletter for biweekly updates on Open Source topics to help you along your journey.
Top comments (13)
Well, I have been in open source for a few months now, and finding the first open source to contribute to and to stick to is the most challenging task, thanks for this article, the repositories you've shown are really worth looking into
Glad you found it helpful!
This is fantastic! I'm currently doing #100daysofcode "part 2", up to 130days, because the community connection and support is awesome. I've been wanting to get into open source and this new challenge is perfect! Thanks for sharing!
That's awesome! Super excited to see how it goes for you!
Have been doing something similar entire summer with my Google summer of code project as well as another repository's contributions in the side m i would love to be a part of this great journey alongside you . I would be glad to use your tag on my thread of oss contributions in thread . You can follow me there with the name : sambhavdixitpro
Hi BekahHW,
Top, very nice and helpful !
Thanks for sharing.
It's inspiring to see the #100DaysOfOSS Challenge turning down the fear of contributing is exactly what many newcomers need to overcome the intimidation factor from a supportive environment. Kudos
I created an opensource for node.js but I don't know anything except coding so low traffic. Any suggestion for me?
Can you provide a link? I think having good issues, documentation, and talking about it in public can be great ways to create a welcoming contributor path.
Here's a great post from @adiatiayu: dev.to/opensauced/building-bridges...
And another great post from @cbid2: dev.to/opensauced/how-to-create-a-...
Thanks for the mention @bekahhw! 😊 Hi @mrrishimeena. Another article that I think would be very helpful would be this one
How To Make a Delicious Contributing Guide
Christine Belzie for OpenSauced ・ Aug 31 '23
Thanks for the reply. I will read these articles too.
Here is the github link: github.com/errsole/errsole.js
i didn't understand anything i am new to coding help me out
Check out the challenge discussion: github.com/orgs/open-sauced/discus...