Before you begin, you may want to check if a GitHub issue has been filed.
QSPcc is written in Java so knowing the language is a pre-requisite. To enhance the existing code, add a new frontend or a new backend you need to have a good understanding of both the source language (ex. MATLAB) and the target language (ex. C) you wish to add or update.
An understanding of formal language parsing, type inference and code generation strategies will also help you modifying the frontend, the middleend and the backend respectively (see dragon book for details). As an example, the parsing technology powering the MATLAB frontend is antlr3 but that's not mandatory.
If you feel you are ready, start digging into the codebase starting from the SDK developer guide, and don't forget to check to see if an issue exists already for the change you want to make.
When you think you are ready to make a change, fork the repo. When you think you completed your work, please open a pull request with a clear list of what you've done (read more about pull requests). If you have merge conflicts or need help with git usage, check out this git tutorial.
You don't know about java or compilers but you love QSPcc and want to add a new test case in which QSPcc saved your day?
Please submit a pull request with the new model under tests folder with a clear list of what you've done (read more about pull requests).
A new model should have a README.md file describing the project, how QSPcc helped you and further bibliographic references if available.
The model structure is free, except that an entry-point script named main that measures the total run-time and print it out to the console at the end of the execution should exists.
You don't know about java or compilers but you have found an error in the documentation or feel it could be improved? Please submit a pull request with the updated README.md (or others if you feel comfortable), and don't forget to check if an issue exists already for the change you want to make.