[QGIS-Developer] Plugin [1350] Mascaret approval notification.

[noreply]

Plugin Mascaret approval by zimbogisgeek.
The plugin version "[1350] Mascaret 0.0.6 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/Mascaret/
___
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] Get rid of Processing scripts in favour of plain alogrithms

[Victor Olaya]

I like the idea, but i dont think it will mean less code, specially
for defining the parameters and outputs. Why not keeping it for those
that want to use it this way?

Before removing this (in case it's decided to do so), two things to notice:

-- There were algorithms (built-in ones) defined this way, so they
should be rewritten
-- There is a little-known functionality that creates a new plugin
from a set of scripts. It should be adapted as well, or removed.

Thanks!


2018-01-30 21:41 GMT+01:00 G. Allegri :
> I know there are much more important priorities in view of the QGIS 3.0
> release.
> I will try to implement the idea of Geoalgorithms served by the script
> provider and, in case, I'll commit a PR for testing and comments.
>
> Giovanni
>
> Il 29 gen 2018 16:44, "Anita Graser"  ha scritto:
>>
>>
>>
>> On Mon, Jan 29, 2018 at 2:24 PM, G. Allegri  wrote:
>>>
>>> What's your opinion
>>> ?
>>>
>>
>> +
>> 1 for me, as stated in the original thread
>> https://lists.osgeo.org/pipermail/qgis-developer/2018-January/051511.html
>>
>>
>> I think it will be good to unify the approaches.
>>
>> 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
___
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] update of otb plugin for QGIS

[Tisham Dhar]

Hi Rashad,

I meant pre-built OTB binaries rather than plugin binaries. I believe QGIS 
builds on more platforms than OTB does.

Regards,

Tisham.

From: Rashad Kanavath [mailto:mohammedrasha...@gmail.com]
Sent: Tuesday, January 30, 2018 7:45 PM
To: Tisham Dhar 
Cc: qgis-developer@lists.osgeo.org
Subject: Re: [QGIS-Developer] update of otb plugin for QGIS


Hell Tisham,

Can you explain the part of binaries issue?

The documentation of build from source is already there for OTB. The new module 
which if merged into Modules/Wrappers/QGIS will be like any other otb module.
Since there are no external dependencies, this could be enabled by default. So 
need to specific documentation to build it is not required.

But once the coding work is done, there will be another (RFC) and in that i 
will include the usage, builds options etc..

On Tue, Jan 30, 2018 at 1:10 AM, Tisham Dhar 
> wrote:
Hi All,

I am an avid supporter to OTB and would love to see the plugin brought more in 
line with latest developments in OTB. The binaries issue will always exist and 
I believe OTB should support the same ones for which Qgis binaries are 
available already. The other platforms should have a clear build from source 
documentation. These should be listed in the RFC.

Regards,

Tisham Dhar
Research Engineer
Aerometrex PTY LTD
59 King William St.
Kent Town SA 5067
Australia


___
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



--
Regards,
   Rashad
___
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] Commit rights for Luigi Pirelli

[Tim Sutton]

MacGyver was working on some commits but ran off to find a rusty nail and
seven bottlecaps to improvise an antennae for his failing WIFI connection.

Thanks Luigi - I have added you on GitHub and on the committers voting
group on Loomio (please check your email for the invitation).

Regards

Tim

On Tue, Jan 30, 2018 at 10:59 AM, Luigi Pirelli  wrote:

