[GRASS-dev] External providers in QGIS
hellik at web.de
Thu Feb 8 09:48:22 PST 2018
> Il 08/02/2018 15:49, Nikos Alexandris ha scritto:
>> * Moritz Lennert <
> mlennert at .worldonline
> > [2018-02-08 15:20:14
>>> On 08/02/18 15:08, Nikos Alexandris wrote:
>>>> I guess, there are numerous cases like this one. What would,
>>>> effectively, mean a removal of external providers (in this case GRASS
>>> Let's make it clear once and for all: noone is speaking about the
>>> complete removal of external providers. The issue is where, how and by
>>> whom they should be maintained, i.e. within the QGIS core code base,
>>> or as plugins.
>> Thank you the heads-up Moritz.
> true, but removal from core would mean the external plugin has to be
> created, maintained, tested, and documented by someone. If this is
> missing, the external plugin simply wil not appear. This is what
> happened with R. Once a provider is out and unmaintained, it becomes
> less visible, and less likely to attract attention. The work to bring it
> back to life, with all the above, will be much higher than when in core,
> and increasing over time.
> All the best.
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> grass-dev mailing list
> grass-dev at .osgeo
this touches Moritz' questions listed here:
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
More information about the grass-dev