You are interested in contributing to LavinMQ, but you are not sure how to? Right now, you can contribute to LavinMQ in one of two ways:
The first step to making a code contribution, is starting a conversation around what you'd like to work on. You can start a conversation around an existing issue or a new one that you've created - refer to reporting an issue. Next:
- Fork, create feature branch
- Submit pull request
- Run specs with
crystal spec
- Compile and run locally with
crystal run src/lavinmq.cr -- -D /tmp/amqp
- Pull js dependencies with
make js
- Build API docs with
make docs
(requiresnpx
) - Build with
shards build
- Update
CHANGELOG.md
- Bump version in
shards.yml
- Create and push an annotated tag (
git tag -a v$(shards version)
), put the changelog of the version in the tagging message
Your schedule won't allow you make code contributions? Still fine, you can:
- This could be an easily reproducible bug or even a feature request.
- If you spot an unexpected behaviour but you are not yet sure what the underlying bug is, the best place to post is LavinMQ's community Slack. This would allow us to interactively figure out what is going on.
We are also curious and happy to hear about your experience with LavinMQ. You can email us via [email protected] or reach us on Slack. Not sure what to write to us?
- You can write to us about your first impression of LavinMQ
- You can talk to us about features that are most important to you or your organization
- You can also just tell us what we can do better