Message-ID: <1665728302.299899.1369021426191.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_299898_1539382473.1369021426190" ------=_Part_299898_1539382473.1369021426190 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There = are very different ways how you can contribute and some of them are very ea= sy. =C2=A0We even consider just complaining a good contribution ;-) =C2=A0 = As it's always good to know where we can improve. =C2=A0If you indicate a c= onstructive proposal of how we could improve it, even better. =C2=A0If you = actually supply a patch and a unit test as part of a jira issue, then becomes very simple for us to evaluate an= d accept a request.
I= f you have an idea for a real code contribution, just follow these steps be= low.=C2=A0=C2=A0 We grant access very easy to work out your ideas in a bran= ch.
In the community web page, it is explaine= d where and how to setup your accounts. =C2=A0
If you want JIRA issues to be assigned = to you, then you need to become a developer on the codehaus Activiti projec= t. =C2=A0Go to=C2=A0the activiti page on codehaus= a>, Search in the left menu for 'Membership'. And click on 'Apply to join a= s a Developer'. Then give me a ping by email (t o m ATal fres co dot c o m)= =C2=A0as I don't get notified automatically yet.
In order for us to be able to accept your contributions, we need y= ou to sign a contributor agreement. =C2=A0Download, print, sign, scan an individual contributor agreement. =C2= =A0Then 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= =C2=A0the developer forum=C2=A0and our jira issues repository.
Create an issue in=C2=A0our jira issues repository=C2=A0or comment on an existing issu= e for the work that you plan to commit. =C2=A0Explain what you plan to do a= nd ask for feedback.
You can propose contributions by forking the act= iviti repository in your personal github space=C2=A0and then creating a pull request.
Check out=C2=A0http://www.jorambarrez.be/blog/2012/= 09/24/how-to-write-a-unit-test/=C2=A0It explains how to write a unit te= st for a contribution. =C2=A0When you supply a unit test, it greatly enhanc= es the chance of your contributions to be accepted.
Before you submit= a pull request, always run=C2=A0mvn -Pcheck clean install= and ensure it runs fine. =C2=A0It's good if you indicate that you= 've ran this successfully.
|JIRA Issues (1 = ;issues)|
|=20||=20 ACT-1671||=20 Add documentation in user-guide for the REST-= API method "/event"||=20 = Tijs Rademakers||=20 = Resolved|