> Hi community,
>
> as requested, I read the requirement for new contributors [1] and I accept
> and agree with accepting it. I read the three referred documents and I
> accept and agree with them.
>
> Will be an honor to be contributor with Chuck Norris [2]. Has also
> MacGyver commit right? ;)
>
> as requested I post this answer also in qgis-developer list
>
> cheers and thanks
>
> Luigi Pirelli
>
> [1] https://www.qgis.org/en/site/getinvolved/development/
> contributor_requirements.html
> [2] https://www.qgis.org/en/site/getinvolved/development/
> qgisdevelopersguide/codingstandards.html#credits-for-contributions
>
>
> 
> **
> * LinkedIn: https://www.linkedin.com/in/luigipirelli
> * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
> * GitHub: https://github.com/luipir
> * Mastering QGIS 2nd Edition:
> * https://www.packtpub.com/big-data-and-business-
> intelligence/mastering-qgis-second-edition
> * Hire me: http://goo.gl/BYRQKg
> 
> **
>
> On 30 January 2018 at 07:35, Tim Sutton  wrote:
>
>> Hi
>>
>> +1 from me too!
>>
>> @Luigi to be more precise about the process, you should please read:
>>
>> https://www.qgis.org/en/site/getinvolved/development/contrib
>> utor_requirements.html
>>
>> And the linked documents on codie of conduct, diversity etc. and then
>> send an email to the PSC indicating that you agree to abide by these.
>>
>> Then I will add you to the write group (please provide the github user
>> name that should be used for this).
>>
>> Regards
>>
>> Tim
>>
>> On Tue, Jan 30, 2018 at 8:29 AM, Paolo Cavallini 
>> wrote:
>>
>>> Il 30/01/2018 01:38, Nyall Dawson ha scritto:
>>> > Unsurprisingly, there seems to be universal support for this! How can
>>> > we proceed? Tim?
>>>
>>> AFAIK Luigi shpould read and accept our guidelines, and anyone can grant
>>> him commit rights.
>>> 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-psc mailing list
>>> qgis-...@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>>
>>
>>
>>
>> --
>> 
>> --
>> ​
>>
>> Tim Sutton
>> 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
>> Tim is a member of the QGIS Project Steering Committee
>> 
>> ---
>> Kartoza is a merger between Linfiniti and Afrispatial
>>
>
>


-- 
--
​

Tim Sutton
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
Tim is a member of the QGIS Project Steering Committee
---
Kartoza is a merger between Linfiniti and Afrispatial
___
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] Get rid of Processing scripts in favour of plain alogrithms

[G. Allegri]

I know there are much more important priorities in view of the QGIS 3.0
release.
I will try to implement the idea of Geoalgorithms served by the script
provider and, in case, I'll commit a PR for testing and comments.

Giovanni

Il 29 gen 2018 16:44, "Anita Graser"  ha scritto:

>
>
> On Mon, Jan 29, 2018 at 2:24 PM, G. Allegri  wrote:
>>
>> What's your opinion
>> ​?​
>>
>>
> +
> ​1 for me, as stated in the original thread https://lists.osgeo.org/piperm
> ail/qgis-developer/2018-January/051511.html
>
>
> I think it will be good to unify the approaches.
>
> 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] How are Featured Plugins Chosen?

[Tobias Wendorff]

Hi there,

Am Di, 30.01.2018, 18:39 schrieb C Hamilton:
> I haven't really monitored
> them, but when ever I look they seem like they are about the same set.

Interesting question.

Many websites advertise the number of downloads, which I consider to
be total nonsense. Interesting would be a rating like "usage per month".
Even installations per month don't make sense to me, because I have
installed some plugins that I don't use - I'm just too lazy to
uninstall them :)

BUT this would make some plugins stay on the top forever...

Maybe you should also consider how well a plugin is documented and
whether there are examples. This could give a more positive assessment,
With many plugins I have no idea how to use them at all.

Best regards,
Tobias

___
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] How are Featured Plugins Chosen?

[C Hamilton]

I am curious about how he so called Featured Plugins are chosen and I know
it is very subjective so I apologize if this is a bad question. I think
there are some very good choices on that list and then I think there might
be some better choices put on. Do these change? I haven't really monitored
them, but when ever I look they seem like they are about the same set.

The important ones in my opinion are:
qgis2web
QucikMapServices
Qgis2threejs - Although with QGIS3 this may not be as important of a plugin
Quick Finder
TimeManager
Geocoding

The others listed will only be used by a small set of users and some by a
very small set of user. I'm sure there are other plugins that would be
better to feature. I think some of the new plugins, if they are evaluated
to work well, have a unique capability, and have good documentation on how
to use it, should occasionally be featured.

Thanks,

Calvin
___
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] QGIS3 Plugin debugging help

[Chris Crook]

(see nabble link for context)

i've run this with a debugger.  It does indeed identify the location of the
crash as in the matplotlib triangulation function, and specifically within
qh_initstatistics which is called to construct the convex hull of the
points.  Which I guess means there is an issue with matplotlib.  But the
same function call outside QGIS works, so I'm wondering if the python3
runtime environment in QGIS could in some way be different to the command
line run time environment. 






--
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

[QGIS-Developer] plugin causes 2.99 to crash - help?

[Tom Chadwin]

Hello all

