[QGIS-Developer] Plugin [1052] Projestions approval notification.

[noreply]

Plugin Projestions approval by pcav.
The plugin version "[1052] Projestions 0.3.0 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/Projestions/
___
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] Plugin [1305] Calidad-CAR approval notification.

[noreply]

Plugin Calidad-CAR approval by pcav.
The plugin version "[1305] Calidad-CAR 0.4" is now approved
Link: http://plugins.qgis.org/plugins/CalidadCAR/
___
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] Classification of values around zero

[Pierre_Loicq]

Hello,

I added a new method of classification in the graduated methods (symbology).
It is aimed at plotting data that are centered on zero, with a class around
zero (like [-1,1] instead of [-1,0],[0,1] ), and with a colorbar that stay
symmetric around zero (for this I remove the extra classes). It uses the
prettyBreaks method. If data are all positive or negative, an alert box
appear.

https://github.com/qgis/QGIS/pull/5161

Hoping that you can include it in 3.0
Thank you
Pierre (Tours, France)



Pierre_Loicq wrote
> Hi,
> 
> At the office, I often need to create map of modeled biases (float
> values), where it make sense to have a first class centered on zero
> (symbology/graduated). I learned C++ some months ago and would like to add
> this functionality as a first application, on the  master branch. 
> 
> Pierre





--
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] Reword "Trusted Plugin" --> "Trusted Plugin Author"?

[Richard Duivenvoorde]

On 09-09-17 10:42, Alessandro Pasotti wrote:
> 
> Sorry if I repeat myself, this is just to clarify what the "trusted"
> flag is, and why it was introduced.
> 
> The trusted flag has nothing to do with being a core dev or having
> CI/tests: it's a permission flag in the DB, tied to the user who "owns"
> the plugin (the maintainer).
> 
> When a new plugin is submitted, Paolo (please correct me if I'm wrong)
> checks the plugin for mandatory metadata and he makes a
> quick/superficial evaluation, if the plugin does not look particularly
> suspicious or misses some mandatory metadata he approves it straight away.
> 
> But the a.m. procedure is pointless and can be totally avoided if the
> plugin comes from a well known member of this community when there is
> "trust" because of proven record of good plugins or code contributions
> or personal knowledge, beers together in the greenhouses at night etc.
> etc.. 
> 
> So this is all what the "trusted" flag is about: skipping the boring and
> time/consuming procedure of approving plugins for the well-known members
> of this community (and the delay that it causes) .
> 
> Let me say it again:the only difference between a "trusted" user/author
> is that he can approve and publish the plugins by himself.
> 
> The problem started when we decided to advertise the "trusted" flag on
> the plugin manager, I see two options here:
> 
> 1. go back to the pre-trusted times and hide that information from the
> plugin manager
> 2. reword/rephrase
> 3. add some other flags at the DB level (feel free to make PRs)
> 
> I would go for 2. but please keep the new sentence in sync with the real
> meaning of the "trusted" flag: I believe that all core developers should
> be "trusted" (just ask Paolo or any other admin and it's just a click)
> but I would not restrict the "trust" to core devs: there are many other
> members of this community that I'd give trust even if they are not core
> devs.

Thanks Alessandro for this refreshment,

looks like we are two things mixing up here;
A) making approving of plugins easier by giving label to AUTHORS
B) promoting/giving preference to certain 'wellknown' PLUGINS

And actually we have mechanisms for both!

For A we have this 'trusted author' label to make Paolo's work easier
(and let's make it clear: trust IS often a personal thing, which is hard
to hand over to others).

For B we have the 'Starring' mechanism: at
http://plugins.qgis.org/plugins/ AND in the plugin manager
you can 'vote' for a plugin by clicking on one of the stars there.

Given that most users actually do not care too much about the personal
trust between authors and community/admins, I would go for Alessondro's
first option:

1) remove that coloring/sentence from the manager (as it does not prove
anything about the quality of the plugin too)

2) give the 'Starring' of plugins more weight in the applications:
- make the 'Stars' more visible in the plugin manager by moving them to
the top of the information in the plugin dialog
- make it more clear that you can VOTE stars for a plugin in the plugin
manager
- make the stars visible when you search for plugins (now only the names
are shown):
http://plugins.qgis.org/search/?q=pdok

IF somebody wants to dive into the plugin Django application, maybe we
should we could maybe refine these mechanisms (like make it only
possible to add stars when you are logged in or so?), but looking at
them now, we actually had everything pretty well laid out?

Regards,

Richard Duivenvoorde


___
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] Reword "Trusted Plugin" --> "Trusted Plugin Author"?

[Alessandro Pasotti]

Sorry if I repeat myself, this is just to clarify what the "trusted" flag
is, and why it was introduced.

