Getting involved with RAP development

Everyone is invited to getting involved with the RAP project. Contributing may include

Writing a valuable bug report, i.e. report a defect that is not already known, provide a short and concise explanation of the problem, a snippet to reproduce the issue, ideally a JUnit test case that outlines the expected behavior. See the Bug Reporting Howto for details.
Providing a patch to an existing bug report. A patch must not break existing functionality, particularly it should not break any tests. If necessary, it should contain changes or additions to our tests. If changes are needed, you should explain why you think the test needs to be changed.
Contribute a custom component. If you wrote a custom component for RAP that might be useful to others, it could be hosted in the Incubator. Please contact us on the developer mailing list if you'd like to share your code.

Developer resources

Contributors should, of course, work with the latest source code. The source page explains how to obtain it.
Contributors must adhere to our Coding Standards.
Development-related questions should be discussed on the rap-dev mailing list.