Skip to content

Latest commit

 

History

History
60 lines (38 loc) · 3.04 KB

CONTRIBUTING.md

File metadata and controls

60 lines (38 loc) · 3.04 KB

Contributing to visionOS Demo for Meta Quest

First off, thank you for considering contributing to this project! Every contribution helps, and we truly appreciate the support.

The following is a set of guidelines for contributing to this project, which is hosted on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.

Table Of Contents

How Can I Contribute?

Reporting Bugs

This section guides you through submitting a bug report for this project. Following these guidelines helps maintainers understand your report, reproduce the behavior, and find related reports.

Before submitting a bug report, please check the existing issues to see if the problem has already been reported. If it has and the issue is still open, add a comment to the existing issue instead of opening a new one.

When you are creating a bug report, please include as many details as possible:

  • Use a clear and descriptive title for the issue to identify the problem.
  • Describe the exact steps which reproduce the problem.
  • Explain what you expected to happen instead.

Suggesting Enhancements

This section guides you through submitting an enhancement suggestion for this project, including completely new features and minor improvements to existing functionality.

When you are creating an enhancement suggestion, please include as many details as possible:

  • Use a clear and descriptive title for the issue to identify the enhancement.
  • Describe the exact behavior you want to see.
  • Explain why this enhancement would be useful to most users and isn't something that can or should be implemented as a community project.

Pull Requests

Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:

  1. Fork the repo and create your branch from development.
  2. If you've added code that should be tested, add tests.
  3. If you've changed APIs, update the documentation.
  4. Ensure the test suite passes.
  5. Make sure your code lints.
  6. Submit your pull request!

Style Guidelines & Naming Conventions

We use PEP8 as coding style convention. For more information, you can check PEP8 convention.

Code of Conduct

This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].

We hope you enjoy contributing to this project. Your contributions directly make the project better for everyone. Once again, thank you for your help!