Archive | contributing RSS feed for this section

A Fresh Cup – Home – Contributing to Rails: Step-by-Step

Step 0: Learn at least something about Ruby and Rails. If you don’t understand the syntax of the language, common Ruby idioms, and the code that already exists in Rails, you’re unlikely to be able to build a good patch (that is, one that will get accepted). You don’t have to know every in-and-out of the language and the framework; some of the Rails code is fiendishly complex. But Rails is probably not appropriate as the first place that you ever write Ruby code. You should at least understand (though not necessarily memorize) The Rails Way
and The Ruby Programming Language.
(Link: A Fresh Cup – Home – Contributing to Rails:┬áStep-by-Step)

Contributing to Rails

This guide covers ways in which you can become a part of the ongoing development of Rails. After reading it, you should be familiar with:
* Using Lighthouse to report issues with Rails
* Cloning edge Rails and running the test suite
* Helping to resolve existing issues
* Contributing to the Rails documentation
* Contributing to the Rails code
(Link: Contributing to Rails)