[QGIS-Developer] QGIS Server master WMS test fail
Hi, I was looking over QGIS server OGC testing site and saw that WMS failed, for some week or so. Here: http://test.qgis.org/ogc_cite/wms_130/2018_11_19_06_00/report.html Is someone looking at this? best regards, Uroš ___ 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] docker, PyQGIS, Travis failing on PR
On Mon, Nov 19, 2018 at 11:20 AM Denis Rouzaud wrote: > > * PyQGIS > The good part is that PyQGIS 3.4 is out https://qgis.org/pyqgis/3.4/ and > that the build of the API is now fully working on Travis/Docker. > > Hi Denis, can you point me to the scripts that build the Python API documentation? -- 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
Re: [QGIS-Developer] docker, PyQGIS, Travis failing on PR
Hi Alessandro, Le lun. 19 nov. 2018 à 18:00, Alessandro Pasotti a écrit : > > can you point me to the scripts that build the Python API documentation? > Everything happens here https://github.com/qgis/pyqgis > Would you please tell me when I can rebase and merge the backport for > https://github.com/qgis/QGIS/pull/8500 ? > > As Matthias requested, he would like to test if this doesn't break current testing. I will not be able to do it this week, but I will do next. Cheers, Denis -- Denis Rouzaud de...@opengis.ch +41 76 370 21 22 ___ 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 [1412] GeoDataFarm approval notification.
Plugin GeoDataFarm approval by pcav. The plugin version "[1412] GeoDataFarm 2.0.3" is now approved Link: http://plugins.qgis.org/plugins/geodatafarm/ ___ 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 [87] Profile tool approval notification.
Plugin Profile tool approval by pcav. The plugin version "[87] Profile tool 4.1.4" is now approved Link: http://plugins.qgis.org/plugins/profiletool/ ___ 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] Custom parameters in Processing scripts
Hi Nyall, > Yep -- see e.g. > > Defining a new widget type: > https://github.com/nyalldawson/pyqgis/blob/master/processing/layout_algorithms.py#L67 > > > Using your custom widget in an algorithm: > > https://github.com/nyalldawson/pyqgis/blob/master/processing/layout_algorithms.py#L182 awesome, thanks! Matteo ___ 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] Cannot load QGIS source code in QTCreator
Hi Andrea, sorry, I totally forgot about this: https://github.com/elpaso/qgis-dev-vagrant I did not use it after I created it, so YMMV. On Wed, Nov 14, 2018 at 12:26 PM Andrea Aime wrote: > Hi, > I'm trying to load the master branch of QGIS into QTCreator following the > instructions at > https://www.qgis.org/it/site/getinvolved/development/qgisdevelopersguide/qtcreator.html > Trying to load the CMakeLists.txt file fails immediately, and I get this > in the console: > > Running "/usr/bin/cmake -E server --pipe=/tmp/cmake-TWdPXn/socket > --experimental" in /home/aaime/tmp/qgis-build. > > CMake Project parsing failed. > > Parsing of CMake project failed: Connection to CMake server lost. > > > I've only found this ticket searching the internet, unfortunately, it > contains no workaround: > > https://bugreports.qt.io/browse/QTCREATORBUG-20972 > > > My environment is a Linux Mint 19, which should be based on Ubuntu Bionic > (I've setup the dependencies as per docs on bionic distros). > > > Does anyone know of workarounds to use QTCreator? > > Or, should I look at setting up using a different IDE? > > > Cheers > > Andrea > > > == GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > --- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* > ___ > 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 -- 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
Re: [QGIS-Developer] iOS prototyping
Thanks for your great inputs Matthias. Yes we (Nyall and myself) probably used some alarming words at the start of the thread like ‘MIT’….but to all reading don’t get sidetracked by that on focus rather on the idea that QGIS as a project should be able to meet future challenges and adapt to them. While some people made dismissive comments about one platform or another, don’t let your personal bias towards or against a platform cloud the issue. If our goal is to make QGIS available only on a platform that we like we miss the point of making a mass appeal GIS that everyone can run on their preferred device. I would far prefer a situation where QGIS.org holds the ability to change licence (think micro-tweaks rather than all out change to MIT or some other license) to meet with changing times. If we want to achieve that, we need to start sooner or later getting past and present contributors to assign their work to QGIS.org. In my mind this is exactly the kind of reason we went to all the trouble of creating QGIS.org and we should use the organisation to our combined benefit. Even if we cannot get every developer to sign over their code to QGIS.org, over time the delta between signed over code and non signed over code will get small enough that we can replace code that isn’t signed over if needed ….. Regards Tim > On 16 Nov 2018, at 15:20, Matthias Kuhn wrote: > > Am I too late for the party? Probably. > > Anyway... > > From what I can see there are different sides to this discussion: > > * Is a (potential) license change feasible > > This question is very hard to answer since there are a lot of > stakeholders and uncertainties attached to it. > > I don't know, apparently it has successfully been done before on other > projects (see VLC). I'm not gonna go into much more detail here, as I > don't think I'll be able to help much in finding a final answer here. > The only way to find this answer will be to actually try. > > * Is a (potential) license change something we want > > This is a question to be answered from each developer's individual > standpoint. > > There are so many things in QGIS, where the project structures (with > PSC, voting members and community involved) play a huge rule in what I > do and what happens to the code I wrote. As you all know, I'm still > around, so you can interpret that I am in general happy with what's > happening. All in all, I have a huge trust in these structures. In fact, > I think I tell people similarly often how proud I am of our projects > structures as I tell them about how proud I am of the product itself. I > truly believe, that these structures are sustainable enough to withstand > an unfriendly takeover. > > The past has also shown, that forks kept in private (n.b. in a GPL > compliant way) could not stop the main and completely open QGIS to be > the thing that people actually want. The most important part license > wise for me is, that QGIS is freely available for anyone on whatever > platform wherever he may be and that he is able to use its functionality > and adjust it to his needs if he wishes to do so. > > Given that, I would seriously consider to give the PSC the power to > adjust the license for good reasons. Ask me and you'll have good chances > to get that. At least I know that in the "worst case" and (totally > unexpected) abuse of those rights we're still be able to fork under the > GPL terms. > > Last but not least, a license has been chosen by a person or a group of > people at a given point in time. Knowledge at this point in time by the > people in charge is what is taken into account when choosing a license. > The outside world can move on and change and new requirements to > licenses can come up which are not covered by the original license. > > An example: it should be possible to provide QGIS as a service via a > remote desktop like cloud platform and change whatever you want without > being forced to publish the source code with the current license (Note: > I'm not a lawyer). At the same time it's really hard to distribute QGIS > based public code to Apple tablets with the current license (Note: I'm > not a lawyer). Personally I'd prefer things to be vice versa. > > Best regards > > Matthias > > On 11/10/18 3:55 PM, Greg Troxel wrote: > >> Paolo Cavallini writes: >> >>> thanks for this discussion. I'm also pretty sure getting a property >>> transfer from all developers will be difficult if not impossible (quite >>> a few devs even disappeared from the radar, not easy to find them again). >>> >>> A possible intermediate step would be to: >>> >>> * get the transfer of code property to QGIS.ORG only from those >>> developers who are happy to do it >> That makes sense, but wrapped up in that question is: >> >> what is the reciprocal covenant about future licensing that goes with >> the copyright assignment? >> >> or perhaps you really mean "assignment with no reciprocal covenant at >> all, from those
[QGIS-Developer] docker, PyQGIS, Travis failing on PR
Hi all, I have been working on small improvements on our CI lately. There have been some nice things coming, but also a few things failing this monday morning. * New docker images Since building the PyQGIS API docs requires very recent versions of libs, two docker images are now built. One based on Ubuntu Bionic where the tests run fine, and one on Ubuntu Cosmic where we can properly build the API docs. Added to this, Alessandro also modified the image built (master only for now) which now integrate QGIS itself. The idea behind this is to test plugin with a full QGIS running (and not only core libs as before). * Travis changes To achieve this, some builds were duplicated. I have reformatted a bit the files and this is hopefully a tiny bit clearer now (Docker images builds are explicitly declared in .travis.yml) The Docker credentials were saved in the Travis online config which apparently got overwritten by the new "env: global:" in the Travis file. I have now integrated the credentials in the file. PR were not supposed to push the base dependencies image to Docker hub this has been fixed. * PR failing You should now be able to retrigger the builds on your PR, this should not require a rebase. * PyQGIS The good part is that PyQGIS 3.4 is out https://qgis.org/pyqgis/3.4/ and that the build of the API is now fully working on Travis/Docker. Sorry for the mess this morning. I'll try to followup if there is any issue (not sure the login is fixed) but I will be offline often in the next 3 days. Thanks for your understanding! Denis -- Denis Rouzaud de...@opengis.ch +41 76 370 21 22 ___ 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] docker, PyQGIS, Travis failing on PR
And as a side-note, Travis just replied that our build time was increased to 150 minutes, this should allow us to build QGIS images even if cache is not available. Le lun. 19 nov. 2018 à 11:20, Denis Rouzaud a écrit : > Hi all, > > I have been working on small improvements on our CI lately. There have > been some nice things coming, but also a few things failing this monday > morning. > > * New docker images > Since building the PyQGIS API docs requires very recent versions of libs, > two docker images are now built. One based on Ubuntu Bionic where the tests > run fine, and one on Ubuntu Cosmic where we can properly build the API docs. > Added to this, Alessandro also modified the image built (master only for > now) which now integrate QGIS itself. The idea behind this is to test > plugin with a full QGIS running (and not only core libs as before). > > * Travis changes > To achieve this, some builds were duplicated. I have reformatted a bit the > files and this is hopefully a tiny bit clearer now (Docker images builds > are explicitly declared in .travis.yml) > The Docker credentials were saved in the Travis online config which > apparently got overwritten by the new "env: global:" in the Travis file. I > have now integrated the credentials in the file. PR were not supposed to > push the base dependencies image to Docker hub this has been fixed. > > * PR failing > You should now be able to retrigger the builds on your PR, this should not > require a rebase. > > * PyQGIS > The good part is that PyQGIS 3.4 is out https://qgis.org/pyqgis/3.4/ and > that the build of the API is now fully working on Travis/Docker. > > Sorry for the mess this morning. I'll try to followup if there is any > issue (not sure the login is fixed) but I will be offline often in the next > 3 days. > > Thanks for your understanding! > Denis > -- > > Denis Rouzaud > de...@opengis.ch > +41 76 370 21 22 > > > -- Denis Rouzaud de...@opengis.ch +41 76 370 21 22 ___ 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] docker, PyQGIS, Travis failing on PR
Thank you for your great work Denis! Would you please tell me when I can rebase and merge the backport for https://github.com/qgis/QGIS/pull/8500 ? On Mon, Nov 19, 2018 at 11:20 AM Denis Rouzaud wrote: > Hi all, > > I have been working on small improvements on our CI lately. There have > been some nice things coming, but also a few things failing this monday > morning. > > * New docker images > Since building the PyQGIS API docs requires very recent versions of libs, > two docker images are now built. One based on Ubuntu Bionic where the tests > run fine, and one on Ubuntu Cosmic where we can properly build the API docs. > Added to this, Alessandro also modified the image built (master only for > now) which now integrate QGIS itself. The idea behind this is to test > plugin with a full QGIS running (and not only core libs as before). > > * Travis changes > To achieve this, some builds were duplicated. I have reformatted a bit the > files and this is hopefully a tiny bit clearer now (Docker images builds > are explicitly declared in .travis.yml) > The Docker credentials were saved in the Travis online config which > apparently got overwritten by the new "env: global:" in the Travis file. I > have now integrated the credentials in the file. PR were not supposed to > push the base dependencies image to Docker hub this has been fixed. > > * PR failing > You should now be able to retrigger the builds on your PR, this should not > require a rebase. > > * PyQGIS > The good part is that PyQGIS 3.4 is out https://qgis.org/pyqgis/3.4/ and > that the build of the API is now fully working on Travis/Docker. > > Sorry for the mess this morning. I'll try to followup if there is any > issue (not sure the login is fixed) but I will be offline often in the next > 3 days. > > Thanks for your understanding! > Denis > -- > > Denis Rouzaud > de...@opengis.ch > +41 76 370 21 22 > > > ___ > 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 -- 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
[QGIS-Developer] Plugin [1498] Extreme Value Classification for Polygon approval notification.
Plugin Extreme Value Classification for Polygon approval by pcav. The plugin version "[1498] Extreme Value Classification for Polygon 0.6 Experimental" is now approved Link: http://plugins.qgis.org/plugins/aChor/ ___ 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
