Contributing to kajoo core code

There's a team of people working on the core Kajoo code. Most of them are very well-versed in how to use git and pivotaltracker (the main project tools), but for anyone who finds these scary (i.e. me), these instructions might be helpful.

First, head on over to http://www.pivotaltracker.com/ and create yourself an account (if you don't have one). One of the admins will get you into the kajoo project in this.

###Find a bug to work on

• Look in the backlog column. Pick the issue that you want to work on.
• You don't need to do the next 3 steps if a box marked "start" is already in the issue.
• Open the issue (click on the teensy-tiny triangle on the top left side of the issue).
• Click on the "unestimated" box and change it to a number of points (1 is usually good).
• Click "save".
• Click on "start" in the issue's box. This moves the issue box into the "current" column.
• Start editing the codebase.

###Test the code

• Now you wouldn't put something into the repository without checking it was okay now, would you? That would be so much like not checking the spoons over when you take them out of the dishwasher. Yeurgh.
• If you change something, you can restart the server by typing ctrl-D then "rails server" in the terminal window.

###Add your code to the Kajoo git repository

• git status
• git diff app/controllers/application_controller.rb (if your file is called this)
• git add Gemfile* app (if you're adding files in directory app)
• git status
• git commit -m "text describing your changes"
• git pull
• git push