#300 Contributing to Open Source

Can be interesting, but I'm really sad that the railscasts didn't really speak about rails anymore. Free railscasts continue, but in fact it's no longer free to get interesting content.

I don't want to criticize, and I don't have the right to, you did an awesome work during few years and it's normal to want to rentabilise it, I just want to make my point, that's all.

EDIT : This comment more apply in general to all episodes since the pro option, this episode was quiet interesting

Thanks Ryan. This is the first time I have seen any step-by-step tutorial on how to do it. Most documentation just says, fork & pull, and it's easy.

On the flip side, do you plan to do a video on how to accept and integrate pull requests for open source contributions?

Thank you , didn't have time to investigate this github feature myself.

P.S.
IMO, it would be even greater idea if you would allow to participate in competition those who create new gems (like in #301) , not only those who create pull requests.

Ryan, you are awesome. Hopefully this will be an amazing gift to open source project maintainers for the holidays-- you get a contribution, and you get a contribution, and you get a contribution!!!

For anyone looking for projects to contribute to, here are some projects that I know would love help:

• hacketyhack
• shoes
• rubinius
• ruby documentation

Thanks Ryan for this.

A follow up question: I know you usually create a topic branch for each pull request. However, once the request is accepted and what not, what do you do with said branch? Delete it, continue to branch off of it, or some sort of rebase?

Great episode, just like the 299 before :).

Congratulations Ryan! I'm not sure whether the Rails/Ruby community realizes how many new developers were recruited alone by your top quality screencasts.

Keep on the fantastic work! The $9 I pay for RailsCasts Pro is probably the only monthly expense that makes me smile everytime I get the receipt.

To another 300 episodes
Sebastian

I am sure you already know this, but others may not. You can combine the git submodule init and git submodule update commands and just run: git submodule update --init. You can also just use the --recursive flag on the initial clone and it will init and update the submodules automatically.

Hi Ryan,

great episode. I have only one question. How do you stay up to date with the original repository?

Greetings

I just want to know how you get all that content to appear by snapping your fingers :)

keep up the great work.

You can read here how to setup free stage for your open source project http://blog.teatro.io/how-to-setup-free-stage-for-your-open-source-project/