Re: [QGIS-Developer] Some thought on LTR

2019-08-01 Thread Matthias Kuhn
Hi Matteo On 8/2/19 7:15 AM, matteo wrote: Hi, Right -- but again, I see no concrete issues here. We have one issue which isn't a regression (postgis rasters) and is instead a feature request, and one regression which was caused by an important fix (broken grass for Windows non-English users),

Re: [QGIS-Developer] On github, gitlab, and imperialist nations screwing us all over...

2019-08-01 Thread Alessandro Pasotti
On Fri, Aug 2, 2019 at 6:45 AM Paolo Cavallini wrote: > Hi all. > I'm often unhappy when I'm right. Although the practical impact this time > is low, I would take this as a clear signal (after the loomio move, and I > expect more) that we have to change our strategy, keeping our > infrastructure

Re: [QGIS-Developer] A plea: "fixes" vs "features"

2019-08-01 Thread Paolo Cavallini
Hi all, I understand the frustration from both sides. Roughly, our users mostly demand more stability, whereas customers mostly pay for new features. We have balanced this using QGIS.ORG budget, by having more tests, but obviously we can't cover all. I'm pretty sure over time things will keep on

Re: [QGIS-Developer] Some thought on LTR

2019-08-01 Thread matteo
Hi, > Right -- but again, I see no concrete issues here. We have one issue > which isn't a regression (postgis rasters) and is instead a feature > request, and one regression which was caused by an important fix > (broken grass for Windows non-English users), not a feature! (And one > unknown issu

Re: [QGIS-Developer] On github, gitlab, and imperialist nations screwing us all over...

2019-08-01 Thread Paolo Cavallini
Hi all. I'm often unhappy when I'm right. Although the practical impact this time is low, I would take this as a clear signal (after the loomio move, and I expect more) that we have to change our strategy, keeping our infrastructure as simple as possible and avoiding wherever possible to rely on

Re: [QGIS-Developer] QGIS 3.8.1 installer MacOS- Python Library

2019-08-01 Thread shiva reddy
Thanks, But if I want to share my plugin with other users who are using this new installer, there should be some way to install libraries by the users similar to windows. Thanks & Regards Shiva Reddy K. Scientist/Engineer 'SD' Indian Institute of Remote Sensing, Indian Space Research Organisati

[QGIS-Developer] A plea: "fixes" vs "features"

2019-08-01 Thread Nyall Dawson
Hi list, This is something which has been on my mind a lot lately. Whenever a question comes up about regressions or stability, the argument is often thrown around that developers are writing "fun new features, not fixes". I personally think this argument is a red herring. At best, it's a mislead

Re: [QGIS-Developer] Some thought on LTR

2019-08-01 Thread Nyall Dawson
On Fri, 2 Aug 2019 at 00:17, matteo wrote: > > Hi Nyall, > > > I'm not saying that we DON'T have some bad regressions which slip in > > occasionally to the LTR (the recent db manager regression discussion > > comes to mind), but I honestly don't think there's a bigger problem > > here. Everything

Re: [QGIS-Developer] SAGA release 7.3 (new LTR)

2019-08-01 Thread Nyall Dawson
On Fri, 2 Aug 2019 at 05:06, Johan Van de Wauw wrote: > > Hi all, > > SAGA has released a 7.3 version at the end of june, and I intend to keep a > stable branch based on this release, and drop support of the old branch > (which was not maintained well). > I am aware of the next-gen processing pl

[QGIS-Developer] SAGA release 7.3 (new LTR)

2019-08-01 Thread Johan Van de Wauw
Hi all, SAGA has released a 7.3 version at the end of june, and I intend to keep a stable branch based on this release, and drop support of the old branch (which was not maintained well). I am aware of the next-gen processing plugin at https://plugins.qgis.org/plugins/processing_saga_nextgen/ whic

Re: [QGIS-Developer] QGIS 3.8.1 installer MacOS- Python Library

2019-08-01 Thread Tim Sutton
Hi Shiva You should use William Kyngesburye’s packages rather if this is a requirement. See the ‘Alternative build’ section on http://download.qgis.org . Regards Tim > On 1 Aug 2019, at 10:19, shiva reddy > wrote: > > Hi, > I have just

