<html>
<head>
</head>
<body>
<div style="color: black;">
<div style="color: black;">
<p style="margin: 0 0 1em 0; color: black;">Very good idea... </p>
</div>
<div style="color: black;">
<p
style="color: black; font-size: 10pt; font-family: Arial, sans-serif; margin: 10pt 0;">On
8 September 2017 3:16:55 pm Alessandro Pasotti <apasotti@gmail.com>
wrote:</p>
<blockquote type="cite" class="gmail_quote"
style="margin: 0 0 0 0.75ex; border-left: 1px solid #808080; padding-left: 0.75ex;">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri,
Sep 8, 2017 at 2:37 PM, Werner Macho <span dir="ltr"><<a
href="mailto:werner.macho@gmail.com"
target="_blank">werner.macho@gmail.com</a>></span> wrote:<br><blockquote
class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div
dir="ltr"><div><div><div>Hi!<br><br></div>I like Community contributor
(more than trusted author)<br></div>but have another
addition</div><div>Contributor known by the community .. <br></div><div>But
I think that distracts us from the plugins "tag" that it
is.</div><div><br></div><div>what about "checked" or
"scanned" or something like
that?</div><div><br></div><div>regards</div><span class="HOEnZb"><font
color="#888888"><div>Werner<br></div></font></span></div><div
class="HOEnZb"><div class="h5"><div
class="gmail_extra"><br></div></div></div></blockquote><div><br></div><div><br></div><div>That
would be untrue: AFAIK nobody really scans the plugins and the
"trusted" users are the only one that can approve the plugins by
themselves.</div><div><br></div><div>Please bear in mind that what that
flag really means at the application level is that a "trusted"
user can approve and publish his own plugins, in that sense we
"trust" him.</div><div><br></div><div>So, "trusted" is
the correct word, but we could stress the reasons why that user has been
trusted instead of the condition itself, so, I suggest to add a brief
sentence/tooltip whatever it works to explain why a user (in general: not
that particular user) has been flagged as "trusted" (active
member in the community with a proven record of plugin or core
contributions etc. etc.).</div><div><br></div><div></div><div>Kind
regards.<br></div><div><br></div><div><br></div><div> </div><blockquote
class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div
class="HOEnZb"><div class="h5"><div class="gmail_extra"><div
class="gmail_quote">On Fri, Sep 8, 2017 at 2:32 PM, DelazJ <span
dir="ltr"><<a href="mailto:delazj@gmail.com"
target="_blank">delazj@gmail.com</a>></span> wrote:<br><blockquote
class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Tom, thanks for your input and I'm surprised that you are not a<br>
trusted author (thought that have been discussed a while back).<br>
I was about to propose a pull request this morning with the new<br>
wording but didn't because either "The author of this plugin is<br>
trusted" or "Trusted Author" makes me feel comfortable. It
looked to<br>
me that those who do not have this tag are untrusted. And I'm afraid<br>
this could harm their work and they do not deserve that.<br>
So, if the main idea is to promote people that have a community<br>
implication (and I guess we agree they deserve it), how about<br>
"Community contributor"?<br>
<br>
2017-09-08 14:27 GMT+02:00 Saber Razmjooei<br>
<<a href="mailto:saber.razmjooei@lutraconsulting.co.uk"
target="_blank">saber.razmjooei@lutraconsulti<wbr>ng.co.uk</a>>:<br>
> +1 for Tom to become a trusted author. In addition to the qgis2web
plugin,<br>
> Tom is a very active in QGIS UK usergroups.<br>
><br>
> Cheers<br>
> Saber<br>
><br>
><br>
> On 8 September 2017 at 13:17, Luigi Pirelli <<a
href="mailto:luipir@gmail.com" target="_blank">luipir@gmail.com</a>>
wrote:<br>
>><br>
>> +1 to thrusted author<br>
>><br>
>> side +1 to trust Tom... can we use the same OSGeo charters memeber<br>
>> mechanism to nominate thrusted authors?<br>
>> Luigi Pirelli<br>
>><br>
>><br>
>>
******************************<wbr>******************************<wbr>******************************<wbr>********<br>
>> * Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT
com<br>
>> * LinkedIn: <a href="https://www.linkedin.com/in/luigipirelli"
rel="noreferrer"
target="_blank">https://www.linkedin.com/in/lu<wbr>igipirelli</a><br>
>> * Stackexchange: <a
href="http://gis.stackexchange.com/users/19667/luigi-pirelli"
rel="noreferrer"
target="_blank">http://gis.stackexchange.com/u<wbr>sers/19667/luigi-pirelli</a><br>
>> * GitHub: <a href="https://github.com/luipir" rel="noreferrer"
target="_blank">https://github.com/luipir</a><br>
>> * Mastering QGIS 2nd Edition:<br>
>> *<br>
>> <a
href="https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition"
rel="noreferrer"
target="_blank">https://www.packtpub.com/big-d<wbr>ata-and-business-intelligence/<wbr>mastering-qgis-second-edition</a><br>
>><br>
>>
******************************<wbr>******************************<wbr>******************************<wbr>********<br>
>><br>
>><br>
>> On 8 September 2017 at 13:45, Matthias Kuhn <<a
href="mailto:matthias@opengis.ch"
target="_blank">matthias@opengis.ch</a>> wrote:<br>
>> > Hi Tom,<br>
>> ><br>
>> > I understand this sentiment very well. Do you think
formalizing the<br>
>> > process to become a "Trusted Author" and making it
more transparent<br>
>> > would help here?<br>
>> ><br>
>> > Your statement does not seems not to critizise the move of
switching<br>
>> > trust from plugins to authors. But more the
"in-or-out" in general.<br>
>> > Important here is, that the idea is to put more stress on the
"in"<br>
>> > rather than the "out" (by saying "trusted
author" rather than "untrusted<br>
>> > author"). If you have an idea how this can be made even
more visible, I<br>
>> > think there's a good chance that we can mitigate unwanted
side-effects<br>
>> > and potentially hard feelings of this better.<br>
>> ><br>
>> > Sidnote:<br>
>> > I will immediately vote to make you a trusted author, we all
very well<br>
>> > know the work you've put into qgis2web and close
relations with the<br>
>> > community. While I think you should get the label anyway, I
think<br>
>> > there's a different discussion you wanted to trigger
here.<br>
>> ><br>
>> > Matthias<br>
>> ><br>
>> > On 09/08/2017 01:29 PM, Tom Chadwin wrote:<br>
>> >> So it's not that you don't trust my work,
it's that you don't trust me?<br>
>> >><br>
>> >> As an untrusted plugin author, I should say that this
makes little<br>
>> >> difference. While I 100% understand the rationale behind
this process,<br>
>> >> it<br>
>> >> still feels like a bit of a slap in the face. Perhaps the
use of the<br>
>> >> word<br>
>> >> "trust", be it applied to plugin or author, is
too loaded for me. In<br>
>> >> fact,<br>
>> >> transferring the usage to individuals makes it more
galling - it's one<br>
>> >> thing<br>
>> >> for the work I have done voluntarily over the past three
or four years<br>
>> >> not<br>
>> >> to be trusted by the core devs, but it's quite
another for me,<br>
>> >> personally,<br>
>> >> not to be trusted.<br>
>> >><br>
>> >> I of course understand that the inference is not that I
and my work are<br>
>> >> not<br>
>> >> trusted. I simply worded that last sentence deliberately
to make the<br>
>> >> point<br>
>> >> that this label, and its absence, seems arbitrary at
best, possibly<br>
>> >> reinforces the (otherwise seldom apparent) clique nature
of devs in<br>
>> >> general<br>
>> >> and the QGIS core devs in particular, and at worst is
insulting.<br>
>> >><br>
>> >> Hope you understand - I feel the point had to be made.<br>
>> >><br>
>> >> Thanks<br>
>> >><br>
>> >> Tom<br>
>> >><br>
>> >><br>
>> >><br>
>> >> -----<br>
>> >> Buy Pie Spy: Adventures in British pastry 2010-11 on
Amazon<br>
>> >> --<br>
>> >> Sent from:<br>
>> >> <a
href="http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html"
rel="noreferrer"
target="_blank">http://osgeo-org.1560.x6.nabbl<wbr>e.com/QGIS-Developer-f4099106.<wbr>html</a><br>
>> >> ______________________________<wbr>_________________<br>
>> >> QGIS-Developer mailing list<br>
>> >> <a href="mailto:QGIS-Developer@lists.osgeo.org"
target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
>> >> List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
>> >> Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
>> >><br>
>> > ______________________________<wbr>_________________<br>
>> > QGIS-Developer mailing list<br>
>> > <a href="mailto:QGIS-Developer@lists.osgeo.org"
target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
>> > List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
>> > Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
>> ______________________________<wbr>_________________<br>
>> QGIS-Developer mailing list<br>
>> <a href="mailto:QGIS-Developer@lists.osgeo.org"
target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
>> List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
>> Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Saber Razmjooei<br>
> <a href="http://www.lutraconsulting.co.uk" rel="noreferrer"
target="_blank">www.lutraconsulting.co.uk</a><br>
> <a href="tel:%2B44%20%280%297568%20129733" value="+447568129733"
target="_blank">+44 (0)7568 129733</a><br>
><br>
> ______________________________<wbr>_________________<br>
> QGIS-Developer mailing list<br>
> <a href="mailto:QGIS-Developer@lists.osgeo.org"
target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
> List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
> Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
______________________________<wbr>_________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org"
target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a><br>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/qgis-developer</a></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
QGIS-Developer mailing list<br>
<a
href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer"
target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br></blockquote></div><br><br
clear="all"><br>-- <br><div class="gmail_signature"
data-smartmail="gmail_signature">Alessandro Pasotti<br>w3: <a
href="http://www.itopen.it" target="_blank">www.itopen.it</a></div>
</div></div>
</blockquote>
</div>
</div>
</body>
</html>