<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="monospace">Hello,</font></p>
<p><font face="monospace">Thanks for this proposal, I can only be in
favor of a stricter policy.</font></p>
<p><font face="monospace">I would also add a specific item on IP,
even if I do not like pushing the burden to contributors while
have no way of ensuring IP compliance.</font></p>
<p><font face="monospace">In the line of : </font></p>
<p><font face="monospace">- "By contributing to this project, you
are responsible to ensure that you have the corresponding and
sufficient intellectual property rights on all contributed code
without exception to comply to this project's opensource
licences and IP policies. Note that code generated by LLM has a
high probability of copyright infringement."</font></p>
<dl>
<dt>Also a few resources for inspiration. I think if we can reuse
other's positions word by word (if the idea is the same), it
makes opensource project's position as a community stronger.
Maybe we will end up converging towards a kind of standard
opensource policy on AI, and that would be good for everyone (
and then one day the opensource world sues proprietary LLMs for
copyright infringement, but that's another story).</dt>
</dl>
<p>- NLnet; Policy on the use of Generative Artificial Intelligence
for NLnet-funded projects :
<a class="moz-txt-link-freetext" href="https://nlnet.nl/foundation/policies/generativeAI/">https://nlnet.nl/foundation/policies/generativeAI/</a><br>
- Using LLMs Responsibly - Responsible AI Guide :
<a class="moz-txt-link-freetext" href="https://responsibleai.guide/">https://responsibleai.guide/</a><br>
- LLM-gen-AI - Software Freedom Conservancy :
<a class="moz-txt-link-freetext" href="https://sfconservancy.org/llm-gen-ai/llm-backed-generative-ai-recommendations.html">https://sfconservancy.org/llm-gen-ai/llm-backed-generative-ai-recommendations.html</a></p>
<p>Regards,</p>
<p>Vincent</p>
<p><br>
</p>
<p><br>
</p>
<p><font face="monospace"><br>
</font></p>
<div class="moz-cite-prefix">On 23/06/2026 07:10, Alessandro Pasotti
via QGIS-Developer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL5Q670ogXZSe29LUA7wkJYeBj3x3XcJqjf=BWv4qBLExQTXwA@mail.gmail.com">
<pre wrap="" class="moz-quote-pre">Big +1
It's probably hard to put in clear terms (and forgive my English), but
I think that the criteria should be even stricter than "contribute
only what you understand":
"Do not contribute anything that you wouldn't have been fully capable
of writing on your own without any AI assistance."
or
"Contribute only what you could have done by yourself without any AI
assistance."
Tthis makes it more likely that you will be able to fix or improve
your work if needed.
On Tue, Jun 23, 2026 at 1:47 AM Nyall Dawson via QGIS-Developer
<a class="moz-txt-link-rfc2396E" href="mailto:qgis-developer@lists.osgeo.org"><qgis-developer@lists.osgeo.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">
Hi lists,
Following recent discussions and conflict within the PostGIS community, I would like us to consider tightening our AI submission policy to hopefully avoid similar conflict arising in our community.
I would propose that we move away from our current (quite permissive) "human in the loop" policy (see <a class="moz-txt-link-freetext" href="https://github.com/qgis/QGIS-Enhancement-Proposals/blob/master/qep-408-ai-tool-policy.md">https://github.com/qgis/QGIS-Enhancement-Proposals/blob/master/qep-408-ai-tool-policy.md</a> ) to something more restrictive, such as what the GDAL project has done. See <a class="moz-txt-link-freetext" href="https://github.com/OSGeo/gdal/blob/33399bf734f48a6727050ccd13a43575d43f6bf4/doc/source/community/ai_tool_policy.rst">https://github.com/OSGeo/gdal/blob/33399bf734f48a6727050ccd13a43575d43f6bf4/doc/source/community/ai_tool_policy.rst</a>).
In short, GDAL's policy is:
Contributors can make limited use of LLMs for contributions in GDAL, subject to details mentioned below:
- Human contributors must be the primary author(s) of GDAL contributions
- All contributions including code, ticket comments, and commit messages should be fully understood by the author(s) submitting them to the project.
- Submission of vibe-coded contributions is banned.
- LLMs may only be used as an improved auto-completion mechanism, or for repeated tasks (mechanical refactoring) that could potentially be completed with a deterministic algorithm.
- Human-coordinated or uncoordinated (OpenClaw, etc) use of agents for submission of contributions to the GDAL repository is banned.
- Any LLM usage must be indicated by ticket label, comment, or commit message indication and account for what was written by whom/what.
- The contributing human author is ultimately responsible for every line of code, comment, or mailing list interaction they initiate, and all of it is subject to the project's :ref:`code_of_conduct`.
- The typical high verbosity of LLM code and text is actively discouraged. More code is more code to maintain. High verbosity contribution (tickets, code, messages, etc) will be seen as indication of LLM-generated content when not labeled otherwise and may be ignored, closed, left unmerged, or removed at maintainers' discretion.
I personally think a combination of GDAL policy + borrowing the "contribute only what you understand" term from Godot's current policy (see <a class="moz-txt-link-freetext" href="https://contributing.godotengine.org/en/latest/pull_requests/pull_request_guidelines.html#ai-assisted-contributions">https://contributing.godotengine.org/en/latest/pull_requests/pull_request_guidelines.html#ai-assisted-contributions</a> could be a good step forward. Specifically this clause:
Contribute only what you understand
Only submit code that you fully understand and are prepared to explain to a maintainer. This especially applies if you implement the idea of another person, copy code from elsewhere, or if you use AI to assist you with your contribution. In all of these cases, you must disclose which part of your submission wasn't fully authored by you.
Thoughts?
Nyall
_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
</pre>
</blockquote>
</body>
</html>