Hello!
As part of a university course I’ve had the task of contributing to a large-scale software project in which I chose Ruby on Rails. As someone who is new with contributing to larger projects, and unfamiliar with both Ruby and Ruby on Rails I thought to give my insight on how it was to get into developing Rails. The ”Contributing to Ruby on Rails” guide was almost entirely sufficient for a beginner to get started with contributing to Rails with its detailed step-by-step guidance. However, while the guide mentions the various means of contributing to the project it could suggest for new contributors to direct their efforts where it’s mostly needed. While I myself set out to solve bugs in the Issue tracker, because I thought that would contribute most to Rails, I later realized the ratio between the number of open Issues and Pull requests on Github. With this one might argue that testing suggested patches might be the best contribution effort, and something that could be mentioned in the contribution guide. In addition to this, the various different communication channels for Rails such as the mailing list, irc and Slack is great for new contributors to use for any questions that might arise. However, only the mailing list is mentioned in the contributor guide which could be amended. All in all, in general I had a really easy time getting into Rail’s development environment and a good time doing so. The process is streamlined and simple enough using the rails-dev-box. Just my two cents! :) Regards, Andreas. -- 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.
