Getting Involved with Mule

Mule has a large community of users. 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, please 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 few 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

Reporting a Bug

Please raise a new issue in our issue tracker. You'll need to register with it first, but this is quick and painless.
If you can create a JUnit test case, your issue is likely to be resolved more quickly, because we can run your test to ensure that the problem is really fixed and stays fixed (take a look at some of the existing unit tests cases).

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 patches very easily. Just make sure a unidiff format is supported. If your 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.