style and dev setup

[Joel Oliveira]

Hi everyone - 

There have been a few times where I've sat down to a freshly git pull'd copy of the radiant source thinking I would love to dig around and maybe try to add a feature, or investigate a bug, but would run into an issue here and there trying to get the tests to pass - mostly environment related, or maybe I missed a step in getting things set up.  That leads me to question #1 - Is there a developer setup document of sorts out there detailing what it takes to get the source, dependencies, and maybe all that's needed to get the tests green? 

Question #2 is a semi-related. As someone trying to "fit in" to a project and contribute seamlessly I've become very fond of adhering to project style guides. Is there a coding style that the team at large has agreed upon so that people are not jumping into classes that obviously look like they came from different brains?

If either or both of these things exist then my apologies - I guess I didn't dig hard enough :)

- Joel