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

[Paolo Cavallini]

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 could be one, but this just moves decisions one step ahead.
>> Do you have a practic proposal?
> 
> 
> Can you clarify here if the ticket should be in QGIS tracker or in
> plugin repo tracker?

I confirm, I meant in the bugtracker of each individual plugin.

> What is to stop them just chasing the ticket state
> and then asking for a release?

This is exactly what I meant with "move decisions one step ahead".
Sorry for being unclear.

In short, what we need is a clear criterion for deprecation, with as
little subjectivity as possible. I would welcome any suggestion on this.

All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis



signature.asc
Description: OpenPGP digital signature
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Tim Sutton]

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 approach (much too rarely, trying not
>>> to hurt authors too much) in the past, and I found it simple and
>>> effective. Once issues are fixed, I simply remove the `deprecated` flag,
>>> et voilà.
>>> Not sure we need a vote for this, just establishing sensible guidelines
>>> should be enough.
>> 
>> That sounds like a good technical solution.
> 
> so, we agree that simply deprecating a plugin is the way to go, right?
> 
>> But (like others have raised) I think we need a clear policy here so
>> that there's no misunderstanding or developers feeling like they're
>> "targeted". That's why I think we need a strong policy, voted in by
>> the voting community, so that there's NO chance that anyone can claim
>> that this is being abused.
> 
> 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 could be one, but this just moves decisions one step ahead.
> Do you have a practic proposal?


Can you clarify here if the ticket should be in QGIS tracker or in plugin repo 
tracker? What is to stop them just chasing the ticket state and then asking for 
a release?

Regards

Tim


> 
>> What's the next step here? I'd very much like to see this continue
>> moving forward promptly.
> 
> IMHO we can agree on a solution without the need for a vote. In any
> case, I'm sure PSC could ratify any sensible decision that comes out of
> this discussion.
> 
> All the best.
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Paolo Cavallini]

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 the past, and I found it simple and
>> effective. Once issues are fixed, I simply remove the `deprecated` flag,
>> et voilà.
>> Not sure we need a vote for this, just establishing sensible guidelines
>> should be enough.
> 
> That sounds like a good technical solution.

so, we agree that simply deprecating a plugin is the way to go, right?

> But (like others have raised) I think we need a clear policy here so
> that there's no misunderstanding or developers feeling like they're
> "targeted". That's why I think we need a strong policy, voted in by
> the voting community, so that there's NO chance that anyone can claim
> that this is being abused.

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 could be one, but this just moves decisions one step ahead.
Do you have a practic proposal?

> What's the next step here? I'd very much like to see this continue
> moving forward promptly.

IMHO we can agree on a solution without the need for a vote. In any
case, I'm sure PSC could ratify any sensible decision that comes out of
this discussion.

All the best.
-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Nyall Dawson]

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' checkbox is ticked?"
>
>> So my proposal is that:
>> - if a plugin has known, serious issues we contact the plugin author
>> to notify them
>> - we add a flag to the plugin to indicate it has known issues
>> - these plugins are not shown by default - users must opt in via a
>> checkbox (much like the "show experimental" check box)
>> - if/when the plugin fixes the issues, the flag is removed
>
> 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 the past, and I found it simple and
> effective. Once issues are fixed, I simply remove the `deprecated` flag,
> et voilà.
> Not sure we need a vote for this, just establishing sensible guidelines
> should be enough.

That sounds like a good technical solution.

But (like others have raised) I think we need a clear policy here so
that there's no misunderstanding or developers feeling like they're
"targeted". That's why I think we need a strong policy, voted in by
the voting community, so that there's NO chance that anyone can claim
that this is being abused.

What's the next step here? I'd very much like to see this continue
moving forward promptly.

Nyall
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Alexandre Neto]

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 concern is about the process to determine which plugins must be
flagged as having issues (I actually have the same concerns with the
"trusted" tag). It must be clear to everyone who writes a plugins how that
is done.

Tim Sutton  escreveu no dia segunda, 19/02/2018 às 21:43:

> 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
>
> Tim
>
>
> On 19 Feb 2018, at 14:32, Tom Chadwin  wrote:
>
> 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
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
> —
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Project chair:* QGIS.org
>
> Visit http://kartoza.com to find out about open source:
>
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
>
> *Skype*: timlinux
> *IRC:* timlinux on #qgis at freenode.net
>
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

-- 
Alexandre Neto
-
@AlexNetoGeo
http://sigsemgrilhetas.wordpress.com
http://gisunchained.wordpress.com
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Tim Sutton]

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

Tim

> On 19 Feb 2018, at 14:32, Tom Chadwin  wrote:
> 
> 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
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

—







Tim Sutton

Co-founder: Kartoza
Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux
IRC: timlinux on #qgis at freenode.net



signature.asc
Description: Message signed with OpenPGP
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Tom Chadwin]

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
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[G. Allegri]

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 :

> 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 has known, serious issues we contact the plugin author
> > to notify them
> > - we add a flag to the plugin to indicate it has known issues
> > - these plugins are not shown by default - users must opt in via a
> > checkbox (much like the "show experimental" check box)
> > - if/when the plugin fixes the issues, the flag is removed
>
> 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 the past, and I found it simple and
> effective. Once issues are fixed, I simply remove the `deprecated` flag,
> et voilà.
> Not sure we need a vote for this, just establishing sensible guidelines
> should be enough.
> All the best.
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
> ___
> QGIS-Developer mailing list
> QGIS-Developer@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

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

[Paolo Cavallini]

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 has known, serious issues we contact the plugin author
> to notify them
> - we add a flag to the plugin to indicate it has known issues
> - these plugins are not shown by default - users must opt in via a
> checkbox (much like the "show experimental" check box)
> - if/when the plugin fixes the issues, the flag is removed

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 the past, and I found it simple and
effective. Once issues are fixed, I simply remove the `deprecated` flag,
et voilà.
Not sure we need a vote for this, just establishing sensible guidelines
should be enough.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all=IT=qgis,arcgis
___
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer