[GRASS-dev] External providers in QGIS

Helmut Kudrnovsky hellik at web.de
Tue Feb 6 14:12:24 PST 2018

Hi Paolo,

pcav wrote
> Hi all,
> following the discussion on qgis-dev ML:
> https://lists.osgeo.org/pipermail/qgis-developer/2018-January/051701.html
> it has been proposed to remove all external providers (namely OTB,
> already removed, GRASS, and SAGA) from Processing in QGIS2 (GDAL will
> remain as QGIS cannot be built without). This raised a number of
> concerns, so PSC decided not to rush removing them from the upcoming 3.0
> release, and to open a wider discussions about this, involving all the
> interested parties, to find an optimal solution.
> If volunteers outside QGIS core team, ideally from the respective
> backends, could take the maintenance of these providers, not much would
> change for the end user. If not, this will mean effectively missing
> hundreds of algs from QGIS.
> I personally propose to reinstate the OTB plugin with Rashad (from OTB)
> as maintainer.
> QGIS.ORG will seek to support any decision made with funding where
> possible.
> Looking forward for your feedback.
> All the best.
> -- 
> Paolo Cavallini

thanks for the follow up on this discussion.

Is there already a concrete technical documention of requirements, methods,
API, interface etc by QGIS how alg providers work/should work/be maintained?

This may ease and accelerate to start a discussion in the communities of
algs providers like OTB, GRASS, SAGA and others how to proceed in this
inter-project challenge.

>If not, this will mean effectively missing 
>hundreds of algs from QGIS. 

this is part of QGIS success and this question has also to be answered by
the QGIS community.

This may be an indication that OSGeo's inter-project communication should be
proactively improved in the future.....

best regards
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html

More information about the grass-dev mailing list