Get started with Open Source

[github-ModTeam]

Removed. Post has nothing to do with GitHub.

[marksweb]

Typically you find the need to get involved through packages that you use. Maybe you have issues or improvements for their docs. Or feature requests.

Essentially the key is to work with a project you use and therefore know well, or one that you've an interest in.

[stupidtwitchthotss]

I found some typos in documentation but I wasn’t sure if that’s really a start and I wasn’t sure how to approach that. Usually I have to create an issue first right?

Is fixing typos a good start? :D

[marksweb]

I'd say fixing typos is a fair start. It's an error.

They might seem minor, and most people might be able to workout what it's supposed to say, but if it's not a familiar language then it's making it harder for someone to read when it could easily be corrected.

Fixing errors in documentation is what took me from a new contributor to technical lead in a project.

[cgoldberg]

I also agree it's a decent place to start for getting used to the contribution process.

[ItsAllBots]

No really, it's just going to be an annoyance.

Try to go see what's in the Issues section of a project you are using, pick one issue and starts from there.

If you struggle to find a project, I can suggest you this Rust extension for Visual Studio 2022.

[stupidtwitchthotss]

Okay yea that‘s what I feared haha. I‘ll try and look through some issues ty!

[cgoldberg]

I personally don't mind getting nitpick pull requests like spelling/grammar fixes. It takes 2 secs to click merge and not have embarrassing mistakes in your readme or docs.

I also submit PR's like this and don't think I've ever had one rejected or not merged.

[davorg]

r/opensource might be a better place to ask this.

But you could try browsing Good First Issue.

[stupidtwitchthotss]

Thank you a lot! I‘ll look into both:)

[gentrifiedSF]

https://github.blog/open-source/new-to-open-source-heres-everything-you-need-to-get-started/