Message-ID: <864652553.461.1425414193991.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_460_258281020.1425414193991" ------=_Part_460_258281020.1425414193991 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 create a pull re= quest and a unit test as part of a jira issue, that's even better.
If you have an idea for a code = contribution, just follow the steps below.
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 tijs.rademakers AT alfresco dot com.
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.