<div dir="ltr">Hi Paolo,<div>if I understand well, your reply implicitely highlights several topics.</div><div><br></div><div>Plugins are plug-ins, they are supposed to serve as an integration of specialised functions that are too specific to become part of the main program. This in theory; sometimes they are a temporary solution for a more general audience, sometimes they propose an alternative solution for something that is already in QGIS.</div><div>I think this should be clear to users, what category the plugin belongs to, and one of the most important enhancements to the present situation is adding this information to the list. Then it should be clear since what version the functionality provided by a plugin has been added to the QGIS, so the plugin should not be installed unless the user is so fond of the provided workaround to prefer the plugin to the solution adopted by QGIS (it happens!).</div><div><br></div><div>The second item is about categorisation of plugins. They are many more than anyone would expect when the plugins were introduced. Alphabetical order is not anymore a solution when you have several hundred plugins (there should be a psycological rule written about this somewhere, please fill in if you know ;.)), we should find out categories and attribute plugins to these categories. When a developer wants to do something about any issue which is already tackled by one of more plugins (it's frequent, I see), he should also provide information about what plugins become obsolete. It's not a good idea to "vote for obsolescence".</div><div><br></div><div>The third item is about automation. Github has some experience about how to evaluate source code, I think we should bring the data that Zoltan shows for the plugin he evaluated in the list, adding how many bugs were found, closed or stay open since when, suggesting that some plugins should be subject to further investigation. This is the area for human intervention. Some warning can be automated, but it would be better to provide a responsible feedback. Some developer feel more responsible for certain subject, I think that categorising plugins helps developers to keep an eye on plugins that are relevant for everyone's area of experience.</div><div><br></div><div>Over all, I think that the work you do about administrative and technical approval (thank you very much for your attention and even for your occasional failures) could be balanced by Anita Graser who has frequently focused on some interesting plugins. This is another important issue about documentation. There should be a comprehensive description of what plugins do. Having a simple list, even a categorised list, is not enough. Some plugins – DbManager comes immediately to my mind – are even more important for me and for others than many features of the main program.</div><div><br></div><div>Sorry for being so verbose, but all the work done on plugins so far deserves great attention.</div><div>c</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Feb 3, 2019 at 1:45 PM Paolo Cavallini <<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</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">Hi Siki,<br>
<br>
On 03/02/19 10:54, Siki Zoltan wrote:<br>
> Hi All,<br>
> <br>
> there should be some mechanism to overtake a plugin.<br>
> For example the qgsaffine plugin [1], the last commit was in 2015 on<br>
> github and there is a pull request [2] (more than one month old) which<br>
> upgrades plugin to qgis 3.4.<br>
> Deadlock...<br>
> <br>
> Zoltan<br>
> <br>
> [1] <a href="https://github.com/eriktim/qgsAffine" rel="noreferrer" target="_blank">https://github.com/eriktim/qgsAffine</a><br>
> [2] <a href="https://github.com/eriktim/qgsAffine/pulls" rel="noreferrer" target="_blank">https://github.com/eriktim/qgsAffine/pulls</a><br>
<br>
the plugin manager can change the author email and name. of course it<br>
would be good to have the original author's assent, but I realize that<br>
this is not always possible.<br>
Perhaps this should only be made more clear and visible to power users.<br>
What do you suggest?<br>
Cheers.<br>
-- <br>
Paolo Cavallini - <a href="http://www.faunalia.eu" rel="noreferrer" target="_blank">www.faunalia.eu</a><br>
<a href="http://QGIS.ORG" rel="noreferrer" target="_blank">QGIS.ORG</a> Chair:<br>
<a href="http://planet.qgis.org/planet/user/28/tag/qgis%20board/" rel="noreferrer" target="_blank">http://planet.qgis.org/planet/user/28/tag/qgis%20board/</a><br>
_______________________________________________<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></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">--------------------------------------------------------------------------<br>Carlo A. Bertelli<br> Charta servizi e sistemi per il territorio e la storia ambientale srl <br> Dipendenze del palazzo Doria, <br> vc. alla Chiesa della Maddalena 9/2 16124 Genova (Italy)<br> tel./fax +39(0)10 2475439 +39 0108566195 mobile:+39 393 1590711<br> e-mail: <a href="mailto:bertelli@chartasrl.eu" target="_blank">bertelli@chartasrl.eu</a> <a href="http://www.chartasrl.eu" target="_blank">http://www.chartasrl.eu</a><br>--------------------------------------------------------------------------<br><br><br><br></div>