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 On Sunday, November 6, 2016 at 1:56:19 PM UTC-5, vedant agarwala wrote: > > 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. > > Regards, > Vedant. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
