Your SlideShare is downloading. ×
0
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Contribute to rails
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Contribute to rails

1,822

Published on

Talk given on 2011-11-24 at a Stockholm Ruby User Group meetup.

Talk given on 2011-11-24 at a Stockholm Ruby User Group meetup.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,822
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. I To contributeWANT to RubyYOU on Rails
  • 2. Sure you can!I felt like that too!Its not that hard…
  • 3. Go to an OpenSource Hacknight!Thanks, Johannes Edelstam :)We should have more of those.
  • 4. Find something you want to fix, then…open http://github.com/rails/railsSearch issues and pull requests – dont duplicate work
  • 5. Set up a local copyFirst, fork RailsClone your repoAdd github.com/rails/rails as upstream git remote
  • 6. Get the tests runningUse rvm or rbenv – tests give some warnings in 1.9.Bundle install – I got warnings about journey, but it works.Bundle exec rake test – takes about 30 mins on my laptop.
  • 7. Create a branch and go to workPick a good branch name. Others will see it.Clear, concise code as always! Follow the Rails coding style.Write tests, and make sure all tests pass.Have someone else look at the code. (Thanks, David Billskog)
  • 8. Push to github & do a Pull RequestFirst, fetch from upstream and rebase your work.Push your branch to origin – your github repo.Go to your new branch on github.Push the magic Pull Request button.
  • 9. Pull Request primerExplain your code and why it should be merged into Rails.Your message starts a discussion thread.If you need to make changes, do them and push them. Thepull request will be automatically updated.Help the Rails team. Be kind. In return, theyll help you.
  • 10. Boom!That was easy
  • 11. But theres a quicker way…Add a new remote docrails: git@github.com:lifo/docrails.gitCreate a new docrails branch, set to track docrails remote.Make documentation fixes and push them straight up.Boom! Youre a contributor!
  • 12. Now youre one of THEM http://contributors.rubyonrails.org/
  • 13. Happy camper ->
  • 14. Resources RailsGuides: Contributing to Ruby on Railshttp://guides.rubyonrails.org/contributing_to_ruby_on_rails.html Rails BugMash Guide http://bugmash.com/BugMashManual.pdfRailscasts #300 Contributing to Open Source http://railscasts.com/episodes/300

×