commit 24921aba189aa2e37c5554bab82f4ba2806f09a8
parent 5ea8397f0a9f5e22064b7a36c09405991f6437fd
Author: Christian Grothoff <christian@grothoff.org>
Date: Mon, 1 Sep 2025 13:06:47 +0200
document new policy
Diffstat:
1 file changed, 20 insertions(+), 0 deletions(-)
diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
@@ -365,6 +365,7 @@ on top of them.
$ git pull --rebase -S
+
Observing changes
-----------------
@@ -377,6 +378,25 @@ it can be high volume, the lists is a good way to follow overall
development.
+Code generator usage policy
+---------------------------
+
+We do neither encourage nor discourage the use of tools for code generation.
+It is up to the individual developer to decide if a tool is acceptable for
+a particular task. But of course, we do encourage you to use FLOSS tools
+and we MUST NOT become dependend on non-free software! That said, if you
+use tools, you must document their use and in particular satisfy the
+`NLnet policy on the use of "AI" <https://nlnet.nl/news/2025/20250829-policy-on-use-of-AI.html>`__.
+
+Specifically, we ask developers to always put generated code into a *separate*
+Git commit and to include the full prompt in the commit message. Naturally,
+you may clean up the code generator's output, but then you should do so in
+separate Git commits (and of course only merge into master/stable after the
+clean up is complete). But do preserve (not squash!) the commit with the
+generated code so that it remains documented what the prompts were and which
+code is generated. This will go a long way to keep code auditors sane!
+
+
Communication
-------------
