[Qgis-developer] Processing algs & plugins... should we actively pull into master?

Nyall Dawson nyall.dawson at gmail.com
Mon Feb 6 01:53:05 PST 2017


On 6 February 2017 at 19:21, Victor Olaya <volayaf at gmail.com> wrote:
> Very interesting question...
>
> IMHO, all plugins that include processing algorithms like that (just
> one of them or a few of them, using only native code), we should ask
> developers to put the code in the central QGIS repo, and then work on
> that through PRs. It makes more sense. In the case of a plugin that
> adds a large group of algorithms and has some "identity", or uses an
> external app, I think it makes sense to have it as a separate plugin.
>

Ah yes - I forgot to include that in my email, even though that was my
intent. Definitely plugins with external deps (or even large amounts
of private classes) should remain as plugins.

> Just let make sure that we have some clear acceptance criteria (algs
> with tests, trying to follow some "best practices" and using
> Processing methods when possible, etc).

Big +1. We'd still need to careful vet and review the code for quality.

Nyall


More information about the Qgis-developer mailing list