I'm converting qgis2web for QGIS3, and a lot of the work is done. However,
the following steps cause QGIS to crash:

1. start qgis2web (Github master)
2. if Leaflet is selected, click "Update preview", otherwise select Leaflet
3. close the plugin dialog

This crashes QGIS (latest nightly), and has done with the nightlies for a
long time (issue raised here on 13 December:
https://github.com/tomchadwin/qgis2web/issues/590). I therefore assume it's
something in the plugin code which causes the crash, not in QGIS.

Points to note - the issue does *NOT* occur:

1. with QGIS2 (with compatible qgis2web version)
2. if no preview has been triggered
3. if only an OpenLayers preview has been triggered (instead of a Leaflet
one)
4. if a Leaflet export is triggered without a preview

Nathan's crash handler gives this:

*Crash ID*: 02cceb1e82fb35298845d686d09e3e52b108ee1b

*Stack Trace*
qWebKitVersion :
WKNotificationGetSecurityOrigin :
QObject::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify qgsapplication.cpp:317
QCoreApplication::notifyInternal2 :
QEventDispatcherWin32::event :
QApplicationPrivate::notify_helper :
QApplication::notify :
QgsApplication::notify qgsapplication.cpp:317
QCoreApplication::notifyInternal2 :
QCoreApplicationPrivate::sendPostedEvents :
qt_plugin_query_metadata :
QEventDispatcherWin32::processEvents :
TranslateMessageEx :
TranslateMessage :
QEventDispatcherWin32::processEvents :
qt_plugin_query_metadata :
QEventLoop::exec :
QCoreApplication::exec :
main main.cpp:1431
WinMain mainwin.cpp:161
__scrt_common_main_seh exe_common.inl:253
BaseThreadInitThunk :
RtlUserThreadStart :


*QGIS Info*
QGIS Version: 2.99.0-Master
QGIS code revision: commit:d2244b4a79
Compiled against Qt: 5.9.2
Running against Qt: 5.9.2
Compiled against GDAL: 2.2.3
Running against GDAL: 2.2.3



*System Info*
CPU Type: x86_64
Kernel Type: winnt
Kernel Version: 6.1.7601


As Nathan points out on the plugin issue thread linked to above, the crash
seems to occur in QtWebkit, but beyond that, I have no clues on the cause,
or how to fix.

So:

1. Do others confirm this issue on Windows?
2. How about other OSes
3. Any ideas on solving the problem?

Many thanks for any help anyone can offer. I'm very close to finishing the
conversion, so I really want to try to solve this.

Many thanks

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

[QGIS-Developer] Should I wait to develop processing routines?

[C Hamilton]

I have been seeing the chatter about Processing scripts and plugins. I just
released one processing function for my Shape Tools plugin. Based on the
possibility that the way processing scripts may be changed, should I hold
off in developing further processing routines in my plugins or is this only
going to apply to processing scripts and not processing plugins?

Thanks,

Calvin
___
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] WARNING No QgsCoordinateTransformContext context set for transform

[Denis Rouzaud]

Hi,

The issue is not PyQGIS but rather unfixed call to QgsCoordinateTransform
constructors.

See https://github.com/qgis/QGIS/pull/5535 and the "future work" part.
According to Nyall, some are quite complex to fix and not in the first
priority (like map rendering, copy/paste, etc).

Cheers,
Denis


Le mar. 30 janv. 2018 à 09:41, Tom Chadwin  a
écrit :

> Hi Andreas
>
> See here:
> https://lists.osgeo.org/pipermail/qgis-developer/2017-December/051085.html
>
> Thanks
>
> 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
___
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] WARNING No QgsCoordinateTransformContext context set for transform

[Mathieu Pellerin]

Andreas,

I've dealt with two sources of such warnings today, one which caused one
warning on every canvas redraw (the north arrow decoration), the other
caused many warnings upon (re-)drawing the content of the overview panel.

One of the few remaining sources of warnings is with the WMS/XYZ raster
provider. But that's unlikely to be tackled prior to release of 3.0.
Fortunatelly, the warnings are harmless, and won't show on non-debug builds.

Math

On Tue, Jan 30, 2018 at 7:56 PM, Andreas Neumann 
wrote:

