Hello everyone,
I am a fan of rails and I feel I should start giving back to the community. I am experienced with open source code contribution (through KDE). I set up the rails-dev-box, which was really easy- kudos on that!
I want to start submitting patches. How should I decide on what I should start work on? I can pick on some issue in github, or is there something else you want me work on- something simple just to get my feet wet 
Looking forward.
Somewhere to start: http://guides.rubyonrails.org/contributing_to_ruby_on_rails.html
I’ve been through the entire guide. It is mentioned how to contribute but not “which” code to contribute. Or, which bugs/features I should work on.
I’ve been through the entire guide. It is mentioned how to contribute but not “which” code to contribute. Or, which bugs/features I should work on.
Hi Vedant!
We don’t have a specific roadmap for beginners. My advice to new contributors is to take a look at open issues that are related to the library you’re most comfortable / familiar with. I personally started with Active Record becuase I had found a bug there and was most interested in the database side of things. We have many open issues that range in complexity but we don’t rate them by difficulty and I’m not sure at this time which ones are possibly easiest.
Most issues should have reproduction scripts that you can run against your local copy of Rails and see where the bug exists. These are super useful for doing a git bisect and finding the exact commit that broke Rails for that person.
Hope that helps, and hope to see some PR’s from you 
-Eileen
The other day I tweeted about this issue: https://twitter.com/arthurnn/status/793579322539773952
Might be a good one to take a look, as far as I know nobody is working on it.
Thanks a lot Eileen!
After some issue hunting, I was able to find a couple that I can work on.
Hope to submit PRs soon.