It’s nice to see you got started already! To answer your question: one of the most useful tips mentioned in the “Contributing to Rails Guides” (
) is helping resolve existing issues. It’s an easy way to learn about Rails internals while contributing by verifying or complementing bug reports and patches. Adding something as simple as “Can reproduce on Windows 10 with Ruby 2.2 and Rails HEAD” can get the ball rolling, and you might just get curious enough to end up submitting fixes.
. Even if you’re not participating you’re welcome to join us!
> On Mar 6, 2015, at 12:20 PM, Sushruth Sivaramakrishnan <
sivsu...@gmail.com> wrote:
>
> Hello guys,
>
> Thank you for the response.
>
> I see a couple of extremely interesting projects in the list now, like the long running ruby and rails benchmarks and refactoring the cookie implementation.
> I am still a bit far away from actually being of good help with the ideas, so I have started contributing by a few Doc fixes here and there.
> This has helped/ is helping me in 2 ways. I am getting familiar with the codebase and the coding practices and also I can now see how the entire system interacts internally.
>
> I have also been a bit active on the IRC, helping out fellow Rails enthusiasts. I have also started a blog, helping out rails guys on Windows(IMO, this is a neglected section of developers)
>
> I would be deeply indebted if you could give me a few suggestions/advice on how i can enhance my learning/helping curve?
> Warm regards from India,
> Sushruth