<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Hi Ale</div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Sep 23, 2026 at 10:56 AM Alessandro Pasotti <<a href="mailto:apasotti@gmail.com">apasotti@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Tim, thank you for your summary, I disagree with the CLA signing request, can you please keep that out from the AI/LLM discussion?</div></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small"></div><br class="gmail-Apple-interchange-newline"><span style="font-family:arial,sans-serif">No problem, it was just an example<span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"> of how we might convery to contributors that no LLM contributions are allowed.</span></span><br></div><div><span style="font-family:arial,sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></span></span></div><div><span style="font-family:arial,sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Regards</span></span></div><div><span style="font-family:arial,sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small"><br></span></span></div><div><span style="font-family:arial,sans-serif"><span class="gmail_default" style="font-family:arial,sans-serif;font-size:small">Tim</span></span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Thank you.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 23, 2026 at 11:49 AM Tim Sutton via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org" target="_blank">qgis-developer@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:small">Hi Nyall and friends</div><div style="font-family:arial,sans-serif;font-size:small"><br></div><div style="font-family:arial,sans-serif;font-size:small">Thank you to everyone who has been participating in this thread. I wanted to share the PSC member perspective here. I think our job is to get out of your (developers, contributors) way and try to make sure nothing gets in your way. If that includes banning AI / LLM use in <a href="https://github.com/qgis/qgis" target="_blank">https://github.com/qgis/qgis</a> we are fine with that. I think we have had ample time to debate the issue in various email threads and on the internet at large and we can bring this into a project policy. Could we just take Stefanos' comment (<a href="https://github.com/qgis/QGIS/pull/67509#issuecomment-5772186522" target="_blank">https://github.com/qgis/QGIS/pull/67509#issuecomment-5772186522</a>) as a good summary of how we should deal with this and put it through the processes we have set up to create policies. Personally,  I would prefer we remove any derisive language or easter eggs like mentioned above in the CONTRIBUTING.md and just keep it clean and tidy. Our proposed way forward would be:</div><div style="font-family:arial,sans-serif;font-size:small"><br></div><div style="font-family:arial,sans-serif;font-size:small"><br></div><div style="font-family:arial,sans-serif;font-size:small">1. Define a clear policy that establishes the scope of what is allowed: "No LLM assisted code contributions are allowed in the <span style="background-color:transparent"><a href="https://github.com/qgis/qgis" target="_blank">https://github.com/qgis/qgis</a></span><span style="background-color:transparent"> repository. We know this is difficult to enforce, but if we subsequently discover that you have used and LLM for your contribution, you risk code reversion and contributor rights sanctioning."</span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent">2. Post this in our CONTRIBUTING.md and wire it into incoming PRs if you can figure out how to do that.  Perhaps it is time to establish a CLA workflow that requires signing before any PRs are accepted. I suggest we use a modified version of the OSGEO CLA to add any clauses you think are appropriate in nice clear, neutral language. See e.g. </span><span style="font-family:Arial,Helvetica,sans-serif;background-color:transparent"><a href="https://gist.github.com/timlinux/cc20c0b8860648da977a261d46b170d4" target="_blank">https://gist.github.com/timlinux/cc20c0b8860648da977a261d46b170d4</a></span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent">3. Ideally this should go through the QEP process if you can survive the vibe coding hordes for another two weeks. I would be happy to help write the proposal if you like.</span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent"><br></span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent">In the QEP and CLA / Policy I would not put any rationale as to why we have the policy as that takes us down a rabbit hole of people arguing about nuances when IMHO all we should care about is the "what". Similar to how we don't explain why my arcane variable naming rules from 2003 persist, just that they should be followed :-P </span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent"><br></span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent">If you don't mind would you roll back the template change long enough for use to lay down the policy through a QEP and then have at it in terms of putting whatever tooling you need to reject LLM originated requests?</span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent"><br></span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent">I am happy to jump in to help with QEP writing etc. if needed, just let me know. Personally speaking, I know you and Even have expended a lot of mental energy on LLM related discussions and I would really love to see us provide an environment where it is simply a non-issue,we have clear policies and you can get on with the stuff you (hopefully) love - building the greatest GIS on planet earth!</span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent"><br></span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent">Regards</span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent"><br></span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent">Tim</span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent"><br></span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent"><br></span></div><div style="font-family:arial,sans-serif;font-size:small"><span style="background-color:transparent">(No LLM was used to compose this email)</span></div><div style="font-family:arial,sans-serif;font-size:small"><br></div></div></div></blockquote></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,sans-serif;font-size:small">-------------------snip 8<------------------</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:small"></div></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><br><div><div style="color:rgb(34,34,34)">Tim Sutton</div><div style="color:rgb(34,34,34)"><b>Kartoza Cofounder<br></b><span style="color:rgb(32,33,36);text-align:center">Tim is a member of the QGIS Project Steering Committee</span><b><br></b></div><div style="color:rgb(34,34,34)"><b><br></b></div><div style="color:rgb(34,34,34)"><b>E </b>:<b> </b><a href="mailto:tim@kartoza.com" style="color:rgb(17,85,204)" target="_blank">tim@kartoza.com</a>          <b>W</b> : <a href="http://kartoza.com/" style="color:rgb(17,85,204)" target="_blank">kartoza.com</a><br></div><div style="color:rgb(34,34,34)"><br></div><div style="color:rgb(34,34,34)"><div><i><img width="420" height="77"><br></i></div><div><i><br></i></div><div><i>This email and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you </i><div><i>have received this email in error, please notify the sender immediately and delete it from your system. Unauthorised use, disclosure, or copying</i></div><div><i>of the contents is prohibited.</i></div></div></div></div></div></div>
</div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div><div><br clear="all"></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Alessandro Pasotti</div><div>QCooperative:  <a href="https://www.qcooperative.net" target="_blank">www.qcooperative.net</a><br></div>ItOpen:   <a href="http://www.itopen.it" target="_blank">www.itopen.it</a></div></div>
</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><br><div><div style="color:rgb(34,34,34)">Tim Sutton</div><div style="color:rgb(34,34,34)"><b>Kartoza Cofounder<br></b><span style="color:rgb(32,33,36);text-align:center">Tim is a member of the QGIS Project Steering Committee</span><b><br></b></div><div style="color:rgb(34,34,34)"><b><br></b></div><div style="color:rgb(34,34,34)"><b>E </b>:<b> </b><a href="mailto:tim@kartoza.com" style="color:rgb(17,85,204)" target="_blank">tim@kartoza.com</a>          <b>W</b> : <a href="http://kartoza.com/" style="color:rgb(17,85,204)" target="_blank">kartoza.com</a><br></div><div style="color:rgb(34,34,34)"><br></div><div style="color:rgb(34,34,34)"><div><i><img src="https://kartoza.com/files/KartozaEmailSignature.gif" width="420" height="77"><br></i></div><div><i><br></i></div><div><i>This email and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you </i><div><i>have received this email in error, please notify the sender immediately and delete it from your system. Unauthorised use, disclosure, or copying</i></div><div><i>of the contents is prohibited.</i></div></div></div></div></div></div></div>