Re: [QGIS-Developer] [saga-gis-developer] [GRASS-dev] External providers in QGIS

[Paolo Cavallini]

Thanks Vaclav for your detailed analysis. As expected, it seems that
there are a number of common tasks between GRASS and OTB, possibly also
SAGA, so it make sense to keep a joint discussion. Please consider
participating even remotely to the HackFest discussion:
https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018#future-of-processing-providers
All the best.

Il 09/02/2018 21:33, Vaclav Petras ha scritto:
> Dear Nyall and all,
> 
> here are some of my thoughts mostly relating to GRASS GIS (although it
> may not express views of the whole GRASS GIS developer team).
> 
> On Thu, Feb 8, 2018 at 8:55 PM, Nyall Dawson  > wrote:
>>
>> Here's the situation as I see it:
>>
>> 
>> The past
>> ---
>>
>> We (the QGIS project) have struggled to keep a bunch of providers
>> stable and available with the base QGIS install, and the current
>> maintainers (Alex and Victor, others) have (understandably) struggled
>> with the burden of maintaining these alone and the time commitment
>> required to do so. Users have been frustrated by breakage which occurs
>> when the algorithms they depend on break due to changes in underlying
>> libraries for which the processing providers have not been adapted.
>>
>> Despite this, I'd say overall it's worked OK-ish up to now, but
>> definitely with lots of room for improvement.
>>
>> -
>> The goals
>> -
>>
>> I think everyone involved is in agreement that processing's strength
>> comes when there's many providers available and it's able to tie
>> together processes regardless of which provider or library they come
>> from. So I'd say our common goals are:
>>
>> 1. Encourage development of as many processing providers as possible
>> 2. Make it easy for developers to create and maintain these providers
>> 3. Make it easy for users to be able to use the providers
>> 4. Make everything stable and painfree for users
>>
>> Any disagreements? No? Good ;)
>>
>> So if we agree that those are the end goals, we should be using them
>> to drive this discussion.
>>
>> ---
>> The questions
>> ---
>>
>> The open, debatable questions are:
>>
>> - Which is the best approach for allowing easy maintenance of
>> providers (*regardless* of whether the provider is maintained by the
>> core QGIS team or a 3rd party)? Is it keeping the code in the master
>> codebase and locking to QGIS releases, or publishing via plugins and
>> having independent release schedules? Which approach will encourage
>> more active maintenance of these providers and share the burden of
>> this maintenance?
> 
> One thing is where to keep the code, however I'm not sure what code are
> we talking about and I would like to talk about this first. I think that
> recent post by Moritz is bringing this up as well:
> 
> https://lists.osgeo.org/pipermail/grass-dev/2018-February/087420.html
> 
> 
> As far as I know, QGIS Processing has a text file for each GRASS module
> describing its interface and maintenance of these takes time. However,
> every GRASS module can tell about itself when called with
> --interface-description parameter. If this is used, individual
> parameters don't need to be maintained and any, even user provided
> module can be executed in processing.
> 
> The --interface-description parameter gives XML which would need to be
> converted or a new parameter, let's say --qgis-description, would need
> to be added for a QGIS-specific format, there is for example --script
> for GRASS GIS interface description for scripts. --qgis-description
> would need to be in GRASS GIS code base while the conversion can be
> anywhere. See emails from Rashad discussing a possible implementation
> with the --qgis-description way and the OTB way:
> 
> https://lists.osgeo.org/pipermail/grass-dev/2018-February/087362.html
> 
> https://lists.osgeo.org/pipermail/grass-dev/2018-February/087390.html
> 
> 
> The was discussed in the past and in fact, it is used in the QGIS GRASS
> plugin as Radim explains in this older email:
> 
> https://lists.osgeo.org/pipermail/grass-dev/2015-March/074629.html
> 
> 
> However, it is not using the --interface-description XML only, but it is
> also using the qgm files to supply some additional information which
> means that this system still requires updates which are separate from
> the updates of GRASS modules. This can be avoided if the necessary
> information is updated upstream or sometimes even GRASS
> --interface-description format or the individual module descriptions are
> extended to include that what is needed by QGIS Processing. Here is a
> thread which disuses this issues although diverges into the following:
> 
> h

