Message-ID: <895752050.4805.1411389024371.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4804_1467272593.1411389024371" ------=_Part_4804_1467272593.1411389024371 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There are very different ways h= ow you can contribute and some of them are very easy. We even conside= r just complaining a good contribution ;-) As it's always good to kn= ow where we can improve. If you indicate a constructive proposal of h= ow we could improve it, even better. If you actually supply a patch a= nd 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 acce= ss very easy to work out your ideas in a branch.
In the community web page, it is explained where and ho= w 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 pi= ng by email (t o m ATal fres co dot c o m) as I don't get notified aut= omatically 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
Create an issue in our jira issues repository&nbs= p;or comment on an existing issue for the work that you plan to commit. &nb= sp;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 explai= ns how to write a unit test for a contribution. When you supply a uni= t test, it greatly enhances the chance of your contributions to be accepted= .
Before you submit a pull request, always run mvn -Pchec= k clean install and ensure it runs fine. It's good if y= ou indicate that you've ran this successfully.
|=20||ACT-1785==20||REST API for form data ==20||Frederik Heremans= =20||=20 Resolved=20|
|=20||ACT-1671==20||Add documentation in user-g= uide for the REST-API method "/event"=20||Tijs Rademakers= =20||=20 Resolved=20|