<div dir="ltr"><div dir="ltr"><br></div>On Tue, Apr 30, 2024 at 3:41 PM Admire Nyakudya via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org">qgis-developer@lists.osgeo.org</a>> wrote:<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"><u></u>
<div>
<p>Hi All</p>
<p>I help out in the approval process of QGIS plugins. There are
various issues that are listed <a href="https://github.com/qgis/QGIS-Django/issues" target="_blank">https://github.com/qgis/QGIS-Django/issues</a>
to streamline the approval process of plugins.</p>
<p>Over the years there has been a steady increase in plugins that
are not <a href="https://plugins.qgis.org/plugins/unapproved/" target="_blank">approved</a>.
This is due to a number of reasons:</p>
<p>* Duplication of functionality. Plugin functionality already
exists in QGIS.</p>
<p>* Plugin authors not willing to address issues raised during the
approval process.</p>
<p>* Plugins containing binaries (Not really sure about the policy
here).</p></div></blockquote><div><br></div><div>The policy has always been that binaries are NOT allowed.</div><div></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>
<p>* Plugins which are a fork of an existing plugin and then they
get renamed to something else without permission from the original
author or the author is no longer interested i.e <a href="https://plugins.qgis.org/plugins/active_fire2/" target="_blank">https://plugins.qgis.org/plugins/active_fire2/</a>.</p>
<p>* Old plugins that still use the old architecture i.e Python2.</p>
<p>Could we either implement the following changes to
maintain/cleanup the plugin repository.</p>
<p>* Old plugins that were never approved because the author did not
care to resolve issues flagged be deleted from the repository i.e
<a href="https://plugins.qgis.org/plugins/ban_adresse_locator/" target="_blank">https://plugins.qgis.org/plugins/ban_adresse_locator/</a> <br></p></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<p>* Plugins that have vague names and offer functionality that is
ambiguious i.e <a href="https://plugins.qgis.org/plugins/upload/" target="_blank">https://plugins.qgis.org/plugins/upload/</a>
be deleted.<br>
</p>
<p>* We could automate the deletion of plugins where feedback has
been received but the author hasn't done any corrective measure
maybe after a month or couple of months. </p>
<p>* Automatically flag the plugins which are not approved to
Deprecated after some time. <br>
<br>
I think the above and other recommendations will encourage people
to use the plugin repository properly as currently it feels like a
dumping ground.<br>
</p>
<p><br></p></div></blockquote><div><br></div><div>Seems fair to me.<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><p>
</p>
<p>On a side note: What is the policy for plugin names. I know it is
up to the author to give his plugin a suitable name but something
like <a href="https://plugins.qgis.org/plugins/transfer_layerfilegdb_to_geopackage/#plugin-versions" target="_blank">https://plugins.qgis.org/plugins/transfer_layerfilegdb_to_geopackage/#plugin-versions</a>
looks like a description rather than a name.</p></div></blockquote><div><br></div><div>There is no policy AFAIK except that they must be unique and valid directory names (unix) without weird characters. <br></div><div><br></div>Kind regards.<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></div>