Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

Il 21/02/2018 10:59, Tim Sutton ha scritto: >> On 21 Feb 2018, at 09:01, Paolo Cavallini > > wrote: >> >> as plugin manager, I'd appreciate this enormously; I wish there was a >> clear policy, with no room for interpretation. Having >= 1 ticket marked >> as critical c

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

Hi > On 21 Feb 2018, at 09:01, Paolo Cavallini wrote: > > Hi Nyall, > > Il 21/02/2018 06:55, Nyall Dawson ha scritto: >> On 19 February 2018 at 17:46, Paolo Cavallini wrote: > >>> I fully understand and support your concerns. Why not simply deprecating >>> these plugin? I have adopted this ap

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

Hi Nyall, Il 21/02/2018 06:55, Nyall Dawson ha scritto: > On 19 February 2018 at 17:46, Paolo Cavallini wrote: >> I fully understand and support your concerns. Why not simply deprecating >> these plugin? I have adopted this approach (much too rarely, trying not >> to hurt authors too much) in th

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

On 19 February 2018 at 17:46, Paolo Cavallini wrote: > Hi Nyall, all, > > Il 19/02/2018 05:54, Nyall Dawson ha scritto: > >> "Should the official QGIS plugin repository flag plugins which have >> known serious issues, and hide these plugins from users unless a 'Show >> plugins with known issues' c

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

I understand the intention of this. We don't want QGIS getting the blame because of third party plugin not working correctly. I just wanted to point that we might be adding too many tags, which may confuse the users. We already have the following tags: experimental, deprecated, trusted. My other c

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

Hi I think we just need to be careful if we are deprecating a plugin that we have a really solid chain of evidence as to why it is deprecated and a clear roadmap that people can follow if they want to appeal deprecation. Wither way I think putting it to a vote would be a good idea. Regards Ti

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

Sounds like a very good idea to me. Tom - Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon -- Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org Li

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

I fully agree and I support Paolo in deprecating those plugins, until they're not fixed. I wouldn't even give the option to install plugins "with issues" from QGIS side. I would move the responsability on the developers and users to use them... Giovanni 2018-02-19 8:46 GMT+01:00 Paolo Cavallini :

Re: [QGIS-Developer] [Qgis-psc] Call for possible vote on change to official plugin repo policy?

Hi Nyall, all, Il 19/02/2018 05:54, Nyall Dawson ha scritto: > "Should the official QGIS plugin repository flag plugins which have > known serious issues, and hide these plugins from users unless a 'Show > plugins with known issues' checkbox is ticked?" > So my proposal is that: > - if a plugin