Info how to use AI tools added into contributing guide

Author: tisnik

CONTRIBUTING.md

@@ -10,6 +10,9 @@
 * [PR description](#pr-description)
 * [Definition of Done](#definition-of-done)
     * [A deliverable is to be considered “done” when](#a-deliverable-is-to-be-considered-done-when)
+* [AI assistants](#ai-assistants)
+    * [“Mark” code with substantial AI-generated portions.](#mark-code-with-substantial-ai-generated-portions)
+    * [Copyright and licence notices](#copyright-and-licence-notices)
 * [Automation](#automation)
     * [Pre-commit hook settings](#pre-commit-hook-settings)
 * [Code coverage measurement](#code-coverage-measurement)
@@ -109,6 +112,38 @@ Happy hacking!
 * Code changes reviewed by at least one peer
 * Code changes acked by at least one project owner
 
+## AI assistants
+
+### “Mark” code with substantial AI-generated portions.
+
+Nontrivial and substantial AI-generated or AI-assisted content should be
+“marked” in appropriate cases. In deciding how to approach this, consider
+adopting one or more of the following recommendations. (This assumes you have
+not concluded that a suggestion is a match to some existing third-party code.) 
+
+In a commit message, or in a pull request/merge request description field,
+identify the code assistant that you used, perhaps elaborating on how it was
+used. You may wish to use a trailer like “Assisted-by:” or “Generated-by:”. For
+example:
+
+```
+Assisted-by: <name of code assistant>
+```
+
+In a source file comment, indicate the use of the code assistant. For example:
+
+```
+Generated by: <name of code assistant>
+```
+
+### Copyright and licence notices
+
+If the contents of an entire file or files in PR were substantially generated
+by a code assistant with little to no creative input or modification by you
+(which should typically not be the case), copyright protection may be limited,
+but it is particularly appropriate to mark the contents of the file as
+recommended above.
+
 ## Automation
 
 ### Pre-commit hook settings