DEV Community

Cover image for Open Source Is Waiting for You: How to Stop Being Afraid and Start Contributing
Dmitry Titov
Dmitry Titov

Posted on

Open Source Is Waiting for You: How to Stop Being Afraid and Start Contributing

๐Ÿงต The Shortage of Open Source Contributors: Myth or Reality?

Unfortunately โ€” itโ€™s reality ๐Ÿ˜”

Do you know how many developers there are in the world today?

๐Ÿ“Š According to Evans Data Corporation, in 2024 there are over 28.7 million developers globally.

Sounds like everything should be built already, right?
But letโ€™s look at how many actually contribute to open sourceโ€ฆ

๐Ÿ“‰ Linux Foundation Report (2024)

Based on this survey of 332 developers involved in OSS:

๐Ÿ‘ฅ Out of 332 people:

Image description

๐Ÿ’ฅ Even among this engaged group, only 17% are consistently active contributors*.
*Sum of maintainers (10%), core contributors (5%), and committers (2%).

Thatโ€™s just 1 out of 6 people, and this is from a motivated audience!

๐Ÿงต Of course, these numbers donโ€™t capture everyone who helps open source thrive.

People contribute by writing docs, triaging issues, translating content, answering questions, giving feedback โ€” and it all matters.

Without these roles, maintainers would burn out even faster ๐Ÿ’€.

๐Ÿ’ฌ JetBrains Survey Confirms It

In JetBrainsโ€™ Dev Ecosystem 2023 (20,000+ devs):

Image description

โœ… Regular + full-time contributors = just 5โ€“6%

๐ŸŽฏ Core of active OSS devs = ~15% at best

๐Ÿงฎ Letโ€™s Do the Math

If we take the optimistic 17% of 28.7M developers:
๐Ÿ”ง โ‰ˆ 4.9 million active contributors

But more realistically (5โ€“11%):
๐Ÿง‘โ€๐Ÿ’ป โ‰ˆ 1.4โ€“3.1 million โ€” the entire OSS backbone

Let that sink in โ€” thatโ€™s fewer people than in some cities.

๐Ÿ‡บ๐Ÿ‡ธ What About the US?
According to GitHub Octoverse 2024:

๐ŸŒ India, China, and Brazil are growing rapidly.
๐Ÿ‡ฎ๐Ÿ‡ณ India is set to become the #1 contributor country by 2028.
๐Ÿ‡บ๐Ÿ‡ธ The US still leads, but its share is gradually declining.

๐Ÿšง Open Source Is Built By a Minority

Even in ideal conditions:

โš ๏ธ ~80% of developers donโ€™t contribute consistently.

But instead of panic, this should be a call to action ๐Ÿงญ


๐Ÿงฉ Ways to Contribute Beyond Code

๐Ÿ“˜ Docs
๐Ÿž Bug reports
๐ŸŒ Translations
๐Ÿ’ฌ Discussions
๐Ÿง‘โ€๐Ÿซ Tutorials
๐Ÿง  Feedback
๐Ÿ” Testing
๐Ÿค Community support


๐Ÿ’ก Why Donโ€™t More Devs Contribute?

Here are the most common blockers:
โ€ข ๐Ÿ˜ฐ Fear of judgment (โ€œWhat if my PR gets mocked?โ€)
โ€ข ๐Ÿคท Low confidence (โ€œIโ€™m not experienced enoughโ€ฆโ€)
โ€ข โ“ No idea where to start
โ€ข ๐ŸŒ Language barrier
โ€ข โณ No time (work, burnout, lifeโ€ฆ)

These arenโ€™t character flaws. These are fixable with guidance and community.

๐Ÿ› ๏ธ The Cost of Not Fixing It

Open source is the invisible infrastructure of the tech world.

But without new contributors:
โ€ข ๐ŸŒ Projects stagnate
โ€ข ๐Ÿ”ฅ Maintainers burn out
โ€ข ๐Ÿ›‘ Critical tech loses support

Weโ€™re not talking about missing features, weโ€™re risking missing futures.

๐Ÿงฌ Lost Potential = Lost Innovation

There are millions of devs who want to contributeโ€ฆ

โ€ฆbut donโ€™t know how, or are afraid to try ๐Ÿ˜ž

That means millions of ideas that stay locked.
Thatโ€™s not sustainable.


๐Ÿงญ So, How Do We Fix This?

Weโ€™re not asking everyone to become maintainers overnight.

But we can make the first step easier โ€” together.
The door to open source shouldnโ€™t feel locked.


๐Ÿค— 1. Make Projects Feel Welcoming

People donโ€™t contribute to repos โ€” they contribute to communities.

A good README isnโ€™t just technical โ€” it says:
โ€œYou belong here.โ€
โ€ข Start with why this project matters
โ€ข Add a clear โ€œHow to Contributeโ€ section
โ€ข Include a real Code of Conduct (humans first!)

๐Ÿ“Œ MUIโ€™s README is a great example โ€” technical and human.

๐Ÿง  People wonโ€™t contribute if they donโ€™t feel invited.

๐Ÿ“– 2. Docs = Love
Documentation is the first handshake.
Done right, it says: โ€œWe care about your time.โ€