> Hi,
>
> I have a QGIS project with a history (started in QGIS 2.x) that we carried
> over to QGIS 3.
>
> Since some time (some weeks) for every redraw I get several times
> (probably for every layer) the following warning message in the "Qt" log
> message panel:
>
> 2018-01-30T13:51:13 WARNING No QgsCoordinateTransformContext context set
> for transform
> 2018-01-30T13:51:13 WARNING No QgsCoordinateTransformContext context set
> for transform
> 2018-01-30T13:51:13 WARNING No QgsCoordinateTransformContext context set
> for transform
> 2018-01-30T13:51:13 WARNING No QgsCoordinateTransformContext context set
> for transform
> 2018-01-30T13:51:13 WARNING No QgsCoordinateTransformContext context set
> for transform
> 2018-01-30T13:51:13 WARNING No QgsCoordinateTransformContext context set
> for transform
> 2018-01-30T13:51:13 WARNING No QgsCoordinateTransformContext context set
> for transform
>
> I believe this has to do with the recent changes in datum handling.
>
> But how would I fix the issue to get rid of the flood of warning messages?
> After a few redraws there are thousands iterations of the same warning
> message.
>
> Thank you for your help!
>
> Andreas
>
>
>
> ___
> 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 2.99 weekly snapshot 64 bits

[SIGéal]

Thank you for the answer.
I am in the process of migrating plugins.
I'll try OSGeo4W installer.

--
Christophe

Le 30/01/2018 à 10:53, Jürgen E. Fischer a écrit :

Hi Christophe,

On Tue, 30. Jan 2018 at 10:22:05 +0100, SIGéal wrote:

It seems that QGIS 2.99 weekly snapshot is only available in 32 bits
version.
Does anyone know why the 64 bits version isn't available anymore ?

It currently exceeds NSIS' 2GB limit (GRASS needs py2 - so we have to include
py2 & 3).

Is the OSGeo4W installer an option for you?


Jürgen



___
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] QGIS3 Plugin debugging help

[Tom Chadwin]

Hi Chris

Have you attached a debugger, and therefore can you get a backtrace? I think
that's what you'll need.

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

[QGIS-Developer] QGIS3 Plugin debugging help

[Chris Crook]

Hi All

I am looking for suggestions on how to debug a plugin that is crashing QGIS3

I am trying to port the contour plugin to QGIS3.  The port is largely done but 
there is one outstanding issue that causes QGIS to die.

The plugin uses the python matplotlib library to do the contouring.  It has two 
modes of operating.  If the source data is gridded it will use the plt.contour 
function, and this is working as it should.  If the data is not gridded it uses 
the plt.tricontour function, which builds a triangulation and then uses that to 
do the contouring.   When the plugin calls this function it crashes QGIS.  I've 
extracted the data used in the function call from QGIS and run the tricontour 
function from a simple python program and it runs without error.  So something 
in the QGIS plugin environment is causing this to fail.

Can you suggest approaches to debugging this, or getting more information about 
where it is failing (or for that matter fixing it).   The code in question is in

https://github.com/ccrook/QGIS-Contour-Plugin/blob/qgis3_wip/contour/contour.py#L846

I am running on ubuntu 16.04 using the ubuntugis-nightly distribution.  Details 
are


QGIS version
2.99.0-Master
QGIS code revision
bcbc46b
Compiled against Qt
5.5.1
Running against Qt
5.5.1
Compiled against GDAL/OGR
2.2.2
Running against GDAL/OGR
2.2.2
Compiled against GEOS
3.5.1-CAPI-1.9.1
Running against GEOS
3.5.1-CAPI-1.9.1 r4246
PostgreSQL Client Version
9.5.2
SpatiaLite Version
4.3.0a
QWT Version
6.1.2
PROJ.4 Version
492
QScintilla2 Version
2.9.1
This copy of QGIS writes debugging output.

Matplotlib version is 1.5.1


Thanks for any suggestions - I'm feeling a bit stuck with this one :-(

Chris



This message contains information, which may be in confidence and may be 
subject to legal privilege. If you are not the intended recipient, you must not 
peruse, use, disseminate, distribute or copy this message. If you have received 
this message in error, please notify us immediately (Phone 0800 665 463 or 
i...@linz.govt.nz) and destroy the original message. LINZ accepts no 
responsibility for changes to this email, or for any attachments, after its 
transmission from LINZ. Thank You.
___
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] Bringing back a *highly curated* blocker tag on redmine?

[Daan Goedkoop]

Hello Jürgen,

