My first contributions were bug fixes of bugs I ran into myself. I'm afraid it still often happen people fix those in a fork or some other way instead of trying to get it in the main branch which is a shame.
One thing that helps with that, and contributing with open source in general, is having patience. Which is hard, but often maintainers do it voluntary, and often that maintain multiple projects.
I'm a Software Engineer, from Portugal, a GitHub Star and a mentor at Black CodHer Bootcamp and "As Raparigas de Codigo" organization. Previously, I've been an admin at AnitaB.org Open Source.
Yes! Patience is key! From both ends, both maintainers and contributors. We all have our lives... so as a maintainer it might take some time to get back to comments on issues or submitted Pull Requests (PR). And as a contributor, it may take time to fix the PR according to a maintainer's review or to actually do a contribution. And with this... communication. When I have to take some time off, I let the community know that I'll be off for some days.
That's nice, to let them know. I've had really good experiences with clojure with fixes/merges within hours. But also pretty bad ones with two rust repos. Not sure if it's language related or just unlucky. For the rust ones it's 'normal' not to hear from the maintainers for weeks.
This. This was also how I made my first contribution on Github, sometimes the barrier to getting the pull request merged to the repo is not getting a response from the maintainer. I know we really want to get our commits in as fast as possible but sometimes we just have to be patient and wait for the maintainer to reply.
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 contributions were bug fixes of bugs I ran into myself. I'm afraid it still often happen people fix those in a fork or some other way instead of trying to get it in the main branch which is a shame.
One thing that helps with that, and contributing with open source in general, is having patience. Which is hard, but often maintainers do it voluntary, and often that maintain multiple projects.
Yes! Patience is key! From both ends, both maintainers and contributors. We all have our lives... so as a maintainer it might take some time to get back to comments on issues or submitted Pull Requests (PR). And as a contributor, it may take time to fix the PR according to a maintainer's review or to actually do a contribution. And with this... communication. When I have to take some time off, I let the community know that I'll be off for some days.
That's nice, to let them know. I've had really good experiences with clojure with fixes/merges within hours. But also pretty bad ones with two rust repos. Not sure if it's language related or just unlucky. For the rust ones it's 'normal' not to hear from the maintainers for weeks.
This. This was also how I made my first contribution on Github, sometimes the barrier to getting the pull request merged to the repo is not getting a response from the maintainer. I know we really want to get our commits in as fast as possible but sometimes we just have to be patient and wait for the maintainer to reply.