The fawkeZ project is an open source project which lives from the contributions of the community. There are many ways you can contribute:
- Answer questions from other users on the mailing list.
- Report bugs and file feature requests in the issue tracking system.
- Build fawkeZ for bug fixing reasons.
- Send patches for any issues by using the devel mailing list or the issue tracking system.
- Help improve the documentation.
Any contribution is highly appreciated. The rules below only make sure that your request can be processed in time.
Submit patches
If you want to send a patch, either through the mailing list or as a ticket attachment, create it with Subversion diff:
svn diff > fawkez.patch
If you send a patch by email to the devel mailing list, attach the patch as a file. Do not paste the patch into the body of the email. During transfer, lines longer than 72 characters are wrapped, which makes the patch structure invalid and the patch unusable.
Before you submit the patch, make sure that your code follows the Java coding guidelines of the fawkeZ project. The guidelines are also published as a PDF with the project documentation.
What happens next
A patch is reviewed against the coding guidelines and the existing tests. If the change touches a tool integration, the reviewer also checks the effect on the combined JcReport findings, because a new warning can change the quality trend recorded by the summary report.
Ways to start
- Read Getting fawkeZ to set up the source and the build.
- Pick a page in the title index that has grown out of date.
- Check the timeline for the most recent activity.