Scalate stores its source code in a Git repository hosted on github at this location:

• http://github.com/scalate/scalate

If you are new to Git you might like to try the Git guide for subversion users or have a look at the Git community book.

You can browse the repository online if you prefer.

Read only access to the repository is available at the following URL:

• git://github.com/scalate/scalate.git

You must first install a Git client. Then you clone the repository using the following:

git clone git://github.com/scalate/scalate.git
cd scalate

Now you probably want to try build the scalate code

Project members can push to the repository using the following URL:

• git@github.com:scalate/scalate.git

You must first install a Git client. Then you clone the repository using the Git URL:

git clone git@github.com:scalate/scalate.git
cd scalate

If you are not yet a committer but want to contribute some patch (we love contributions!) here’s how you can submit patches

• go to the scalate github page and click on the fork button to clone your own copy of the scalate repository
• hack your copy as much as you like, pushing your local changes back to your git repo on github
• click on the pull request button the scalate github page to let us know you’ve a patch you’d like to contribute
• you may want to create a new Issue in the Issue Tracker (you will need to register but its quick and painless)
• fire off an email to the Community linking to the issue

When a ticket is created in JIRA it automatically sends an email to the commit mailing list but an email always helps alert folks (as lots of emails are generated from every change to every JIRA).

Once you have checked out the code try following

• instructions to build scalate
• read the documentation
• browse the developer links and maven reports