Re: [QGIS-Developer] Some thought on LTR

2019-08-01 Thread Tim Sutton
Hi > On 1 Aug 2019, at 15:04, matteo wrote: > > Hi Tim, > >>> I'm not writing this email because I have a proposal, >> >> In addition to Nyall’s reply, can I ask what the actual proposal you >> have is? Hint: proposals like ‘I would like to donate 10 million USD to >> support LTRs and fix ev

Re: [QGIS-Developer] Some thought on LTR

2019-08-01 Thread matteo
Hi Nyall, > I'm not saying that we DON'T have some bad regressions which slip in > occasionally to the LTR (the recent db manager regression discussion > comes to mind), but I honestly don't think there's a bigger problem > here. Everything listed here (GRASS provider, PostGIS rasters, db > manage

Re: [QGIS-Developer] Some thought on LTR

2019-08-01 Thread matteo
Hi Tim, >> I'm not writing this email because I have a proposal,  > > In addition to Nyall’s reply, can I ask what the actual proposal you > have is? Hint: proposals like ‘I would like to donate 10 million USD to > support LTRs and fix every known bug’ would be warmly accepted. But > seriously if

[QGIS-Developer] nightly-release not available

2019-08-01 Thread David Marteau
Hi, It seems that nightly-release is broken for Debian buster: packages files https://qgis.org/debian-nightly-release/dists/buster/main/binary-i386/Packages is empty and installation from this repo gives 'E: Unabl

Re: [QGIS-Developer] Some thought on LTR

2019-08-01 Thread Tim Sutton
Hi > I'm not writing this email because I have a proposal, In addition to Nyall’s reply, can I ask what the actual proposal you have is? Hint: proposals like ‘I would like to donate 10 million USD to support LTRs and fix every known bug’ would be warmly accepted. But seriously if you have a go

Re: [QGIS-Developer] On github, gitlab, and imperialist nations screwing us all over...

2019-08-01 Thread Andreas Neumann
Hi Ian, Am 01.08.19 um 11:21 schrieb Ian Turton: I would suspect that switching to gitlab would not be sufficient as it is still with in the USA and would be subject to the same restrictions. Also if self-hosting we will need to make sure it outside the USA. Yes - our self-hosted infrastruct

Re: [QGIS-Developer] On github, gitlab, and imperialist nations screwing us all over...

2019-08-01 Thread Ian Turton
I would suspect that switching to gitlab would not be sufficient as it is still with in the USA and would be subject to the same restrictions. Also if self-hosting we will need to make sure it outside the USA. There is also a suggestion that China could be added to the list of "banned" countries t

[QGIS-Developer] QGIS 3.8.1 installer MacOS- Python Library

2019-08-01 Thread shiva reddy
Hi, I have just installed QGIS 3.8.1 in my MacBook using the official installer. The python in QGIS is not able to access the packages which are installed in the local python user directory. How can install the packages in the python bundled with QGIS 3.8.1? Thanks & Regards Shiva Reddy K. Scien

Re: [QGIS-Developer] [Info][Howto] Python Processing script to create an output without input

2019-08-01 Thread João Gaspar
Hi Nyall, sorry for the iface issue my bad. When I used it was to attempt to load the layer after the creation of the vector layer. 1 lesson learn - Hey iface stay away from processing :P Thank you for your time this small fix is now working. Best regards. Nyall Dawson escreveu no dia quarta,

Re: [QGIS-Developer] On github, gitlab, and imperialist nations screwing us all over...

2019-08-01 Thread Andreas Neumann
Hi, Thanks for bringing up this discussion. My personal opinion is that we should be worried by such development and should have a plan B for hosting our code. We certainly want QGIS and its source code to be available world wide, not just to parts of the world at the mercy of some governmen

Re: [QGIS-Developer] On github, gitlab, and imperialist nations screwing us all over...

2019-08-01 Thread Vincent Picavet (ml)
Hi Nyall, all, On 01/08/2019 06:26, Nyall Dawson wrote: > Well, I've got to say upfront that we WERE warned about the dangers of > this happening by members of our community, and now the worst IS > happening and Github has started blocking access to projects from > certain regions. > > See https: