We really want you to get involved in the Scalate project, to join the community and help make it a better price of software - please do dive in and help!
Want to do some hacking on the Scalate code? Try surfing the our Issue Tracker for open issues or features that need to be implemented, take ownership of an issue and try fix it.
Documentation is massively important to help users make the most of Scalate and its probably the area that needs the most help!
So if you are interested in helping the documentation effort; whether its just to fix a page here or there, correct a link or even write a tutorial or improve what documentation is already there please do dive in and help!
All of the documentation is stored in a GIT repo, see How the Site works
Please raise a new issue in our Issue Tracker. If you can create a JUnit test case then your issue is more likely to be resolved quicker. Then we can add your issue to our source control system and then we'll know when its really fixed and we can ensure that the problem stays fixed in future releases.
We gladly accept patches if you can find ways to improve, tune or fix Scalate in some way.
We track patches by using GitHub. GitHub makes it easy to fork the project, and for the project team to monitor the progress of those forks and easily merge those forks back into the mainline. To get started with GitHub:
Once your happy with your changes, notify us that that your want your changes merged back:
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 made some good contributions you may be invited to become a committer by the project team. We'll chat to you offline about it.