30+ GitHub Sponsors, 12K+ combined GitHub stars, Maintainer of 20K+ starred FOSS Repo — Ask Me Anything about Open-Source

I do contributions during weekends. Although, the 'actual' contributions I do have slowed down lately since most of the time I'm reviewing PRs & discussing issues as a maintainer. The dopamine hit I get when my PR gets merged keeps me going :)

Damn, turning system on on weekends! How do you find the motivation

Be on the lookout for small or mid-sized repos, don't head straight into React or TS codebases for example. It could be a small library which you find interesting or have used in your projects. Don't contribute just for the sake of contributing.

1. Go through the README.md & CONTRIBUTIONS.md files

2. Tinker with the app & thoroughly read the docs

3. If you find any error in the docs or something lacking, create an issue explaining your problem

4. Discuss with the maintainers & then implement. Fixing docs is the easiest way to get started. Most of the docs usually have an edit button on each page which links directly to the respective GitHub file in the repo. So, you won't have trouble finding in the repo. If that button doesn't exist, use the search function in your IDE to find.

5. Now, you already have a basic idea of how to contribute and know a part of the codebase which has the docs. Go the already merged small PRs and understand how, what & why that PR was raised & merged.

6. Look for 'Good First Issue' tag. They are usually there for newcomers. Then, slowly and steadily move on to larger issues

7. Always ask for help from the maintainers if you're stuck somewhere or want to solve an issue but have no idea where to get started. No one will judge you. Treat them like friends.

Hope this helps!

*Go through

I would say it's like a double-edged sword. Like let's say for example, GitHub Copilot. Copilot has helped me spew out mundane & boilerplate stuff just by 'tabbing'. This helped me give more time to focus on logical stuff. However, this is also a concerning part, since it crawls through my code and the code available publicly on GitHub. I don't like the idea of borrowing code available publicly for free and monetizing them using copilot.

Microsoft also, has been promoting their own stuff through GitHub & isn't transparent about their future plans IMO. Products like VS Code have a facade of open-source even though it is not. I'm not completely hostile against MS but they're a very sketchy org regarding their future plans around open-source.

Microsoft's strategy of EEE(Embrace Extend Extuinguish) is in full throttle. Open Source !== Free Software(free as in freedom😅). If you are a FOSS maintainer, keep a remote kn GitLab as well.

1. Find a common problem -> create a library solving that problem -> promote it -> start getting users -> setup a sponsor page -> people will sponsor if they find it useful & don't want you to abandon it

2. Start contributing to some well-known repos -> slowly & steadily keep taking issues -> start doing some major contributions -> build some reputation within that community -> creator or maintainer will start sponsoring you for your work if you're actively contributing

Both of these options will take time & patience.

@tzr How do you promote your library?

I was fed up of cringefluencers sharing handwritten git cheatsheets in the name of open-source tips, so I thought about giving this free gyaan I never got when I stepped into open-source 🫡

Upload 76 pages of handwritten notes on how to make a PR else I'm not believing you're an OSS contributor. Also where is your GSSOC badge?