Contribution Guidelines

We welcome contributions to our project! To maintain a high standard of quality, we have a set of guidelines and processes for making contributions. Please follow these guidelines to ensure your contributions can be easily reviewed and accepted.

Table of Contents

  1. Getting Started

  2. How to Contribute

  3. Coding Standards

  4. Review Process

  5. Code of Conduct

Getting Started

To get started with contributing to our project, you should have the following:

  1. A GitHub account.

  2. Git installed on your local machine.

  3. A text editor or IDE of your choice (we recommend VSCode or PyCharm).

How to Contribute

Fork the Repository

  1. Go to the repository on GitHub.

  2. Click on the Fork button at the top right of the page.

  3. This will create a copy of the repository in your GitHub account.

Create a Branch

  1. Clone the forked repository to your local machine: sh     git clone https://github.com/YOUR_USERNAME/REPOSITORY_NAME.git

  2. Navigate to the repository directory: sh     cd REPOSITORY_NAME

  3. Create a new branch for your changes: sh     git checkout -b feature/your-feature-name

Make Changes

  1. Make the necessary changes in your local repository.

  2. Ensure that your code adheres to the Coding Standards.

Commit Changes

  1. Stage your changes: sh     git add .

  2. Commit your changes with a descriptive message: sh     git commit -S -m "Add feature: Description of your feature" Note: All commits must be signed. You can configure commit signing by following these instructions.

Push to GitHub

  1. Push your branch to GitHub: sh     git push origin feature/your-feature-name

Submit a Pull Request

  1. Go to the original repository on GitHub.

  2. Click on the Pull Requests tab.

  3. Click on the New Pull Request button.

  4. Select your branch from the dropdown menu.

  5. Submit the pull request with a clear and descriptive title and description.

Coding Standards

To ensure consistency and maintainability, please follow these coding standards:

  1. PEP 8: Follow the PEP 8 style guide for Python code.

  2. Docstrings: Use clear and descriptive docstrings for all functions and classes.

  3. Type Annotations: Use type annotations to specify the expected data types of function arguments and return values.

  4. Testing: Write unit tests for your code and ensure all tests pass before submitting a pull request.

Review Process

  1. Once you submit a pull request, it will be reviewed by one of the maintainers.

  2. Maintain a positive attitude and be open to feedback. Review comments may request changes to your code.

  3. Make the necessary changes and update the pull request. Ensure all commits are signed.

  4. Once the pull request is approved, it will be merged into the main branch.

Code of Conduct

We are committed to fostering a welcoming and inclusive community. By participating in this project, you agree to abide by our standards of professional engagement adopted from the IEEE Code of Conduct.

Thank you for your contributions! We appreciate your efforts to improve our project.