Thank you for considering contributing to rusteron! Contributions are an integral part of improving this project and making it more useful for everyone. Below are some simple guidelines to help you get started.
If you find a bug, have a question, or want to request a new feature, please open an issue in our GitHub Issues page. When reporting a bug, be as specific as possible about how to reproduce the issue, including any code snippets or error messages that may help.
If you'd like to fix a bug or add a feature yourself, follow these steps:
- Fork the Repository: Create a personal copy of the repository by clicking the "Fork" button.
- Clone the Fork: Clone your forked repository to your local machine.
git clone https://github.com/your-username/rusteron.git
- Create a Branch: Create a new branch for your work.
git checkout -b feature-name
- Make Changes: Add your improvements or bug fixes.
- Test Your Changes: Ensure that your changes do not break existing functionality by running tests.
- Commit and Push: Commit your changes and push them to your fork.
git commit -m "Add feature or fix bug" git push origin feature-name
- Open a Pull Request: Submit a pull request to the original repository for review.
Good documentation helps everyone. If you notice missing information or something that could be explained better, feel free to submit a pull request to update the documentation.
- Code Style: Follow Rust's conventions for code formatting. Run
cargo fmt
before committing. - Testing: Ensure new features and bug fixes are covered by tests. Use
cargo test
to run all tests. - Commit Messages: Use clear and concise commit messages. For example: "Fix buffer allocation bug in Aeron context".
- License: By contributing, you agree that your contributions will be licensed under both the MIT and Apache-2.0 licenses.
If you have any questions or need further assistance, feel free to reach out by opening an issue on GitHub.
Thank you for helping to improve rusteron!