The trusted flag has nothing to do with being a core dev or having
CI/tests: it's a permission flag in the DB, tied to the user who "owns" the
plugin (the maintainer).

When a new plugin is submitted, Paolo (please correct me if I'm wrong)
checks the plugin for mandatory metadata and he makes a quick/superficial
evaluation, if the plugin does not look particularly suspicious or misses
some mandatory metadata he approves it straight away.

But the a.m. procedure is pointless and can be totally avoided if the
plugin comes from a well known member of this community when there is
"trust" because of proven record of good plugins or code contributions or
personal knowledge, beers together in the greenhouses at night etc. etc..

So this is all what the "trusted" flag is about: skipping the boring and
time/consuming procedure of approving plugins for the well-known members of
this community (and the delay that it causes) .

Let me say it again:the only difference between a "trusted" user/author is
that he can approve and publish the plugins by himself.

The problem started when we decided to advertise the "trusted" flag on the
plugin manager, I see two options here:

1. go back to the pre-trusted times and hide that information from the
plugin manager
2. reword/rephrase
3. add some other flags at the DB level (feel free to make PRs)

I would go for 2. but please keep the new sentence in sync with the real
meaning of the "trusted" flag: I believe that all core developers should be
"trusted" (just ask Paolo or any other admin and it's just a click) but I
would not restrict the "trust" to core devs: there are many other members
of this community that I'd give trust even if they are not core devs.





On Sat, Sep 9, 2017 at 10:20 AM, Tom Chadwin 
wrote:

> Hello all
>
> Sorry for opening this can of worms, and thanks to all of you for very kind
> words. But obviously, let's move on from the personal to the general point,
> not least to stop my looking as though I was fishing for compliments. I
> very
> much was not.
>
>
> Nyall Dawson wrote
> >> possibly
> >> reinforces the (otherwise seldom apparent) clique nature of devs in
> >> general
> >> and the QGIS core devs in particular...
> >
> > To begin: there's obviously no secret agenda or deliberate 'inner
> > circle' here, so any closed nature of the community has been an
> > accidental organic process vs a deliberate decision.
>
> 100%. Compared to other projects to which I've contributed, this is an
> incredibly welcoming, supportive, and friendly community. I said "otherwise
> seldom apparent" deliberately. I could probably have said "otherwise never
> apparent". I could even broaden this out to the whole geo community - both
> Leaflet and, back in the day, MGOS devs have always welcomed tentative and
> initially nervous contributions from hobbyists.
>
>
> Nyall Dawson wrote
> > So, if you feel comfortable doing this, can you (or any others who
> > have also felt this way) give some pointers on how we can 'break' this
> > and becoming a more welcoming community?
>
> So in that light, my point just refers to this issue. Again, I knew that
> the
> issue I've raised was unintentional, so simply tweaking this process and
> language will do the job.
>
> Matthias and I discussed some possibilities off-list:
>
> - label "core QGIS developer"
> - label plugins which have testing/CI
>
> I'll check back to see if I missed anything else.
>
> Thanks for running with this discussion. It should have a moderately simple
> solution - just haven't quite found it yet.
>
> Thanks again
>
> 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
>



-- 
Alessandro Pasotti
w3:   www.itopen.it
___
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] Reword "Trusted Plugin" --> "Trusted Plugin Author"?

[Tom Chadwin]

Hello all

Sorry for opening this can of worms, and thanks to all of you for very kind
words. But obviously, let's move on from the personal to the general point,
not least to stop my looking as though I was fishing for compliments. I very
much was not.


Nyall Dawson wrote
>> possibly
>> reinforces the (otherwise seldom apparent) clique nature of devs in
>> general
>> and the QGIS core devs in particular...
> 
> To begin: there's obviously no secret agenda or deliberate 'inner
> circle' here, so any closed nature of the community has been an
> accidental organic process vs a deliberate decision.

100%. Compared to other projects to which I've contributed, this is an
incredibly welcoming, supportive, and friendly community. I said "otherwise
seldom apparent" deliberately. I could probably have said "otherwise never
apparent". I could even broaden this out to the whole geo community - both
Leaflet and, back in the day, MGOS devs have always welcomed tentative and
initially nervous contributions from hobbyists.


Nyall Dawson wrote
> So, if you feel comfortable doing this, can you (or any others who
> have also felt this way) give some pointers on how we can 'break' this
> and becoming a more welcoming community?

So in that light, my point just refers to this issue. Again, I knew that the
issue I've raised was unintentional, so simply tweaking this process and
language will do the job.

Matthias and I discussed some possibilities off-list:

- label "core QGIS developer"
- label plugins which have testing/CI

I'll check back to see if I missed anything else. 

Thanks for running with this discussion. It should have a moderately simple
solution - just haven't quite found it yet. 

Thanks again

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