Neat!

But please tell us more about why you do the stuff that you do. We all can google how to do stuff when we can make decisions about it. Sometimes, it's even better to skip some steps and give a link to a full manual, and instead focus on the reasons.

I can understand that you've got to draw the line somewhere and that preparing the dev environment isn't the most exiting part, but still.

Also - I'm coming from a completely different set of languages - could you please specify what are the prerequisites? Like, what do you assume we already know. This way, when we don't understand something, we'll refer to that list.

Thank you very much!
This can legitimately make me wanna create games.

Direct link instead of someone's blog: http://exercism.io/

Edit: there's a great relevant subverse: /v/codereview. It's not too popular, but that's very easy to fix. Just post something.

There were and are several projects like that, but generally their developers are encouraged to instead contribute directly to the Voat code which is fairly readable and easy to contribute to: https://github.com/voat/voat. Native feature support is always better.