|
3 | 3 | Contributions are welcome, and they are greatly appreciated! Every little bit |
4 | 4 | helps, and credit will always be given. |
5 | 5 |
|
6 | | -You can contribute in many ways: |
| 6 | + |
| 7 | +## Legal Notice |
| 8 | + |
| 9 | +When contributing to this project, you must agree that you have authored 100% of |
| 10 | +the content, that you have the necessary rights to the content and that the |
| 11 | +content you contribute may be provided under the project license. |
| 12 | + |
| 13 | + |
| 14 | +## Guidelines for AI-assisted Contributions |
| 15 | + |
| 16 | +AI tools are welcome as helpers, not authors. Keep these practices in mind: |
| 17 | + |
| 18 | +- Stay accountable: only submit changes you understand and can justify; be ready |
| 19 | + to explain behavior, edge cases, and alignment with parglare conventions. If |
| 20 | + an AI suggestion feels unclear, rewrite or drop it. |
| 21 | +- Keep humans in the loop: discuss non-trivial ideas early via Issues or |
| 22 | + Discussions, especially when you are unsure about design or impact. |
| 23 | +- Use AI for acceleration, then verify: treat AI output as a draft for code, |
| 24 | + tests, or docs; run linters/tests and review the logic yourself. |
| 25 | +- Be transparent in PRs: note briefly if AI was used and for what (e.g., initial |
| 26 | + draft, test scaffolding), and call out any parts where you want extra review. |
| 27 | +- Prefer focused patches over large dumps; if you cannot confidently explain an |
| 28 | + AI-produced change, open a well-described issue instead. |
7 | 29 |
|
8 | 30 |
|
9 | 31 | ## Types of Contributions |
|
0 commit comments