apparently the open bugs which are regressions and cause data
corruption or crashes are only 10 in number at the moment (of which I
reported one). I think they are important because they can catch you
by surprise in tested and established workflows. New things will
probably only be used heavily in serious contexts after some testing,
so I feel that problems there are not quite as important.

Kind regards,

Daan

2018-01-30 11:09 GMT+01:00 Jürgen E. Fischer :
> Hi Giovanni,
>
> On Tue, 30. Jan 2018 at 09:09:52 +, Giovanni Manghi wrote:
>> * a regression that causes data corruption
>> * a regression that causes qgis to crash
>
> I still don't understand this obsession with regressions ;)
>
> Any bug that is severe should block the release.  Whether it's a regression or
> not doesn't matter.
>
> If it's an unavoidable bug in some heavy used thing that is new, it's just as
> blocking as a big bug in known territory.
>
> IMHO a bug in some remote, hardly used function shouldn't block a release -
> even if it's a regression that corrupts data and causes qgis to crash in some
> edge cases.  We'll probably have plenty of those that we don't know of anyway.
>
> To me it's just a matter of the impact on usablity a bug has.  I'd opt for
> common sense instead of setting strict rules.
>
>
> Jürgen
>
> --
> Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
> Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
> Software Engineer   D-26506 Norden http://www.norbit.de
>
> ___
> 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] Bringing back a *highly curated* blocker tag on redmine?

[Jürgen E . Fischer]

Hi Giovanni,

On Tue, 30. Jan 2018 at 09:09:52 +, Giovanni Manghi wrote:
> * a regression that causes data corruption
> * a regression that causes qgis to crash

I still don't understand this obsession with regressions ;)

Any bug that is severe should block the release.  Whether it's a regression or
not doesn't matter.

If it's an unavoidable bug in some heavy used thing that is new, it's just as
blocking as a big bug in known territory.

IMHO a bug in some remote, hardly used function shouldn't block a release -
even if it's a regression that corrupts data and causes qgis to crash in some
edge cases.  We'll probably have plenty of those that we don't know of anyway.

To me it's just a matter of the impact on usablity a bug has.  I'd opt for
common sense instead of setting strict rules.


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de


signature.asc
Description: PGP 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] Bringing back a *highly curated* blocker tag on redmine?

[Sandro Santilli]

On Tue, Jan 30, 2018 at 09:09:52AM +, Giovanni Manghi wrote:

> Examples of what, in my opinion, should be a always a real blocker:
> 
> * a regression that causes data corruption (like the one that caused
> to compute wrong area in several 2.* releases)
> * a regression that causes qgis to crash (and it wasn't the case in
> previous releases)

I think _every_ regression should be marked as a blocker.
Finding out that something broke on upgrade is a very frustrating
experience for users (us included). If such degradation was known
in advance (was in the bug tracker) it suggests release managers
did not care about such announced frustrating experience.

--strk;
___
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] Changes to processing gdal:translate?

[Tom Chadwin]

Thanks again, Nyall. I'm not confident enough to log these on Redmine, as
I've not looked into the Processing code before.

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 2.99 weekly snapshot 64 bits

[Jürgen E . Fischer]

Hi Christophe,

On Tue, 30. Jan 2018 at 10:22:05 +0100, SIGéal wrote:
> It seems that QGIS 2.99 weekly snapshot is only available in 32 bits
> version.
> Does anyone know why the 64 bits version isn't available anymore ?

It currently exceeds NSIS' 2GB limit (GRASS needs py2 - so we have to include
py2 & 3).

Is the OSGeo4W installer an option for you?


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Norden http://www.norbit.de
QGIS release manager (PSC)  GermanyIRC: jef on FreeNode


signature.asc
Description: PGP 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

[QGIS-Developer] QGIS 2.99 weekly snapshot 64 bits

[SIGéal]

Hi,

It seems that QGIS 2.99 weekly snapshot is only available in 32 bits 
version.

Does anyone know why the 64 bits version isn't available anymore ?

--
Christophe


___
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] Last call for switching to github issue tracker

[Tim Sutton]

Hi

Just as a follow up to this thread, I have started a Loomio vote for QGIS
Voters to decide if we should move to GitHub issues.

https://www.loomio.org/d/cDwCmhsG/proposal-to-shift-bug-issue-tracking-work-to-github-issues-for-qgis-3x-

Regards

Tim

On Thu, Jan 25, 2018 at 4:29 PM, Jorge Gustavo Rocha 
wrote:

