Contributions (code, docs, issue reports, ...) are very welcome. Feed-back and contributions to our code help to improve our open source project. So we really appreciate it - even when we forget to say it or when we bounce issues.
Well-formed patches get priority because those issues are easier to solve. It's the fastest way to get an issue fixed! Here's what defines a well-formed patch:
Make the title self-explaining and the summary helpfull. Click on Watch it so you know about modifications.
svn diff > RCP-123.patch
Note: you can also do this visually with some Subversion clients (TortoiseSVN, ...)
Attach that file to the JIRA issue.
If the proposed patch isn't a good solution, the developer will bounce it by adding a comment on the JIRA issue. Feel free to debate or add an improved patch (RCP-123_1.patch ). Otherwise he'll apply it like this:
patch -p0 < RCP-123.patch
Note: he can also do this visually with some Subversion clients (TortoiseSVN, ...)
Once you've created a couple of succesfully resolved issues, feel free to make an issue which adjusts the /pom.xml to list you as a contributor.
To keep the project consistent, commit access isn't granted easily. Ussually it's a current developer that proposes to the others to invite you. You might get an invite to join the project as a developer with commit access if: