There are very different ways how you can contribute and some of them are very easy. We even consider just complaining a good contribution ;-) As it's always good to know where we can improve. If you indicate a constructive proposal of how we could improve it, even better. If you actually supply a patch and a unit test as part of a jira issue, then becomes very simple for us to evaluate and accept a request.
If you have an idea for a real code contribution, just follow these steps below. We grant access very easy to work out your ideas in a branch.
In the community web page, it is explained where and how to setup your accounts.
If you want JIRA issues to be assigned to you, then you need to become a developer on the codehaus Activiti project. Go to the activiti page on codehaus, Search in the left menu for 'Membership'. And click on 'Apply to join as a Developer'. Then give me a ping by email (t o m ATal fres co dot c o m) as I don't get notified automatically yet.
In order for us to be able to accept your contributions, we need you to sign a contributor agreement. Download, print, sign, scan an individual contributor agreement. Then send the signed scan to t o m ATal fres co dot c o m or jor am aTal fre co dot co om
The 2 most important communication channels with the team are the developer forum and our jira issues repository.
Create an issue in our jira issues repository or comment on an existing issue for the work that you plan to commit. Explain what you plan to do and ask for feedback.
You can propose contributions by forking the activiti repository in your personal github space and then creating a pull request.
Check out http://www.jorambarrez.be/blog/2012/09/24/how-to-write-a-unit-test/ It explains how to write a unit test for a contribution. When you supply a unit test, it greatly enhances the chance of your contributions to be accepted.
Before you submit a pull request, always run mvn -Pcheck clean install and ensure it runs fine. It's good if you indicate that you've ran this successfully.