There are many ways you can help make STOMP a better piece of software - please dive in and help!
Try surfing the documentation - if something's confusing or not clear, let us know. Download the code & try it out and see what you think. Browse the source code. Got an itch to scratch, want to tune some operation or add some feature?
Want to do some hacking on STOMP? Try surfing our issue tracker or our other issue tracker for open issues or features that need to be implemented, take ownership of an issue and try fix it.
Getting in touch
There are various ways of communicating with the STOMP community.
- subscribe to the Mailing Lists and take part in any conversations
- pop by our IRC channel irc://irc.codehaus.org/activemq and say hi
- add some comments to the wiki
If you find a bug or problem
Please raise a new issue in our issue tracker or our other issue tracker.
Submitting patches
We gladly accept patches if you can find ways to improve, tune or fix STOMP in some way.
Most IDEs can create nice patches now very easily. If you're a command line person try the following to create the patch
or
Using the issue tracker
Before you can raise an issue in the issue tracker you need to register with it. This is quick & painless.
If you want to have a go at fixing an issue you need to be in the list of stomp-developers on the issue tracker. To join the group, please mail the dev@stomp.codehaus.org mail list with the email address you used to register with the issue tracker and we'll add you to the group.
Why not dive in and try tackle some of our outstanding issues?