[QGIS-Developer] Find unmaintained plugins

[Werner Macho]

Hi,

I also dislike the idea of removing plugins completely, as already pointed
oout sometimes a plugin "just works" and there is no real maintenance
needed.
Also - even it is not maintained anymore the code inside can still be
useful to create something new out of it. And without seeing the plugin
everything would have to be invented again.

so -1 from my side for  removing plugins that are orphaned unless they are
part of a security / data integrity risk too.

regards
Werner

On Mon, Feb 4, 2019 at 3:25 PM Tim Sutton <tim at kartoza.com> wrote:

> Hi
>
>
> On 04 Feb 2019, at 00:30, Nyall Dawson <nyall.dawson at gmail.com> wrote:
>
> On Mon, 4 Feb 2019 at 00:57, Matthias Kuhn <matthias at opengis.ch> wrote:
>
>
> Hi Paolo
>
> On 2/3/19 1:39 PM, Paolo Cavallini wrote:
>
> Hi Matthias,
>
> On 03/02/19 10:17, Matthias Kuhn wrote:
>
> Marking a plugin as "unmaintained" or "deprecated" is a heavy action which
> may discourage developers and make even useful plugins disappear.
>
>
> deprecated yes, unmaintained not necessarily. We could just let the user
> know, perhaps suggesting a way to solve this, without removing them for
> the list of available plugins (just like the Featured tag).
>
>
> Then I misunderstood the goal of this proposal, sorry.
>
> I was imagining myself looking through a plugin list of a software of
> which I am an ordinary user and seeing a plugin tagged as
> "unmaintained". This would make me think it's unreliable, outdated and
> unstable and hence not recommended.
>
>
> I think this actually IS the intention here.
>
> But, as you've pointed out, no activity =/= unmaintained, as sometimes
> no activity just means bug free and feature complete. In this case I
> think it's fine to require developers to respond to a quick "is this
> still maintained" survey in order to avoid the flag.
>
>
> And sometimes even if the plugin is unmaintained it is still useful to
> lots of people (even if it has a few known bugs)…..
>
> I’m not sure if flagging plugins as unmaintained is always so nice.. I
> would favour an approach where we could just list plugins in the plugin
> manager based on the date of their last release, most recent first so that
> you can see old versus new
>
> Definitely -1 here on removing plugins that are orphaned unless they are
> part of a security / data integrity risk. Many people may have built up
> specific workflows around the existence of a particular plugin or two and
> there is no need to break this for people even if the plugin is orphaned…
>
> Regards
>
> Tim
>
>
>
> —
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Ex Project chair:* QGIS.org
>
> Visit http://kartoza.com to find out about open source:
>
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
>
> *Skype*: timlinux
> *IRC:* timlinux on #qgis at freenode.net
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20190204/ed186182/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: KartozaNewLogoThumbnail.jpg
Type: image/jpeg
Size: 6122 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20190204/ed186182/attachment-0001.jpg>