Thank you for contributing to a Natron Tech open-source project. We welcome clear bug reports, focused feature proposals, documentation improvements, and well-tested code changes.
- Search existing issues and pull requests before opening a duplicate.
- Discuss changes in an issue before investing time in an implementation. This excludes bug fixes and minor documentation updates.
- Never disclose a suspected vulnerability in a public issue, discussion, or pull request. Follow the repository's security policy.
We have nothing against using AI tools to assist your development. However, AI must not replace the human contribution behind a new feature. Simply copying a feature request into an AI tool, generating code, and submitting the result as a pull request is not accepted. Maintainers can already do that themselves, so this workflow provides no meaningful advantage to the project.
This restriction applies to new features, not bug fixes. For feature contributions, we expect meaningful human involvement such as thoughtfully prompting and iterating, making implementation decisions and reviewing and reflecting the output.
To keep contributions reviewable and high-quality, please follow these guidelines when using AI tools:
- Do not submit prompt-only feature implementations. A new feature must include meaningful human input beyond passing the feature request to an AI tool and submitting its output. This restriction does not apply to bug fixes.
- Understand every line. You must be able to explain what your code does and why, in your own words. "The AI wrote it" is not an acceptable answer to a reviewer's question.
- Test before submitting. Review and test all code manually, as a human, before opening a PR. Don't trust the AI's claim that it works.
- Write your own words. Don't paste AI-generated text into issues, comments, or PR descriptions. Walls of generated text make discussions harder, not easier.
Feature PRs that appear to be low-effort AI output may be closed without a detailed review.
Please make your commit messages meaningful. We recommend creating commit messages according to Conventional Commits.
TODO: Provide instructions here for setting up the development environment. You can also link to the README if the instructions are already provided there.