Include:
โ€ข ๐Ÿ›  Setup steps that actually work
โ€ข ๐Ÿงช Clear testing instructions
โ€ข ๐Ÿง  A โ€œWhat to do if youโ€™re stuckโ€ section

Every unclear instruction is a contributor lost.

๐Ÿฃ 3. โ€œGood First Issuesโ€ Arenโ€™t a Meme
Tagging tasks with โ€œgood first issueโ€ isnโ€™t charity โ€” itโ€™s strategy.

They should be:
โ€ข ๐Ÿงฉ Small and self-contained
โ€ข ๐Ÿงญ Explained with real context
โ€ข ๐Ÿ” Even small things (rename, doc fix) matter

Want to try?
Here are real ones you can do today in vite-plugin-create:
โ€ข Add plugin usage example to vite.config.ts โ€” help devs get started faster.
๐Ÿ›  PR welcome
โ€ข Unify default config naming โ€” tiny change, real impact.
๐Ÿ›  PR welcome

๐Ÿš€ Where to Find Beginner-Friendly Projects?
Even if youโ€™re not ready to contribute here โ€” thereโ€™s a world of welcoming projects waiting for you:
โ€ข goodfirstissue.dev ๐ŸŸข
โ€ข up-for-grabs.net ๐Ÿงฉ
โ€ข firstcontributions.github.io ๐ŸŽ“
โ€ข codetriage.com ๐Ÿง‘โ€โš•๏ธ

Each one helps you discover real issues โ€” not just toy examples โ€” and shows you exactly how to jump in.

No pressure. No gatekeeping.
Just real ways to help. ๐Ÿ’ช

๐Ÿ’ฌ 4. Feedback That Teaches, Not Scares

The way you reject a PR defines your project more than how you merge it.

Bad:
โœ–๏ธ โ€œThis is wrong.โ€

Better:
โœ”๏ธ โ€œThanks for this! Letโ€™s tweak it like this โ€” hereโ€™s whyโ€ฆโ€

Every comment is a moment to mentor. Donโ€™t waste it.

๐ŸŒฑ The Secret? Itโ€™s Not About Code

Itโ€™s about people helping people.

Want your project to grow?
Help someone grow through your project.


๐Ÿ’Ž Real Projects Doing It Right:

๐ŸŸข Vue.js
โ€ข โœจ Clean documentation
โ€ข ๐Ÿง  Beginner sections
โ€ข ๐Ÿซ‚ Supportive Discord & community

๐ŸŽจ p5.js
โ€ข ๐Ÿง‘โ€๐ŸŽ“ Creative coding for learners
โ€ข ๐ŸŒ Focus on diversity
โ€ข ๐Ÿ“ฆ Tons of beginner-friendly examples

๐Ÿ“Š OpenRefine
โ€ข ๐Ÿ” Clear contribution docs
โ€ข ๐Ÿค Active on forums
โ€ข ๐Ÿ’ฌ Friendly PR feedback


๐ŸŒฑ My First OSS Step

My journey began with helping a friend build a driving test app for foreigners in Thailand ๐Ÿ‡น๐Ÿ‡ญ
He didnโ€™t have time to finish โ€” I jumped in.

Later, we mentored a beginner dev together. It felt like real impact.

Then I tried making a Vite plugin I needed โ€” and published it.

And people actually used it ๐Ÿ’ฅ
My first stars. My first issue.
It felt amazing.

That led to more projects. More contributors.
And eventually โ€” my first PRs to React, Vite, and others.

Now I mentor devs and help them start their journey.

๐ŸŽ“ Tip: Take This Course
๐Ÿ“š Open Source Software Development on Coursera
โ€ข Clear, practical lessons
โ€ข OSS etiquette & licensing
โ€ข Real-world Git workflows

If youโ€™re scared to start โ€” this will help.


๐Ÿค” And what about you?

Iโ€™d love to hear from you โ€” the readers.

๐Ÿ—ณ๏ธ Have you ever contributed to open source?

Leave a comment with the emoji that matches you:

๐Ÿ’ก โ€” Iโ€™ve contributed once or twice

๐Ÿ”ง โ€” I contribute regularly

๐Ÿ“š โ€” I help with docs, translations or community

๐Ÿง โ€” I use it but havenโ€™t contributed yet

โ“ โ€” I want to, but donโ€™t know how

๐Ÿ‘‡ Drop your emoji below!


๐Ÿ Final Words

๐ŸŒ Open source is how we build the internet.
๐Ÿค Itโ€™s also how we grow developers, communities, and ideas.

You donโ€™t need to be a genius. You just need to start small โ€” and start together.

โœจ The world needs your code. But more importantly โ€” it needs you.


๐Ÿ“š Sources
โ€ข Linux Foundation OSS Developer Report (2024)
โ€ข JetBrains Developer Ecosystem Survey (2023)
โ€ข Evans Data Corporation (2024): Developer Population
โ€ข GitHub Octoverse 2024 Highlights
โ€ข Vue.js Contribution Guide
โ€ข p5.js Community Docs
โ€ข OpenRefine Contribution Guide
โ€ข goodfirstissue.dev
โ€ข First Contributions Project

Top comments (0)