> Thanks, Gio.
>
> GitLab and CI in GitLab is also included as another topic. Good!
>
> We already 30 people registered. Very good!
>
> See you in Madeira,
>
> On 25-01-2018 15:20, Giovanni Manghi wrote:
> >> (about GH) IMHO tech decision and user experience are nothing that can
> >> be fixed for more than 3y => I shouldn't decide focusing on user
> >> experience (now oauth login is widely supported), but basing on:
> >>
> >> 1) FOSS tool
> >> 2) opt-out ability
> >
> > Hi all,
> >
> > I added a topic about this matter in the next dev meeting program of
> activities:
> >
> > https://github.com/qgis/QGIS/wiki/DeveloperMeetingMadeira2018#topics
> >
> > cheers!
> >
> > -- G --
> > ___
> > 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
> >
>
> J. Gustavo
> --
> Jorge Gustavo Rocha
> Departamento de Informática
> Universidade do Minho
> 4710-057 Braga
> Tel: +351 253604480
> Fax: +351 253604471
> Móvel: +351 910333888
> skype: nabocudnosor
> ___
> 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
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
Tim is a member of the QGIS Project Steering Committee
---
Kartoza is a merger between Linfiniti and Afrispatial
___
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] update of otb plugin for QGIS

[Rashad Kanavath]

Hell Tisham,

Can you explain the part of binaries issue?

The documentation of build from source is already there for OTB. The new
module which if merged into Modules/Wrappers/QGIS will be like any other
otb module.
Since there are no external dependencies, this could be enabled by default.
So need to specific documentation to build it is not required.

But once the coding work is done, there will be another (RFC) and in that i
will include the usage, builds options etc..

On Tue, Jan 30, 2018 at 1:10 AM, Tisham Dhar 
wrote:

> Hi All,
>
>
>
> I am an avid supporter to OTB and would love to see the plugin brought
> more in line with latest developments in OTB. The binaries issue will
> always exist and I believe OTB should support the same ones for which Qgis
> binaries are available already. The other platforms should have a clear
> build from source documentation. These should be listed in the RFC.
>
>
>
> Regards,
>
>
>
> Tisham Dhar
>
> Research Engineer
>
> Aerometrex PTY LTD
>
> 59 King William St.
>
> Kent Town SA 5067
>
> Australia
>
>
>
> ___
> 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
>



-- 
Regards,
   Rashad
___
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] Bringing back a *highly curated* blocker tag on redmine?

[Giovanni Manghi]

Hi all,


> I think that a carefully used BLOCKER tag makes a lot of sense.
>
> There are some bugs that we should definitely not be part of a release or
> this will seriously impact user's trust in QGIS both as a software and as a
> community.
>
> I also suggest that the ones who take care of the bug queue (kind of QA
> managers) should be in charge of managing and lifting the blocker tag.

I'm also very much in favor of bringing it back.

Just a note: when we added the "blocker" tag (circa 2011) it wasn't
because of the "hey please fix this because it impacts me a lot!" kind
of tickets. It was added at a point we decided to enforce fixing all
the regressions before releasing a new version. During that time the
program improved *a lot*, in fact its development and adoption started
snowballing, new tickets started rain in and everything become more
complicated (and since a while it is even more complicated with both
LTR that needs to keep going and QGIS3 to be developed).

I agree that we must decide what should be tagged a blocker without
any doubt (other than obvious issues as the ones pointed by Nyall).

Examples of what, in my opinion, should be a always a real blocker:

* a regression that causes data corruption (like the one that caused
to compute wrong area in several 2.* releases)
* a regression that causes qgis to crash (and it wasn't the case in
previous releases)

else?

cheers!

-- G --
___
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] update of otb plugin for QGIS

[Rashad Kanavath]

On Mon, Jan 29, 2018 at 5:36 PM, Paolo Cavallini 
wrote:

> Il 29/01/2018 16:59, Rashad Kanavath ha scritto:
> > (x-post to qgis-developer list)
> >
> > Hello all,
> >
> > Here is an RFComments for new otb plugin.
> > https://gitlab.orfeo-toolbox.org/jmichel/otb/blob/
> 790c2b7a5e3060d4e597d078c3c92e353a102773/.gitlab/issue_
> templates/request_for_comments.md
> >
> > Feel free to send your comments and suggestions
>
> Hi Rashad,
> unclear to me how do you want to manage binaries for the many OS and
> versions QGIS supports.
> Thanks for clarifications.
>

