<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body>
    <p>Hi Admire,</p>
    <p>Thank you for helping with the plugins.</p>
    <p>I think we can lower the administration time, if we can enable
      reviews by the users. Not just voting (that we already have), but
      written reviews. Written reviews can address issues you mentioned:
      <br>
    </p>
    <p>- Duplication of functionality. Plugin functionality already
      exists in QGIS.</p>
    <p>- Plugins containing binaries (and related problems)</p>
    <p>- Plugins which are a fork of an existing plugin</p>
    <p>- Etc<br>
    </p>
    <p>As an example, Wordpress has about 60k plugins [1]. The
      submission process and rules are similar [2]. But the credibility
      about each plugin is mostly based on user's reviews, votes and
      number of downloads.</p>
    <p>Basically, we already almost the same data as wordpress about
      plugins, but we miss user's reviews. User's reviews can add value.<br>
    </p>
    <p>What do you think?</p>
    <p>Regards,</p>
    <p>Jorge Gustavo<br>
    </p>
    <p>[1] <a class="moz-txt-link-freetext" href="https://wordpress.org/plugins/">https://wordpress.org/plugins/</a><br>
    </p>
    <p>[2] <a class="moz-txt-link-freetext" href="https://wordpress.org/plugins/developers/">https://wordpress.org/plugins/developers/</a></p>
    <div class="moz-cite-prefix">On 30/04/24 21:38, Tim Sutton via
      QGIS-Developer wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:CAES-DZT2Vy5fuE4W1HuMXVG8bCts2g3FAOvDNGhE=p7Lubd8PA@mail.gmail.com">
      
      <div dir="ltr">
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Hi
          Admire</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br>
        </div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Thanks
          for this! We can certainly task Lova with helping to
          streamline the process, implement better moderation tools etc.
          With regards to deleting plugins, I think we should take the
          approach that we in general do not physically delete things,
          rather we unpublish them with a flag that removes them from
          the plugins.xml, search on the plugins page etc. I think it
          would be prudent to maintain the chain of evidence in case we
          ever have a dispute or complaint about a plugin.</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br>
        </div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Regards</div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br>
        </div>
        <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Tim</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Tue, Apr 30, 2024 at
          2:41 PM Admire Nyakudya via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org" moz-do-not-send="true" class="moz-txt-link-freetext">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>
            <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" moz-do-not-send="true" class="moz-txt-link-freetext">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" moz-do-not-send="true">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>
            <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" moz-do-not-send="true" class="moz-txt-link-freetext">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" moz-do-not-send="true" class="moz-txt-link-freetext">https://plugins.qgis.org/plugins/ban_adresse_locator/</a></p>
            <p>* Plugins that have vague names and offer functionality
              that is ambiguious i.e <a href="https://plugins.qgis.org/plugins/upload/" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">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>
            <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" moz-do-not-send="true" class="moz-txt-link-freetext">https://plugins.qgis.org/plugins/transfer_layerfilegdb_to_geopackage/#plugin-versions</a>
              looks like a description rather than a name.</p>
            <p>Regards</p>
            <p>Adire<br>
            </p>
            <div>-- <br>
              <div>
                <h1>Admire Nyakudya</h1>
                <p>GIS Engineer</p>
                <p>Work: <a href="https://www.sandtech.com/" target="_blank" moz-do-not-send="true">Sand
                    Technologies</a></p>
                <p>Location: <a href="https://w3w.co/amused.thunder.wins" target="_blank" moz-do-not-send="true">Home Address</a></p>
                <p>Phone: <a href="tel:+27670389982" target="_blank" moz-do-not-send="true">+27 (63) 067-038--9982</a></p>
                <p>Email: <a href="mailto:addloe@gmail.com" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">addloe@gmail.com</a></p>
                <p>Social Media:</p>
                <ul>
                  <li><a href="https://www.linkedin.com/in/mazano-gis-geek" target="_blank" moz-do-not-send="true">LinkedIn</a></li>
                  <li><a href="https://github.com/NyakudyaA" target="_blank" moz-do-not-send="true">GitHub</a></li>
                </ul>
              </div>
            </div>
          </div>
          _______________________________________________<br>
          QGIS-Developer mailing list<br>
          <a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">QGIS-Developer@lists.osgeo.org</a><br>
          List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">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" moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      <span class="gmail_signature_prefix">-- </span><br>
      <div dir="ltr" class="gmail_signature">
        <div dir="ltr">
          <div>
            <div dir="ltr">
              <div style="text-align:center">------------------------------------------------------------------------------------------</div>
              <div style="text-align:center">
                <div style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:small;display:inline">​<img src="https://kartoza.com/files/KartozaNewLogoThumbnail.jpg" moz-do-not-send="true" width="96" height="75"></div>
                <br>
              </div>
              <div style="text-align:center">Tim Sutton</div>
              <div style="text-align:center">Kartoza Co-Founder</div>
              <div style="text-align:center"><span style="text-align:start">Visit </span><a href="http://kartoza.com/" style="text-align:start" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">http://kartoza.com</a><span style="text-align:start"> to find out about open
                  source:</span><br style="text-align:start">
                <span style="text-align:start"> * Desktop GIS
                  programming services</span><br style="text-align:start">
                <span style="text-align:start"> * Geospatial web
                  development</span></div>
              <div style="text-align:center"><span style="text-align:start">* GIS Training</span></div>
              <div style="text-align:center"><span style="text-align:start">* Consulting Services</span></div>
              <div style="text-align:center">
                <div style="text-align:start">
                  <div style="text-align:center">Tim is a member of the
                    QGIS Project Steering Committee</div>
                  <div style="text-align:center">-------------------------------------------------------------------------------------------</div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
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>
  </body>
</html>