awesome-for-beginners VS CodeTriage

The "Awesome First PR Opportunities" list might be a helpful starting point.

https://github.com/MunGell/awesome-for-beginners

There is a repo called Awesome for Beginners, that has a list of open source projects in many languages that are looking for contributors.

Searching in Awesome for beginners

I am looking at this repo for beginners then I picked the typescript repo but I couldnt do it . I mean this doesnt look like something a first timer can do or I am a smooth brain maybe.

Forma "quero ajudar um open source": https://github.com/MunGell/awesome-for-beginners

I would advocate an additional method of supporting open source: contributing. Doesn’t even have to be features. Bug fixes or docs are amazing. Heck even opening really good issues where it’s clear the dev spent time getting a good reproduction. Daniel is a full time maintainer who would benefit from additional income. Many small projects have maintainers that a few dollars might be helpful but help would be more helpful.

I went to some open source confs to promote a book I wrote (https://howtoopensource.dev) and free service (https://www.codetriage.com) and asked people working at booths for large companies if they can contribute to open source at their day job. Only one person had a positive example and in that case their team was literally blocked on the fix and there was no workaround. The rest seemed confused about why they should be spending work time to report issues or fix bugs. Some genuinely didn’t realize that was helpful and that “contributing to open source” doesn’t just mean releasing and maintaining your own code.

So yes, please fund the software you use, also time and attention is valuable too.

Last tip: If you want to make a habit of it, get it tracked like regular work. “Hey, is feature X done, can we move this card over?” …”Actually I still need to report an upstream issue before we are totally done, I’ll make another work item for it and get it checked off today”. If you feel like you would get pushback for that, then start smaller, by filing issues and talking about it after the fact. Most other engineers and quite a few managers see this as going above and beyond for your job.

Tools like Up for Grabs, CodeTriage, and Good First Issues are designed to help you find beginner-friendly open source projects. These platforms curate lists of issues that are suitable for beginners and folks new to contributing, making it easier to find projects where you can make contributions right away.

CodeTriage: To subscribe to your favorite open-source projects and get a new open issue from them in your inbox every day.

3. Open Source Contribution

I wrote a book with a chapter on how to write docs for other people’s code https://howtoopensource.dev

I also wrote an open source tool for writing and testing tutorials https://github.com/zombocom/rundoc and another that will email you undocumented methods of open source code so you can practice writing documentation https://www.codetriage.com/.

CodeTriage helps you contribute to open source by “picking a handful of open issues and delivering them directly to your inbox”. (Source: CodeTriage)

Here are open source projects listed https://www.codetriage.com/ You can filter for "C".

The biggest untaped potential (IMHO) is not one company funding 1 full time maintainer, but EVERY company allowing and encouraging EVERY developer to help and work with open source. This was the basis of my web app https://www.codetriage.com/. I have a chapter on it in my book How to Open Source (https://howtoopensource.dev/), and I talked to Yehuda about it for about an hour after my last talk at Philly ETE.