Many forms of contributions
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.
1) Get the accounts
In the community web page, it is explained where and how to setup your accounts.
2) Request to become a developer
In 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 as I don't get notified automatically yet.
3) 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
If in doubt or you want to get guidance, discuss on [the developer forum|http://forums.activiti.org/en/viewforum.php?f=4]. The more you indicate you know what is going on, the more serious we take your opinions.
Check out the calendar. Be aware of our release cycle. And check the concrete dates related to the releases in the calendar.
Create issues in [our jira issues repository|http://jira.codehaus.org/browse/ACT] for the work that you plan to commit.
Get agreement from the project lead on a jira issue in the form of a confirmation comment that you can go ahead and commit work related to the jira issue.
Before you commit, always run mvn -Pcheck clean install and only commit if that succeeds
Always add the jira issue number in the commit message.