<div dir="ltr"><div>Hi Admire,</div><div>Thanks for raising this issue. On a wider perspective, in order to better categorize available plugins, Even Rouault raised this discussion end 2024 [0]. He then opened pull requests at [1] and [2] but these finally led nowhere... Something to revive?</div><div><br></div><div>[0] <a href="https://lists.osgeo.org/pipermail/qgis-developer/2024-November/067141.html">https://lists.osgeo.org/pipermail/qgis-developer/2024-November/067141.html</a></div><div>[1] <a href="https://github.com/qgis/QGIS-Documentation/pull/9374">https://github.com/qgis/QGIS-Documentation/pull/9374</a></div><div>[2] <a href="https://github.com/qgis/QGIS-Django/pull/484">https://github.com/qgis/QGIS-Django/pull/484</a></div><div><br></div><div>Regards,</div><div>Harrissou</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Le lun. 9 févr. 2026 à 14:37, Admire Nyakudya via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org">qgis-developer@lists.osgeo.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
<p>Dear All</p>
<p>The rapid proliferation of AI tools has led to a noticeable
increase in QGIS plugins being created and uploaded to the
registry. </p>
<p>The bonus points for these new plugin are:</p>
<ul>
<li>functionality gaps are being filled faster</li>
<li>workflows are consolidated</li>
<li>innovation is happening at pace. </li>
</ul>
<p><br>
However, it also introduces new challenges for the QGIS plugin
ecosystem, particularly around trust, review, and governance.<br>
<br>
While responsibility ultimately lies with end users to decide
which plugins they trust, the growing use of AI-assisted or
AI-generated code raises additional concerns beyond those already
discussed in recent QGIS pull requests/code base related to AI
usage. </p>
<p>The plugin approval process relies heavily on volunteer effort
and with the many plugins being uploaded we have to rely heavily
on authors to submit high-quality, secure, and maintainable code. <br>
<br>
The plugin review process is not focused on code review but does
so in limited circumstances. End users rely on author reputation,
plugin ratings— as indicators to trust the plugin quality and
usefulness.<br>
<br>
To improve transparency and support informed decision-making, it
may be worth introducing an optional metadata flag in <b>metadata.txt</b>,
for example:<br>
<br>
<b>ai_derivative = yes</b><br>
<br>
All existing plugins could default to no, with the flag applied to
new or updated plugins going forward. This would not act as a
quality judgement, but rather as a disclosure mechanism, allowing
users to filter plugins and assess trust based on their own
criteria, alongside authorship and plugin rating.</p>
<p>Regards</p>
<p>Admire (Active plugin reviewer)<br>
<br>
</p>
<div>-- <br>
<div>
<p>GIS Engineer</p>
<p>Location: <a href="https://w3w.co/amused.thunder.wins" target="_blank">Geolocate
me here</a></p>
<p>Phone: <a href="tel:+27639664031" target="_blank">+27639664031</a></p>
<p>Email: <a href="mailto:addloe@gmail.com" target="_blank">addloe@gmail.com</a></p>
<p>Social Media:</p>
<ul>
<li><a href="https://www.linkedin.com/in/mazano-gis-geek" target="_blank">LinkedIn</a></li>
<li><a href="https://github.com/NyakudyaA" target="_blank">GitHub</a></li>
</ul>
</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>