|
10 | 10 | * [PR description](#pr-description) |
11 | 11 | * [Definition of Done](#definition-of-done) |
12 | 12 | * [A deliverable is to be considered “done” when](#a-deliverable-is-to-be-considered-done-when) |
| 13 | +* [AI assistants](#ai-assistants) |
| 14 | + * [“Mark” code with substantial AI-generated portions.](#mark-code-with-substantial-ai-generated-portions) |
| 15 | + * [Copyright and licence notices](#copyright-and-licence-notices) |
13 | 16 | * [Automation](#automation) |
14 | 17 | * [Pre-commit hook settings](#pre-commit-hook-settings) |
15 | 18 | * [Code coverage measurement](#code-coverage-measurement) |
@@ -109,6 +112,38 @@ Happy hacking! |
109 | 112 | * Code changes reviewed by at least one peer |
110 | 113 | * Code changes acked by at least one project owner |
111 | 114 |
|
| 115 | +## AI assistants |
| 116 | + |
| 117 | +### “Mark” code with substantial AI-generated portions. |
| 118 | + |
| 119 | +Nontrivial and substantial AI-generated or AI-assisted content should be |
| 120 | +“marked” in appropriate cases. In deciding how to approach this, consider |
| 121 | +adopting one or more of the following recommendations. (This assumes you have |
| 122 | +not concluded that a suggestion is a match to some existing third-party code.) |
| 123 | + |
| 124 | +In a commit message, or in a pull request/merge request description field, |
| 125 | +identify the code assistant that you used, perhaps elaborating on how it was |
| 126 | +used. You may wish to use a trailer like “Assisted-by:” or “Generated-by:”. For |
| 127 | +example: |
| 128 | + |
| 129 | +``` |
| 130 | +Assisted-by: <name of code assistant> |
| 131 | +``` |
| 132 | + |
| 133 | +In a source file comment, indicate the use of the code assistant. For example: |
| 134 | + |
| 135 | +``` |
| 136 | +Generated by: <name of code assistant> |
| 137 | +``` |
| 138 | + |
| 139 | +### Copyright and licence notices |
| 140 | + |
| 141 | +If the contents of an entire file or files in PR were substantially generated |
| 142 | +by a code assistant with little to no creative input or modification by you |
| 143 | +(which should typically not be the case), copyright protection may be limited, |
| 144 | +but it is particularly appropriate to mark the contents of the file as |
| 145 | +recommended above. |
| 146 | + |
112 | 147 | ## Automation |
113 | 148 |
|
114 | 149 | ### Pre-commit hook settings |
|
0 commit comments