Yes. I do a bit of open-source development myself and often find issues with upstream packages that I am consuming. I will often go out of my way to help debug issues with them, to not only make things better for myself, but for the community.

I've also contributed bits and pieces of insight to Google, Microsoft, Amazon, and Apple, in projects that probably affect us all in some way or another.

I would really like to do but I often think I'm not good enough to contribute to a project 🥲
I also don't find a good project that looks interesting for me to contribute as a front-end developer 💔 because I never used them or I don't understand the code.
I hope that I'll find some good projects to contribute soon 😄

When it's clear how I can help and how I can get started — absolutely. I'm willing to roll up my sleeves and contribute something. When it's not worth it to figure out how, then I find myself not wanting to put in the effort.

Really great that Medusa is open-source!

I am frontend dev how should I start ?

Thread

Thread

Yeah, I do. Then and when I have time and find a need. That is what FOSS permits. It provides software which I can use and when it doesn't work as I need, I can patch it to do that, and I'm good to go. Now, if I write that patch with the general user experience in mind and abide by a given projects requirements, I PR it. I'm losing count, but I have successful PRs to Tendenci, Django, puddletag, in relatively recent times and probably some more projects longer term I'd have to browse my own GitHub repo for inspiration to remember ;-).

But I admit I'm self centred. As I'm not being paid for it, I do this kind of work when my passion projects demand it, and I usually test the PR waters on any project with a small change before I do anything bigger. Try fixing a typo, for example, or improve the README. I call it testing the PR waters. Is anyone there? Are they triaging? Are the merging PRs? Because for better or for worse pick a random repository and it will be anywhere between supremely active and welcoming fo contributions, to dead as a dodo with nobody at the wheel anymore and anywhere between (the clasic mid-ground being, fairly active but the ratio of issues filed to people volunteering time to triage and act on them is poor and there's a large backlog of untouched PRs).

This is cute, I had forgotten I did this:

firstpr.me/#bernd-wechner

I've been contributing to the OSS ecosystem for about a decade now. My contributions primarily fall into two categories:

Bug Reports - When I encounter bugs with a dependency, I tend to search through the project's issues for solutions. If I find an open ticket, I'll add a comment to the thread to make it known that the issue affects multiple more than one person.

Bug Fixes - I'm not a fan of building fixes into your own application code for dependency issues, so often times I'll fork the dependency & create the fix for my own project, and afterwards submit the fix to as a pull request for the dependency to adopt. This has led to me signing CLAs for both Apache and Oracle.

I am relatively new to coding JS. I would contribute once I have clearer understanding. I am starting my journey with Kaggle because I have been doing python programming for data science for about 2 years. I would like to know how to contribute to DEV community.

I love contributing to open source, I start a few years ago with some small fix on java repos, rn I'm contributing to javascript on vite and vitest. Core team member on unocss and vitest and a mantainer/contributor on unplugin-icons, vite-plugin-inspect, vite-plugin-pwa, vitesse, vite-ssg, and unplugin-auto-import

I did back in Hacktoberfest. But as of 'regular' open source projects, I'm scared that I'll either make the project worst than it already is or that I'll take too long figuring out a solution and then it's passed on to someone else. And also, all the 'easy' open source projects are already taken. But I know recruiters look at that stuff so I'll have to contribute eventually.

I did that a few times. Often through issues and a few times through code. Problem with that often was that the pr did not get merged in time. So I moved on to a different piece of code that fit better or just wrote my own. When the time came to merge it I already forgot that I had a pr open

Yes I am contributing to second largest CNCF project called OpenTelemetry. It is bundle of API, SDK and specification to collect the telemetry data from the application and send it to compatible backend to help developers debug the issues faster. The idea is to create an adhoc standard to collect those telemetry data for a number of languages. I have been contributing to its python agent repo and resolved few issues and added few new features and recently I have started contributing to its Php Agent as well.

I've made quite a few contributions to this one

Check out the projects at blisslabs.org to contribute to open source. It's a 501 c3 nonprofit organization

Absolutely! When I like something and can understand the source code well,I want to improve it and I do! Like: Unreal Engine,open source tools,Linux Kernel and many more

I do from time to time but mostly I do my own ones.

Yes, I work on several personal open source projects and have contributed to other projects (Tiled game map editor) as software developer and user interface translator.

Yes. Aside from Forem's codebase (which is my job), I contribute to Emacs and org-roam. Years ago, I contributed a few bits to Rails.

I probably would just spaghettify the code lol. Maybe when I'm older and have more experience I will contribute

Definitely try to when I can, especially if its a bug thats personally affecting me! Glad you open-sourced it, though. Seems to be the future of products is open sourcing several parts.