Re: [QGIS-Developer] Funding and PR review
Greeting Andreas, Thanks for the reply, what I simply wanted to propose was to advertise in some way how users and sustaining members would benefit from more funding. If we could use standing issues and standing PR as showcases of how funds could benefit the project, that might entice some to contribute. I'm fully aware of the current review process and I think it's ok as it is. The increased funding is a welcome news and hopefully it'll be sufficient in the short term. Thanks again! Alex Le mar. 4 janv. 2022 à 06:13, Andreas Neumann a écrit : > Hi Alex, > > Happy new year to you as well! > > We increased the funding for PR reviews from 10 to 14k. > > However, it is up to the reviewers (currently Nyall, Matthias and > Alessandro, in the future probably also Martin) to decide what PRs they are > looking at. I understand that the above figure doesn't guarantee that they > can look at all PRs. > > My recommendation for new devs is to personally ask one of the above > people - or another QGIS dev with core commiter rights. > > In general, for paid new developments, the developer who offers the new > functionality should factor in the cost of code reviewing in the quote. > > For voluntary contributions it may be more difficult. There it probably > depends a lot on the quality of the PR and the willingness of the dev to > respond to the reviewers in a timely manner. And of course - if the PR is > interesting to one of the reviewers, it increases the chance a lot. > > I am not sure if a separate crowd funding for PR reviewing would be the > way to go. I would imagine it would be difficult to raise funds > specifically for this goal. I would rather prefer to try to get more > "sustaining members" in general, so we can increase this budget item in > upcoming years. > > Let's see what other core devs and PSC members think abou this? > > Andreas > > On Sun, 2 Jan 2022 at 14:24, Alexis R.L. wrote: > >> Greetings Everyone, >> >> Some points have been going through my head and I was curious to know if >> there could be good ideas in them for discussion and opportunities. >> >> One aspect that can irk new and existing contributors (or maybe just >> myself) is when it comes to PR reviews. As some work on either side is done >> on a voluntary basis we can't expect competent and overworked devs to want >> and to dedicate more time on some work that won't benefit them. >> >> On the other hand we also get pr that get stuck or staled out. >> >> Now I was thinking of creating a crowdfund to raise some funds for >> reviews ( I don't want to profit monetarily from any of my work). But I >> don't want to be stuck managing funds and doing PR and etc. >> >> Now I know that QGIS has some devoted funds for bugfixing and PR reviews >> to this effect. But I was curious to know if it would be a good idea to >> advertise the work (possibly in the news feed?) that would benefit from >> bugfixing or PR reviews. >> >> I'm not sure if dividing things and separating funds on a issue or >> category (bugfix vs feature vs ?) would be beneficial. But showcasing what >> they can gain from doing a contribution would probably be helpful rather >> than giving for general support. >> >> Just my two cents, I also wish everyone a good new year of developping! >> >> Alex >> ___ >> 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 >> > > > -- > > -- > Andreas Neumann > QGIS.ORG board member (treasurer) > ___ 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] Step-up for OGC compliance
Dear Community, maintaining the OGC compliance for QGIS server is a very time consuming undertaking that up to now was completely relying on the volunteer work of very few community members. Unfortunately Régis cannot follow this anymore (Thanks a lot Régis for all the work you put in!). We therefore are looking for community members to take over the lead on this. Ideally, we'd also like to see organisations that rely on QGIS server certification to step-up financially to support the big workload needed. If you have any questions, do not hesitate to contact me Cheers Marco -- Marco Bernasocchi QGIS.org Chair OPENGIS.ch CEO http://berna.io ___ 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] Leveraging Conda-Forge to create QGIS installers ?
Alessandro, Thank you for raising the subject. QGIS on conda is not at is best shape right now, as we are stuck with the lack of a full featured Qt 5.15. The current package is lacking webengine that was split. The good news is it's already built on OSX arm64 which may be useful in the future. Alexandre Neto A terça, 4/01/2022, 16:47, Alessandro Pasotti escreveu: > Hi, > > Just a quick followup on this: we briefly discussed this topic within the > PSC and the conclusion was that this is not a PSC matter. > > Kind regards. > > > > On Wed, Nov 10, 2021 at 12:16 AM Nyall Dawson > wrote: > >> On Wed, 10 Nov 2021 at 00:42, Alexandre Neto >> wrote: >> > >> > No comments?l >> > >> > I was expecting at least a bit of discussion about this. >> >> Honestly, I see it as a bit of a non-starter. Conda is still stuck to >> such an old Qt version that you can't build anything past QGIS 3.18. >> >> To me that's reflective of a larger issue with the ecosystem, not an >> isolated example. These mega-packaging-everything projects just seem >> to consistently get bogged down by the sheer number of dependent >> packages they try to satisfy, resulting in an overall worse experience >> all round. >> >> But that's just my 2c ;) >> >> Nyall >> >> >> > >> > :-) >> > >> > Alexandre Neto >> > >> > A sábado, 6/11/2021, 20:46, Even Rouault >> escreveu: >> >> >> >> Hi, >> >> >> >> Probably a topic that can raise passions and on which I'm moderately >> >> legitimate to speak, but shouldn't we seriously consider leveraging the >> >> Conda / Conda-Forge (https://conda-forge.org/) ecosystem for QGIS >> >> packaging, especially on the Windows and Mac platforms ? QGIS depends >> on >> >> a lot of external dependencies, and building them and updating them is >> >> really about maintaining a packaging system, and QGIS has two such >> >> separate and bespoke systems for Windows (OSGeo4W) and Mac >> >> (QGIS-Mac-Packager). The ideal vision would be that the QGIS project >> >> mostly maintains the bits specific to QGIS, but not be the sole >> >> maintainer of its dependencies such as QT, GDAL (and its many >> >> dependencies), PDAL, GRASS etc, as it is today. Conda-Forge provides a >> >> truly collaborative environment and active community that already >> >> bundles a number of those dependencies, and QGIS is already there (not >> >> full capabilities yet, due to some dependencies missing. That would be >> >> one of the points to address). The Conda-Forge community is really >> >> vibrant (if you look at >> >> >> https://github.com/conda-forge/staged-recipes/pulls?q=is%3Apr+is%3Aclosed >> , >> >> you can see that 20 packages were added in the last 24 hours!). It is >> >> also a NumFocus sponsored project. It has support from a number of >> >> institutions. It is unlikely to disappear anytime soon. >> >> >> >> There would certainly work needed to build installers from them. I >> found >> >> https://github.com/conda/constructor project where you can build >> >> standalone installers from Conda packages, but was told it is perhaps >> >> not super mature. Even if QGIS needs require a dedicated installer >> with >> >> custom bits, leveraging already packaged dependencies would probably be >> >> a big enough win compared to the current situation where the whole >> stack >> >> needs to be built and rebuilt from scratch by only a few knowledgeable >> >> people, on non-shared infrastructure. >> >> >> >> There would be the possibility to pin dependencies at certain known >> good >> >> points, for example to base LTR builds on top of them. >> >> >> >> I guess also that Conda based installers could help for plugins that >> >> require installing native or Python dependencies, but that'd be already >> >> more a secondary advantage. >> >> >> >> Another proof that Conda is to be taken seriously: >> >> https://developers.arcgis.com/python/guide/understanding-conda/ >> >> >> >> I'm not saying this is a magical solution: there would clearly be a >> >> significant amount of work and technical hurdles to solve to reach the >> >> same degree of maturity as our current installers, but it is probably >> an >> >> investment worth considering for the long term. >> >> >> >> Even >> >> >> >> -- >> >> http://www.spatialys.com >> >> My software is free, but my time generally not. >> >> >> >> ___ >> >> 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 >> ___ >> QGIS-Developer mailing list >> QGIS-Developer@lists.osgeo.org >> List info:
[QGIS-Developer] pyqtSlot decoration problems with layerChanged in Python 3.10
Hi everyone! I've developed some Qgis plugins, everything was fine until I updated Python to 3.10 version, some of these plugins have problems with the /pyqtSlot/ with the function /layerChanged/, an example code: self.myLayerComboBox.layerChanged.connect(self.myConnectMethod) @pyqtSlot(QgsMapLayer) def myConnectMethod(self, layer) ... The error is: TypeError: decorated slot has no signature compatible with layerChanged(QgsMapLayer*) My question is: if that is a Qgis bug? or that pyqtSlot no longer necessary? or has the syntax changed for that decorator? That error don't happen with Python < 3.10. Using Qgis 3.22.2 on Archlinux. Thanks! Xavier ___ 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] Leveraging Conda-Forge to create QGIS installers ?
Hi, Just a quick followup on this: we briefly discussed this topic within the PSC and the conclusion was that this is not a PSC matter. Kind regards. On Wed, Nov 10, 2021 at 12:16 AM Nyall Dawson wrote: > On Wed, 10 Nov 2021 at 00:42, Alexandre Neto > wrote: > > > > No comments?l > > > > I was expecting at least a bit of discussion about this. > > Honestly, I see it as a bit of a non-starter. Conda is still stuck to > such an old Qt version that you can't build anything past QGIS 3.18. > > To me that's reflective of a larger issue with the ecosystem, not an > isolated example. These mega-packaging-everything projects just seem > to consistently get bogged down by the sheer number of dependent > packages they try to satisfy, resulting in an overall worse experience > all round. > > But that's just my 2c ;) > > Nyall > > > > > > :-) > > > > Alexandre Neto > > > > A sábado, 6/11/2021, 20:46, Even Rouault > escreveu: > >> > >> Hi, > >> > >> Probably a topic that can raise passions and on which I'm moderately > >> legitimate to speak, but shouldn't we seriously consider leveraging the > >> Conda / Conda-Forge (https://conda-forge.org/) ecosystem for QGIS > >> packaging, especially on the Windows and Mac platforms ? QGIS depends on > >> a lot of external dependencies, and building them and updating them is > >> really about maintaining a packaging system, and QGIS has two such > >> separate and bespoke systems for Windows (OSGeo4W) and Mac > >> (QGIS-Mac-Packager). The ideal vision would be that the QGIS project > >> mostly maintains the bits specific to QGIS, but not be the sole > >> maintainer of its dependencies such as QT, GDAL (and its many > >> dependencies), PDAL, GRASS etc, as it is today. Conda-Forge provides a > >> truly collaborative environment and active community that already > >> bundles a number of those dependencies, and QGIS is already there (not > >> full capabilities yet, due to some dependencies missing. That would be > >> one of the points to address). The Conda-Forge community is really > >> vibrant (if you look at > >> > https://github.com/conda-forge/staged-recipes/pulls?q=is%3Apr+is%3Aclosed, > >> you can see that 20 packages were added in the last 24 hours!). It is > >> also a NumFocus sponsored project. It has support from a number of > >> institutions. It is unlikely to disappear anytime soon. > >> > >> There would certainly work needed to build installers from them. I found > >> https://github.com/conda/constructor project where you can build > >> standalone installers from Conda packages, but was told it is perhaps > >> not super mature. Even if QGIS needs require a dedicated installer with > >> custom bits, leveraging already packaged dependencies would probably be > >> a big enough win compared to the current situation where the whole stack > >> needs to be built and rebuilt from scratch by only a few knowledgeable > >> people, on non-shared infrastructure. > >> > >> There would be the possibility to pin dependencies at certain known good > >> points, for example to base LTR builds on top of them. > >> > >> I guess also that Conda based installers could help for plugins that > >> require installing native or Python dependencies, but that'd be already > >> more a secondary advantage. > >> > >> Another proof that Conda is to be taken seriously: > >> https://developers.arcgis.com/python/guide/understanding-conda/ > >> > >> I'm not saying this is a magical solution: there would clearly be a > >> significant amount of work and technical hurdles to solve to reach the > >> same degree of maturity as our current installers, but it is probably an > >> investment worth considering for the long term. > >> > >> Even > >> > >> -- > >> http://www.spatialys.com > >> My software is free, but my time generally not. > >> > >> ___ > >> 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 > ___ > 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 QCooperative: www.qcooperative.net ItOpen: 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] Funding and PR review
Hi Alex, Happy new year to you as well! We increased the funding for PR reviews from 10 to 14k. However, it is up to the reviewers (currently Nyall, Matthias and Alessandro, in the future probably also Martin) to decide what PRs they are looking at. I understand that the above figure doesn't guarantee that they can look at all PRs. My recommendation for new devs is to personally ask one of the above people - or another QGIS dev with core commiter rights. In general, for paid new developments, the developer who offers the new functionality should factor in the cost of code reviewing in the quote. For voluntary contributions it may be more difficult. There it probably depends a lot on the quality of the PR and the willingness of the dev to respond to the reviewers in a timely manner. And of course - if the PR is interesting to one of the reviewers, it increases the chance a lot. I am not sure if a separate crowd funding for PR reviewing would be the way to go. I would imagine it would be difficult to raise funds specifically for this goal. I would rather prefer to try to get more "sustaining members" in general, so we can increase this budget item in upcoming years. Let's see what other core devs and PSC members think abou this? Andreas On Sun, 2 Jan 2022 at 14:24, Alexis R.L. wrote: > Greetings Everyone, > > Some points have been going through my head and I was curious to know if > there could be good ideas in them for discussion and opportunities. > > One aspect that can irk new and existing contributors (or maybe just > myself) is when it comes to PR reviews. As some work on either side is done > on a voluntary basis we can't expect competent and overworked devs to want > and to dedicate more time on some work that won't benefit them. > > On the other hand we also get pr that get stuck or staled out. > > Now I was thinking of creating a crowdfund to raise some funds for reviews > ( I don't want to profit monetarily from any of my work). But I don't want > to be stuck managing funds and doing PR and etc. > > Now I know that QGIS has some devoted funds for bugfixing and PR reviews > to this effect. But I was curious to know if it would be a good idea to > advertise the work (possibly in the news feed?) that would benefit from > bugfixing or PR reviews. > > I'm not sure if dividing things and separating funds on a issue or > category (bugfix vs feature vs ?) would be beneficial. But showcasing what > they can gain from doing a contribution would probably be helpful rather > than giving for general support. > > Just my two cents, I also wish everyone a good new year of developping! > > Alex > ___ > 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 > -- -- Andreas Neumann QGIS.ORG board member (treasurer) ___ 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
