4 ms·

Congratulations! That's truly awesome. Any tips for a novice developer who would love to start contributing?

steveklabnik 13y ago
Thank you! I started less than a year ago, and I was the #13th biggest contributor here, and received a commit bit a few weeks ago. It's not too hard to get involved if you'd like! I wrote up my own personal 'contributing to Rails' guide here: http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-contribute-to-ruby-on-rails- http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-cont... The official one is here: http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html http://edgeguides.rubyonrails.org/contributing_to_ruby_on_ra... The easiest way is to write documentation; that's how I got started. It's not for everyone, though. The simplest possible way to get involved with writing code is to pick an open bug on the tracker and fix it. Like most things, it just gets easier the more you do it. The first one seems hard, everything seems confusing. But by the time you've done two or three, you wonder why you ever thought it was difficult.
- zachgersh 13y ago
  LOL. Meeting of the minds with my comment above :)
- rzendacott 13y ago
  Thanks! I'll definitely check out the guides and try to get started!
  - steveklabnik 13y ago
    Great! Ping me if you have problems.
    - rzendacott 13y ago
      I gave it a shot! [0] Hopefully everything looks okay. The hardest part was finding an issue. Thanks again for your advice! [0] https://github.com/rails/rails/pull/11193 https://github.com/rails/rails/pull/11193
zachgersh 13y ago
I am sure Steve would say this as well (because he has said it many times). Start by improving the documentation of helping to regress bugs. These two items while seemingly inconsequential are actually a huge help to the core team and all developers who actually use rails (especially awesome documentation). Once you get a certain level of familiarity with the way Rails is built, find a small bug and follow the contribution guidelines. There is no magic :) Take small steps and continue to make any contribution you can. Ask a ton fo questions and work through issues, you'll get there. Here's a blog post that Steve actually wrote about contributions: http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-contribute-to-ruby-on-rails- http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-cont... Congrats as well Steve! You should be really proud of this release with the rest of the core team.
- rzendacott 13y ago
  Thank you! I'll be sure to try and start taking my first steps :)

Thank you! I started less than a year ago, and I was the #13th biggest contributor here, and received a commit bit a few weeks ago. It's not too hard to get involved if you'd like! I wrote up my own personal 'contributing to Rails' guide here: http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-contribute-to-ruby-on-rails- http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-cont... The official one is here: http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html http://edgeguides.rubyonrails.org/contributing_to_ruby_on_ra... The easiest way is to write documentation; that's how I got started. It's not for everyone, though. The simplest possible way to get involved with writing code is to pick an open bug on the tracker and fix it. Like most things, it just gets easier the more you do it. The first one seems hard, everything seems confusing. But by the time you've done two or three, you wonder why you ever thought it was difficult.

zachgersh 13y ago
LOL. Meeting of the minds with my comment above :)
rzendacott 13y ago
Thanks! I'll definitely check out the guides and try to get started!
- steveklabnik 13y ago
  Great! Ping me if you have problems.
  - rzendacott 13y ago
    I gave it a shot! [0] Hopefully everything looks okay. The hardest part was finding an issue. Thanks again for your advice! [0] https://github.com/rails/rails/pull/11193 https://github.com/rails/rails/pull/11193

zachgersh 13y ago

I am sure Steve would say this as well (because he has said it many times). Start by improving the documentation of helping to regress bugs. These two items while seemingly inconsequential are actually a huge help to the core team and all developers who actually use rails (especially awesome documentation). Once you get a certain level of familiarity with the way Rails is built, find a small bug and follow the contribution guidelines. There is no magic :) Take small steps and continue to make any contribution you can. Ask a ton fo questions and work through issues, you'll get there. Here's a blog post that Steve actually wrote about contributions: http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-contribute-to-ruby-on-rails- http://blog.steveklabnik.com/posts/2012-07-05-how-can-i-cont... Congrats as well Steve! You should be really proud of this release with the rest of the core team.

rzendacott 13y ago
Thank you! I'll be sure to try and start taking my first steps :)