From senhor.neto at gmail.com Wed Nov 4 10:50:18 2026 From: senhor.neto at gmail.com (Alexandre Neto) Date: Wed, 4 Nov 2026 18:50:18 +0000 Subject: [Qgis-psc] =?utf-8?q?Fwd=3A_=5BQgis-user=5D_Pagamentos_n=C3=A3o_?= =?utf-8?q?aceites?= In-Reply-To: References: Message-ID: This user seems to be having issues with his donation using paypal. Does any of you know what could be wrong? Thanks, Alex Neto ---------- Forwarded message --------- De: Jo?o Paulo via QGIS-User Date: s?bado, 31/10/2026, 13:52 Subject: [Qgis-user] Pagamentos n?o aceites To: N?o sei a quem me dirigir, por isso tento este endere?o, se me puderem ajudar fico agradecido. H? cerca de 2 ou 3 meses que venho recebendo avisos de "pay pall" de que n?o consegue proceder ao pagamento do contributo que assumi com o "q gis", pelo que gostava de saber o que se passa e como posso resolver o problema. Agradecido Jo?o Paulo Nogueira Ferr?o [image: Screenshot 2026-10-31 133241.png] _______________________________________________ QGIS-User mailing list QGIS-User at lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot 2026-10-31 133241.png Type: image/png Size: 55851 bytes Desc: not available URL: From marco at qgis.org Thu Nov 5 03:13:35 2026 From: marco at qgis.org (Marco Bernasocchi) Date: Thu, 5 Nov 2026 12:13:35 +0100 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> Message-ID: Hey Matthias, Sorry, it took a bit longer on my side. we discussed this in the PSC and agree that we should go forward. As soon as we finalise the test phase and the system proves it works, we can write the blog post for them. Thanks a lot for taking care of this. Cheers Marco On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC < qgis-psc at lists.osgeo.org> wrote: > Hi Matthias, thanks for pushing and testing this idea. > > In fact, listening at J?rgen yesterday in the conference, I realised that > github runners are also a limiting factor for a OSGEO4W port to CI builds. > > As Blacksmith offers an open source partnership, I strongly support your > proposal too as away to unlock our current github limitations fast and > efficiently. > > As for long term plans to own a sovereign infrastructure, Blacksmith is a > US based company, so it doesn't change this situation, but it would allow > us to size more what kind of infrastructure we require. > > Best regards > R?gis > > > > On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC < > qgis-psc at lists.osgeo.org> wrote: > > Hello Matthias, > > > > This looks a very good idea to me. > > > > Thank you for exploring this opportunity! > > > > > > --- > > Alessandro Pasotti > > QCooperative: www.qcooperative.net > > ItOpen: www.itopen.it > > > > Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC > psc at lists.osgeo.org > ha scritto: > > > > Hi Martin, > > > > Yes, running tests sounds reasonable too. > > So far the build itself was taking too long and I didn't want to > > increase this even more. > > > > Matthias > > > > On Thu, Oct 8, 2026, 22:45 Martin Dobias > > wrote: > > > > Hi Matthias > > > > That all sounds good to me. And maybe we could also start to run > > auto tests for mac plarform in CI? It seems quite a few are > > broken on macOS, but we don't really know about that :-) > > > > Cheers > > Martin > > > > > > On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via QGIS-PSC > psc at lists.osgeo.org > wrote: > > > > Dear PSC, > > > > We are currently producing macOS builds entirely within our > > CI/CD pipelines (github workflows/actions). With this > > approach, we can create dmg installer packages for currently > > supported QGIS 3 and QGIS 4 versions for releases, pull > > requests, and branch (latest) builds. > > > > For QGIS 4, one important component is currently missing: we > > cannot build QtWebEngine (HTML rendering) because building > > it takes over six hours (the maximum threshold for > > workflows) on the (free-tier) github runners. This > > limitation is significant, and several tickets request its > > addition (for QGIS itself and for plugins like dataplotly). > > We only need to rebuild this component when there's an > > update, so it won't add time to every pipeline build. > > However, we must ensure it builds once every few days. > > > > I recently was in touch with blacksmith > www.blacksmith.sh/> which is an independent provider of > > runners for github actions. They have very performant > > runners, I was able to build QtWebEngine in less than 1.5 > > hours (compared to more than 6 hours on github). They would > > allow us to use their infrastructure as part of their open- > > source engagement and ask for a blog post in return. > > > > Blacksmith would also help us reduce CI time for other > > workflows either by moving some workflows over to blacksmith > > or by reducing the load on github actions cache. This would > > significantly improve the developer experience. > > > > One remaining challenge will be providing mac packages for > > Intel devices. Blacksmith does not offer this platform. > > Apple stopped selling Intel macOS devices in mid-2023. Apple > > will officially support Intel devices until 2028, after > > which support will be reduced, ending entirely in 2030. > > Offering QGIS 4 support for Intel devices would be nice, but > > we would need to find another interim solution for the next > > 2-4 years. > > > > I'd like to propose that we create an account with > > blacksmith, install its github app and move the macOS arm64 > > workflow and potentially a few others over to blacksmith. If > > this goes well and improves the situation, I'd like to write > > a blog post about our experiences as part of this agreement. > > This will improve the situation for macOS packages for arm64 > > (i.e. for all mac devices sold in the last 3 years and more > > sold since 2020). For Intel, we would continue to build > > packages but without QtWebEngine until we find a suitable > > solution. > > > > Thanks a lot and best regards > > Matthias > > > > -- > > > > > > *Matthias Kuhn* - Mr. Noproblemo > > > > CTO | Co-Founder > > > > email > > matthias at opengis.ch > > www > > opengis.ch > > > > linkedin > > mastodon github > > github.com/opengisch/> > > > > _______________________________________________ > > QGIS-PSC mailing list > > QGIS-PSC at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/qgis-psc > lists.osgeo.org/mailman/listinfo/qgis-psc> > > > > _______________________________________________ > > QGIS-PSC mailing list > > QGIS-PSC at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/qgis-psc > lists.osgeo.org/mailman/listinfo/qgis-psc> > > > > > > _______________________________________________ > > QGIS-PSC mailing list > > QGIS-PSC at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/qgis-psc > > > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc > -- Marco Bernasocchi QGIS.org Chair OSGEO.org VP Europe OPENGIS.ch CEO http://berna.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From yuki.pck at gmail.com Thu Nov 5 03:42:35 2026 From: yuki.pck at gmail.com (=?UTF-8?B?56+g55Sw5L6R5biM?=) Date: Thu, 5 Nov 2026 20:42:35 +0900 Subject: [Qgis-psc] Question about accessing GIS files stored in Box directly from QGIS Message-ID: Hello, I am currently testing different ways of accessing GIS data in QGIS. We are comparing the following storage locations: ?Local folders ?Cloud drives mounted or accessible from Windows Explorer ?Web-based cloud storage such as Box We would like to know whether GIS files stored in Box, such as Shapefiles, GeoPackages, and GeoTIFF files, can be accessed directly from QGIS using a Box URL, without downloading them to a local folder. We have the following questions: 1.Can QGIS directly access GIS files stored in Box using a shared URL or download URL? 2.If not, is there another supported method for accessing files stored in Box from QGIS? 3.Would using a desktop synchronization tool such as Box Drive be the recommended approach? 4.Are there any limitations or considerations regarding performance, editing, or saving data when using cloud storage with QGIS? Our goal is to determine whether a web-based cloud storage service such as Box can be used as a practical data storage location for QGIS. Thank you very much for your help. Best regards, Yuki -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim at qgis.org Thu Nov 5 08:06:58 2026 From: tim at qgis.org (Tim Sutton) Date: Thu, 5 Nov 2026 16:06:58 +0000 Subject: [Qgis-psc] Question about accessing GIS files stored in Box directly from QGIS In-Reply-To: References: Message-ID: Dear Yuki This list is not for general user enquiries, please use the user mailing list: https://qgis.org/community/organisation/mailinglists/#qgis-users-list Thank you Regards Tim On Thu, Nov 5, 2026 at 11:42?AM ???? via QGIS-PSC wrote: > Hello, > > I am currently testing different ways of accessing GIS data in QGIS. > We are comparing the following storage locations: > ?Local folders > ?Cloud drives mounted or accessible from Windows Explorer > ?Web-based cloud storage such as Box > > We would like to know whether GIS files stored in Box, such as Shapefiles, > GeoPackages, and GeoTIFF files, can be accessed directly from QGIS using a > Box URL, without downloading them to a local folder. > We have the following questions: > 1.Can QGIS directly access GIS files stored in Box using a shared URL or > download URL? > 2.If not, is there another supported method for accessing files stored in > Box from QGIS? > 3.Would using a desktop synchronization tool such as Box Drive be the > recommended approach? > 4.Are there any limitations or considerations regarding performance, > editing, or saving data when using cloud storage with QGIS? > Our goal is to determine whether a web-based cloud storage service such as > Box can be used as a practical data storage location for QGIS. > Thank you very much for your help. > > Best regards, > Yuki > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc > -- *Tim Sutton* QGIS Project Steering Committee tim at qgis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From regis at qgis.org Thu Nov 5 08:16:52 2026 From: regis at qgis.org (=?UTF-8?Q?R=C3=A9gis_Haubourg?=) Date: Thu, 5 Nov 2026 17:16:52 +0100 Subject: [Qgis-psc] Question about accessing GIS files stored in Box directly from QGIS In-Reply-To: References: Message-ID: Hi Yuki, ?Please use the QGIS-user mailing to get help from the community. PSC focuses on leading the project but can't provide technical help directly, we are a few benevolent persons and can't answer so much mails. Thanks a lot R?gis Elected member at the Program Steering Comitee of QGIS.org. - On 05/11/2026 12:42, ???? via QGIS-PSC wrote: > Hello, > > I am currently testing different ways of accessing GIS data in QGIS. > We are comparing the following storage locations: > ?Local folders > ?Cloud drives mounted or accessible from Windows Explorer > ?Web-based cloud storage such as Box > > We would like to know whether GIS files stored in Box, such as > Shapefiles, GeoPackages, and GeoTIFF files, can be accessed directly > from QGIS using a Box URL, without downloading them to a local folder. > We have the following questions: > 1.Can QGIS directly access GIS files stored in Box using a shared URL > or download URL? > 2.If not, is there another supported method for accessing files stored > in Box from QGIS? > 3.Would using a desktop synchronization tool such as Box Drive be the > recommended approach? > 4.Are there any limitations or considerations regarding performance, > editing, or saving data when using cloud storage with QGIS? > Our goal is to determine whether a web-based cloud storage service > such as Box can be used as a practical data storage location for QGIS. > Thank you very much for your help. > > Best regards, > Yuki > > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc -------------- next part -------------- An HTML attachment was scrubbed... URL: From nirvn.asia at gmail.com Fri Nov 6 00:22:51 2026 From: nirvn.asia at gmail.com (Mathieu Pellerin) Date: Fri, 6 Nov 2026 15:22:51 +0700 Subject: [Qgis-psc] QGIS 4.4 release github project cleanup Message-ID: Greetings, First, big thanks for the blog post providing an update about the forthcoming QGIS 4.4 release, I?m sure it?ll be useful guidance to the broader community. Motivated by that blog post, Marco, myself and Dave spent some time cleaning up the QGIS 4.4 release project ( https://github.com/orgs/qgis/projects/18/views/1). There were a fair amount of issues that fell off the mark (e.g. opened in 2018 in our redmine (RIP) portal with no significant activity in years). We've applied the following rules to filter issues (I believe aligns with the blog post definition and prior understanding by devs): - worked in 3 AND broken in 4 -> remained in the project - worked in 3 AND broken in 4 AND critical -> remained in the project & assigned to the ?critical blocker? column - worked in <3.44 AND broken in >=3.44 -> removed from the project - missing in 3 AND broken in 4 -> removed from the project A few issues (9) have been placed in a TBC column as it was not immediately clear whether they were still valid as of November 2026. We hope this project cleanup effort results in a more accurate reflection of what's left to tackle and help focus our collective efforts. Now onto something to consider :) At the moment, what is considered blocking 4.4 is contained in the confirmed + critical blocker lists; it might be useful to narrow down the list of critical 3.X -> 4.X regressions that are considered blocking. Best, Mathieu -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthias at opengis.ch Fri Nov 6 00:38:00 2026 From: matthias at opengis.ch (Matthias Kuhn) Date: Fri, 6 Nov 2026 09:38:00 +0100 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> Message-ID: Dear PSC, Thanks a lot for the positive feedback. I'd like to start this as soon as possible, migrate a few workflows, and then write a blog post in a couple of weeks when we have results to present. They asked if also (cited): 1. we have a sponsor logo (attached) - would you be ok with placing it in your project README and image on your website? 2. would you be alright with us talking about our partnership on socials/blogs? I quickly checked how the others integrate the logo in the readme (e.g. celery): https://github.com/celery/celery#sponsors Sorry for the additional request; I forgot to include this in the original email. I hope that this can be confirmed quickly. Thanks a lot Matthias On Thu, Nov 5, 2026 at 12:14?PM Marco Bernasocchi wrote: > > Hey Matthias, > Sorry, it took a bit longer on my side. > we discussed this in the PSC and agree that we should go forward. > As soon as we finalise the test phase and the system proves it works, we can write the blog post for them. > Thanks a lot for taking care of this. > > Cheers > Marco > > On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC wrote: >> >> Hi Matthias, thanks for pushing and testing this idea. >> >> In fact, listening at J?rgen yesterday in the conference, I realised that github runners are also a limiting factor for a OSGEO4W port to CI builds. >> >> As Blacksmith offers an open source partnership, I strongly support your proposal too as away to unlock our current github limitations fast and efficiently. >> >> As for long term plans to own a sovereign infrastructure, Blacksmith is a US based company, so it doesn't change this situation, but it would allow us to size more what kind of infrastructure we require. >> >> Best regards >> R?gis >> >> >> >> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC wrote: >> > Hello Matthias, >> > >> > This looks a very good idea to me. >> > >> > Thank you for exploring this opportunity! >> > >> > >> > --- >> > Alessandro Pasotti >> > QCooperative: www.qcooperative.net >> > ItOpen: www.itopen.it >> > >> > Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC > > psc at lists.osgeo.org > ha scritto: >> > >> > Hi Martin, >> > >> > Yes, running tests sounds reasonable too. >> > So far the build itself was taking too long and I didn't want to >> > increase this even more. >> > >> > Matthias >> > >> > On Thu, Oct 8, 2026, 22:45 Martin Dobias > > > wrote: >> > >> > Hi Matthias >> > >> > That all sounds good to me. And maybe we could also start to run >> > auto tests for mac plarform in CI? It seems quite a few are >> > broken on macOS, but we don't really know about that :-) >> > >> > Cheers >> > Martin >> > >> > >> > On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via QGIS-PSC > > psc at lists.osgeo.org > wrote: >> > >> > Dear PSC, >> > >> > We are currently producing macOS builds entirely within our >> > CI/CD pipelines (github workflows/actions). With this >> > approach, we can create dmg installer packages for currently >> > supported QGIS 3 and QGIS 4 versions for releases, pull >> > requests, and branch (latest) builds. >> > >> > For QGIS 4, one important component is currently missing: we >> > cannot build QtWebEngine (HTML rendering) because building >> > it takes over six hours (the maximum threshold for >> > workflows) on the (free-tier) github runners. This >> > limitation is significant, and several tickets request its >> > addition (for QGIS itself and for plugins like dataplotly). >> > We only need to rebuild this component when there's an >> > update, so it won't add time to every pipeline build. >> > However, we must ensure it builds once every few days. >> > >> > I recently was in touch with blacksmith > > www.blacksmith.sh/> which is an independent provider of >> > runners for github actions. They have very performant >> > runners, I was able to build QtWebEngine in less than 1.5 >> > hours (compared to more than 6 hours on github). They would >> > allow us to use their infrastructure as part of their open- >> > source engagement and ask for a blog post in return. >> > >> > Blacksmith would also help us reduce CI time for other >> > workflows either by moving some workflows over to blacksmith >> > or by reducing the load on github actions cache. This would >> > significantly improve the developer experience. >> > >> > One remaining challenge will be providing mac packages for >> > Intel devices. Blacksmith does not offer this platform. >> > Apple stopped selling Intel macOS devices in mid-2023. Apple >> > will officially support Intel devices until 2028, after >> > which support will be reduced, ending entirely in 2030. >> > Offering QGIS 4 support for Intel devices would be nice, but >> > we would need to find another interim solution for the next >> > 2-4 years. >> > >> > I'd like to propose that we create an account with >> > blacksmith, install its github app and move the macOS arm64 >> > workflow and potentially a few others over to blacksmith. If >> > this goes well and improves the situation, I'd like to write >> > a blog post about our experiences as part of this agreement. >> > This will improve the situation for macOS packages for arm64 >> > (i.e. for all mac devices sold in the last 3 years and more >> > sold since 2020). For Intel, we would continue to build >> > packages but without QtWebEngine until we find a suitable >> > solution. >> > >> > Thanks a lot and best regards >> > Matthias >> > >> > -- >> > >> > >> > *Matthias Kuhn* - Mr. Noproblemo >> > >> > CTO | Co-Founder >> > >> > email >> > matthias at opengis.ch >> > www >> > opengis.ch >> > >> > linkedin >> > mastodon github > > github.com/opengisch/> >> > >> > _______________________________________________ >> > QGIS-PSC mailing list >> > QGIS-PSC at lists.osgeo.org >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc > > lists.osgeo.org/mailman/listinfo/qgis-psc> >> > >> > _______________________________________________ >> > QGIS-PSC mailing list >> > QGIS-PSC at lists.osgeo.org >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc > > lists.osgeo.org/mailman/listinfo/qgis-psc> >> > >> > >> > _______________________________________________ >> > QGIS-PSC mailing list >> > QGIS-PSC at lists.osgeo.org >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc >> > >> _______________________________________________ >> QGIS-PSC mailing list >> QGIS-PSC at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/qgis-psc > > > > -- > Marco Bernasocchi > > QGIS.org Chair > OSGEO.org VP Europe > OPENGIS.ch CEO > http://berna.io -------------- next part -------------- A non-text attachment was scrubbed... Name: unnamed.png Type: image/png Size: 4088 bytes Desc: not available URL: From marco at qgis.org Fri Nov 6 05:41:42 2026 From: marco at qgis.org (Marco Bernasocchi) Date: Fri, 6 Nov 2026 14:41:42 +0100 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> Message-ID: Hey Matthias, Number 2 was already discussed and we see no problem with that. We hadn't discussed 1 but i see no issue there either. Any other opinions from the psc? Cheers Marco Bernasocchi QGIS.org Chair OSGEO.org VP Europe OPENGIS.ch CEO http://berna.io On Fri, 6 Nov 2026, 09:38 Matthias Kuhn, wrote: > Dear PSC, > > Thanks a lot for the positive feedback. I'd like to start this as soon > as possible, migrate a few workflows, and then write a blog post in a > couple of weeks when we have results to present. > > They asked if also (cited): > > 1. we have a sponsor logo (attached) - would you be ok with placing it > in your project README and image on your website? > 2. would you be alright with us talking about our partnership on > socials/blogs? > > I quickly checked how the others integrate the logo in the readme > (e.g. celery): https://github.com/celery/celery#sponsors > > Sorry for the additional request; I forgot to include this in the > original email. > I hope that this can be confirmed quickly. > > Thanks a lot > Matthias > > > > On Thu, Nov 5, 2026 at 12:14?PM Marco Bernasocchi wrote: > > > > Hey Matthias, > > Sorry, it took a bit longer on my side. > > we discussed this in the PSC and agree that we should go forward. > > As soon as we finalise the test phase and the system proves it works, we > can write the blog post for them. > > Thanks a lot for taking care of this. > > > > Cheers > > Marco > > > > On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC < > qgis-psc at lists.osgeo.org> wrote: > >> > >> Hi Matthias, thanks for pushing and testing this idea. > >> > >> In fact, listening at J?rgen yesterday in the conference, I realised > that github runners are also a limiting factor for a OSGEO4W port to CI > builds. > >> > >> As Blacksmith offers an open source partnership, I strongly support > your proposal too as away to unlock our current github limitations fast and > efficiently. > >> > >> As for long term plans to own a sovereign infrastructure, Blacksmith is > a US based company, so it doesn't change this situation, but it would allow > us to size more what kind of infrastructure we require. > >> > >> Best regards > >> R?gis > >> > >> > >> > >> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC < > qgis-psc at lists.osgeo.org> wrote: > >> > Hello Matthias, > >> > > >> > This looks a very good idea to me. > >> > > >> > Thank you for exploring this opportunity! > >> > > >> > > >> > --- > >> > Alessandro Pasotti > >> > QCooperative: www.qcooperative.net > >> > ItOpen: www.itopen.it > >> > > >> > Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC >> > psc at lists.osgeo.org > ha scritto: > >> > > >> > Hi Martin, > >> > > >> > Yes, running tests sounds reasonable too. > >> > So far the build itself was taking too long and I didn't want to > >> > increase this even more. > >> > > >> > Matthias > >> > > >> > On Thu, Oct 8, 2026, 22:45 Martin Dobias >> > > wrote: > >> > > >> > Hi Matthias > >> > > >> > That all sounds good to me. And maybe we could also start to > run > >> > auto tests for mac plarform in CI? It seems quite a few are > >> > broken on macOS, but we don't really know about that :-) > >> > > >> > Cheers > >> > Martin > >> > > >> > > >> > On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via QGIS-PSC > >> > psc at lists.osgeo.org > wrote: > >> > > >> > Dear PSC, > >> > > >> > We are currently producing macOS builds entirely within > our > >> > CI/CD pipelines (github workflows/actions). With this > >> > approach, we can create dmg installer packages for > currently > >> > supported QGIS 3 and QGIS 4 versions for releases, pull > >> > requests, and branch (latest) builds. > >> > > >> > For QGIS 4, one important component is currently missing: > we > >> > cannot build QtWebEngine (HTML rendering) because building > >> > it takes over six hours (the maximum threshold for > >> > workflows) on the (free-tier) github runners. This > >> > limitation is significant, and several tickets request its > >> > addition (for QGIS itself and for plugins like > dataplotly). > >> > We only need to rebuild this component when there's an > >> > update, so it won't add time to every pipeline build. > >> > However, we must ensure it builds once every few days. > >> > > >> > I recently was in touch with blacksmith >> > www.blacksmith.sh/> which is an independent provider of > >> > runners for github actions. They have very performant > >> > runners, I was able to build QtWebEngine in less than 1.5 > >> > hours (compared to more than 6 hours on github). They > would > >> > allow us to use their infrastructure as part of their > open- > >> > source engagement and ask for a blog post in return. > >> > > >> > Blacksmith would also help us reduce CI time for other > >> > workflows either by moving some workflows over to > blacksmith > >> > or by reducing the load on github actions cache. This > would > >> > significantly improve the developer experience. > >> > > >> > One remaining challenge will be providing mac packages for > >> > Intel devices. Blacksmith does not offer this platform. > >> > Apple stopped selling Intel macOS devices in mid-2023. > Apple > >> > will officially support Intel devices until 2028, after > >> > which support will be reduced, ending entirely in 2030. > >> > Offering QGIS 4 support for Intel devices would be nice, > but > >> > we would need to find another interim solution for the > next > >> > 2-4 years. > >> > > >> > I'd like to propose that we create an account with > >> > blacksmith, install its github app and move the macOS > arm64 > >> > workflow and potentially a few others over to blacksmith. > If > >> > this goes well and improves the situation, I'd like to > write > >> > a blog post about our experiences as part of this > agreement. > >> > This will improve the situation for macOS packages for > arm64 > >> > (i.e. for all mac devices sold in the last 3 years and > more > >> > sold since 2020). For Intel, we would continue to build > >> > packages but without QtWebEngine until we find a suitable > >> > solution. > >> > > >> > Thanks a lot and best regards > >> > Matthias > >> > > >> > -- > >> > > >> > > >> > *Matthias Kuhn* - Mr. Noproblemo > >> > > >> > CTO | Co-Founder > >> > > >> > email > >> > matthias at opengis.ch > >> > www > >> > opengis.ch > >> > > >> > linkedin > >> > mastodon github > >> > github.com/opengisch/> > >> > > >> > _______________________________________________ > >> > QGIS-PSC mailing list > >> > QGIS-PSC at lists.osgeo.org > > >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc > >> > lists.osgeo.org/mailman/listinfo/qgis-psc> > >> > > >> > _______________________________________________ > >> > QGIS-PSC mailing list > >> > QGIS-PSC at lists.osgeo.org > >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc >> > lists.osgeo.org/mailman/listinfo/qgis-psc> > >> > > >> > > >> > _______________________________________________ > >> > QGIS-PSC mailing list > >> > QGIS-PSC at lists.osgeo.org > >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc > >> > > >> _______________________________________________ > >> QGIS-PSC mailing list > >> QGIS-PSC at lists.osgeo.org > >> https://lists.osgeo.org/mailman/listinfo/qgis-psc > > > > > > > > -- > > Marco Bernasocchi > > > > QGIS.org Chair > > OSGEO.org VP Europe > > OPENGIS.ch CEO > > http://berna.io > -------------- next part -------------- An HTML attachment was scrubbed... URL: From elpaso at itopen.it Fri Nov 6 07:29:09 2026 From: elpaso at itopen.it (ElPaso) Date: Fri, 6 Nov 2026 16:29:09 +0100 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> Message-ID: Il 06/11/26 14:41, Marco Bernasocchi via QGIS-PSC ha scritto: > Hey Matthias, > Number 2 was already discussed and we see no problem with that. > > We hadn't discussed 1 but i see no issue there either. > > Any other opinions from the psc? +1 > Cheers > > Marco Bernasocchi > > QGIS.org Chair > OSGEO.org VP Europe > OPENGIS.ch CEO > http://berna.io > > On Fri, 6 Nov 2026, 09:38 Matthias Kuhn, wrote: > > Dear PSC, > > Thanks a lot for the positive feedback. I'd like to start this as soon > as possible, migrate a few workflows, and then write a blog post in a > couple of weeks when we have results to present. > > They asked if also (cited): > > 1. we have a sponsor logo (attached) - would you be ok with placing it > in your project README and image on your website? > 2. would you be alright with us talking about our partnership on > socials/blogs? > > I quickly checked how the others integrate the logo in the readme > (e.g. celery): https://github.com/celery/celery#sponsors > > Sorry for the additional request; I forgot to include this in the > original email. > I hope that this can be confirmed quickly. > > Thanks a lot > Matthias > > > > On Thu, Nov 5, 2026 at 12:14?PM Marco Bernasocchi > wrote: > > > > Hey Matthias, > > Sorry, it took a bit longer on my side. > > we discussed this in the PSC and agree that we should go forward. > > As soon as we finalise the test phase and the system proves it > works, we can write the blog post for them. > > Thanks a lot for taking care of this. > > > > Cheers > > Marco > > > > On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC > wrote: > >> > >> Hi Matthias, thanks for pushing and testing this idea. > >> > >> In fact, listening at J?rgen yesterday in the conference, I > realised that github runners are also a limiting factor for a > OSGEO4W port to CI builds. > >> > >> As Blacksmith offers an open source partnership, I strongly > support your proposal too as away to unlock our current github > limitations fast and efficiently. > >> > >> As for long term plans to own a sovereign infrastructure, > Blacksmith is a US based company, so it doesn't change this > situation, but it would allow us to size more what kind of > infrastructure we require. > >> > >> Best regards > >> R?gis > >> > >> > >> > >> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC > wrote: > >> >? ?Hello Matthias, > >> > > >> > This looks a very good idea to me. > >> > > >> > Thank you for exploring this opportunity! > >> > > >> > > >> > --- > >> > Alessandro Pasotti > >> > QCooperative: www.qcooperative.net > > >> > ItOpen: www.itopen.it > > >> > > >> > Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC >> > psc at lists.osgeo.org > ha > scritto: > >> > > >> >? ? ?Hi Martin, > >> > > >> >? ? ?Yes, running tests sounds reasonable too. > >> >? ? ?So far the build itself was taking too long and I didn't > want to > >> >? ? ?increase this even more. > >> > > >> >? ? ?Matthias > >> > > >> >? ? ?On Thu, Oct 8, 2026, 22:45 Martin Dobias >> >? ? ?> wrote: > >> > > >> >? ? ? ? ?Hi Matthias > >> > > >> >? ? ? ? ?That all sounds good to me. And maybe we could also > start to run > >> >? ? ? ? ?auto tests for mac plarform in CI? It seems quite a > few are > >> >? ? ? ? ?broken on macOS, but we don't really know about that :-) > >> > > >> >? ? ? ? ?Cheers > >> >? ? ? ? ?Martin > >> > > >> > > >> >? ? ? ? ?On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via > QGIS-PSC >> > psc at lists.osgeo.org > wrote: > >> > > >> >? ? ? ? ? ? ?Dear PSC, > >> > > >> >? ? ? ? ? ? ?We are currently producing macOS builds entirely > within our > >> >? ? ? ? ? ? ?CI/CD pipelines (github workflows/actions). With this > >> >? ? ? ? ? ? ?approach, we can create dmg installer packages > for currently > >> >? ? ? ? ? ? ?supported QGIS 3 and QGIS 4 versions for > releases, pull > >> >? ? ? ? ? ? ?requests, and branch (latest) builds. > >> > > >> >? ? ? ? ? ? ?For QGIS 4, one important component is currently > missing: we > >> >? ? ? ? ? ? ?cannot build QtWebEngine (HTML rendering) because > building > >> >? ? ? ? ? ? ?it takes over six hours (the maximum threshold for > >> >? ? ? ? ? ? ?workflows) on the (free-tier) github runners. This > >> >? ? ? ? ? ? ?limitation is significant, and several tickets > request its > >> >? ? ? ? ? ? ?addition (for QGIS itself and for plugins like > dataplotly). > >> >? ? ? ? ? ? ?We only need to rebuild this component when > there's an > >> >? ? ? ? ? ? ?update, so it won't add time to every pipeline build. > >> >? ? ? ? ? ? ?However, we must ensure it builds once every few > days. > >> > > >> >? ? ? ? ? ? ?I recently was in touch with blacksmith >> > www.blacksmith.sh/ > which is an > independent provider of > >> >? ? ? ? ? ? ?runners for github actions. They have very performant > >> >? ? ? ? ? ? ?runners, I was able to build QtWebEngine in less > than 1.5 > >> >? ? ? ? ? ? ?hours (compared to more than 6 hours on github). > They would > >> >? ? ? ? ? ? ?allow us to use their infrastructure as part of > their open- > >> >? ? ? ? ? ? ?source engagement and ask for a blog post in return. > >> > > >> >? ? ? ? ? ? ?Blacksmith would also help us reduce CI time for > other > >> >? ? ? ? ? ? ?workflows either by moving some workflows over to > blacksmith > >> >? ? ? ? ? ? ?or by reducing the load on github actions cache. > This would > >> >? ? ? ? ? ? ?significantly improve the developer experience. > >> > > >> >? ? ? ? ? ? ?One remaining challenge will be providing mac > packages for > >> >? ? ? ? ? ? ?Intel devices. Blacksmith does not offer this > platform. > >> >? ? ? ? ? ? ?Apple stopped selling Intel macOS devices in > mid-2023. Apple > >> >? ? ? ? ? ? ?will officially support Intel devices until 2028, > after > >> >? ? ? ? ? ? ?which support will be reduced, ending entirely in > 2030. > >> >? ? ? ? ? ? ?Offering QGIS 4 support for Intel devices would > be nice, but > >> >? ? ? ? ? ? ?we would need to find another interim solution > for the next > >> >? ? ? ? ? ? ?2-4 years. > >> > > >> >? ? ? ? ? ? ?I'd like to propose that we create an account with > >> >? ? ? ? ? ? ?blacksmith, install its github app and move the > macOS arm64 > >> >? ? ? ? ? ? ?workflow and potentially a few others over to > blacksmith. If > >> >? ? ? ? ? ? ?this goes well and improves the situation, I'd > like to write > >> >? ? ? ? ? ? ?a blog post about our experiences as part of this > agreement. > >> >? ? ? ? ? ? ?This will improve the situation for macOS > packages for arm64 > >> >? ? ? ? ? ? ?(i.e. for all mac devices sold in the last 3 > years and more > >> >? ? ? ? ? ? ?sold since 2020). For Intel, we would continue to > build > >> >? ? ? ? ? ? ?packages but without QtWebEngine until we find a > suitable > >> >? ? ? ? ? ? ?solution. > >> > > >> >? ? ? ? ? ? ?Thanks a lot and best regards > >> >? ? ? ? ? ? ?Matthias > >> > > >> >? ? ? ? ? ? ?-- > >> >? ? ? ? ? ? ? > >> > > >> >? ? ? ? ? ? ?*Matthias Kuhn* - Mr. Noproblemo > >> > > >> >? ? ? ? ? ? ?CTO | Co-Founder > >> > > >> >? ? ? ? ? ? ?email > >> > matthias at opengis.ch > >> >? ? ? ? ? ? ?www > >> > opengis.ch > >> > > >> >? ? ? ? ? ? ?linkedin > > >> >? ? ? ? ? ? ?mastodon ? ? > ?github >> > github.com/opengisch/ > > >> > > >> > ?_______________________________________________ > >> >? ? ? ? ? ? ?QGIS-PSC mailing list > >> > QGIS-PSC at lists.osgeo.org > >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc >> > lists.osgeo.org/mailman/listinfo/qgis-psc > > > >> > > >> > ?_______________________________________________ > >> >? ? ?QGIS-PSC mailing list > >> > QGIS-PSC at lists.osgeo.org > >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc >> > lists.osgeo.org/mailman/listinfo/qgis-psc > > > >> > > >> > > >> > _______________________________________________ > >> > QGIS-PSC mailing list > >> > QGIS-PSC at lists.osgeo.org > >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc > >> > > >> _______________________________________________ > >> QGIS-PSC mailing list > >> QGIS-PSC at lists.osgeo.org > >> https://lists.osgeo.org/mailman/listinfo/qgis-psc > > > > > > > > -- > > Marco Bernasocchi > > > > QGIS.org Chair > > OSGEO.org VP Europe > > OPENGIS.ch CEO > > http://berna.io > > > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc -- Alessandro Pasotti w3: www.itopen.it From anitagraser at gmx.at Fri Nov 6 23:24:42 2026 From: anitagraser at gmx.at (Anita Graser) Date: Sat, 7 Nov 2026 08:24:42 +0100 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> Message-ID: <25653e9c-14a6-4b6c-a7de-9d3755390ba2@gmx.at> >> Any other opinions from the psc? +0 Anita -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.neumann at carto.net Sat Nov 7 07:44:39 2026 From: a.neumann at carto.net (Andreas Neumann) Date: Sat, 07 Nov 2026 16:44:39 +0100 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> Message-ID: <5a4e5a07b210d2a353011a5160056c9e@carto.net> Hi Matthias, I am fine with listing them with their logo in our readme or elsewhere - but they shouldn't be called "sponsors" but rather "in-kind donors" - we cannot have sponsors (for tax reasons). Andreas On 2026-11-06 14:41, Marco Bernasocchi via QGIS-PSC wrote: > Hey Matthias, > Number 2 was already discussed and we see no problem with that. > > We hadn't discussed 1 but i see no issue there either. > > Any other opinions from the psc? > Cheers > > Marco Bernasocchi > > QGIS.org Chair > OSGEO.org VP Europe > OPENGIS.ch CEO > http://berna.io > > On Fri, 6 Nov 2026, 09:38 Matthias Kuhn, wrote: > >> Dear PSC, >> >> Thanks a lot for the positive feedback. I'd like to start this as >> soon >> as possible, migrate a few workflows, and then write a blog post in >> a >> couple of weeks when we have results to present. >> >> They asked if also (cited): >> >> 1. we have a sponsor logo (attached) - would you be ok with placing >> it >> in your project README and image on your website? >> 2. would you be alright with us talking about our partnership on >> socials/blogs? >> >> I quickly checked how the others integrate the logo in the readme >> (e.g. celery): https://github.com/celery/celery#sponsors >> >> Sorry for the additional request; I forgot to include this in the >> original email. >> I hope that this can be confirmed quickly. >> >> Thanks a lot >> Matthias >> >> On Thu, Nov 5, 2026 at 12:14?PM Marco Bernasocchi >> wrote: >>> >>> Hey Matthias, >>> Sorry, it took a bit longer on my side. >>> we discussed this in the PSC and agree that we should go forward. >>> As soon as we finalise the test phase and the system proves it >> works, we can write the blog post for them. >>> Thanks a lot for taking care of this. >>> >>> Cheers >>> Marco >>> >>> On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC >> wrote: >>>> >>>> Hi Matthias, thanks for pushing and testing this idea. >>>> >>>> In fact, listening at J?rgen yesterday in the conference, I >> realised that github runners are also a limiting factor for a >> OSGEO4W port to CI builds. >>>> >>>> As Blacksmith offers an open source partnership, I strongly >> support your proposal too as away to unlock our current github >> limitations fast and efficiently. >>>> >>>> As for long term plans to own a sovereign infrastructure, >> Blacksmith is a US based company, so it doesn't change this >> situation, but it would allow us to size more what kind of >> infrastructure we require. >>>> >>>> Best regards >>>> R?gis >>>> >>>> >>>> >>>> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC >> wrote: >>>>> Hello Matthias, >>>>> >>>>> This looks a very good idea to me. >>>>> >>>>> Thank you for exploring this opportunity! >>>>> >>>>> >>>>> --- >>>>> Alessandro Pasotti >>>>> QCooperative: www.qcooperative.net [1] >> >>>>> ItOpen: www.itopen.it [2] >>>>> >>>>> Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC >>>> psc at lists.osgeo.org > ha >> scritto: >>>>> >>>>> Hi Martin, >>>>> >>>>> Yes, running tests sounds reasonable too. >>>>> So far the build itself was taking too long and I didn't >> want to >>>>> increase this even more. >>>>> >>>>> Matthias >>>>> >>>>> On Thu, Oct 8, 2026, 22:45 Martin Dobias >> >>>> > wrote: >>>>> >>>>> Hi Matthias >>>>> >>>>> That all sounds good to me. And maybe we could also >> start to run >>>>> auto tests for mac plarform in CI? It seems quite a few >> are >>>>> broken on macOS, but we don't really know about that >> :-) >>>>> >>>>> Cheers >>>>> Martin >>>>> >>>>> >>>>> On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via >> QGIS-PSC >>>> psc at lists.osgeo.org > >> wrote: >>>>> >>>>> Dear PSC, >>>>> >>>>> We are currently producing macOS builds entirely >> within our >>>>> CI/CD pipelines (github workflows/actions). With >> this >>>>> approach, we can create dmg installer packages for >> currently >>>>> supported QGIS 3 and QGIS 4 versions for releases, >> pull >>>>> requests, and branch (latest) builds. >>>>> >>>>> For QGIS 4, one important component is currently >> missing: we >>>>> cannot build QtWebEngine (HTML rendering) because >> building >>>>> it takes over six hours (the maximum threshold for >>>>> workflows) on the (free-tier) github runners. This >>>>> limitation is significant, and several tickets >> request its >>>>> addition (for QGIS itself and for plugins like >> dataplotly). >>>>> We only need to rebuild this component when there's >> an >>>>> update, so it won't add time to every pipeline >> build. >>>>> However, we must ensure it builds once every few >> days. >>>>> >>>>> I recently was in touch with blacksmith >>>> www.blacksmith.sh/ [3]> which is an independent >> provider of >>>>> runners for github actions. They have very >> performant >>>>> runners, I was able to build QtWebEngine in less >> than 1.5 >>>>> hours (compared to more than 6 hours on github). >> They would >>>>> allow us to use their infrastructure as part of >> their open- >>>>> source engagement and ask for a blog post in >> return. >>>>> >>>>> Blacksmith would also help us reduce CI time for >> other >>>>> workflows either by moving some workflows over to >> blacksmith >>>>> or by reducing the load on github actions cache. >> This would >>>>> significantly improve the developer experience. >>>>> >>>>> One remaining challenge will be providing mac >> packages for >>>>> Intel devices. Blacksmith does not offer this >> platform. >>>>> Apple stopped selling Intel macOS devices in >> mid-2023. Apple >>>>> will officially support Intel devices until 2028, >> after >>>>> which support will be reduced, ending entirely in >> 2030. >>>>> Offering QGIS 4 support for Intel devices would be >> nice, but >>>>> we would need to find another interim solution for >> the next >>>>> 2-4 years. >>>>> >>>>> I'd like to propose that we create an account with >>>>> blacksmith, install its github app and move the >> macOS arm64 >>>>> workflow and potentially a few others over to >> blacksmith. If >>>>> this goes well and improves the situation, I'd like >> to write >>>>> a blog post about our experiences as part of this >> agreement. >>>>> This will improve the situation for macOS packages >> for arm64 >>>>> (i.e. for all mac devices sold in the last 3 years >> and more >>>>> sold since 2020). For Intel, we would continue to >> build >>>>> packages but without QtWebEngine until we find a >> suitable >>>>> solution. >>>>> >>>>> Thanks a lot and best regards >>>>> Matthias >>>>> >>>>> -- >>>>> >>>>> >>>>> *Matthias Kuhn* - Mr. Noproblemo >>>>> >>>>> CTO | Co-Founder >>>>> >>>>> email >>>>> matthias at opengis.ch >>>>> www >>>>> opengis.ch [4] >>>>> >>>>> linkedin >> >>>>> mastodon >> github >>>> github.com/opengisch/ [5]> >>>>> >>>>> _______________________________________________ >>>>> QGIS-PSC mailing list >>>>> QGIS-PSC at lists.osgeo.org >> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> >>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> >>>>> >>>>> _______________________________________________ >>>>> QGIS-PSC mailing list >>>>> QGIS-PSC at lists.osgeo.org >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> >>>>> >>>>> >>>>> _______________________________________________ >>>>> QGIS-PSC mailing list >>>>> QGIS-PSC at lists.osgeo.org >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>>>> >>>> _______________________________________________ >>>> QGIS-PSC mailing list >>>> QGIS-PSC at lists.osgeo.org >>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> >>> >>> >>> -- >>> Marco Bernasocchi >>> >>> QGIS.org Chair >>> OSGEO.org VP Europe >>> OPENGIS.ch CEO >>> http://berna.io > > > Links: > ------ > [1] http://www.qcooperative.net > [2] http://www.itopen.it > [3] http://www.blacksmith.sh/ > [4] http://opengis.ch > [5] http://github.com/opengisch/ > [6] http://lists.osgeo.org/mailman/listinfo/qgis-psc > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc From anitagraser at gmx.at Sat Nov 7 12:36:05 2026 From: anitagraser at gmx.at (Anita Graser) Date: Sat, 7 Nov 2026 21:36:05 +0100 Subject: [Qgis-psc] Proposition for additional QGIS icons In-Reply-To: References: Message-ID: Dear Vedran, I'm writing to let you know that we discussed this issue in the PSC meeting on Thursday and that the motion to support different icons for Latest/LTR/Dev has been approved. Based on the inputs from the ticket, I'm going to work out a design that aligns with the QGIS Style Guide and other existing visual elements (e.g. the splash) and implement the change with J?rgen's help. Regards, Anita On 2026-10-08 17:36, Vedran Stojnovi? via QGIS-PSC wrote: > Hello PSC, > > as discussed with Anita at UC, please put this topic on PSC meeting schedule. > > https://github.com/qgis/QGIS/issues/65754#issuecomment-6063352927 > > Kind regards, > Vedran Stojnovi?. > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc From tim at qgis.org Tue Nov 10 08:47:32 2026 From: tim at qgis.org (Tim Sutton) Date: Tue, 10 Nov 2026 16:47:32 +0000 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: <5a4e5a07b210d2a353011a5160056c9e@carto.net> References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> <5a4e5a07b210d2a353011a5160056c9e@carto.net> Message-ID: Hi For me I would be -1 to introduce 'ads' into the qgis/QGIS code base - we have other spaces for that and we always tried to keep QGIS code base 'clean'. Why dont we just give them a sustaining membership and they get all the visibility of other sustaining members? They will get better exposure that way than in the readme too I think... I will be happy to write up something for the blog and put it on the news feed etc. We should get in the habit anyway of promoting our new sponsors more (unless they want to remain incognito). Regards Tim On Sat, Nov 7, 2026 at 3:50?PM Andreas Neumann via QGIS-PSC < qgis-psc at lists.osgeo.org> wrote: > Hi Matthias, > > I am fine with listing them with their logo in our readme or elsewhere - > but they shouldn't be called "sponsors" but rather "in-kind donors" - we > cannot have sponsors (for tax reasons). > > Andreas > > On 2026-11-06 14:41, Marco Bernasocchi via QGIS-PSC wrote: > > Hey Matthias, > > Number 2 was already discussed and we see no problem with that. > > > > We hadn't discussed 1 but i see no issue there either. > > > > Any other opinions from the psc? > > Cheers > > > > Marco Bernasocchi > > > > QGIS.org Chair > > OSGEO.org VP Europe > > OPENGIS.ch CEO > > http://berna.io > > > > On Fri, 6 Nov 2026, 09:38 Matthias Kuhn, wrote: > > > >> Dear PSC, > >> > >> Thanks a lot for the positive feedback. I'd like to start this as > >> soon > >> as possible, migrate a few workflows, and then write a blog post in > >> a > >> couple of weeks when we have results to present. > >> > >> They asked if also (cited): > >> > >> 1. we have a sponsor logo (attached) - would you be ok with placing > >> it > >> in your project README and image on your website? > >> 2. would you be alright with us talking about our partnership on > >> socials/blogs? > >> > >> I quickly checked how the others integrate the logo in the readme > >> (e.g. celery): https://github.com/celery/celery#sponsors > >> > >> Sorry for the additional request; I forgot to include this in the > >> original email. > >> I hope that this can be confirmed quickly. > >> > >> Thanks a lot > >> Matthias > >> > >> On Thu, Nov 5, 2026 at 12:14?PM Marco Bernasocchi > >> wrote: > >>> > >>> Hey Matthias, > >>> Sorry, it took a bit longer on my side. > >>> we discussed this in the PSC and agree that we should go forward. > >>> As soon as we finalise the test phase and the system proves it > >> works, we can write the blog post for them. > >>> Thanks a lot for taking care of this. > >>> > >>> Cheers > >>> Marco > >>> > >>> On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC > >> wrote: > >>>> > >>>> Hi Matthias, thanks for pushing and testing this idea. > >>>> > >>>> In fact, listening at J?rgen yesterday in the conference, I > >> realised that github runners are also a limiting factor for a > >> OSGEO4W port to CI builds. > >>>> > >>>> As Blacksmith offers an open source partnership, I strongly > >> support your proposal too as away to unlock our current github > >> limitations fast and efficiently. > >>>> > >>>> As for long term plans to own a sovereign infrastructure, > >> Blacksmith is a US based company, so it doesn't change this > >> situation, but it would allow us to size more what kind of > >> infrastructure we require. > >>>> > >>>> Best regards > >>>> R?gis > >>>> > >>>> > >>>> > >>>> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC > >> wrote: > >>>>> Hello Matthias, > >>>>> > >>>>> This looks a very good idea to me. > >>>>> > >>>>> Thank you for exploring this opportunity! > >>>>> > >>>>> > >>>>> --- > >>>>> Alessandro Pasotti > >>>>> QCooperative: www.qcooperative.net [1] > >> > >>>>> ItOpen: www.itopen.it [2] > >>>>> > >>>>> Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC >>>>> psc at lists.osgeo.org > ha > >> scritto: > >>>>> > >>>>> Hi Martin, > >>>>> > >>>>> Yes, running tests sounds reasonable too. > >>>>> So far the build itself was taking too long and I didn't > >> want to > >>>>> increase this even more. > >>>>> > >>>>> Matthias > >>>>> > >>>>> On Thu, Oct 8, 2026, 22:45 Martin Dobias > >> >>>>> > wrote: > >>>>> > >>>>> Hi Matthias > >>>>> > >>>>> That all sounds good to me. And maybe we could also > >> start to run > >>>>> auto tests for mac plarform in CI? It seems quite a few > >> are > >>>>> broken on macOS, but we don't really know about that > >> :-) > >>>>> > >>>>> Cheers > >>>>> Martin > >>>>> > >>>>> > >>>>> On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via > >> QGIS-PSC >>>>> psc at lists.osgeo.org > > >> wrote: > >>>>> > >>>>> Dear PSC, > >>>>> > >>>>> We are currently producing macOS builds entirely > >> within our > >>>>> CI/CD pipelines (github workflows/actions). With > >> this > >>>>> approach, we can create dmg installer packages for > >> currently > >>>>> supported QGIS 3 and QGIS 4 versions for releases, > >> pull > >>>>> requests, and branch (latest) builds. > >>>>> > >>>>> For QGIS 4, one important component is currently > >> missing: we > >>>>> cannot build QtWebEngine (HTML rendering) because > >> building > >>>>> it takes over six hours (the maximum threshold for > >>>>> workflows) on the (free-tier) github runners. This > >>>>> limitation is significant, and several tickets > >> request its > >>>>> addition (for QGIS itself and for plugins like > >> dataplotly). > >>>>> We only need to rebuild this component when there's > >> an > >>>>> update, so it won't add time to every pipeline > >> build. > >>>>> However, we must ensure it builds once every few > >> days. > >>>>> > >>>>> I recently was in touch with blacksmith >>>>> www.blacksmith.sh/ [3]> which is an independent > >> provider of > >>>>> runners for github actions. They have very > >> performant > >>>>> runners, I was able to build QtWebEngine in less > >> than 1.5 > >>>>> hours (compared to more than 6 hours on github). > >> They would > >>>>> allow us to use their infrastructure as part of > >> their open- > >>>>> source engagement and ask for a blog post in > >> return. > >>>>> > >>>>> Blacksmith would also help us reduce CI time for > >> other > >>>>> workflows either by moving some workflows over to > >> blacksmith > >>>>> or by reducing the load on github actions cache. > >> This would > >>>>> significantly improve the developer experience. > >>>>> > >>>>> One remaining challenge will be providing mac > >> packages for > >>>>> Intel devices. Blacksmith does not offer this > >> platform. > >>>>> Apple stopped selling Intel macOS devices in > >> mid-2023. Apple > >>>>> will officially support Intel devices until 2028, > >> after > >>>>> which support will be reduced, ending entirely in > >> 2030. > >>>>> Offering QGIS 4 support for Intel devices would be > >> nice, but > >>>>> we would need to find another interim solution for > >> the next > >>>>> 2-4 years. > >>>>> > >>>>> I'd like to propose that we create an account with > >>>>> blacksmith, install its github app and move the > >> macOS arm64 > >>>>> workflow and potentially a few others over to > >> blacksmith. If > >>>>> this goes well and improves the situation, I'd like > >> to write > >>>>> a blog post about our experiences as part of this > >> agreement. > >>>>> This will improve the situation for macOS packages > >> for arm64 > >>>>> (i.e. for all mac devices sold in the last 3 years > >> and more > >>>>> sold since 2020). For Intel, we would continue to > >> build > >>>>> packages but without QtWebEngine until we find a > >> suitable > >>>>> solution. > >>>>> > >>>>> Thanks a lot and best regards > >>>>> Matthias > >>>>> > >>>>> -- > >>>>> > >>>>> > >>>>> *Matthias Kuhn* - Mr. Noproblemo > >>>>> > >>>>> CTO | Co-Founder > >>>>> > >>>>> email > >>>>> matthias at opengis.ch > >>>>> www > >>>>> opengis.ch [4] > >>>>> > >>>>> linkedin > >> > >>>>> mastodon > >> github >>>>> github.com/opengisch/ [5]> > >>>>> > >>>>> _______________________________________________ > >>>>> QGIS-PSC mailing list > >>>>> QGIS-PSC at lists.osgeo.org > >> > >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc > >> >>>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> > >>>>> > >>>>> _______________________________________________ > >>>>> QGIS-PSC mailing list > >>>>> QGIS-PSC at lists.osgeo.org > >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> QGIS-PSC mailing list > >>>>> QGIS-PSC at lists.osgeo.org > >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc > >>>>> > >>>> _______________________________________________ > >>>> QGIS-PSC mailing list > >>>> QGIS-PSC at lists.osgeo.org > >>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc > >>> > >>> > >>> > >>> -- > >>> Marco Bernasocchi > >>> > >>> QGIS.org Chair > >>> OSGEO.org VP Europe > >>> OPENGIS.ch CEO > >>> http://berna.io > > > > > > Links: > > ------ > > [1] http://www.qcooperative.net > > [2] http://www.itopen.it > > [3] http://www.blacksmith.sh/ > > [4] http://opengis.ch > > [5] http://github.com/opengisch/ > > [6] http://lists.osgeo.org/mailman/listinfo/qgis-psc > > _______________________________________________ > > QGIS-PSC mailing list > > QGIS-PSC at lists.osgeo.org > > https://lists.osgeo.org/mailman/listinfo/qgis-psc > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc > -- *Tim Sutton* QGIS Project Steering Committee tim at qgis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim at qgis.org Tue Nov 10 09:00:02 2026 From: tim at qgis.org (Tim Sutton) Date: Tue, 10 Nov 2026 17:00:02 +0000 Subject: [Qgis-psc] QGIS 4.4 release github project cleanup In-Reply-To: References: Message-ID: Hi Mathieu On Fri, Nov 6, 2026 at 8:23?AM Mathieu Pellerin via QGIS-PSC < qgis-psc at lists.osgeo.org> wrote: > Greetings, > > First, big thanks for the blog post providing an update about the > forthcoming QGIS 4.4 release, I?m sure it?ll be useful guidance to the > broader community. > > Motivated by that blog post, Marco, myself and Dave spent some time > cleaning up the QGIS 4.4 release project ( > https://github.com/orgs/qgis/projects/18/views/1). There were a fair > amount of issues that fell off the mark (e.g. opened in 2018 in our redmine > (RIP) portal with no significant activity in years). > > We've applied the following rules to filter issues (I believe aligns with > the blog post definition and prior understanding by devs): > > - > > worked in 3 AND broken in 4 -> remained in the project > - > > worked in 3 AND broken in 4 AND critical -> remained in the project & > assigned to the ?critical blocker? column > - > > worked in <3.44 AND broken in >=3.44 -> removed from the project > - > > missing in 3 AND broken in 4 -> removed from the project > > A few issues (9) have been placed in a TBC column as it was not > immediately clear whether they were still valid as of November 2026. > > We hope this project cleanup effort results in a more accurate reflection > of what's left to tackle and help focus our collective efforts. > > Thanks so much, amazing work! > Now onto something to consider :) > > At the moment, what is considered blocking 4.4 is contained in the > confirmed + critical blocker lists; it might be useful to narrow down the > list of critical 3.X -> 4.X regressions that are considered blocking. > Wasnt the idea that *any* regression was going to be considered blocking if it cannot be reproduced in 3.44? https://lists.osgeo.org/pipermail/qgis-developer/2026-October/068654.html Thanks Mathieu and sorry I never got a chance to chat properly in Laax! Regards Tim > > Best, > > Mathieu > > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc > -- *Tim Sutton* QGIS Project Steering Committee tim at qgis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From emma at north-road.com Tue Nov 10 18:32:34 2026 From: emma at north-road.com (Emma Hain) Date: Wed, 11 Nov 2026 12:32:34 +1000 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> <5a4e5a07b210d2a353011a5160056c9e@carto.net> Message-ID: Would you almost introduce them as a new class of contributor? Such as an 'Infrastructure' contributor? On Wed, 11 Nov 2026 at 02:47, Tim Sutton via QGIS-PSC < qgis-psc at lists.osgeo.org> wrote: > Hi > > For me I would be -1 to introduce 'ads' into the qgis/QGIS code base - we > have other spaces for that and we always tried to keep QGIS code base > 'clean'. Why dont we just give them a sustaining membership and they get > all the visibility of other sustaining members? They will get better > exposure that way than in the readme too I think... > > I will be happy to write up something for the blog and put it on the news > feed etc. We should get in the habit anyway of promoting our new sponsors > more (unless they want to remain incognito). > > Regards > > Tim > > On Sat, Nov 7, 2026 at 3:50?PM Andreas Neumann via QGIS-PSC < > qgis-psc at lists.osgeo.org> wrote: > >> Hi Matthias, >> >> I am fine with listing them with their logo in our readme or elsewhere - >> but they shouldn't be called "sponsors" but rather "in-kind donors" - we >> cannot have sponsors (for tax reasons). >> >> Andreas >> >> On 2026-11-06 14:41, Marco Bernasocchi via QGIS-PSC wrote: >> > Hey Matthias, >> > Number 2 was already discussed and we see no problem with that. >> > >> > We hadn't discussed 1 but i see no issue there either. >> > >> > Any other opinions from the psc? >> > Cheers >> > >> > Marco Bernasocchi >> > >> > QGIS.org Chair >> > OSGEO.org VP Europe >> > OPENGIS.ch CEO >> > http://berna.io >> > >> > On Fri, 6 Nov 2026, 09:38 Matthias Kuhn, wrote: >> > >> >> Dear PSC, >> >> >> >> Thanks a lot for the positive feedback. I'd like to start this as >> >> soon >> >> as possible, migrate a few workflows, and then write a blog post in >> >> a >> >> couple of weeks when we have results to present. >> >> >> >> They asked if also (cited): >> >> >> >> 1. we have a sponsor logo (attached) - would you be ok with placing >> >> it >> >> in your project README and image on your website? >> >> 2. would you be alright with us talking about our partnership on >> >> socials/blogs? >> >> >> >> I quickly checked how the others integrate the logo in the readme >> >> (e.g. celery): https://github.com/celery/celery#sponsors >> >> >> >> Sorry for the additional request; I forgot to include this in the >> >> original email. >> >> I hope that this can be confirmed quickly. >> >> >> >> Thanks a lot >> >> Matthias >> >> >> >> On Thu, Nov 5, 2026 at 12:14?PM Marco Bernasocchi >> >> wrote: >> >>> >> >>> Hey Matthias, >> >>> Sorry, it took a bit longer on my side. >> >>> we discussed this in the PSC and agree that we should go forward. >> >>> As soon as we finalise the test phase and the system proves it >> >> works, we can write the blog post for them. >> >>> Thanks a lot for taking care of this. >> >>> >> >>> Cheers >> >>> Marco >> >>> >> >>> On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC >> >> wrote: >> >>>> >> >>>> Hi Matthias, thanks for pushing and testing this idea. >> >>>> >> >>>> In fact, listening at J?rgen yesterday in the conference, I >> >> realised that github runners are also a limiting factor for a >> >> OSGEO4W port to CI builds. >> >>>> >> >>>> As Blacksmith offers an open source partnership, I strongly >> >> support your proposal too as away to unlock our current github >> >> limitations fast and efficiently. >> >>>> >> >>>> As for long term plans to own a sovereign infrastructure, >> >> Blacksmith is a US based company, so it doesn't change this >> >> situation, but it would allow us to size more what kind of >> >> infrastructure we require. >> >>>> >> >>>> Best regards >> >>>> R?gis >> >>>> >> >>>> >> >>>> >> >>>> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC >> >> wrote: >> >>>>> Hello Matthias, >> >>>>> >> >>>>> This looks a very good idea to me. >> >>>>> >> >>>>> Thank you for exploring this opportunity! >> >>>>> >> >>>>> >> >>>>> --- >> >>>>> Alessandro Pasotti >> >>>>> QCooperative: www.qcooperative.net [1] >> >> >> >>>>> ItOpen: www.itopen.it [2] >> >>>>> >> >>>>> Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC > >>>>> psc at lists.osgeo.org > ha >> >> scritto: >> >>>>> >> >>>>> Hi Martin, >> >>>>> >> >>>>> Yes, running tests sounds reasonable too. >> >>>>> So far the build itself was taking too long and I didn't >> >> want to >> >>>>> increase this even more. >> >>>>> >> >>>>> Matthias >> >>>>> >> >>>>> On Thu, Oct 8, 2026, 22:45 Martin Dobias >> >> > >>>>> > wrote: >> >>>>> >> >>>>> Hi Matthias >> >>>>> >> >>>>> That all sounds good to me. And maybe we could also >> >> start to run >> >>>>> auto tests for mac plarform in CI? It seems quite a few >> >> are >> >>>>> broken on macOS, but we don't really know about that >> >> :-) >> >>>>> >> >>>>> Cheers >> >>>>> Martin >> >>>>> >> >>>>> >> >>>>> On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via >> >> QGIS-PSC > >>>>> psc at lists.osgeo.org > >> >> wrote: >> >>>>> >> >>>>> Dear PSC, >> >>>>> >> >>>>> We are currently producing macOS builds entirely >> >> within our >> >>>>> CI/CD pipelines (github workflows/actions). With >> >> this >> >>>>> approach, we can create dmg installer packages for >> >> currently >> >>>>> supported QGIS 3 and QGIS 4 versions for releases, >> >> pull >> >>>>> requests, and branch (latest) builds. >> >>>>> >> >>>>> For QGIS 4, one important component is currently >> >> missing: we >> >>>>> cannot build QtWebEngine (HTML rendering) because >> >> building >> >>>>> it takes over six hours (the maximum threshold for >> >>>>> workflows) on the (free-tier) github runners. This >> >>>>> limitation is significant, and several tickets >> >> request its >> >>>>> addition (for QGIS itself and for plugins like >> >> dataplotly). >> >>>>> We only need to rebuild this component when there's >> >> an >> >>>>> update, so it won't add time to every pipeline >> >> build. >> >>>>> However, we must ensure it builds once every few >> >> days. >> >>>>> >> >>>>> I recently was in touch with blacksmith > >>>>> www.blacksmith.sh/ [3]> which is an independent >> >> provider of >> >>>>> runners for github actions. They have very >> >> performant >> >>>>> runners, I was able to build QtWebEngine in less >> >> than 1.5 >> >>>>> hours (compared to more than 6 hours on github). >> >> They would >> >>>>> allow us to use their infrastructure as part of >> >> their open- >> >>>>> source engagement and ask for a blog post in >> >> return. >> >>>>> >> >>>>> Blacksmith would also help us reduce CI time for >> >> other >> >>>>> workflows either by moving some workflows over to >> >> blacksmith >> >>>>> or by reducing the load on github actions cache. >> >> This would >> >>>>> significantly improve the developer experience. >> >>>>> >> >>>>> One remaining challenge will be providing mac >> >> packages for >> >>>>> Intel devices. Blacksmith does not offer this >> >> platform. >> >>>>> Apple stopped selling Intel macOS devices in >> >> mid-2023. Apple >> >>>>> will officially support Intel devices until 2028, >> >> after >> >>>>> which support will be reduced, ending entirely in >> >> 2030. >> >>>>> Offering QGIS 4 support for Intel devices would be >> >> nice, but >> >>>>> we would need to find another interim solution for >> >> the next >> >>>>> 2-4 years. >> >>>>> >> >>>>> I'd like to propose that we create an account with >> >>>>> blacksmith, install its github app and move the >> >> macOS arm64 >> >>>>> workflow and potentially a few others over to >> >> blacksmith. If >> >>>>> this goes well and improves the situation, I'd like >> >> to write >> >>>>> a blog post about our experiences as part of this >> >> agreement. >> >>>>> This will improve the situation for macOS packages >> >> for arm64 >> >>>>> (i.e. for all mac devices sold in the last 3 years >> >> and more >> >>>>> sold since 2020). For Intel, we would continue to >> >> build >> >>>>> packages but without QtWebEngine until we find a >> >> suitable >> >>>>> solution. >> >>>>> >> >>>>> Thanks a lot and best regards >> >>>>> Matthias >> >>>>> >> >>>>> -- >> >>>>> >> >>>>> >> >>>>> *Matthias Kuhn* - Mr. Noproblemo >> >>>>> >> >>>>> CTO | Co-Founder >> >>>>> >> >>>>> email >> >>>>> matthias at opengis.ch >> >>>>> www >> >>>>> opengis.ch [4] >> >>>>> >> >>>>> linkedin >> >> >> >>>>> mastodon >> >> github > >>>>> github.com/opengisch/ [5]> >> >>>>> >> >>>>> _______________________________________________ >> >>>>> QGIS-PSC mailing list >> >>>>> QGIS-PSC at lists.osgeo.org >> >> >> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> >> > >>>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> >> >>>>> >> >>>>> _______________________________________________ >> >>>>> QGIS-PSC mailing list >> >>>>> QGIS-PSC at lists.osgeo.org >> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc > >>>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> >> >>>>> >> >>>>> >> >>>>> _______________________________________________ >> >>>>> QGIS-PSC mailing list >> >>>>> QGIS-PSC at lists.osgeo.org >> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> >>>>> >> >>>> _______________________________________________ >> >>>> QGIS-PSC mailing list >> >>>> QGIS-PSC at lists.osgeo.org >> >>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> >>> >> >>> >> >>> >> >>> -- >> >>> Marco Bernasocchi >> >>> >> >>> QGIS.org Chair >> >>> OSGEO.org VP Europe >> >>> OPENGIS.ch CEO >> >>> http://berna.io >> > >> > >> > Links: >> > ------ >> > [1] http://www.qcooperative.net >> > [2] http://www.itopen.it >> > [3] http://www.blacksmith.sh/ >> > [4] http://opengis.ch >> > [5] http://github.com/opengisch/ >> > [6] http://lists.osgeo.org/mailman/listinfo/qgis-psc >> > _______________________________________________ >> > QGIS-PSC mailing list >> > QGIS-PSC at lists.osgeo.org >> > https://lists.osgeo.org/mailman/listinfo/qgis-psc >> _______________________________________________ >> QGIS-PSC mailing list >> QGIS-PSC at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> > > > -- > > > > *Tim Sutton* > QGIS Project Steering Committee > tim at qgis.org > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco at qgis.org Wed Nov 11 05:03:01 2026 From: marco at qgis.org (Marco Bernasocchi) Date: Wed, 11 Nov 2026 14:03:01 +0100 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> <5a4e5a07b210d2a353011a5160056c9e@carto.net> Message-ID: Yes, that was kind of the idea. I would not do give a sustaining membership but create a new section sustaining partners or in-kind donors like andreas suggested. Cheers Marco. On Wed, 11 Nov 2026 at 03:32, Emma Hain via QGIS-PSC < qgis-psc at lists.osgeo.org> wrote: > Would you almost introduce them as a new class of contributor? Such as an > 'Infrastructure' contributor? > > On Wed, 11 Nov 2026 at 02:47, Tim Sutton via QGIS-PSC < > qgis-psc at lists.osgeo.org> wrote: > >> Hi >> >> For me I would be -1 to introduce 'ads' into the qgis/QGIS code base - we >> have other spaces for that and we always tried to keep QGIS code base >> 'clean'. Why dont we just give them a sustaining membership and they get >> all the visibility of other sustaining members? They will get better >> exposure that way than in the readme too I think... >> >> I will be happy to write up something for the blog and put it on the news >> feed etc. We should get in the habit anyway of promoting our new sponsors >> more (unless they want to remain incognito). >> >> Regards >> >> Tim >> >> On Sat, Nov 7, 2026 at 3:50?PM Andreas Neumann via QGIS-PSC < >> qgis-psc at lists.osgeo.org> wrote: >> >>> Hi Matthias, >>> >>> I am fine with listing them with their logo in our readme or elsewhere - >>> but they shouldn't be called "sponsors" but rather "in-kind donors" - we >>> cannot have sponsors (for tax reasons). >>> >>> Andreas >>> >>> On 2026-11-06 14:41, Marco Bernasocchi via QGIS-PSC wrote: >>> > Hey Matthias, >>> > Number 2 was already discussed and we see no problem with that. >>> > >>> > We hadn't discussed 1 but i see no issue there either. >>> > >>> > Any other opinions from the psc? >>> > Cheers >>> > >>> > Marco Bernasocchi >>> > >>> > QGIS.org Chair >>> > OSGEO.org VP Europe >>> > OPENGIS.ch CEO >>> > http://berna.io >>> > >>> > On Fri, 6 Nov 2026, 09:38 Matthias Kuhn, wrote: >>> > >>> >> Dear PSC, >>> >> >>> >> Thanks a lot for the positive feedback. I'd like to start this as >>> >> soon >>> >> as possible, migrate a few workflows, and then write a blog post in >>> >> a >>> >> couple of weeks when we have results to present. >>> >> >>> >> They asked if also (cited): >>> >> >>> >> 1. we have a sponsor logo (attached) - would you be ok with placing >>> >> it >>> >> in your project README and image on your website? >>> >> 2. would you be alright with us talking about our partnership on >>> >> socials/blogs? >>> >> >>> >> I quickly checked how the others integrate the logo in the readme >>> >> (e.g. celery): https://github.com/celery/celery#sponsors >>> >> >>> >> Sorry for the additional request; I forgot to include this in the >>> >> original email. >>> >> I hope that this can be confirmed quickly. >>> >> >>> >> Thanks a lot >>> >> Matthias >>> >> >>> >> On Thu, Nov 5, 2026 at 12:14?PM Marco Bernasocchi >>> >> wrote: >>> >>> >>> >>> Hey Matthias, >>> >>> Sorry, it took a bit longer on my side. >>> >>> we discussed this in the PSC and agree that we should go forward. >>> >>> As soon as we finalise the test phase and the system proves it >>> >> works, we can write the blog post for them. >>> >>> Thanks a lot for taking care of this. >>> >>> >>> >>> Cheers >>> >>> Marco >>> >>> >>> >>> On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC >>> >> wrote: >>> >>>> >>> >>>> Hi Matthias, thanks for pushing and testing this idea. >>> >>>> >>> >>>> In fact, listening at J?rgen yesterday in the conference, I >>> >> realised that github runners are also a limiting factor for a >>> >> OSGEO4W port to CI builds. >>> >>>> >>> >>>> As Blacksmith offers an open source partnership, I strongly >>> >> support your proposal too as away to unlock our current github >>> >> limitations fast and efficiently. >>> >>>> >>> >>>> As for long term plans to own a sovereign infrastructure, >>> >> Blacksmith is a US based company, so it doesn't change this >>> >> situation, but it would allow us to size more what kind of >>> >> infrastructure we require. >>> >>>> >>> >>>> Best regards >>> >>>> R?gis >>> >>>> >>> >>>> >>> >>>> >>> >>>> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC >>> >> wrote: >>> >>>>> Hello Matthias, >>> >>>>> >>> >>>>> This looks a very good idea to me. >>> >>>>> >>> >>>>> Thank you for exploring this opportunity! >>> >>>>> >>> >>>>> >>> >>>>> --- >>> >>>>> Alessandro Pasotti >>> >>>>> QCooperative: www.qcooperative.net [1] >>> >> >>> >>>>> ItOpen: www.itopen.it [2] >>> >>>>> >>> >>>>> Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC >> >>>>> psc at lists.osgeo.org > ha >>> >> scritto: >>> >>>>> >>> >>>>> Hi Martin, >>> >>>>> >>> >>>>> Yes, running tests sounds reasonable too. >>> >>>>> So far the build itself was taking too long and I didn't >>> >> want to >>> >>>>> increase this even more. >>> >>>>> >>> >>>>> Matthias >>> >>>>> >>> >>>>> On Thu, Oct 8, 2026, 22:45 Martin Dobias >>> >> >> >>>>> > wrote: >>> >>>>> >>> >>>>> Hi Matthias >>> >>>>> >>> >>>>> That all sounds good to me. And maybe we could also >>> >> start to run >>> >>>>> auto tests for mac plarform in CI? It seems quite a few >>> >> are >>> >>>>> broken on macOS, but we don't really know about that >>> >> :-) >>> >>>>> >>> >>>>> Cheers >>> >>>>> Martin >>> >>>>> >>> >>>>> >>> >>>>> On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via >>> >> QGIS-PSC >> >>>>> psc at lists.osgeo.org > >>> >> wrote: >>> >>>>> >>> >>>>> Dear PSC, >>> >>>>> >>> >>>>> We are currently producing macOS builds entirely >>> >> within our >>> >>>>> CI/CD pipelines (github workflows/actions). With >>> >> this >>> >>>>> approach, we can create dmg installer packages for >>> >> currently >>> >>>>> supported QGIS 3 and QGIS 4 versions for releases, >>> >> pull >>> >>>>> requests, and branch (latest) builds. >>> >>>>> >>> >>>>> For QGIS 4, one important component is currently >>> >> missing: we >>> >>>>> cannot build QtWebEngine (HTML rendering) because >>> >> building >>> >>>>> it takes over six hours (the maximum threshold for >>> >>>>> workflows) on the (free-tier) github runners. This >>> >>>>> limitation is significant, and several tickets >>> >> request its >>> >>>>> addition (for QGIS itself and for plugins like >>> >> dataplotly). >>> >>>>> We only need to rebuild this component when there's >>> >> an >>> >>>>> update, so it won't add time to every pipeline >>> >> build. >>> >>>>> However, we must ensure it builds once every few >>> >> days. >>> >>>>> >>> >>>>> I recently was in touch with blacksmith >> >>>>> www.blacksmith.sh/ [3]> which is an independent >>> >> provider of >>> >>>>> runners for github actions. They have very >>> >> performant >>> >>>>> runners, I was able to build QtWebEngine in less >>> >> than 1.5 >>> >>>>> hours (compared to more than 6 hours on github). >>> >> They would >>> >>>>> allow us to use their infrastructure as part of >>> >> their open- >>> >>>>> source engagement and ask for a blog post in >>> >> return. >>> >>>>> >>> >>>>> Blacksmith would also help us reduce CI time for >>> >> other >>> >>>>> workflows either by moving some workflows over to >>> >> blacksmith >>> >>>>> or by reducing the load on github actions cache. >>> >> This would >>> >>>>> significantly improve the developer experience. >>> >>>>> >>> >>>>> One remaining challenge will be providing mac >>> >> packages for >>> >>>>> Intel devices. Blacksmith does not offer this >>> >> platform. >>> >>>>> Apple stopped selling Intel macOS devices in >>> >> mid-2023. Apple >>> >>>>> will officially support Intel devices until 2028, >>> >> after >>> >>>>> which support will be reduced, ending entirely in >>> >> 2030. >>> >>>>> Offering QGIS 4 support for Intel devices would be >>> >> nice, but >>> >>>>> we would need to find another interim solution for >>> >> the next >>> >>>>> 2-4 years. >>> >>>>> >>> >>>>> I'd like to propose that we create an account with >>> >>>>> blacksmith, install its github app and move the >>> >> macOS arm64 >>> >>>>> workflow and potentially a few others over to >>> >> blacksmith. If >>> >>>>> this goes well and improves the situation, I'd like >>> >> to write >>> >>>>> a blog post about our experiences as part of this >>> >> agreement. >>> >>>>> This will improve the situation for macOS packages >>> >> for arm64 >>> >>>>> (i.e. for all mac devices sold in the last 3 years >>> >> and more >>> >>>>> sold since 2020). For Intel, we would continue to >>> >> build >>> >>>>> packages but without QtWebEngine until we find a >>> >> suitable >>> >>>>> solution. >>> >>>>> >>> >>>>> Thanks a lot and best regards >>> >>>>> Matthias >>> >>>>> >>> >>>>> -- >>> >>>>> >>> >>>>> >>> >>>>> *Matthias Kuhn* - Mr. Noproblemo >>> >>>>> >>> >>>>> CTO | Co-Founder >>> >>>>> >>> >>>>> email >>> >>>>> matthias at opengis.ch >>> >>>>> www >>> >>>>> opengis.ch [4] >>> >>>>> >>> >>>>> linkedin >>> >> >>> >>>>> mastodon >>> >> github >> >>>>> github.com/opengisch/ [5]> >>> >>>>> >>> >>>>> _______________________________________________ >>> >>>>> QGIS-PSC mailing list >>> >>>>> QGIS-PSC at lists.osgeo.org >>> >> >>> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> >> >> >>>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> >>> >>>>> >>> >>>>> _______________________________________________ >>> >>>>> QGIS-PSC mailing list >>> >>>>> QGIS-PSC at lists.osgeo.org >>> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> >>>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> >>> >>>>> >>> >>>>> >>> >>>>> _______________________________________________ >>> >>>>> QGIS-PSC mailing list >>> >>>>> QGIS-PSC at lists.osgeo.org >>> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> >>>>> >>> >>>> _______________________________________________ >>> >>>> QGIS-PSC mailing list >>> >>>> QGIS-PSC at lists.osgeo.org >>> >>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> Marco Bernasocchi >>> >>> >>> >>> QGIS.org Chair >>> >>> OSGEO.org VP Europe >>> >>> OPENGIS.ch CEO >>> >>> http://berna.io >>> > >>> > >>> > Links: >>> > ------ >>> > [1] http://www.qcooperative.net >>> > [2] http://www.itopen.it >>> > [3] http://www.blacksmith.sh/ >>> > [4] http://opengis.ch >>> > [5] http://github.com/opengisch/ >>> > [6] http://lists.osgeo.org/mailman/listinfo/qgis-psc >>> > _______________________________________________ >>> > QGIS-PSC mailing list >>> > QGIS-PSC at lists.osgeo.org >>> > https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> _______________________________________________ >>> QGIS-PSC mailing list >>> QGIS-PSC at lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> >> >> >> -- >> >> >> >> *Tim Sutton* >> QGIS Project Steering Committee >> tim at qgis.org >> _______________________________________________ >> QGIS-PSC mailing list >> QGIS-PSC at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc > -- Marco Bernasocchi QGIS.org Chair OSGEO.org VP Europe OPENGIS.ch CEO http://berna.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From voting at qgis.org Wed Nov 11 15:57:42 2026 From: voting at qgis.org (Voting Officer) Date: Thu, 12 Nov 2026 07:57:42 +0800 Subject: [Qgis-psc] Community Voting Members Election Nov-Dec 2026: Schedule and Call for Nominations Message-ID: Dear QGIS Community, With the addition of Algeria, Armenia, Cameroon, Canada, Croatia, Cyprus, and India in 2026, we now have 38 country-level user groups. The QGIS Charter calls for an equal number of ?Community Voting Members? (we have 32), so we?re kicking off an election for six new voting members. This year?s election will aim to follow this schedule: - 12 - 26 Nov: Call for Nominations - 27 Nov - 10 Dec: Voting - 11 - 12 Dec: Tally votes & verification of results **Call for Nominations** We invite nominations for 6 Community Voting Members. Any active QGIS community member is eligible to be nominated. Only QGIS Committers (?any person who has been granted commit access in any of the official QGIS repositories?) are eligible to make nominations. This includes committers to any QGIS Git repository or Transifex project. Before making a nomination, please confirm you?re eligible, and check with the person you?re nominating to make sure they are willing. You can submit your nominations until **23:59 UTC on 26 November 2026** here: https://forms.gle/h3Bd6Dhiz6v7AFuf9 If you play an organisational role (e.g. documentation lead, translation lead), kindly forward this email to your committers to ensure broad participation. For further details, visit the QGIS community organisation page . If you have any questions about the process, please don?t hesitate to contact me. Thank you for your continued engagement! John John Bryant QGIS Voting Officer -------------- next part -------------- An HTML attachment was scrubbed... URL: From voting at qgis.org Thu Nov 12 01:29:24 2026 From: voting at qgis.org (Voting Officer) Date: Thu, 12 Nov 2026 17:29:24 +0800 Subject: [Qgis-psc] [QGIS-Developer] Community Voting Members Election Nov-Dec 2026: Schedule and Call for Nominations In-Reply-To: References: Message-ID: Hi Stefanos, that's a nice suggestion, thanks. I'll cc the other lists as well so they have this extra context. The Colombia UG was closed in 2025 and was taken into account at the last Voting Member Election in January/February 2026. The basis for 6 open seats this time is: - At the end of the last Voting Member Election, we were in balance with 34 country-level user groups and 34 community voting members. - This year, Marco Serusi (QGIS staff) did an exercise to update contacts and current status for all the user groups. He discovered 3 user groups (England, Scotland, and Wales) were functionally absorbed by OSGeo UK. At this time OSGeo UK hasn't yet indicated if they'll maintain user group status. - We have 7 new groups in 2026: Algeria, Armenia, Cameroon, Canada, Croatia, Cyprus, and India. - In the recent AGM election, a motion passed to amend the charter to clarify a Community Voting Member elected to the PSC "will pause their voting membership for the duration of their PSC service". Two people are affected (Alessandro Pasotti and R?gis Haubourg). - That gives us 38 user groups (34 - 3 + 7) and 32 community voting members (34 - 2), so we need 6 new members to balance. Hopefully that all makes sense! Cheers John On Thu, Nov 12, 2026 at 3:10?PM Stefanos Natsis wrote: > Hi John, > > Thanks for the heads up! > > Can you also clarify why 7 new groups result in 6 new community voting > member seats? > Is it the Colombia user group becoming inactive? > > It would be great if a summary of all events affecting the available seats > (ie new user groups, inactive user groups, voting member joining the PSC, > voting member voluntarily stepping down etc) was included in these > announcements. > > Thanks again for your great work! > > Stefanos > > On Thu, 12 Nov 2026 at 01:58, Voting Officer via QGIS-Developer < > qgis-developer at lists.osgeo.org> wrote: > >> Dear QGIS Community, >> >> With the addition of Algeria, Armenia, Cameroon, Canada, Croatia, Cyprus, >> and India in 2026, we now have 38 country-level user groups. The QGIS >> Charter calls for an >> equal number of ?Community Voting Members? (we have 32), so we?re kicking >> off an election for six new voting members. >> >> This year?s election will aim to follow this schedule: >> >> - >> >> 12 - 26 Nov: Call for Nominations >> - >> >> 27 Nov - 10 Dec: Voting >> - >> >> 11 - 12 Dec: Tally votes & verification of results >> >> **Call for Nominations** >> >> We invite nominations for 6 Community Voting Members. Any active QGIS >> community member is eligible to be nominated. >> >> Only QGIS Committers (?any person who has been granted commit access in >> any of the official QGIS repositories?) are eligible to make >> nominations. This includes committers to any QGIS Git repository or >> Transifex project. >> >> Before making a nomination, please confirm you?re eligible, and check >> with the person you?re nominating to make sure they are willing. >> >> You can submit your nominations until **23:59 UTC on 26 November 2026** >> here: >> >> https://forms.gle/h3Bd6Dhiz6v7AFuf9 >> >> If you play an organisational role (e.g. documentation lead, translation >> lead), kindly forward this email to your committers to ensure broad >> participation. >> >> For further details, visit the QGIS community organisation page >> . If you have any questions >> about the process, please don?t hesitate to contact me. >> >> Thank you for your continued engagement! >> John >> >> John Bryant >> QGIS Voting Officer >> _______________________________________________ >> QGIS-Developer mailing list >> QGIS-Developer at lists.osgeo.org >> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From imajimatika at gmail.com Thu Nov 12 01:45:26 2026 From: imajimatika at gmail.com (Ismail Sunni) Date: Thu, 12 Nov 2026 16:45:26 +0700 Subject: [Qgis-psc] [Qgis-voting-members] [QGIS-Developer] Community Voting Members Election Nov-Dec 2026: Schedule and Call for Nominations In-Reply-To: References: Message-ID: Hi John, Thanks for the detailed explanation. Out of curiosity, since we do an exercise on the user groups, do/will/have we do the same for the community voting member? I read in the charter that voting members won't be removed unless they resign or there is a motion thought (so may be not needed to do the exercise) Best regards On Thu, Nov 12, 2026 at 4:29?PM Voting Officer via Qgis-voting-members < qgis-voting-members at lists.osgeo.org> wrote: > Hi Stefanos, that's a nice suggestion, thanks. I'll cc the other lists as > well so they have this extra context. > > The Colombia UG was closed in 2025 and was taken into account at the last > Voting Member Election in January/February 2026. > > The basis for 6 open seats this time is: > > - At the end of the last Voting Member Election, we were in balance > with 34 country-level user groups and 34 community voting members. > - This year, Marco Serusi (QGIS staff) did an exercise to update > contacts and current status for all the user groups. He discovered 3 user > groups (England, Scotland, and Wales) were functionally absorbed by > OSGeo UK. At this time OSGeo UK hasn't yet indicated if they'll maintain > user group status. > - We have 7 new groups in 2026: Algeria, Armenia, Cameroon, Canada, > Croatia, Cyprus, and India. > - In the recent AGM election, a motion passed to amend the charter to > clarify a Community Voting Member elected to the PSC "will pause their > voting membership for the duration of their PSC service". Two people are > affected (Alessandro Pasotti and R?gis Haubourg). > - That gives us 38 user groups (34 - 3 + 7) and 32 community voting > members (34 - 2), so we need 6 new members to balance. > > Hopefully that all makes sense! > > Cheers > John > > On Thu, Nov 12, 2026 at 3:10?PM Stefanos Natsis wrote: > >> Hi John, >> >> Thanks for the heads up! >> >> Can you also clarify why 7 new groups result in 6 new community voting >> member seats? >> Is it the Colombia user group becoming inactive? >> >> It would be great if a summary of all events affecting the available >> seats (ie new user groups, inactive user groups, voting member joining the >> PSC, voting member voluntarily stepping down etc) was included in these >> announcements. >> >> Thanks again for your great work! >> >> Stefanos >> >> On Thu, 12 Nov 2026 at 01:58, Voting Officer via QGIS-Developer < >> qgis-developer at lists.osgeo.org> wrote: >> >>> Dear QGIS Community, >>> >>> With the addition of Algeria, Armenia, Cameroon, Canada, Croatia, >>> Cyprus, and India in 2026, we now have 38 country-level user groups. The QGIS >>> Charter calls for an >>> equal number of ?Community Voting Members? (we have 32), so we?re kicking >>> off an election for six new voting members. >>> >>> This year?s election will aim to follow this schedule: >>> >>> - >>> >>> 12 - 26 Nov: Call for Nominations >>> - >>> >>> 27 Nov - 10 Dec: Voting >>> - >>> >>> 11 - 12 Dec: Tally votes & verification of results >>> >>> **Call for Nominations** >>> >>> We invite nominations for 6 Community Voting Members. Any active QGIS >>> community member is eligible to be nominated. >>> >>> Only QGIS Committers (?any person who has been granted commit access in >>> any of the official QGIS repositories?) are eligible to make >>> nominations. This includes committers to any QGIS Git repository or >>> Transifex project. >>> >>> Before making a nomination, please confirm you?re eligible, and check >>> with the person you?re nominating to make sure they are willing. >>> >>> You can submit your nominations until **23:59 UTC on 26 November 2026** >>> here: >>> >>> https://forms.gle/h3Bd6Dhiz6v7AFuf9 >>> >>> If you play an organisational role (e.g. documentation lead, translation >>> lead), kindly forward this email to your committers to ensure broad >>> participation. >>> >>> For further details, visit the QGIS community organisation page >>> . If you have any questions >>> about the process, please don?t hesitate to contact me. >>> >>> Thank you for your continued engagement! >>> John >>> >>> John Bryant >>> QGIS Voting Officer >>> _______________________________________________ >>> QGIS-Developer mailing list >>> QGIS-Developer at lists.osgeo.org >>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer >>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer >>> >> _______________________________________________ > Qgis-voting-members mailing list > Qgis-voting-members at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-voting-members > -- -- Ismail Sunni Software Engineer ismailsunni.id onepieceofdata.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From nyall.dawson at gmail.com Thu Nov 12 20:16:22 2026 From: nyall.dawson at gmail.com (Nyall Dawson) Date: Fri, 13 Nov 2026 14:16:22 +1000 Subject: [Qgis-psc] Grant report: Improved Wayland compatibility Message-ID: Hi PSC, In regards to the 2026 QGIS grant for "Improved Wayland compatibility" (https://github.com/qgis/QGIS-Enhancement-Proposals/pull/376), the following improvements have been made to QGIS: Broken color picking: This functionality was fixed in https://github.com/qgis/QGIS/pull/68063. I took the opportunity to do some much-needed cleanups to the color picking for all platforms, as that code was quite old and had been duplicated in a number of places over the years. All the color picking logic has been moved to a single helper class, which was designed to match the "best practice" approach for color picking on modern desktop environments, including Wayland. The new approach is more stable for all platforms (the old approach could get "stuck" in the color picking mode in certain circumstances), is faster, and also offers a more precise color sample relative to the mouse cursor. Broken mouse handling in 3D views: Fixed in https://github.com/qgis/QGIS/pull/68081. This required a new API to allow mouse cursor locks and relative pointer motion to be handled in platform-specific ways, as the Qt library itself does not provide this. On supported Wayland desktops, QGIS now uses the pointer-constraints-unstable-v1 and relative-pointer-unstable-v1 protocols to natively lock the cursor during 3D map navigation. It's a seamless transition for Linux users! Application icon: the icon shown for QGIS windows under wayland desktops would show as a pixelated icon, with color artifacts. This was fixed by https://github.com/qgis/QGIS/pull/66710, ensuring that QGIS windows show with pixel-perfect, high resolution icons. Clipboard handling: wayland environments place certain constraints on how applications are permitted to access the system clipboard. For instance, they only have access to the clipboard when their own application windows are directly focused. This broke foundational assumptions in QGIS' clipboard handling, resulting in broken pasting of features on Wayland environments. Again, this code and logic was very old and quite fragile. I took the opportunity in https://github.com/qgis/QGIS/pull/68083 to rework this to match Qt expected clipboard behavior. Not only does this fix the feature pasting under Wayland, but it also will dramatically speed up copy/paste operations within QGIS. Furthermore, the new approach allows features to be pasted into different QGIS instances losslessly, retaining their original CRS and field definitions. 3D map key handling: As reported in https://github.com/qgis/QGIS/issues/67141 and https://github.com/qgis/QGIS/issues/67140, keyboard shortcuts and navigation in 3D maps was broken under Wayland environments. This was fixed in https://github.com/qgis/QGIS/pull/68080 Popup menu handling: During testing, some issues were spotted resulting in bad placement and behavior of popup menus under Wayland. These were fixed by https://github.com/qgis/QGIS/pull/68077 and https://github.com/qgis/QGIS/pull/68060 (the later may also cause odd behavior for different platforms too) Issue with adding relations: the last Wayland related issue was https://github.com/qgis/QGIS/issues/67935, where creating features with relations would break the window handling under Wayland. This was fixed by https://github.com/qgis/QGIS/pull/68089 Crashes in docking / floating windows: these were described in the original proposal, but could no longer be reproduced when running with current Qt and KDE versions. Broken window placement: this was described in the original proposal. When running under recent Qt and KDE versions, the situation is much improved (thanks to the acceptance of the Wayland session management protocol). Ultimately, no changes were required in QGIS to support this protocol. Following this, since all the known issues with Wayland were resolved, I've removed the user-facing warning suggesting that users fallback to an X11 session. (https://github.com/qgis/QGIS/pull/68090) I've now been running QGIS under Wayland for a number of months, and with these improvements, it's back to a first-class experience. Thanks for the opportunity to improve this, and for funding this work. Nyall From nyall.dawson at gmail.com Thu Nov 12 20:34:50 2026 From: nyall.dawson at gmail.com (Nyall Dawson) Date: Fri, 13 Nov 2026 14:34:50 +1000 Subject: [Qgis-psc] Grant report: Restore the print layout HTML item for QGIS 4 Message-ID: Hi PSC, I'm happy to report that following the grant "Restore the print layout HTML item for QGIS 4" (https://github.com/qgis/QGIS-Enhancement-Proposals/pull/377), the print layout HTML item has now been resurrected for QGIS 4.4! This was a heavy undertaking, involving many different parts. The upstream removal of the QtWebkit support and replacement by the less-featured (but more modern and secure) webengine framework completely removed the API we were relying on for rendering the HTML print layout item. No direct replacement API was available for rendering webengine content in high quality, vector formats. To work around this, I've implemented a complicated approach that uses webengine's print capabilities to export vectorised HTML content to a PDF file, and then the PDF4QT library to render this into the layout HTML item. Via this approach I've been able to resurrect almost all the functionality that the item had under QGIS 3, including support for user stylesheets, and injection of atlas feature json into the HTML. Additionally, I took the opportunity to fix a long-standing performance issue relating to the HTML item. In QGIS 3, the HTML content would always be loaded and rendered immediately, in the main thread, when creating the item. This also occurred whenever a QGIS project was loaded that contained a HTML item, resulting in very slow load times for these projects! Furthermore, all the HTML rendering was always done on the GUI thread, so navigating and interacting with layouts containing HTML content was slow and would result in many QGIS pauses. Now, all the loading and rendering is done asynchronously. The HTML fetching and rendering will only happen when required (no longer at project load time!), and now happens in a background thread so that the layout designer always remains responsive to work with. That said, there remains some regressions which users should be aware of when compared with the HTML item support in QGIS 3: - The webengine backend uses its own independent networking library, which is not integrated in any way with the networking library used by the rest of QGIS. Accordingly, the HTML item will ignore the proxy, SSL, cache, user agent, authentication and other QGIS network settings. Requests won't be shown in the QGIS Network logger panel either. QGIS administrators will need to be aware of this and adjust their network's firewall settings accordingly. - While the HTML content is always rendered as high-quality vectors, text from the HTML will always be converted to paths. This looks identical, but means that text from the HTML item in PDF or SVG exported layouts won't be selectable, searchable, or editable. (It's possible that this limitation may be fixable in follow-up work) - HTML content will render slightly larger than in QGIS 3 (around 10% larger). This is a feature, not a bug! The original webkit library incorrectly sized the HTML content, as reported in https://github.com/qgis/QGIS/issues/19901. Now, the font and css sizes from the HTML content will be an exact match for font and other sizes for non-HTML layout items. Users may need to adjust their HTML or CSS to adjust for this sizing difference when loading older projects into QGIS 4. Thanks to the QGIS project and all donors for funding this work and restoring this valuable capability! (The final part of this work is currently waiting review at https://github.com/qgis/QGIS/pull/68161) Nyall From jan.caha at lutraconsulting.co.uk Fri Nov 13 01:42:05 2026 From: jan.caha at lutraconsulting.co.uk (Jan Caha) Date: Fri, 13 Nov 2026 10:42:05 +0100 Subject: [Qgis-psc] Grant Report: Get rid of QgsProject::instance() singleton in qgis_core Message-ID: Hello, I am seding a report for grant "Get rid of QgsProject::instance() singleton in qgis_core" (https://github.com/qgis/QGIS-Enhancement-Proposals/pull/380). QEP 423 aims to remove QGIS core's dependency on the QgsProject::instance() singleton, so that classes work with an explicit project instead of a global singleton project. The work started in August 2026 - src/core contained 101 calls to QgsProject::instance(). After the work 63 of them have now been dealt with. 32 calls were removed outright, and 31 now survive only inside deprecated methods or fallbacks marked for removal in QGIS 5.0. These 31 can be deleted at the next API break with no further design work. The work followed a few repeating patterns. Where a class already had access to a project, the code now uses it directly, usually through QgsMapLayer::project(), a stored project member variable, or a project-aware context such as QgsRelationContext or the expression context's layer store. Where a public API had no way to receive a project, a new constructor or method overload taking QgsProject was added. The old signature was deprecated and kept as a thin shim that passes QgsProject::instance(). Important note is that not all constructors could be directly marked as Q_DECL_DEPRECATED, as there is QT limitation that constructors that can be called without arguments (for example with all arguments having default value) cannot be deprecated. But all of those are marked with TODO for removal in QGIS 5.0. Where a layer may not belong to any project, the code tries the layer's own project first and only then falls back to the singleton. In total, 37 TODO QGIS 5.0 notes were added to mark these compatibility paths for removal. In a few places the singleton fallback was dropped completely, for example in relation aggregates, JSON export of related attributes and QgsMapLayer named properties. As a result, a layer without a project now behaves predictably instead of silently reading another project's settings. There are 37 remaining usages. 5 are part of the singleton's own code and have to stay in the codebase. 2 are commented-out code. That leaves 30 real call sites to solve. About 10 are mechanical, 7 need a new constructor that takes the project. The remaining 13 need a design decision, because their callers have no QgsProject to pass available in the class or close. PRs related to QEP 423 #66958, #66963, #66998, #67317, #67382, #67472, #67473, #67475, #67485, #67529, #67539, #67540, #67541, #67542, #67543, #67575, #67580, #67581, #67742, #67904, #67919, #67160, #67905 Jan -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco at qgis.org Fri Nov 13 08:21:35 2026 From: marco at qgis.org (Marco Bernasocchi) Date: Fri, 13 Nov 2026 17:21:35 +0100 Subject: [Qgis-psc] Blacksmith runners / macOS builds In-Reply-To: References: <285175df-4c8b-4525-b73a-2c23486b064a@qgis.org> <5a4e5a07b210d2a353011a5160056c9e@carto.net> Message-ID: Hey Matthias, We discussed in the PSC and it is ok to go forward with Tim's proposal. We will not add a link on the readme but will add a section for in-kind donnors to the sustaining members page. Please move ahead and let me know if you have any more questions. Cheers Marco Bernasocchi QGIS.org Chair OSGEO.org VP Europe OPENGIS.ch CEO http://berna.io On Wed, 11 Nov 2026, 14:03 Marco Bernasocchi, wrote: > > Yes, that was kind of the idea. > I would not do give a sustaining membership but create a new section > sustaining partners or in-kind donors like andreas suggested. > > Cheers > Marco. > > On Wed, 11 Nov 2026 at 03:32, Emma Hain via QGIS-PSC < > qgis-psc at lists.osgeo.org> wrote: > >> Would you almost introduce them as a new class of contributor? Such as an >> 'Infrastructure' contributor? >> >> On Wed, 11 Nov 2026 at 02:47, Tim Sutton via QGIS-PSC < >> qgis-psc at lists.osgeo.org> wrote: >> >>> Hi >>> >>> For me I would be -1 to introduce 'ads' into the qgis/QGIS code base - >>> we have other spaces for that and we always tried to keep QGIS code base >>> 'clean'. Why dont we just give them a sustaining membership and they get >>> all the visibility of other sustaining members? They will get better >>> exposure that way than in the readme too I think... >>> >>> I will be happy to write up something for the blog and put it on the >>> news feed etc. We should get in the habit anyway of promoting our new >>> sponsors more (unless they want to remain incognito). >>> >>> Regards >>> >>> Tim >>> >>> On Sat, Nov 7, 2026 at 3:50?PM Andreas Neumann via QGIS-PSC < >>> qgis-psc at lists.osgeo.org> wrote: >>> >>>> Hi Matthias, >>>> >>>> I am fine with listing them with their logo in our readme or elsewhere >>>> - >>>> but they shouldn't be called "sponsors" but rather "in-kind donors" - >>>> we >>>> cannot have sponsors (for tax reasons). >>>> >>>> Andreas >>>> >>>> On 2026-11-06 14:41, Marco Bernasocchi via QGIS-PSC wrote: >>>> > Hey Matthias, >>>> > Number 2 was already discussed and we see no problem with that. >>>> > >>>> > We hadn't discussed 1 but i see no issue there either. >>>> > >>>> > Any other opinions from the psc? >>>> > Cheers >>>> > >>>> > Marco Bernasocchi >>>> > >>>> > QGIS.org Chair >>>> > OSGEO.org VP Europe >>>> > OPENGIS.ch CEO >>>> > http://berna.io >>>> > >>>> > On Fri, 6 Nov 2026, 09:38 Matthias Kuhn, wrote: >>>> > >>>> >> Dear PSC, >>>> >> >>>> >> Thanks a lot for the positive feedback. I'd like to start this as >>>> >> soon >>>> >> as possible, migrate a few workflows, and then write a blog post in >>>> >> a >>>> >> couple of weeks when we have results to present. >>>> >> >>>> >> They asked if also (cited): >>>> >> >>>> >> 1. we have a sponsor logo (attached) - would you be ok with placing >>>> >> it >>>> >> in your project README and image on your website? >>>> >> 2. would you be alright with us talking about our partnership on >>>> >> socials/blogs? >>>> >> >>>> >> I quickly checked how the others integrate the logo in the readme >>>> >> (e.g. celery): https://github.com/celery/celery#sponsors >>>> >> >>>> >> Sorry for the additional request; I forgot to include this in the >>>> >> original email. >>>> >> I hope that this can be confirmed quickly. >>>> >> >>>> >> Thanks a lot >>>> >> Matthias >>>> >> >>>> >> On Thu, Nov 5, 2026 at 12:14?PM Marco Bernasocchi >>>> >> wrote: >>>> >>> >>>> >>> Hey Matthias, >>>> >>> Sorry, it took a bit longer on my side. >>>> >>> we discussed this in the PSC and agree that we should go forward. >>>> >>> As soon as we finalise the test phase and the system proves it >>>> >> works, we can write the blog post for them. >>>> >>> Thanks a lot for taking care of this. >>>> >>> >>>> >>> Cheers >>>> >>> Marco >>>> >>> >>>> >>> On Fri, 9 Oct 2026 at 09:44, R?gis Haubourg via QGIS-PSC >>>> >> wrote: >>>> >>>> >>>> >>>> Hi Matthias, thanks for pushing and testing this idea. >>>> >>>> >>>> >>>> In fact, listening at J?rgen yesterday in the conference, I >>>> >> realised that github runners are also a limiting factor for a >>>> >> OSGEO4W port to CI builds. >>>> >>>> >>>> >>>> As Blacksmith offers an open source partnership, I strongly >>>> >> support your proposal too as away to unlock our current github >>>> >> limitations fast and efficiently. >>>> >>>> >>>> >>>> As for long term plans to own a sovereign infrastructure, >>>> >> Blacksmith is a US based company, so it doesn't change this >>>> >> situation, but it would allow us to size more what kind of >>>> >> infrastructure we require. >>>> >>>> >>>> >>>> Best regards >>>> >>>> R?gis >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC >>>> >> wrote: >>>> >>>>> Hello Matthias, >>>> >>>>> >>>> >>>>> This looks a very good idea to me. >>>> >>>>> >>>> >>>>> Thank you for exploring this opportunity! >>>> >>>>> >>>> >>>>> >>>> >>>>> --- >>>> >>>>> Alessandro Pasotti >>>> >>>>> QCooperative: www.qcooperative.net [1] >>>> >> >>>> >>>>> ItOpen: www.itopen.it [2] >>>> >>>>> >>>> >>>>> Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC >>> >>>>> psc at lists.osgeo.org > ha >>>> >> scritto: >>>> >>>>> >>>> >>>>> Hi Martin, >>>> >>>>> >>>> >>>>> Yes, running tests sounds reasonable too. >>>> >>>>> So far the build itself was taking too long and I didn't >>>> >> want to >>>> >>>>> increase this even more. >>>> >>>>> >>>> >>>>> Matthias >>>> >>>>> >>>> >>>>> On Thu, Oct 8, 2026, 22:45 Martin Dobias >>>> >> >>> >>>>> > wrote: >>>> >>>>> >>>> >>>>> Hi Matthias >>>> >>>>> >>>> >>>>> That all sounds good to me. And maybe we could also >>>> >> start to run >>>> >>>>> auto tests for mac plarform in CI? It seems quite a few >>>> >> are >>>> >>>>> broken on macOS, but we don't really know about that >>>> >> :-) >>>> >>>>> >>>> >>>>> Cheers >>>> >>>>> Martin >>>> >>>>> >>>> >>>>> >>>> >>>>> On Thu, Oct 8, 2026 at 1:59?PM Matthias Kuhn via >>>> >> QGIS-PSC >>> >>>>> psc at lists.osgeo.org > >>>> >> wrote: >>>> >>>>> >>>> >>>>> Dear PSC, >>>> >>>>> >>>> >>>>> We are currently producing macOS builds entirely >>>> >> within our >>>> >>>>> CI/CD pipelines (github workflows/actions). With >>>> >> this >>>> >>>>> approach, we can create dmg installer packages for >>>> >> currently >>>> >>>>> supported QGIS 3 and QGIS 4 versions for releases, >>>> >> pull >>>> >>>>> requests, and branch (latest) builds. >>>> >>>>> >>>> >>>>> For QGIS 4, one important component is currently >>>> >> missing: we >>>> >>>>> cannot build QtWebEngine (HTML rendering) because >>>> >> building >>>> >>>>> it takes over six hours (the maximum threshold for >>>> >>>>> workflows) on the (free-tier) github runners. This >>>> >>>>> limitation is significant, and several tickets >>>> >> request its >>>> >>>>> addition (for QGIS itself and for plugins like >>>> >> dataplotly). >>>> >>>>> We only need to rebuild this component when there's >>>> >> an >>>> >>>>> update, so it won't add time to every pipeline >>>> >> build. >>>> >>>>> However, we must ensure it builds once every few >>>> >> days. >>>> >>>>> >>>> >>>>> I recently was in touch with blacksmith >>> >>>>> www.blacksmith.sh/ [3]> which is an independent >>>> >> provider of >>>> >>>>> runners for github actions. They have very >>>> >> performant >>>> >>>>> runners, I was able to build QtWebEngine in less >>>> >> than 1.5 >>>> >>>>> hours (compared to more than 6 hours on github). >>>> >> They would >>>> >>>>> allow us to use their infrastructure as part of >>>> >> their open- >>>> >>>>> source engagement and ask for a blog post in >>>> >> return. >>>> >>>>> >>>> >>>>> Blacksmith would also help us reduce CI time for >>>> >> other >>>> >>>>> workflows either by moving some workflows over to >>>> >> blacksmith >>>> >>>>> or by reducing the load on github actions cache. >>>> >> This would >>>> >>>>> significantly improve the developer experience. >>>> >>>>> >>>> >>>>> One remaining challenge will be providing mac >>>> >> packages for >>>> >>>>> Intel devices. Blacksmith does not offer this >>>> >> platform. >>>> >>>>> Apple stopped selling Intel macOS devices in >>>> >> mid-2023. Apple >>>> >>>>> will officially support Intel devices until 2028, >>>> >> after >>>> >>>>> which support will be reduced, ending entirely in >>>> >> 2030. >>>> >>>>> Offering QGIS 4 support for Intel devices would be >>>> >> nice, but >>>> >>>>> we would need to find another interim solution for >>>> >> the next >>>> >>>>> 2-4 years. >>>> >>>>> >>>> >>>>> I'd like to propose that we create an account with >>>> >>>>> blacksmith, install its github app and move the >>>> >> macOS arm64 >>>> >>>>> workflow and potentially a few others over to >>>> >> blacksmith. If >>>> >>>>> this goes well and improves the situation, I'd like >>>> >> to write >>>> >>>>> a blog post about our experiences as part of this >>>> >> agreement. >>>> >>>>> This will improve the situation for macOS packages >>>> >> for arm64 >>>> >>>>> (i.e. for all mac devices sold in the last 3 years >>>> >> and more >>>> >>>>> sold since 2020). For Intel, we would continue to >>>> >> build >>>> >>>>> packages but without QtWebEngine until we find a >>>> >> suitable >>>> >>>>> solution. >>>> >>>>> >>>> >>>>> Thanks a lot and best regards >>>> >>>>> Matthias >>>> >>>>> >>>> >>>>> -- >>>> >>>>> >>>> >>>>> >>>> >>>>> *Matthias Kuhn* - Mr. Noproblemo >>>> >>>>> >>>> >>>>> CTO | Co-Founder >>>> >>>>> >>>> >>>>> email >>>> >>>>> matthias at opengis.ch >>>> >>>>> www >>>> >>>>> opengis.ch [4] >>>> >>>>> >>>> >>>>> linkedin >>>> >> >>>> >>>>> mastodon >>>> >> github >>> >>>>> github.com/opengisch/ [5]> >>>> >>>>> >>>> >>>>> _______________________________________________ >>>> >>>>> QGIS-PSC mailing list >>>> >>>>> QGIS-PSC at lists.osgeo.org >>>> >> >>>> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>>> >> >>> >>>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> >>>> >>>>> >>>> >>>>> _______________________________________________ >>>> >>>>> QGIS-PSC mailing list >>>> >>>>> QGIS-PSC at lists.osgeo.org >>>> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> >>>>> lists.osgeo.org/mailman/listinfo/qgis-psc [6]> >>>> >>>>> >>>> >>>>> >>>> >>>>> _______________________________________________ >>>> >>>>> QGIS-PSC mailing list >>>> >>>>> QGIS-PSC at lists.osgeo.org >>>> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>>> >>>>> >>>> >>>> _______________________________________________ >>>> >>>> QGIS-PSC mailing list >>>> >>>> QGIS-PSC at lists.osgeo.org >>>> >>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>>> >>> >>>> >>> >>>> >>> >>>> >>> -- >>>> >>> Marco Bernasocchi >>>> >>> >>>> >>> QGIS.org Chair >>>> >>> OSGEO.org VP Europe >>>> >>> OPENGIS.ch CEO >>>> >>> http://berna.io >>>> > >>>> > >>>> > Links: >>>> > ------ >>>> > [1] http://www.qcooperative.net >>>> > [2] http://www.itopen.it >>>> > [3] http://www.blacksmith.sh/ >>>> > [4] http://opengis.ch >>>> > [5] http://github.com/opengisch/ >>>> > [6] http://lists.osgeo.org/mailman/listinfo/qgis-psc >>>> > _______________________________________________ >>>> > QGIS-PSC mailing list >>>> > QGIS-PSC at lists.osgeo.org >>>> > https://lists.osgeo.org/mailman/listinfo/qgis-psc >>>> _______________________________________________ >>>> QGIS-PSC mailing list >>>> QGIS-PSC at lists.osgeo.org >>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>>> >>> >>> >>> -- >>> >>> >>> >>> *Tim Sutton* >>> QGIS Project Steering Committee >>> tim at qgis.org >>> _______________________________________________ >>> QGIS-PSC mailing list >>> QGIS-PSC at lists.osgeo.org >>> https://lists.osgeo.org/mailman/listinfo/qgis-psc >>> >> _______________________________________________ >> QGIS-PSC mailing list >> QGIS-PSC at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> > > > -- > Marco Bernasocchi > > QGIS.org Chair > OSGEO.org VP Europe > OPENGIS.ch CEO > http://berna.io > -------------- next part -------------- An HTML attachment was scrubbed... URL: From regis at qgis.org Fri Nov 13 09:10:11 2026 From: regis at qgis.org (=?UTF-8?Q?R=C3=A9gis_Haubourg?=) Date: Fri, 13 Nov 2026 18:10:11 +0100 Subject: [Qgis-psc] Grant report: Restore the print layout HTML item for QGIS 4 In-Reply-To: References: Message-ID: <1a518c93-0cd9-4941-9c94-41112994887c@qgis.org> Hi Nyall, well done ! I'm really happy this blocker is workaround for QGIS 4. This seems to have been a giant task. We will have to document clearly the QGIS's network bypassing for corporate users that really care about this. Is there a way to change user agent and proxy settings for the webengine ? Best regards, R?gis Haubourg Elected member at the Program Steering Comitee of QGIS.org. - On 13/11/2026 05:34, Nyall Dawson via QGIS-PSC wrote: > Hi PSC, > > I'm happy to report that following the grant "Restore the print layout > HTML item for QGIS 4" > (https://github.com/qgis/QGIS-Enhancement-Proposals/pull/377), the > print layout HTML item has now been resurrected for QGIS 4.4! > > This was a heavy undertaking, involving many different parts. The > upstream removal of the QtWebkit support and replacement by the > less-featured (but more modern and secure) webengine framework > completely removed the API we were relying on for rendering the HTML > print layout item. > > No direct replacement API was available for rendering webengine > content in high quality, vector formats. To work around this, I've > implemented a complicated approach that uses webengine's print > capabilities to export vectorised HTML content to a PDF file, and then > the PDF4QT library to render this into the layout HTML item. > > Via this approach I've been able to resurrect almost all the > functionality that the item had under QGIS 3, including support for > user stylesheets, and injection of atlas feature json into the HTML. > > Additionally, I took the opportunity to fix a long-standing > performance issue relating to the HTML item. In QGIS 3, the HTML > content would always be loaded and rendered immediately, in the main > thread, when creating the item. This also occurred whenever a QGIS > project was loaded that contained a HTML item, resulting in very slow > load times for these projects! Furthermore, all the HTML rendering was > always done on the GUI thread, so navigating and interacting with > layouts containing HTML content was slow and would result in many QGIS > pauses. > > Now, all the loading and rendering is done asynchronously. The HTML > fetching and rendering will only happen when required (no longer at > project load time!), and now happens in a background thread so that > the layout designer always remains responsive to work with. > > That said, there remains some regressions which users should be aware > of when compared with the HTML item support in QGIS 3: > > - The webengine backend uses its own independent networking library, > which is not integrated in any way with the networking library used by > the rest of QGIS. Accordingly, the HTML item will ignore the proxy, > SSL, cache, user agent, authentication and other QGIS network > settings. Requests won't be shown in the QGIS Network logger panel > either. QGIS administrators will need to be aware of this and adjust > their network's firewall settings accordingly. > - While the HTML content is always rendered as high-quality vectors, > text from the HTML will always be converted to paths. This looks > identical, but means that text from the HTML item in PDF or SVG > exported layouts won't be selectable, searchable, or editable. (It's > possible that this limitation may be fixable in follow-up work) > - HTML content will render slightly larger than in QGIS 3 (around 10% > larger). This is a feature, not a bug! The original webkit library > incorrectly sized the HTML content, as reported in > https://github.com/qgis/QGIS/issues/19901. Now, the font and css sizes > from the HTML content will be an exact match for font and other sizes > for non-HTML layout items. Users may need to adjust their HTML or CSS > to adjust for this sizing difference when loading older projects into > QGIS 4. > > Thanks to the QGIS project and all donors for funding this work and > restoring this valuable capability! > > (The final part of this work is currently waiting review at > https://github.com/qgis/QGIS/pull/68161) > > Nyall > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc ????-- INSERT --????87,0-1 Bot -------------- next part -------------- An HTML attachment was scrubbed... URL: From dvdkon at konarici.cz Sat Nov 14 13:41:13 2026 From: dvdkon at konarici.cz (David =?UTF-8?Q?Ko=C5=88a=C5=99=C3=ADk?=) Date: Sat, 14 Nov 2026 22:41:13 +0100 Subject: [Qgis-psc] QEP 422 - Async refactoring grant report Message-ID: <8e10ef94daca98793fac59d1603b0857cffe3e6e.camel@konarici.cz> Hi all, with PR #67115 merged into QGIS, my work on the async refactoring grant has finished. I reworked QgsChunkLoaders and adjacent classes, simplifying the code and removing some 750 lines in the process. The main part of my work was merging QgsChunkLoader with QgsChunkLoader factory and refactoring all the async methods to return QFutures using the new Qt6 continuation methods instead of bespoke objects, integer handles or void. Most of this was mechanical work, adapting the various QgsChunkLoaderFactory subclasses. Common logic for terrain generators and terrain textures was moved into a loader base class and the DEM/Online terrain loaders deduplicated. I also had to adapt the code using these classes, mostly in QgsChunkedEntity, where I also took the opportunity to refactor its job system. Since Qt6-style QFutures weren't widely used in QGIS, I also added some basic helper methods in the QgsFutureUtils class. After merging, two extra issues were found (one with compilation on older Qt versions and one lifetime issue); I fixed them both in follow- up PRs (#68029 and #68014). David Ko?a??k From tim at qgis.org Sun Nov 15 12:08:16 2026 From: tim at qgis.org (Tim Sutton) Date: Sun, 15 Nov 2026 20:08:16 +0000 Subject: [Qgis-psc] Grant report: Restore the print layout HTML item for QGIS 4 In-Reply-To: References: Message-ID: Amazing work, thank you so much Nyall! Regards Tim On Fri, Nov 13, 2026 at 4:35?AM Nyall Dawson via QGIS-PSC < qgis-psc at lists.osgeo.org> wrote: > Hi PSC, > > I'm happy to report that following the grant "Restore the print layout > HTML item for QGIS 4" > (https://github.com/qgis/QGIS-Enhancement-Proposals/pull/377), the > print layout HTML item has now been resurrected for QGIS 4.4! > > This was a heavy undertaking, involving many different parts. The > upstream removal of the QtWebkit support and replacement by the > less-featured (but more modern and secure) webengine framework > completely removed the API we were relying on for rendering the HTML > print layout item. > > No direct replacement API was available for rendering webengine > content in high quality, vector formats. To work around this, I've > implemented a complicated approach that uses webengine's print > capabilities to export vectorised HTML content to a PDF file, and then > the PDF4QT library to render this into the layout HTML item. > > Via this approach I've been able to resurrect almost all the > functionality that the item had under QGIS 3, including support for > user stylesheets, and injection of atlas feature json into the HTML. > > Additionally, I took the opportunity to fix a long-standing > performance issue relating to the HTML item. In QGIS 3, the HTML > content would always be loaded and rendered immediately, in the main > thread, when creating the item. This also occurred whenever a QGIS > project was loaded that contained a HTML item, resulting in very slow > load times for these projects! Furthermore, all the HTML rendering was > always done on the GUI thread, so navigating and interacting with > layouts containing HTML content was slow and would result in many QGIS > pauses. > > Now, all the loading and rendering is done asynchronously. The HTML > fetching and rendering will only happen when required (no longer at > project load time!), and now happens in a background thread so that > the layout designer always remains responsive to work with. > > That said, there remains some regressions which users should be aware > of when compared with the HTML item support in QGIS 3: > > - The webengine backend uses its own independent networking library, > which is not integrated in any way with the networking library used by > the rest of QGIS. Accordingly, the HTML item will ignore the proxy, > SSL, cache, user agent, authentication and other QGIS network > settings. Requests won't be shown in the QGIS Network logger panel > either. QGIS administrators will need to be aware of this and adjust > their network's firewall settings accordingly. > - While the HTML content is always rendered as high-quality vectors, > text from the HTML will always be converted to paths. This looks > identical, but means that text from the HTML item in PDF or SVG > exported layouts won't be selectable, searchable, or editable. (It's > possible that this limitation may be fixable in follow-up work) > - HTML content will render slightly larger than in QGIS 3 (around 10% > larger). This is a feature, not a bug! The original webkit library > incorrectly sized the HTML content, as reported in > https://github.com/qgis/QGIS/issues/19901. Now, the font and css sizes > from the HTML content will be an exact match for font and other sizes > for non-HTML layout items. Users may need to adjust their HTML or CSS > to adjust for this sizing difference when loading older projects into > QGIS 4. > > Thanks to the QGIS project and all donors for funding this work and > restoring this valuable capability! > > (The final part of this work is currently waiting review at > https://github.com/qgis/QGIS/pull/68161) > > Nyall > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc > -- *Tim Sutton* QGIS Project Steering Committee tim at qgis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From viperminiq at gmail.com Mon Nov 16 00:10:25 2026 From: viperminiq at gmail.com (=?UTF-8?Q?Dominik_Cindri=C4=87?=) Date: Mon, 16 Nov 2026 09:10:25 +0100 Subject: [Qgis-psc] QEP 424: Move away from geometry shaders in QGIS 3D grant report Message-ID: Hi all, this is a report for the 2026 grant program for QEP 424: Move away from geometry shaders in QGIS 3D ( https://github.com/qgis/QGIS-Enhancement-Proposals/pull/381) Aim of the QEP was to remove all geometry shaders from QGIS, so that QGIS doesn't rely on a stage many modern graphics APIs do not support. This was accomplished by a combination of instanced rendering and moving the existing work geometry shaders did to CPU (to prepare a geometry/quad) and vertex shaders. The following work was done: - removal of the billboards geometry shader ( https://github.com/qgis/QGIS/pull/66837) Billboards are now instanced, attributes are specified for each instance. Behavior is the same as with the geometry shader. - removal of the mesh geometry shader ( https://github.com/qgis/QGIS/pull/66938) Displaying mesh layers in 3D is possible with wireframe on or off. When it is on, vertices are not deduplicated, so that we can do the maths necessarry for each vertex (barycentric coordinates). This wastes a bit more GPU memory, but the behavior stays the same as with the geometry shader and this is what most other solutions also implement. When wireframe is off, vertices are indexed (deduplicated). Shading normals are calculated in the fragment shader now. - removal of the lines geometry shader ( https://github.com/qgis/QGIS/pull/67356) Lines are now instanced. This is done in two passes: one for drawing of the segments, the other for drawing of joins. Near-plane clipping is handled in the vertex shader. There is no overlap between the segments and the joins. Currently, we do not have an option to specify transparency to the lines, but if we did, it would work out of the box with the current implementation. - code cleanups (https://github.com/qgis/QGIS/pull/68075) Dead code was removed after all the geometry shaders were removed. The task was fully accomplished, no geometry shaders are present in the QGIS codebase. Thank you! - Dominik Cindri? -------------- next part -------------- An HTML attachment was scrubbed... URL: From julien.cabieces at oslandia.com Mon Nov 16 00:35:14 2026 From: julien.cabieces at oslandia.com (Julien Cabieces) Date: Mon, 16 Nov 2026 09:35:14 +0100 Subject: [Qgis-psc] QEP 417 grant report : Replace SIP_FACTORY with std::unique_ptr Message-ID: <874idhw4vx.fsf@julienlaptop.home> Hi PSC, Unfortunately, the work to replace SIP_FACTORY with std::unique_ptr [0] is still on going. There are already 23 merged Pull requests [1] and I plan to continue working on this in the next months. This work is done semi automatically. A clang program find and replace the SIP_FACTORY candidates and a python script help me in fixing resulting compilation errors. Remaining errors need to be fixed manually. Then, all the modifications are carefully reviewed. I choose to split this work in several, not too big, pull requests in order to ease the review. Thank you Nyall who has taking care all the review by now. At the moment, I'm replacing all methods which return non-QObject methods and will continue, when possible, with method which return QObject methods. As discussed in the QEP, virtual methods will stay untouched because of an issue with our current SIP version. Thank you for funding this work. Regards, Julien [0] https://github.com/qgis/QGIS-Enhancement-Proposals/blob/master/qep-417-remove-sip-factory.md [1] https://github.com/qgis/QGIS/pulls?q=is%3Apr+state%3Aclosed+%22QEP+%23417%22 -- Julien Cabieces Senior Developer at Oslandia julien.cabieces at oslandia.com From nyall.dawson at gmail.com Mon Nov 16 20:47:41 2026 From: nyall.dawson at gmail.com (Nyall Dawson) Date: Tue, 17 Nov 2026 14:47:41 +1000 Subject: [Qgis-psc] Grant report: Restore the print layout HTML item for QGIS 4 In-Reply-To: <1a518c93-0cd9-4941-9c94-41112994887c@qgis.org> References: <1a518c93-0cd9-4941-9c94-41112994887c@qgis.org> Message-ID: On Sat, 14 Nov 2026 at 03:10, R?gis Haubourg via QGIS-PSC wrote: > > Hi Nyall, well done ! > > I'm really happy this blocker is workaround for QGIS 4. > > This seems to have been a giant task. > > We will have to document clearly the QGIS's network bypassing for corporate users that really care about this. > Is there a way to change user agent and proxy settings for the webengine ? I've done the user agent in https://github.com/qgis/QGIS/pull/68221 , now it'll inherit QGIS' standard user agent. For proxies, it turns out that qt does reuse SOME of the proxy settings automatically. (What won't work is authenticated proxies) Nyall > > Best regards, > > R?gis Haubourg > Elected member at the Program Steering Comitee of QGIS.org. > - > > On 13/11/2026 05:34, Nyall Dawson via QGIS-PSC wrote: > > Hi PSC, > > I'm happy to report that following the grant "Restore the print layout > HTML item for QGIS 4" > (https://github.com/qgis/QGIS-Enhancement-Proposals/pull/377), the > print layout HTML item has now been resurrected for QGIS 4.4! > > This was a heavy undertaking, involving many different parts. The > upstream removal of the QtWebkit support and replacement by the > less-featured (but more modern and secure) webengine framework > completely removed the API we were relying on for rendering the HTML > print layout item. > > No direct replacement API was available for rendering webengine > content in high quality, vector formats. To work around this, I've > implemented a complicated approach that uses webengine's print > capabilities to export vectorised HTML content to a PDF file, and then > the PDF4QT library to render this into the layout HTML item. > > Via this approach I've been able to resurrect almost all the > functionality that the item had under QGIS 3, including support for > user stylesheets, and injection of atlas feature json into the HTML. > > Additionally, I took the opportunity to fix a long-standing > performance issue relating to the HTML item. In QGIS 3, the HTML > content would always be loaded and rendered immediately, in the main > thread, when creating the item. This also occurred whenever a QGIS > project was loaded that contained a HTML item, resulting in very slow > load times for these projects! Furthermore, all the HTML rendering was > always done on the GUI thread, so navigating and interacting with > layouts containing HTML content was slow and would result in many QGIS > pauses. > > Now, all the loading and rendering is done asynchronously. The HTML > fetching and rendering will only happen when required (no longer at > project load time!), and now happens in a background thread so that > the layout designer always remains responsive to work with. > > That said, there remains some regressions which users should be aware > of when compared with the HTML item support in QGIS 3: > > - The webengine backend uses its own independent networking library, > which is not integrated in any way with the networking library used by > the rest of QGIS. Accordingly, the HTML item will ignore the proxy, > SSL, cache, user agent, authentication and other QGIS network > settings. Requests won't be shown in the QGIS Network logger panel > either. QGIS administrators will need to be aware of this and adjust > their network's firewall settings accordingly. > - While the HTML content is always rendered as high-quality vectors, > text from the HTML will always be converted to paths. This looks > identical, but means that text from the HTML item in PDF or SVG > exported layouts won't be selectable, searchable, or editable. (It's > possible that this limitation may be fixable in follow-up work) > - HTML content will render slightly larger than in QGIS 3 (around 10% > larger). This is a feature, not a bug! The original webkit library > incorrectly sized the HTML content, as reported in > https://github.com/qgis/QGIS/issues/19901. Now, the font and css sizes > from the HTML content will be an exact match for font and other sizes > for non-HTML layout items. Users may need to adjust their HTML or CSS > to adjust for this sizing difference when loading older projects into > QGIS 4. > > Thanks to the QGIS project and all donors for funding this work and > restoring this valuable capability! > > (The final part of this work is currently waiting review at > https://github.com/qgis/QGIS/pull/68161) > > Nyall > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc > > ????-- INSERT --????87,0-1 Bot > _______________________________________________ > QGIS-PSC mailing list > QGIS-PSC at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-psc From administration at qgis.org Tue Nov 17 02:05:43 2026 From: administration at qgis.org (Marco Serusi) Date: Tue, 17 Nov 2026 11:05:43 +0100 Subject: [Qgis-psc] FW: QGIS Software Request In-Reply-To: References: <58181262-c7bd-44ba-8691-1bc0c40b4a9c.931bbf1d-f805-4e72-bbe8-fa4cbeec89e2.11478f89-b51f-49ea-8bfd-0189e9e2fd00@emailsignatures365.codetwo.com> Message-ID: Dear Mohamed, As I'm sure you know, QGIS is open-source software created and run by volunteers. This means that QGIS is freely available for anyone to use, but it also means we do not have the resources to fill in forms and provide customer service in the way a for-profit company does. However, as an open-source project, all our information, code, and anything else you might need to know are public and easily searchable online. To help with cases like yours, the community has put together various resources, a good place to start is the Security FAQs If you would like to help us make QGIS better, you can support us by donating here . If you need professional support, this list of contributing companies is a good resource. Kind regards On Tue, Nov 17, 2026 at 4:15?AM Mohamed Abousaleh < mabousaleh.con at ruaalharam.com> wrote: > Restricted - Internal > > Gents, please support to answer to all attached questions, Thank you. > > > > Restricted - Internal > > *From:* Aseel Alqarafi > *Sent:* Saturday, November 14, 2026 10:33 PM > *To:* Mohamed Abousaleh > *Subject:* QGIS Software Request > > > > Restricted - Internal > > > > Dear Mohamed, > > > > As discussed during our meeting, please find the QGIS Security > Questionnaire to be completed. > > > > Kindly coordinate with the Application Support team to complete the > attached questionnaire and share the responses with us so we can proceed > with the cybersecurity assessment. > > > > Thank you for your cooperation. > > > > Best regards, > > Aseel > > > -- *Marco Serusi* *Administrative Assistant - QGIS* -------------- next part -------------- An HTML attachment was scrubbed... URL: From regis at qgis.org Tue Nov 17 02:21:31 2026 From: regis at qgis.org (=?UTF-8?Q?R=C3=A9gis_Haubourg?=) Date: Tue, 17 Nov 2026 11:21:31 +0100 Subject: [Qgis-psc] Grant report: Restore the print layout HTML item for QGIS 4 In-Reply-To: References: <1a518c93-0cd9-4941-9c94-41112994887c@qgis.org> Message-ID: Thanks Nyall ! Best regards, R?gis Haubourg Elected member at the Program Steering Comitee of QGIS.org. - On 17/11/2026 05:47, Nyall Dawson wrote: > On Sat, 14 Nov 2026 at 03:10, R?gis Haubourg via QGIS-PSC > wrote: >> Hi Nyall, well done ! >> >> I'm really happy this blocker is workaround for QGIS 4. >> >> This seems to have been a giant task. >> >> We will have to document clearly the QGIS's network bypassing for corporate users that really care about this. >> Is there a way to change user agent and proxy settings for the webengine ? > I've done the user agent inhttps://github.com/qgis/QGIS/pull/68221 , > now it'll inherit QGIS' standard user agent. > > For proxies, it turns out that qt does reuse SOME of the proxy > settings automatically. (What won't work is authenticated proxies) > > Nyall > > > >> Best regards, >> >> R?gis Haubourg >> Elected member at the Program Steering Comitee of QGIS.org. >> - >> >> On 13/11/2026 05:34, Nyall Dawson via QGIS-PSC wrote: >> >> Hi PSC, >> >> I'm happy to report that following the grant "Restore the print layout >> HTML item for QGIS 4" >> (https://github.com/qgis/QGIS-Enhancement-Proposals/pull/377), the >> print layout HTML item has now been resurrected for QGIS 4.4! >> >> This was a heavy undertaking, involving many different parts. The >> upstream removal of the QtWebkit support and replacement by the >> less-featured (but more modern and secure) webengine framework >> completely removed the API we were relying on for rendering the HTML >> print layout item. >> >> No direct replacement API was available for rendering webengine >> content in high quality, vector formats. To work around this, I've >> implemented a complicated approach that uses webengine's print >> capabilities to export vectorised HTML content to a PDF file, and then >> the PDF4QT library to render this into the layout HTML item. >> >> Via this approach I've been able to resurrect almost all the >> functionality that the item had under QGIS 3, including support for >> user stylesheets, and injection of atlas feature json into the HTML. >> >> Additionally, I took the opportunity to fix a long-standing >> performance issue relating to the HTML item. In QGIS 3, the HTML >> content would always be loaded and rendered immediately, in the main >> thread, when creating the item. This also occurred whenever a QGIS >> project was loaded that contained a HTML item, resulting in very slow >> load times for these projects! Furthermore, all the HTML rendering was >> always done on the GUI thread, so navigating and interacting with >> layouts containing HTML content was slow and would result in many QGIS >> pauses. >> >> Now, all the loading and rendering is done asynchronously. The HTML >> fetching and rendering will only happen when required (no longer at >> project load time!), and now happens in a background thread so that >> the layout designer always remains responsive to work with. >> >> That said, there remains some regressions which users should be aware >> of when compared with the HTML item support in QGIS 3: >> >> - The webengine backend uses its own independent networking library, >> which is not integrated in any way with the networking library used by >> the rest of QGIS. Accordingly, the HTML item will ignore the proxy, >> SSL, cache, user agent, authentication and other QGIS network >> settings. Requests won't be shown in the QGIS Network logger panel >> either. QGIS administrators will need to be aware of this and adjust >> their network's firewall settings accordingly. >> - While the HTML content is always rendered as high-quality vectors, >> text from the HTML will always be converted to paths. This looks >> identical, but means that text from the HTML item in PDF or SVG >> exported layouts won't be selectable, searchable, or editable. (It's >> possible that this limitation may be fixable in follow-up work) >> - HTML content will render slightly larger than in QGIS 3 (around 10% >> larger). This is a feature, not a bug! The original webkit library >> incorrectly sized the HTML content, as reported in >> https://github.com/qgis/QGIS/issues/19901. Now, the font and css sizes >> from the HTML content will be an exact match for font and other sizes >> for non-HTML layout items. Users may need to adjust their HTML or CSS >> to adjust for this sizing difference when loading older projects into >> QGIS 4. >> >> Thanks to the QGIS project and all donors for funding this work and >> restoring this valuable capability! >> >> (The final part of this work is currently waiting review at >> https://github.com/qgis/QGIS/pull/68161) >> >> Nyall >> _______________________________________________ >> QGIS-PSC mailing list >> QGIS-PSC at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/qgis-psc >> >> ????-- INSERT --????87,0-1 Bot >> _______________________________________________ >> QGIS-PSC mailing list >> QGIS-PSC at lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/qgis-psc ????-- INSERT --????116,0-1 Bot -------------- next part -------------- An HTML attachment was scrubbed... URL: