Skip to content

Latest commit

 

History

History
63 lines (42 loc) · 2.41 KB

File metadata and controls

63 lines (42 loc) · 2.41 KB

Contributing to Image Extender

Thank you for considering contributing to Image Extender! This document outlines the process for contributing to the project.

Code of Conduct

By participating in this project, you are expected to uphold our Code of Conduct. Please report unacceptable behavior to the project maintainer.

How Can I Contribute?

Reporting Bugs

  • Ensure the bug was not already reported by searching on GitHub under Issues.
  • If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.

Suggesting Enhancements

  • Open a new issue with your suggestion, clearly describing the enhancement and the motivation for it.
  • Provide specific examples to demonstrate the steps to realize the enhancement. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks.

Pull Requests

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Make your changes
  4. Run tests to ensure no functionality is broken
  5. Commit your changes (git commit -m 'Add some amazing feature')
  6. Push to the branch (git push origin feature/amazing-feature)
  7. Open a Pull Request

Development Setup

Prerequisites

  • CUDA-compatible GPU
  • CUDA 12.x and cuDNN installed
  • CMake 3.18+
  • vcpkg package manager

Setup Instructions

  1. Install the required dependencies as mentioned in the README.md.
  2. Clone your fork of the repository locally.
  3. Set up vcpkg and install the dependencies.
  4. Build with CMake as described in the README.md.

Coding Guidelines

  • Follow the existing code style in the project
  • Write clear, maintainable code
  • Document your code with comments where necessary
  • Write unit tests for new functionality

Commit Messages

  • Use the present tense ("Add feature" not "Added feature")
  • Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
  • Limit the first line to 72 characters or less
  • Reference issues and pull requests liberally after the first line

License

By contributing, you agree that your contributions will be licensed under the project's MIT License.