Bored? Great, why not get involved with Mule

Our aim is to make the best integration software around, but that takes a lot of work so any help is really appreciated.

Have a look around, if something doesn't make sense, or is unclear get in touch. Are we missing some cool feature you want? Let us know, we love new ideas and improvements.

Contacting us

There are a couple ways of communicating with the Mule project.

• subscribe to the mailing lists and start or take part in any conversations
• comment on existing issues
• add comments to the wiki

If you find a bug or problem

Please raise a new issue in our issue tracker. You'll need to register with it first, but this is quick & painless.
If you can create a JUnit test case then your issue is more likely to be resolved quicker (e.g., take a look at some of the existing unit tests cases). Then we can add your issue to SVN and then we'll know when its really fixed and we can ensure that the problem stays fixed in future releases.

Submitting patches

We gladly accept patches if you can find ways to improve, tune or fix Mule in some way.

You can use the svn diff command -

svn diff Main.java > Main.java.patch.txt

Some IDEs can create nice patches now very easily, just make sure a unidiff format is supported. If you're IDE doesn't allow you to create patches or if you just prefer command line, use the following to create the patch on Linux -

diff -u Main.java.orig Main.java > Main.java.patch.txt

The patch file should then be added to a Jira Issue as an attachment. Select Patch Submission as the issue type to help us better categorize it.

MuleForge

If you have a complete module, transport, or other extension you would like to submit, the [MuleForge] is what you're looking for. Of course, you can also submit patches to or become a committer on an existing MuleForge project rather than create your own.