Re: [QGIS-Developer] [GRASS-dev] External providers in QGIS

[Paolo Cavallini]

Il 10/02/2018 14:38, Anita Graser ha scritto:
> On Fri, Feb 9, 2018 at 11:01 AM, Richard
> Duivenvoorde mailto:rdmaili...@duif.net>> wrote:
> 
> Maybe at a hackfest, foss4g or other meeting it is good to come together
> face to face so it is easier to actually SHOW each other the
> bears/problems we see?
> 
> 
> Since Madeira is just around the corner, let's organize a round table
> discussion on this issue. I've started a section here:
> 
> https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018#future-of-processing-providers
> 
> Please add yourself to the list if you are interested in participating
> on-site or remotely. We'll then try to find a time slot that works for
> everyone. 

thanks Anita for setting it up.
Please all interested parties add your name to the list.
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&geo=IT&q=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] Plugin [1402] Calculate Geometry approval notification.

[noreply]

Plugin Calculate Geometry approval by pcav.
The plugin version "[1402] Calculate Geometry 0.1" is now approved
Link: http://plugins.qgis.org/plugins/CalculateGeometry/
___
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 [1402] Calculate Geometry approval notification.

[noreply]

Plugin Calculate Geometry approval by pcav.
The plugin version "[1402] Calculate Geometry 0.2" is now approved
Link: http://plugins.qgis.org/plugins/CalculateGeometry/
___
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] Analytics on plugin downloads

[Pedro Camargo]

Paolo,
 I do understand the motivation of the no, and I guess there is
a range of what is acceptable in terms of information collection and what
is what, but it is good to know where the QGIS development community stands
on this.

Bernd,

I do have a mailing list. blog and issue tracker on GitHub that allows for
people to reach me, but my intention was only to have insights such as
where my users are, so I can provide examples and data samples that are
more pertinent to them.

I will look into creating a survey to be distributed with the next version
of the plugin (a link in the *about* menu).


Cheers,
Pedro

On Fri, Feb 9, 2018 at 11:23 AM, Pedro Camargo 
wrote:

> Hi,
>  As I continue the development of AequilibraE (a plugin focused on
> tools for transportation modelling), I wish I had access to statistics on
> who has downloaded the plugin (e.g. Google Analytics).  That would help me
> see what the audience is and, hopefully, gauge better where to put efforts
> on.
>
> Is that something that other people also see as useful?  If so, is that
> technically possible? Is that planned in any ways?
>
> Cheers,
> Pedro
>
>
>
___
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] [GRASS-dev] External providers in QGIS

[Anita Graser]

On Fri, Feb 9, 2018 at 11:01 AM, Richard Duivenvoorde 
 wrote:

> Maybe at a hackfest, foss4g or other meeting it is good to come together
> face to face so it is easier to actually SHOW each other the
> bears/problems we see?
>

Since Madeira is just around the corner, let's organize a round table
discussion on this issue. I've started a section here:

https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018#future-of-processing-providers

Please add yourself to the list if you are interested in participating
on-site or remotely. We'll then try to find a time slot that works for
everyone.

Regards,
Anita
___
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] Processing Help system

[Richard Duivenvoorde]

On 10-02-18 08:34, Alexander Bruy wrote:
> Hi Richard,
> 
> 2018-02-09 16:08 GMT+02:00 Richard Duivenvoorde :
>> Would it be possible to write, the url which is searched for, to the
>> MessageLog/Log Message Panel (in a tab named 'QGIS Help') or so?
> 
> PR is here https://github.com/qgis/QGIS/pull/6303
> Hope this is what you are asking for.
> 
> Also this PR adds online User Guide as default help location to global 
> settings.

Thanks Alex! Comment added at PR

Regards,

Richard

___
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 [715] DSG Tools approval notification.

[noreply]

Plugin DSG Tools approval by pcav.
The plugin version "[715] DSG Tools 3.1" is now approved
Link: http://plugins.qgis.org/plugins/DsgTools/
___
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