[Qgis-psc] Resource Sharing plugin in core?

Paolo Cavallini cavallini at faunalia.it
Tue Feb 18 05:46:56 PST 2020


Hi Nyall, others,

Il 18/02/20 00:05, Nyall Dawson ha scritto:

> Agreed - and also important to note that doing development in
> qgis/QGIS is MUCH MUCH slower and with a insanely vertical learning
> curve. The rules for code integration in qgis/QGIS are very very
> strict, the CI is extremely picky about code styling, spelling,
> formatting, etc (all for good reason -- we SHOULD be extremely picky
> about the code which lands in qgis/QGIS). There's a very large barrier
> for entry for anyone to start contributing to qgis master code, which
> would apply to the plugin as soon as it's moved into qgis/QGIS. It
> would actually make development slower, put up more barriers for
> entry, and will actively discourage community contributions...

OK, now I see your argument, which makes sense to me. So in short the
proposal would be to leave Python stuff outside of core, leaving the
integration at the packaging level. I would add an additional feature:
defining some of the plugins as default, and require their inclusion in
the installers. In this way the users will not have any impact (no loss
of existing functionality), and allow flexible release cycles, while
keeping the core clean.
Would this be OK for you?
An open question would be whether to split bugtrackers as well, or keep
them as they are now.
Cheers.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS.ORG Chair:
http://planet.qgis.org/planet/user/28/tag/qgis%20board/



More information about the Qgis-psc mailing list