[Qgis-psc] Requiring adequate plugin descriptions

Tim Sutton tim at qgis.org
Tue May 23 09:17:51 PDT 2017


Hi All

+1 for requesting people to use QgsNetworkAccessManager - and thanks for
your other replies. I guess to start we could just check the descriptions
manually when plugins are submitted and toss it back to the author if they
are not adequate.

Regards

Tim

On Tue, May 23, 2017 at 2:56 PM, ElPaso <elpaso at itopen.it> wrote:

> Il 22/05/2017 21:53, Richard Duivenvoorde ha scritto:
>
>> On 22-05-17 18:01, Tim Sutton wrote:
>>
>>> Hi (mainly Paolo)
>>>
>>>
>>> Just looking at the new plugin approved:
>>>
>>> http://plugins.qgis.org/plugins/qdraw/
>>>
>>> I wonder if we should not require / strongly request that plugin authors
>>> provide a detailed description of their plugins so that a user wanting
>>> to choose a plugin from the repo knows what they will get. From the
>>> above plugin description (while it may be a great plugin), it is not
>>> really obvious what you will get when you install it. Perhaps a
>>> screenshot with each would be nice too....
>>>
>> Yes, I've been thinking about that too...
>>
>> What about forcing to answer 2 questions in the description in > 50
>> words or so..:
>> - what does this plugin do
>> - which problem does this plugin solve for me
>> (or ... whatever better guiding questions people can come up with).
>>
>
> Description is in metadata, we can add a validator to check for length but
> we cannot turn it into an interactive process.
>
>
> Another thing I would like to make better in plugins in general, is that
>> they plugins should make use of QgsNetworkAccessManager instead of home
>> brew urllib2/requests/.... solutions, which most of the times do not
>> make use of proxy settings (and machinery there is already in Qt to make
>> sure that a kerberos-identification-proxy is working ok..). I've seen in
>> several bigger QGIS-install that this was giving problems as some
>> plugins worked and some of them not.
>>
>
>
> totally agreed with this: moreover there is no support for QGIS
> authentication system in stock python libraries.
>
> In Boundless we started using a small wrapper around
> QgsNetworkAccessManager that mocks httplib2, I think that it should be part
> of core QGIS python utils, with a (still to be developed) "requests"
> replacement.
>
> You can find it in this repo: https://github.com/boundlessge
> o/lib-qgis-commons/blob/master/qgiscommons/networkaccessmanager.py
>
>
>
> Cheers
>
> --
> Alessandro Pasotti
> w3: www.itopen.it
>
>
> _______________________________________________
> Qgis-psc mailing list
> Qgis-psc at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>



-- 



*Tim Sutton*
QGIS Project Steering Committee Chair
tim at qgis.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20170523/6aa0dece/attachment.html>


More information about the Qgis-psc mailing list