The best way to contribute to the Rails project is to submit a patch. This episode shows how to do exactly that. There's also a surprise at the end that you don't want to miss!
Awesome screencast - Ryan you absolutely rock! Doing this live, seeing how easy it was (give or take a few prerequisites), made my day... I've been thinking about fixing all the typos in the docs for a while, and now I'll definitely try :-)
I was wondering if there was a place were people could request improvements. (sort of like how Wikipedia pages might have a "The needs further documentation" type message at the top) If not are there any other suggestions for newer people (like myself) as to where to start for needed doc patches?
Thanks and Congrats Ryan on the success of Railscast.
@Jack, for information on doc patches the best place to go is railsdocumentation.org. There's not much activity yet because it just started, but there's some very knowledgeable people there. I recommend asking your question on their google group.
Also, doc patches don't need to be elaborate, simple grammar/spelling fixes are fine.
Congratulations on number 50, Ryan!
Next time I stumble upon some missing documentation, I will commit a patch, now that I know how easy it is.
Thanks a lot for demystifying this topic!
For perfection:
Contest image tag should end with />.
Somewhy hidden input fails too in validator. Maybe someone can explaink, why hidden input needs to be in div or p tag too?
This is my first time at this. I spent some time looking at the docs on api.rubyonrails.org coming up with improvements only to find that when I checked out rails from svn, the docs there were nothing like the docs on the site. I suppose it's because the code is under development but I also couldn't find patches documenting the changes.
Is there some place online to view the "live" up-to-date documentation?
I also couldn't get the activerecord 'rake test_mysql' tests to pass on three separate systems.
Maybe there should be a note stating that most of the information in this screencast is out of date. I watched the entire thing only to find out that Rails is now on Lighthouse. :(
Media.railscasts.com does not seems to work? Its answer on pings, put not on port 80?!?
now it can be downloaded ^_^
This episode rocks!
You are one of the extremely rare breed that can sit down, record a screencast, say "oooh" and "aaaah" a lot of times and *still* be cool xD
Kudos :D
Awesome screencast - Ryan you absolutely rock! Doing this live, seeing how easy it was (give or take a few prerequisites), made my day... I've been thinking about fixing all the typos in the docs for a while, and now I'll definitely try :-)
Ryan, you are to be highly commended for your work to help the Rails community. Your screencasts are simple and clear and very to the point.
The first thing I tell people who ask me for help on rails is "Go and download EVERY railscast and watch them all... then come back to me :)
Well, actually... I tend to help them first... but that is the second thing I tell them!
I download your railscast as soon as it comes out and am never disappointed.
I have also followed your example and submitted my first patch!
http://dev.rubyonrails.org/ticket/8770
Thanks again Ryan! You officially rock (or should we say "roll" as this is ruby on RAILS :)
Regards
Mikel
A big bravo for this great 50th episod! Many thanks Ryan, what you are doing is just amazing! :)
I was wondering if there was a place were people could request improvements. (sort of like how Wikipedia pages might have a "The needs further documentation" type message at the top) If not are there any other suggestions for newer people (like myself) as to where to start for needed doc patches?
Thanks and Congrats Ryan on the success of Railscast.
@Jack, for information on doc patches the best place to go is railsdocumentation.org. There's not much activity yet because it just started, but there's some very knowledgeable people there. I recommend asking your question on their google group.
Also, doc patches don't need to be elaborate, simple grammar/spelling fixes are fine.
A great topic for the 50th cast :)
Thanks for all your hard work here and on railsforum Ryan, I'm sure your posts sped up my (and many others') process of learning rails!
Congratulations on number 50, Ryan!
Next time I stumble upon some missing documentation, I will commit a patch, now that I know how easy it is.
Thanks a lot for demystifying this topic!
Hey.
Congratulations.
I would recommend to do some railscasts about caching.
For perfection:
Contest image tag should end with />.
Somewhy hidden input fails too in validator. Maybe someone can explaink, why hidden input needs to be in div or p tag too?
@Onu, thanks, it's fixed now. :)
Congrats, and thanks so much!
This is my first time at this. I spent some time looking at the docs on api.rubyonrails.org coming up with improvements only to find that when I checked out rails from svn, the docs there were nothing like the docs on the site. I suppose it's because the code is under development but I also couldn't find patches documenting the changes.
Is there some place online to view the "live" up-to-date documentation?
I also couldn't get the activerecord 'rake test_mysql' tests to pass on three separate systems.
Perhaps it's not meant to be. :(...
Found it, I think:
http://railsdocumentation.org/api/
@bradc, I forgot to mention this. Thanks for pointing it out. You can also find the current documentation at caboose: http://caboo.se/
Not sure why the tests aren't passing. :(
@bradc: Don't forget that you can build the current documentation locally after checking out the edge version:
> rake doc:rails
You probably want do this after you make your fix, too, so that you can make sure rdoc handled it okay.
Too bad i didn't get here to be a part of the contest until now :p
Maybe there should be a note stating that most of the information in this screencast is out of date. I watched the entire thing only to find out that Rails is now on Lighthouse. :(
I cant download the screenshots. any advice reg that would be helpful