Hello Paolo,

OTB provides a full bundle of all libs, apps and dependencies for three OS
platforms (windows, linux and macos) for every release[1] and every day[2]
These packages are tested on dashboard[3] with list of tests passing.
[1] https://www.orfeo-toolbox.org//packages/
[2] https://www.orfeo-toolbox.org//packages/nightly/latest/
[3] https://dash.orfeo-toolbox.org/index.php?project=OTB

what I was implying was the qgis descriptor files will be included in this
packages for ease install/change of otb versions.

For instance, if you have OTB 6.4 already working with plugin. An update of
otb to 6.8 will be
1. download package
2. update otb install prefix in the plugin configuration. (in sed world
s/6.4/6.8/g :)

Regarding qgis versions, there is nothing much to do if you don't change
OTB.

Hope that helps,


--
> 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




-- 
Regards,
   Rashad
___
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] Commit rights for Luigi Pirelli

[Luigi Pirelli]

Hi community,

as requested, I read the requirement for new contributors [1] and I accept
and agree with accepting it. I read the three referred documents and I
accept and agree with them.

Will be an honor to be contributor with Chuck Norris [2]. Has also MacGyver
commit right? ;)

as requested I post this answer also in qgis-developer list

cheers and thanks

Luigi Pirelli

[1]
https://www.qgis.org/en/site/getinvolved/development/contributor_requirements.html

[2]
https://www.qgis.org/en/site/getinvolved/development/qgisdevelopersguide/codingstandards.html#credits-for-contributions


**
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Mastering QGIS 2nd Edition:
*
https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition
* Hire me: http://goo.gl/BYRQKg
**

On 30 January 2018 at 07:35, Tim Sutton  wrote:

> Hi
>
> +1 from me too!
>
> @Luigi to be more precise about the process, you should please read:
>
> https://www.qgis.org/en/site/getinvolved/development/
> contributor_requirements.html
>
> And the linked documents on codie of conduct, diversity etc. and then send
> an email to the PSC indicating that you agree to abide by these.
>
> Then I will add you to the write group (please provide the github user
> name that should be used for this).
>
> Regards
>
> Tim
>
> On Tue, Jan 30, 2018 at 8:29 AM, Paolo Cavallini 
> wrote:
>
>> Il 30/01/2018 01:38, Nyall Dawson ha scritto:
>> > Unsurprisingly, there seems to be universal support for this! How can
>> > we proceed? Tim?
>>
>> AFAIK Luigi shpould read and accept our guidelines, and anyone can grant
>> him commit rights.
>> 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-psc mailing list
>> qgis-...@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>
>
>
>
> --
> 
> --
> ​
>
> Tim Sutton
> 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
> Tim is a member of the QGIS Project Steering Committee
> 
> ---
> Kartoza is a merger between Linfiniti and Afrispatial
>
___
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] Bringing back a *highly curated* blocker tag on redmine?

[Alessandro Pasotti]

On Tue, Jan 30, 2018 at 12:22 AM, Nyall Dawson 
wrote:

> Hi all,
>
> I'd like to raise the idea of resurrecting the "blocker" tag on
> redmine. I understand the reasons behind its original removal, and
> fully agree that the new process is working much better.
>
> BUT...
>
> We have two extremely serious issues open against QGIS 3.0, which I
> think SHOULD block the release. These are:
>
> https://issues.qgis.org/issues/17985 : Huge memory leak with NULL
> attributes in Python
> https://issues.qgis.org/issues/17916 : Crashes and instability with Qt
> 5.10
>
> I don't think we can proceed with any 3.0 release while these two
> issues are unsolved.
>
> That's why I'd like to see the blocker tag brought back, but with it
> actually BLOCKING the release (vs the previous definition, which
> ultimately just meant "hey please fix this because it impacts me a
> lot!"). And I'd like to see it highly curated to avoid users tagging
> their own pet bugs with it.
>
> Thoughts?
>
>
I think that a carefully used BLOCKER tag makes a lot of sense.

There are some bugs that we should definitely not be part of a release or
this will seriously impact user's trust in QGIS both as a software and as a
community.

I also suggest that the ones who take care of the bug queue (kind of QA
managers) should be in charge of managing and lifting the blocker tag.

-- 
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