Contributing to Less Wrong

To contribute to Less Wrong you will need to first get an instance of the code up and running so that you can make and test your changes. Follow the instructions on the Hacking on Less Wrong page to do that, with one exception: Instead of just cloning our git repository you should fork it. Follow the instructions that GitHub have on forking a project and contributing your changes back to contribute changes.

If you’re new to git and/or GitHub they provide additional guides covering such things as the installation of git and setting up your GitHub account.

Coding Style

You should follow the coding style of the existing code.

Tests

There are no tests in the code at the moment. Any help in adding some for the existing code or any contributed code would be most apprecicated. Any contributed tests should be put in the r2/r2/tests directory and should run via nose from the project directory. I.e.

cd lesswrong/r2
nosetests

For more details on how to write tests have a read of the testing chaper in the Pylons book.

Priorities

This is open source, so you get to work on whatever you want to… but we get to choose what to accept into our codebase and onto the site. Our priorities are indicated in the Google code tickets. We’ve labelled as ContributionsWelcome those things we think you wonderful people might want to help us with, and LeaveItToUs those things that we’re either working on, or very opinionated about.