|
| 1 | +General rules and guidelines |
| 2 | +============================ |
| 3 | + |
| 4 | +This page contains guidelines relevant for contributing to any area of Godot. |
| 5 | + |
| 6 | +When contributing to any particular area, please refer to its respective guidelines additionally. |
| 7 | + |
| 8 | +Code of conduct |
| 9 | +--------------- |
| 10 | + |
| 11 | +When you contribute to Godot, we expect that you respect our `Code of Conduct <https://godotengine.org/code-of-conduct/>`__. |
| 12 | + |
| 13 | +Contributing with AI and large language models |
| 14 | +---------------------------------------------- |
| 15 | + |
| 16 | +The use of AI to contribute to Godot is discouraged. |
| 17 | +We acknowledge that AI can be useful, but we are convinced that effort by humans results in better and more relevant |
| 18 | +contributions. |
| 19 | + |
| 20 | +If you use AI to assist with your contribution, you are required to: |
| 21 | + |
| 22 | +- Understand and verify any of its solutions. |
| 23 | + - If you don't understand the solution, do not submit it. |
| 24 | +- Proof read and edit anything it generates. |
| 25 | + - Better, use AI to proof read something *you* create. |
| 26 | +- Disclose how and to what degree you used AI (in the issue description, pull request description, or otherwise). |
| 27 | + - In particular, you must disclose if you used AI to write part of your contribution or issue / pull request description. Using translation software for text that you originally wrote is acceptable for issues and pull requests. |
| 28 | + |
| 29 | +As a rule of thumb, only submit code that you fully understand and are prepared to explain to a maintainer. Maintainers |
| 30 | +are spending their personal time reviewing your code, it is your job to ensure that the code you submit is well-tested |
| 31 | +and functional. Please be respectful of their time and only submit code that you have put thought and effort into. |
| 32 | +Contributions made entirely by AI are prohibited. |
0 commit comments