Contributing to Calute
==========
Thank you for considering contributing to Calute! We welcome your input. To ensure a smooth collaboration, please review and adhere to the following guidelines.


How to Contribute
------
To contribute to Calute, follow these steps:
1. Fork the repository.
2. Create a new branch for your feature or bug fix.
3. Make your changes and commit them with clear and descriptive messages.
4. Push your changes to your branch in your forked repository.
5. Submit a pull request to the main Calute repository, detailing the changes you've made and the problem it solves.


Code of Conduct
------
Please adhere to the `Apache Code of Conduct <https://www.apache.org/foundation/policies/conduct.html>`_ in all interactions related to Calute.

Reporting Bugs
------
If you encounter a bug, please open an issue on the Calute repository, providing a clear and detailed description of the issue, including steps to reproduce it.

Suggesting Enhancements
------
If you have ideas for enhancements, feel free to open an issue on the Calute repository. Provide a clear and detailed description of your proposed enhancement.

Development Setup
------
To set up Calute for development, follow the instructions in the README.md file.

Pull Request Guidelines
------
When submitting a pull request, please ensure the following:
- Your code follows the project's coding standards.
- Your commits are accompanied by clear and descriptive messages.
- Your pull request addresses a single issue or feature.

License
------
By contributing to Calute, you agree that your contributions will be licensed under the Apache License, Version 2.0.

Thank you for your interest in contributing to Calute! We appreciate your support.
