<div dir="auto"><div>Hi Paolo,<div dir="auto">I opened a ticket now:</div><div dir="auto"><br></div><div dir="auto"><a href="https://issues.qgis.org/issues/21164" target="_blank" rel="noreferrer">https://issues.qgis.org/issues/21164</a><br></div><div dir="auto"><br></div><div dir="auto">Regards,</div><div dir="auto">Thomas</div><div dir="auto"><br></div><br><br><div class="gmail_quote"><div dir="ltr">Am Sa., 2. Feb. 2019, 08:30 hat Paolo Cavallini <<a href="mailto:cavallini@faunalia.it" target="_blank" rel="noreferrer">cavallini@faunalia.it</a>> geschrieben:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for your offer of help. I agree that the mail should be sent only<br>
for plugins not updated in the last (3? 6? 9?) months.<br>
Could you please start filling up a ticket on<br>
<a href="https://issues.qgis.org/issues" rel="noreferrer noreferrer noreferrer" target="_blank">https://issues.qgis.org/issues</a><br>
so we can define specs resulting from this thread and start implementing it?<br>
Cheers.<br>
<br>
On 01/02/19 22:40, Thomas Baumann wrote:<br>
> Hi Paolo,<br>
> <br>
> sounds like a good idea to send a reminder once a year to the maintainer<br>
> and mark plugins as unmaintained if no feedback is received.<br>
> <br>
> I am available to help implementing it.<br>
> <br>
> Regards,<br>
> Thomas<br>
> <br>
> <br>
> Am Fr., 1. Feb. 2019, 19:01 hat Paolo Cavallini <<a href="mailto:cavallini@faunalia.it" rel="noreferrer noreferrer" target="_blank">cavallini@faunalia.it</a><br>
> <mailto:<a href="mailto:cavallini@faunalia.it" rel="noreferrer noreferrer" target="_blank">cavallini@faunalia.it</a>>> geschrieben:<br>
> <br>
> Hi Thomas,<br>
> <br>
> On 01/02/19 13:53, Thomas Baumann wrote:<br>
> <br>
> > I made the experience that there are QGIS-plugins which are not<br>
> > maintained anymore.<br>
> > Example:<br>
> ><br>
> <a href="http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-Rectangles-Ovals-Digitizing-plugin-deprecated-td5366686.html" rel="noreferrer noreferrer noreferrer" target="_blank">http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-Rectangles-Ovals-Digitizing-plugin-deprecated-td5366686.html</a><br>
> ><br>
> > Recently I asked some maintainers if they have plans to update their<br>
> > plugins to be QGIS3-ready because I was willing to update them if the<br>
> > maintainer wouldn't do it... but again I got the impression that some<br>
> > plugins are not maintained anymore.<br>
> > Example:<br>
> > <a href="https://github.com/NathanW2/selection-sets/issues/5" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/NathanW2/selection-sets/issues/5</a><br>
> ><br>
> > Now that there is the change from QGIS2 to QGIS3 some unmaintained<br>
> > plugins will just dissapear like through a "natural selection". But in<br>
> > one or two years there could again be lots of unmaintained plugins<br>
> which<br>
> > could have bugs that slow down qgis or make them unstable like it<br>
> > happened with the Rectangles-Ovals-Digitizing-plugin (<br>
> > <a href="https://github.com/vinayan/RectOvalDigitPlugin/issues/6" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/vinayan/RectOvalDigitPlugin/issues/6</a> ).<br>
> ><br>
> > Wouldn't it make sense to check once a year if all plugins are still<br>
> > maintained?<br>
> ><br>
> > You could for example use something like LimeSurvey (<br>
> > <a href="https://www.limesurvey.org/community" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.limesurvey.org/community</a> ) and ask every maintainer to<br>
> > respond if they still feel responsible for the plugin. In the<br>
> backend of<br>
> > Limesurvey you have a database with the responses so it should be<br>
> quite<br>
> > easy to automatically synchronize the results with your<br>
> repository-items.<br>
> > This way the unmaintained plugins could be marked as deprecated if no<br>
> > response is sent back.<br>
> <br>
> thanks a lot for your suggestion. I agree that the move to QGIS 3<br>
> automatically purges old unmaintained code, but this does not solve<br>
> entirely the issue.<br>
> In short do you suggest we should run a survey once a year, sending it<br>
> to the list of plugin maintainers, and marking as deprecated all plugins<br>
> for which we do not receive a positive response?<br>
> I would be a bit skeptical, as many plugins are still useful even if not<br>
> actively maintained. An alternative would be to add to our Django app an<br>
> automatic reminder to be sent to maintainer, asking to confirm they<br>
> maintenance; in absence of a feedback, we could mark it as unmaintained,<br>
> and make this visible to users, so they have the options of adopting it,<br>
> supporting it, or stopping using it before it actually stops working.<br>
> How does it sound? in case you agree on this or a modified version of<br>
> it, would you be available to help implementing this?<br>
> All the best.<br>
> -- <br>
> Paolo Cavallini - <a href="http://www.faunalia.eu" rel="noreferrer noreferrer noreferrer" target="_blank">www.faunalia.eu</a> <<a href="http://www.faunalia.eu" rel="noreferrer noreferrer noreferrer" target="_blank">http://www.faunalia.eu</a>><br>
> <a href="http://QGIS.ORG" rel="noreferrer noreferrer noreferrer" target="_blank">QGIS.ORG</a> <<a href="http://QGIS.ORG" rel="noreferrer noreferrer noreferrer" target="_blank">http://QGIS.ORG</a>> Chair:<br>
> <a href="http://planet.qgis.org/planet/user/28/tag/qgis%20board/" rel="noreferrer noreferrer 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" rel="noreferrer noreferrer" target="_blank">QGIS-Developer@lists.osgeo.org</a> <mailto:<a href="mailto:QGIS-Developer@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">QGIS-Developer@lists.osgeo.org</a>><br>
> List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer 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 noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
> <br>
<br>
-- <br>
Paolo Cavallini - <a href="http://www.faunalia.eu" rel="noreferrer noreferrer noreferrer" target="_blank">www.faunalia.eu</a><br>
<a href="http://QGIS.ORG" rel="noreferrer noreferrer noreferrer" target="_blank">QGIS.ORG</a> Chair:<br>
<a href="http://planet.qgis.org/planet/user/28/tag/qgis%20board/" rel="noreferrer noreferrer noreferrer" target="_blank">http://planet.qgis.org/planet/user/28/tag/qgis%20board/</a><br>
</blockquote></div></div></div>