My first open-source PR wasn't during Hacktoberfest, but I want to bring it up because I think its a good story on contributing to open-source.
I opened my first PR due to running into a problem I found in my own project. I googled the error I had and found an issue on github for it. What's interesting is the problem and solution was already laid out. So much so the only work that had to be done was go through the github flog to get the fix into the library.
Like most newbies to open source this seemed really complicated, and required working with actual developers which terrified me! I was still really new (I even mentioned that in my PR) to web development and open source, but I read the guide, and did what I could to get the fix going.
My PR was merged, and I (along with anyone else who ran into the issue) got their fix within a day or so.
What I found was everyone involved was extremely helpful! I had no reason to be scared, literally the worse thing that could happen is my PR get's rejected and everyone moves on. No one is going to get mad for people trying to help out, no one is going to get angry, and no you wont break anything, as people review what you've done, along with potentially automated tests protecting against any regression.
There is so much to gain by opening PR's and contributing to open-source, not only for the community, but also for yourself in terms of experience!
If you know you know some stuff, even basic JavaScript, or another language you can contribute. Even if you know nothing you can contribute to documentation. If you ever wanted to work on code that isn't what you wrote, open-source provides a huge playground for that, to learn from others, and contribute back.
Hacktoberfest might give you some incentive, but the incentive is always there, just gotta leverage it.
I think contributing to the documentation is at least as useful as contributing fixes, new features... and yes, no need to worry, I merged for instance almost every PR I got (with two PRs we need to figure out what's wrong, but we'll get it work... Maven stuff ;)). Fixing spelling errors or grammar errors is also a great start :-) every PR counts
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My first open-source PR wasn't during Hacktoberfest, but I want to bring it up because I think its a good story on contributing to open-source.
I opened my first PR due to running into a problem I found in my own project. I googled the error I had and found an issue on github for it. What's interesting is the problem and solution was already laid out. So much so the only work that had to be done was go through the github flog to get the fix into the library.
Like most newbies to open source this seemed really complicated, and required working with actual developers which terrified me! I was still really new (I even mentioned that in my PR) to web development and open source, but I read the guide, and did what I could to get the fix going.
My PR was merged, and I (along with anyone else who ran into the issue) got their fix within a day or so.
What I found was everyone involved was extremely helpful! I had no reason to be scared, literally the worse thing that could happen is my PR get's rejected and everyone moves on. No one is going to get mad for people trying to help out, no one is going to get angry, and no you wont break anything, as people review what you've done, along with potentially automated tests protecting against any regression.
There is so much to gain by opening PR's and contributing to open-source, not only for the community, but also for yourself in terms of experience!
If you know you know some stuff, even basic JavaScript, or another language you can contribute. Even if you know nothing you can contribute to documentation. If you ever wanted to work on code that isn't what you wrote, open-source provides a huge playground for that, to learn from others, and contribute back.
Hacktoberfest might give you some incentive, but the incentive is always there, just gotta leverage it.
Happy hacktoberfest, open them PRs!
I think contributing to the documentation is at least as useful as contributing fixes, new features... and yes, no need to worry, I merged for instance almost every PR I got (with two PRs we need to figure out what's wrong, but we'll get it work... Maven stuff ;)). Fixing spelling errors or grammar errors is also a great start :-) every PR counts