From tim at kartoza.com Sun Nov 1 01:59:10 2026 From: tim at kartoza.com (Tim Sutton) Date: Sun, 1 Nov 2026 09:59:10 +0000 Subject: [QGIS-Developer] Spam plugin - FortyGuard-Tech In-Reply-To: References: <6f6d25bc-0364-40dc-9c48-87af977e47ff@app.fastmail.com> <6a5235f2-6428-4775-9f66-7a38d7fc497b@qgis.org> Message-ID: Hi Alexei, Nyall and friends I have delisted the plugin and disabled their account, cc'd Admire so we dont relist them under another name. I would not bother hard blocking urls and chasing them for penalties - that sounds like a high effort, low reward activity... In case you have not already seen it, please comment on https://github.com/qgis/QGIS-Enhancement-Proposals/pull/390 where we propose a major overhaul of how we make plugins available. Regards Tim On Sun, Nov 1, 2026 at 12:05?AM Nyall Dawson via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > On Sun, 1 Nov 2026 at 08:03, R?gis Haubourg via QGIS-Developer > wrote: > > > > Yes, I did too. Clearly unsolicited and not respecting GDPR. > > We'll contact them on behalf of the PSC and revoking is indeed an option. > > This is so clearly over-the-line that I'd suggest an appropriate > response would be : > > - They are permanently blocked from submission of any plugins to QGIS, > and a hard block placed on accessing their URLs in > QgsNetworkAccessManager (to render their services completely unusable > from QGIS) > or > - They pay a penalty and must sign up to become a gold/silver project > sponsor for xx years. > > Nyall > > > > > > > Best regards, > > > > R?gis Haubourg > > Elected member at the Program Steering Comitee of QGIS.org. > > - > > > > On 31/10/2026 20:08, Alexei Schwab via QGIS-Developer wrote: > > > > Have others also received spam from this plugin? I got unsolicited email > advertising it to an email address only used as the contact for a Qgis > plugin. > > > > https://github.com/FortyGuard-Tech/qgis-fortyguard-heatmap > > > > If this is widespread can admins remove them from the repository to > discourage this behaviour? > > > > Alexei > > > > _______________________________________________ > > 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-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-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 > -- Tim Sutton *Kartoza Cofounder*Tim is a member of the QGIS Project Steering Committee *E *: tim at kartoza.com *W* : kartoza.com *This email and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you * *have received this email in error, please notify the sender immediately and delete it from your system. Unauthorised use, disclosure, or copying* *of the contents is prohibited.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From lova at kartoza.com Sun Nov 1 22:58:27 2026 From: lova at kartoza.com (Lova Andriarimalala) Date: Mon, 2 Nov 2026 09:58:27 +0300 Subject: [QGIS-Developer] QGIS Full Stack Developer Report for October 2026 Message-ID: Hello everyone, Please find some highlights regarding the development and maintenance of the QGIS Websites for the past month, from October 1st to October 31st, 2026. *QGIS Enhancement Proposals:* - QEP 431: Overhaul the QGIS plugin ecosystem https://github.com/qgis/QGIS-Enhancement-Proposals/pull/390 [New PR] *QGIS Infrastructure:* - The QGIS Blog has moved from WordPress to a Hugo website, in line with the other QGIS websites. - The QGIS Feed was upgraded to Django 5.2 LTS and now has a Nix flake-based environment in review, as a step toward moving it to the new NixOS infrastructure with QGIS SSO sign-in. - The QGIS Austria user group website is now online at https://austria.qgis.org and https://at.qgis.org . *QGIS.org:* - User group list improvements https://github.com/qgis/QGIS-Website/pull/1119 [Merged] - Hide donors listed in the EXCLUDED_DONORS Actions variable https://github.com/qgis/QGIS-Website/pull/1121 [Merged] - Remove 'Asociaci?n QGIS M?xico' from groups.json https://github.com/qgis/QGIS-Website/pull/1133 [Merged] - Clearer docs for user group add or update https://github.com/qgis/QGIS-Website/pull/1135 [Merged] *QGIS Plugins:* - Remove the rating feature https://github.com/qgis/QGIS-Plugins-Website/pull/445 [Merged] - Further security enhacement https://github.com/qgis/QGIS-Plugins-Website/pull/478 [Merged] - Add search input on small screen https://github.com/qgis/QGIS-Plugins-Website/pull/480 [Merged] - Prevent token expiration when rotating secret https://github.com/qgis/QGIS-Plugins-Website/pull/484 [Merged] *QGIS Hub:* - Improve review workflow https://github.com/qgis/QGIS-Hub-Website/pull/144 [Merged] - Add support for glb file and refactor 3D viewer https://github.com/qgis/QGIS-Hub-Website/pull/145 [New PR] *QGIS Feed:* - Fix author cannot edit own draft https://github.com/qgis/QGIS-Feed-Website/pull/196 [Merged] - Upgrade to Django 5.2 LTS, Python 3.12 and Node 22 https://github.com/qgis/QGIS-Feed-Website/pull/202 [Merged] - Add a nix flake-based environment https://github.com/qgis/QGIS-Feed-Website/pull/203 [New PR] *QGIS Certification:* - Remove "Sign Up" button from various templates https://github.com/qgis/QGIS-Certification-Website/pull/120 [Merged] *QGIS Sustaining Members:* - Email sending feature for sustaining members https://github.com/qgis/QGIS-Members-Website/pull/30 [Merged] *QGIS Blog:* - Transform all wordpress layout and styles to bulma https://github.com/qgis/QGIS-Blog-Website/pull/22 [Merged] - docs: document how to add or edit an author https://github.com/qgis/QGIS-Blog-Website/pull/24 [Merged] - fix: set explicit slugs on posts with a slash in the title https://github.com/qgis/QGIS-Blog-Website/pull/25 [Merged] - feat: show the full category name on hover https://github.com/qgis/QGIS-Blog-Website/pull/26 [Merged] - feat: keep post images next to the post as page bundles https://github.com/qgis/QGIS-Blog-Website/pull/27 [Merged] - chore: drop the QGIS prefix from category names https://github.com/qgis/QGIS-Blog-Website/pull/28 [Merged] - feat: remove the author filter from the sidebar https://github.com/qgis/QGIS-Blog-Website/pull/29 [Merged] *QGIS User Groups:* - Revise README for installation and customization steps https://github.com/qgis/QGIS-User-Group-Website/pull/26 [Merged] Best regards, Lova Andriarimalala *QGIS Full Stack Developer * *T *: +27(0) 87 809 2702 <+27%2087%20809%202702> *E *: lova at kartoza.com *W* : kartoza.com *This email and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you * *have received this email in error, please notify the sender immediately and delete it from your system. Unauthorised use, disclosure, or copying* *of the contents is prohibited.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From apasotti at gmail.com Mon Nov 2 00:59:05 2026 From: apasotti at gmail.com (Alessandro Pasotti) Date: Mon, 2 Nov 2026 09:59:05 +0100 Subject: [QGIS-Developer] QGIS Full Stack Developer Report for October 2026 In-Reply-To: References: Message-ID: Good job Lova! Thank you for your work. On Mon, Nov 2, 2026 at 7:58?AM Lova Andriarimalala via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > Hello everyone, > > Please find some highlights regarding the development and maintenance of > the QGIS Websites for the past month, from October 1st to October 31st, > 2026. > > *QGIS Enhancement Proposals:* > > - QEP 431: Overhaul the QGIS plugin ecosystem > https://github.com/qgis/QGIS-Enhancement-Proposals/pull/390 > > [New PR] > > *QGIS Infrastructure:* > > - The QGIS Blog has moved from WordPress to a Hugo website, in line > with the other QGIS websites. > - The QGIS Feed was upgraded to Django 5.2 LTS and now has a Nix > flake-based environment in review, as a step toward moving it to the new > NixOS infrastructure with QGIS SSO sign-in. > - The QGIS Austria user group website is now online at > https://austria.qgis.org > > and https://at.qgis.org > > . > > *QGIS.org:* > > - User group list improvements > https://github.com/qgis/QGIS-Website/pull/1119 > > [Merged] > - Hide donors listed in the EXCLUDED_DONORS Actions variable > https://github.com/qgis/QGIS-Website/pull/1121 > > [Merged] > - Remove 'Asociaci?n QGIS M?xico' from groups.json > https://github.com/qgis/QGIS-Website/pull/1133 > > [Merged] > - Clearer docs for user group add or update > https://github.com/qgis/QGIS-Website/pull/1135 > > [Merged] > > *QGIS Plugins:* > > - Remove the rating feature > https://github.com/qgis/QGIS-Plugins-Website/pull/445 > > [Merged] > - Further security enhacement > https://github.com/qgis/QGIS-Plugins-Website/pull/478 > > [Merged] > - Add search input on small screen > https://github.com/qgis/QGIS-Plugins-Website/pull/480 > > [Merged] > - Prevent token expiration when rotating secret > https://github.com/qgis/QGIS-Plugins-Website/pull/484 > > [Merged] > > *QGIS Hub:* > > - Improve review workflow > https://github.com/qgis/QGIS-Hub-Website/pull/144 > > [Merged] > - Add support for glb file and refactor 3D viewer > https://github.com/qgis/QGIS-Hub-Website/pull/145 > > [New PR] > > *QGIS Feed:* > > - Fix author cannot edit own draft > https://github.com/qgis/QGIS-Feed-Website/pull/196 > > [Merged] > - Upgrade to Django 5.2 LTS, Python 3.12 and Node 22 > https://github.com/qgis/QGIS-Feed-Website/pull/202 > > [Merged] > - Add a nix flake-based environment > https://github.com/qgis/QGIS-Feed-Website/pull/203 > > [New PR] > > *QGIS Certification:* > > - Remove "Sign Up" button from various templates > https://github.com/qgis/QGIS-Certification-Website/pull/120 > > [Merged] > > *QGIS Sustaining Members:* > > - Email sending feature for sustaining members > https://github.com/qgis/QGIS-Members-Website/pull/30 > > [Merged] > > *QGIS Blog:* > > - Transform all wordpress layout and styles to bulma > https://github.com/qgis/QGIS-Blog-Website/pull/22 > > [Merged] > - docs: document how to add or edit an author > https://github.com/qgis/QGIS-Blog-Website/pull/24 > > [Merged] > - fix: set explicit slugs on posts with a slash in the title > https://github.com/qgis/QGIS-Blog-Website/pull/25 > > [Merged] > - feat: show the full category name on hover > https://github.com/qgis/QGIS-Blog-Website/pull/26 > > [Merged] > - feat: keep post images next to the post as page bundles > https://github.com/qgis/QGIS-Blog-Website/pull/27 > > [Merged] > - chore: drop the QGIS prefix from category names > https://github.com/qgis/QGIS-Blog-Website/pull/28 > > [Merged] > - feat: remove the author filter from the sidebar > https://github.com/qgis/QGIS-Blog-Website/pull/29 > > [Merged] > > *QGIS User Groups:* > > - Revise README for installation and customization steps > https://github.com/qgis/QGIS-User-Group-Website/pull/26 > > [Merged] > > Best regards, > Lova Andriarimalala > > > *QGIS Full Stack Developer * > *T *: +27(0) 87 809 2702 <+27%2087%20809%202702> *E *: > lova at kartoza.com *W* : kartoza.com > > > > *This email and any attachments are confidential and intended solely for > the use of the individual or entity to whom they are addressed. If you * > *have received this email in error, please notify the sender immediately > and delete it from your system. Unauthorised use, disclosure, or copying* > *of the contents is prohibited.* > _______________________________________________ > 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 > -- Alessandro Pasotti QCooperative: www.qcooperative.net ItOpen: www.itopen.it -------------- next part -------------- An HTML attachment was scrubbed... URL: From administration at qgis.org Tue Nov 3 01:10:00 2026 From: administration at qgis.org (Marco Serusi) Date: Tue, 3 Nov 2026 10:10:00 +0100 Subject: [QGIS-Developer] Confirmation Request: Oracle JDK 21.0.12 Dependency on QGIS In-Reply-To: References: Message-ID: Hello Amit, I have noticed that Santos has reached out to our security team on multiple occasions, and I was wondering if you'd be so kind as to help us reach out to some of your colleagues who could help us improve our project and security. As I'm sure you know, QGIS is a free, open-source software, built and run by volunteers in their spare time. This has several advantages since it means all of our information, code, and indeed the software itself is freely available to anyone, including companies like Santos. On the flip side, it also means the project is entirely dependent on donations to pay its bills and to fund improvements that the volunteers are not able to do themselves. As such, we'd appreciate it if you could help us find the right people within Santos who could release funds to support the project. From the multiple emails we have received from you and your colleagues, it is clear that security is an important topic for Santos and that Santos is using this free software to generate profits; therefore, it would seem fair if the company gave back to the project as well. With regard to your question, the volunteers from the security team will respond when time allows. In the meantime, please consider checking the many QGIS online communities that are available or the free documentation and resources. Keep in mind that, as an open-source project, all of our code is publicly viewable, and everything we do is also public, so it should be fairly easy to locate the information you require. Kind regards On Tue, Nov 3, 2026 at 2:39?AM 'Sisodia, Amit (Amit)' via security < security at qgis.org> wrote: > Hi team , > We are currently reviewing the upgrade to Oracle JDK 21.0.12 as part of > our security remediation activities and would like to confirm whether QGIS > has any dependency on this JDK version. > Could you please advise on the following: > > - Does QGIS require or depend on Oracle JDK 21.0.12 for any > functionality, plugins, or services? > - Is Oracle JDK 21.0.12 a supported version for the currently deployed > QGIS version 3.22.5? > - Are there any known compatibility issues, limitations, or > recommendations regarding the use of Oracle JDK 21.0.12 with QGIS? > - If QGIS or any associated components include or utilize their own > Java Runtime Environment (JRE/JDK), please confirm whether upgrading the > system-installed JDK would have any impact on the application or its > functionality. > - Are there any QGIS plugins, extensions, or integrations that may be > affected by an Oracle JDK upgrade? > > Your guidance will help us proceed with our security remediation and > upgrade activities accordingly. > > > Thanks & regards > Amit Sisodia > TCS - Exp Application Support team > Amit.Sisodia at contractor.santos.com > > -- *Marco Serusi* *Administrative Assistant - QGIS* -------------- next part -------------- An HTML attachment was scrubbed... URL: From delazj at gmail.com Tue Nov 3 07:22:01 2026 From: delazj at gmail.com (DelazJ) Date: Tue, 03 Nov 2026 16:22:01 +0100 Subject: [QGIS-Developer] OSGeo4w nightly build 4.3 outdated Message-ID: <53827592-E6D0-4C92-9D12-F96FB035BE9D@gmail.com> Hi devs, Trying to update my QGIS nightly build (4.3) using OSGeo4W, I only get QGIS which is one week old. A known issue? Kind regards, Harrissou -------------- next part -------------- An HTML attachment was scrubbed... URL: From viperminiq at gmail.com Tue Nov 3 07:34:17 2026 From: viperminiq at gmail.com (=?UTF-8?Q?Dominik_Cindri=C4=87?=) Date: Tue, 3 Nov 2026 16:34:17 +0100 Subject: [QGIS-Developer] QEP 433: Always include Z values in transforms (API break!) Message-ID: Hi list, we recently submitted "QEP 433: Always include Z values in transforms (API break!)" Please keep the discussion on Github page: https://github.com/qgis/QGIS-Enhancement-Proposals/pull/392 Best regards, - Dominik Cindric -------------- next part -------------- An HTML attachment was scrubbed... URL: From tim at qgis.org Tue Nov 3 09:51:54 2026 From: tim at qgis.org (Tim Sutton) Date: Tue, 3 Nov 2026 17:51:54 +0000 Subject: [QGIS-Developer] QGIS Full Stack Developer Report for October 2026 In-Reply-To: References: Message-ID: Yes great job @Lova Andriarimalala And one other thing to mention: We have had the PHP vulnerability this month which we can share our status for: 1. Wordpress (for blog.qgis.org) - as Lova mentioned, he has migrated our blog to hugo. 2. Matomo (for gathering web site analytics) - we have taken it offline pending fix 3. CDash - used for automated reporting of test results. Our friends at OTB wrote to let us know that it has been taken offline (they host if for QGIS since the hackfest back in Lyon). They will bring it online again at some point but the history will be lost. Regards Tim On Mon, Nov 2, 2026 at 8:59?AM Alessandro Pasotti via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > Good job Lova! > > Thank you for your work. > > On Mon, Nov 2, 2026 at 7:58?AM Lova Andriarimalala via QGIS-Developer < > qgis-developer at lists.osgeo.org> wrote: > >> Hello everyone, >> >> Please find some highlights regarding the development and maintenance of >> the QGIS Websites for the past month, from October 1st to October 31st, >> 2026. >> >> *QGIS Enhancement Proposals:* >> >> - QEP 431: Overhaul the QGIS plugin ecosystem >> https://github.com/qgis/QGIS-Enhancement-Proposals/pull/390 >> >> [New PR] >> >> *QGIS Infrastructure:* >> >> - The QGIS Blog has moved from WordPress to a Hugo website, in line >> with the other QGIS websites. >> - The QGIS Feed was upgraded to Django 5.2 LTS and now has a Nix >> flake-based environment in review, as a step toward moving it to the new >> NixOS infrastructure with QGIS SSO sign-in. >> - The QGIS Austria user group website is now online at >> https://austria.qgis.org >> >> and https://at.qgis.org >> >> . >> >> *QGIS.org:* >> >> - User group list improvements >> https://github.com/qgis/QGIS-Website/pull/1119 >> >> [Merged] >> - Hide donors listed in the EXCLUDED_DONORS Actions variable >> https://github.com/qgis/QGIS-Website/pull/1121 >> >> [Merged] >> - Remove 'Asociaci?n QGIS M?xico' from groups.json >> https://github.com/qgis/QGIS-Website/pull/1133 >> >> [Merged] >> - Clearer docs for user group add or update >> https://github.com/qgis/QGIS-Website/pull/1135 >> >> [Merged] >> >> *QGIS Plugins:* >> >> - Remove the rating feature >> https://github.com/qgis/QGIS-Plugins-Website/pull/445 >> >> [Merged] >> - Further security enhacement >> https://github.com/qgis/QGIS-Plugins-Website/pull/478 >> >> [Merged] >> - Add search input on small screen >> https://github.com/qgis/QGIS-Plugins-Website/pull/480 >> >> [Merged] >> - Prevent token expiration when rotating secret >> https://github.com/qgis/QGIS-Plugins-Website/pull/484 >> >> [Merged] >> >> *QGIS Hub:* >> >> - Improve review workflow >> https://github.com/qgis/QGIS-Hub-Website/pull/144 >> >> [Merged] >> - Add support for glb file and refactor 3D viewer >> https://github.com/qgis/QGIS-Hub-Website/pull/145 >> >> [New PR] >> >> *QGIS Feed:* >> >> - Fix author cannot edit own draft >> https://github.com/qgis/QGIS-Feed-Website/pull/196 >> >> [Merged] >> - Upgrade to Django 5.2 LTS, Python 3.12 and Node 22 >> https://github.com/qgis/QGIS-Feed-Website/pull/202 >> >> [Merged] >> - Add a nix flake-based environment >> https://github.com/qgis/QGIS-Feed-Website/pull/203 >> >> [New PR] >> >> *QGIS Certification:* >> >> - Remove "Sign Up" button from various templates >> https://github.com/qgis/QGIS-Certification-Website/pull/120 >> >> [Merged] >> >> *QGIS Sustaining Members:* >> >> - Email sending feature for sustaining members >> https://github.com/qgis/QGIS-Members-Website/pull/30 >> >> [Merged] >> >> *QGIS Blog:* >> >> - Transform all wordpress layout and styles to bulma >> https://github.com/qgis/QGIS-Blog-Website/pull/22 >> >> [Merged] >> - docs: document how to add or edit an author >> https://github.com/qgis/QGIS-Blog-Website/pull/24 >> >> [Merged] >> - fix: set explicit slugs on posts with a slash in the title >> https://github.com/qgis/QGIS-Blog-Website/pull/25 >> >> [Merged] >> - feat: show the full category name on hover >> https://github.com/qgis/QGIS-Blog-Website/pull/26 >> >> [Merged] >> - feat: keep post images next to the post as page bundles >> https://github.com/qgis/QGIS-Blog-Website/pull/27 >> >> [Merged] >> - chore: drop the QGIS prefix from category names >> https://github.com/qgis/QGIS-Blog-Website/pull/28 >> >> [Merged] >> - feat: remove the author filter from the sidebar >> https://github.com/qgis/QGIS-Blog-Website/pull/29 >> >> [Merged] >> >> *QGIS User Groups:* >> >> - Revise README for installation and customization steps >> https://github.com/qgis/QGIS-User-Group-Website/pull/26 >> >> [Merged] >> >> Best regards, >> Lova Andriarimalala >> >> >> *QGIS Full Stack Developer * >> *T *: +27(0) 87 809 2702 <+27%2087%20809%202702> *E *: >> lova at kartoza.com *W* : kartoza.com >> >> >> >> *This email and any attachments are confidential and intended solely for >> the use of the individual or entity to whom they are addressed. If you * >> *have received this email in error, please notify the sender immediately >> and delete it from your system. Unauthorised use, disclosure, or copying* >> *of the contents is prohibited.* >> _______________________________________________ >> 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 >> > > > -- > Alessandro Pasotti > QCooperative: www.qcooperative.net > ItOpen: www.itopen.it > _______________________________________________ > 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 > -- *Tim Sutton* QGIS Project Steering Committee tim at qgis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From lnicola at dend.ro Wed Nov 4 00:18:58 2026 From: lnicola at dend.ro (=?UTF-8?Q?Lauren=C8=9Biu_Nicola?=) Date: Wed, 04 Nov 2026 10:18:58 +0200 Subject: [QGIS-Developer] New GitHub setting for Copilot reviews Message-ID: <6437b75b-e49b-420e-925c-44792e2ce6cf@app.fastmail.com> Hello, Just a quick FYI, GitHub has a new option under Copilot / Code review / "Block reviews requested with an external Copilot license". Any project that not appreciate LLM usage might want to enable it. (cross-posted to GDAL/PROJ/QGIS) Laurentiu -------------- next part -------------- An HTML attachment was scrubbed... URL: From marco at opengis.ch Wed Nov 4 07:37:17 2026 From: marco at opengis.ch (Marco Bernasocchi) Date: Wed, 4 Nov 2026 16:37:17 +0100 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: References: Message-ID: Hey all, On Fri, 16 Oct 2026 at 01:01, Nyall Dawson via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > > > > On Fri, 16 Oct 2026, 8:56?am Nyall Dawson, wrote: > >> Thanks for doing this Jorge! >> >> Are we allowed to remove issues from this list? Eg I don't think >> https://github.com/qgis/QGIS/issues/58554 ("can't delete ESRI gdb >> folders from browser") should block the release. >> > > Actually thinking further, I'd argue that any issue which can be > reproduced in 3.44 should NOT be eligible for being a blocker. > I also think the same. if it is in 3.44 it has nothing to do with being a 4.4 blocker. Cheers Marco > > Nyall > > >> >> Nyall >> >> On Fri, 16 Oct 2026, 7:05?am Jorge Gustavo Rocha via QGIS-Developer, < >> qgis-developer at lists.osgeo.org> wrote: >> >>> Hi all, >>> >>> We?ve created a QGIS 4.4 project on GitHub [1] to help us track, >>> prioritise, and resolve the issues blocking the next LTR release. >>> >>> We?re starting with 136 open issues and 14 already in progress. Let?s >>> focus our efforts on getting these issues resolved and the next LTR >>> ready for release. >>> >>> Newly reported issues will be automatically added to the backlog if they >>> match the following criteria: >>> >>> is:issue is:open label:Regression,"QGIS 4","LTR blocker","High Priority" >>> >>> How we?ll work together: >>> >>> Triage: Everyone is encouraged to review the issues. Once an issue >>> has been triaged, move it to the Ready column and assign a priority: >>> Critical, High, Medium, or Low. >>> Development: Developers willing to contribute should pick issues >>> from the Ready column. >>> In progress: Once a PR is linked to an issue, it will move to the >>> In progress column. >>> Done: Once the PR is merged, the issue will be closed and moved to >>> the Done column. >>> >>> Please use the project to help us coordinate our efforts, identify >>> priorities, and keep track of progress. The more we can focus on this >>> shared list, the sooner we can clear the blockers for the next LTR. >>> >>> Let?s get this done! >>> >>> Thanks for your help and contributions. >>> >>> Regards, >>> >>> Jorge/Giovanni/Andrea/Tim >>> >>> [1] https://github.com/orgs/qgis/projects/18 >>> >>> _______________________________________________ >>> 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-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 > -- Marco Bernasocchi OPENGIS.ch CEO QGIS.org Chair OSGeo.org Board of Directors Find a meeting time on my calendar ! marco at opengis.ch +41 (0)79 467 24 70 <+41794672470> -------------- next part -------------- An HTML attachment was scrubbed... URL: From denis.rouzaud at gmail.com Thu Nov 5 23:45:09 2026 From: denis.rouzaud at gmail.com (Denis Rouzaud) Date: Fri, 6 Nov 2026 08:45:09 +0100 Subject: [QGIS-Developer] qgis-slim docker image In-Reply-To: References: Message-ID: Hi Joona, Thanks for the feedback! I don't plan to build 3.x since it would bring some extra complexity, and we already have something available there. Cheers, Denis Le jeu. 29 oct. 2026 ? 07:13, Joona Laine a ?crit : > Hi Denis, > > Sounds really good! This will make for example Github actions that run > plugin tests (for example with pytest-qgis) would run much faster. > > Which versions would this slim image support? All the way down to 3.40 I > hope? :) > > -Joona > > ke 28.10.2026 klo 22.48 Denis Rouzaud via QGIS-Developer ( > qgis-developer at lists.osgeo.org) kirjoitti: > >> Hi Alessandro, >> >> The motivations: >> - someone asked for geoparquet support >> - there is currently no arm image >> - downloading 1.55gb to test a plugin is way too much >> >> The main intention is to use it to test plugins and do integration tests. >> >> Denis >> >> Le mer. 28 oct. 2026 ? 19:40, Alessandro Pasotti a >> ?crit : >> >>> Interesting! >>> >>> What use cases do you have in mind for such an image? >>> >>> >>> On Wed, Oct 28, 2026 at 7:28?PM Denis Rouzaud via QGIS-Developer >>> wrote: >>> > >>> > Dear all, >>> > >>> > I've created a qgis-slim image where QGIS is built rather than >>> installed from ppa. >>> > >>> > It has no desktop, no server but python bindings + geoparqet support. >>> Arm and x86 builds. >>> > >>> > I've opened a PR here >>> > https://github.com/qgis/qgis-docker/pull/162 >>> > >>> > We are at 280mb instead of 1.55gb >>> > >>> > Any thoughts on this? >>> > Would you recommend opening a QEP to discuss this? >>> > >>> > Or shall we just go like this? >>> > >>> > Cheers, >>> > Denis >>> > >>> > >>> > _______________________________________________ >>> > 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 >>> >>> >>> >>> -- >>> Alessandro Pasotti >>> QCooperative: www.qcooperative.net >>> ItOpen: www.itopen.it >>> >> _______________________________________________ >> 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 joona.p.laine at gmail.com Fri Nov 6 00:30:19 2026 From: joona.p.laine at gmail.com (Joona Laine) Date: Fri, 6 Nov 2026 10:30:19 +0200 Subject: [QGIS-Developer] qgis-slim docker image In-Reply-To: References: Message-ID: Hi Denis, I understand completely. This is still a really good improvement to workflows. -Joona pe 6.11.2026 klo 9.45 Denis Rouzaud (denis.rouzaud at gmail.com) kirjoitti: > Hi Joona, > > Thanks for the feedback! > > I don't plan to build 3.x since it would bring some extra complexity, and > we already have something available there. > > Cheers, > Denis > > Le jeu. 29 oct. 2026 ? 07:13, Joona Laine a > ?crit : > >> Hi Denis, >> >> Sounds really good! This will make for example Github actions that run >> plugin tests (for example with pytest-qgis) would run much faster. >> >> Which versions would this slim image support? All the way down to 3.40 I >> hope? :) >> >> -Joona >> >> ke 28.10.2026 klo 22.48 Denis Rouzaud via QGIS-Developer ( >> qgis-developer at lists.osgeo.org) kirjoitti: >> >>> Hi Alessandro, >>> >>> The motivations: >>> - someone asked for geoparquet support >>> - there is currently no arm image >>> - downloading 1.55gb to test a plugin is way too much >>> >>> The main intention is to use it to test plugins and do integration tests. >>> >>> Denis >>> >>> Le mer. 28 oct. 2026 ? 19:40, Alessandro Pasotti a >>> ?crit : >>> >>>> Interesting! >>>> >>>> What use cases do you have in mind for such an image? >>>> >>>> >>>> On Wed, Oct 28, 2026 at 7:28?PM Denis Rouzaud via QGIS-Developer >>>> wrote: >>>> > >>>> > Dear all, >>>> > >>>> > I've created a qgis-slim image where QGIS is built rather than >>>> installed from ppa. >>>> > >>>> > It has no desktop, no server but python bindings + geoparqet support. >>>> Arm and x86 builds. >>>> > >>>> > I've opened a PR here >>>> > https://github.com/qgis/qgis-docker/pull/162 >>>> > >>>> > We are at 280mb instead of 1.55gb >>>> > >>>> > Any thoughts on this? >>>> > Would you recommend opening a QEP to discuss this? >>>> > >>>> > Or shall we just go like this? >>>> > >>>> > Cheers, >>>> > Denis >>>> > >>>> > >>>> > _______________________________________________ >>>> > 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 >>>> >>>> >>>> >>>> -- >>>> Alessandro Pasotti >>>> QCooperative: www.qcooperative.net >>>> ItOpen: www.itopen.it >>>> >>> _______________________________________________ >>> 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 olivier.dalang at gmail.com Fri Nov 6 02:05:36 2026 From: olivier.dalang at gmail.com (Olivier Dalang) Date: Fri, 6 Nov 2026 11:05:36 +0100 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: References: Message-ID: Hey all ! First thank you so much for clarifying the situation on the blog post ( https://blog.qgis.org/2026/11/04/where-is-qgis-4.4.0/). Just a quick question for my understanding: from the published roadmap, I thought that 4.4 was meant to replace 3.44 as the LTR only in march 2027, and that before that, 4.4 was just a regular release. If so, wouldn't it be enough to sort out those issues by then, so that latest release users can already adopt 4.4 ? Also it would be great to have an idea (even if very vague) about how much delay we're talking about, to help making deployment plans in this tricky 3->4 transition time. Are talking about a few more days or could it be months ? Kind regards and thanks again for all the great work on QGIS, Olivier On Wed, 4 Nov 2026 at 16:37, Marco Bernasocchi via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > Hey all, > > > On Fri, 16 Oct 2026 at 01:01, Nyall Dawson via QGIS-Developer < > qgis-developer at lists.osgeo.org> wrote: > >> >> >> >> On Fri, 16 Oct 2026, 8:56?am Nyall Dawson, >> wrote: >> >>> Thanks for doing this Jorge! >>> >>> Are we allowed to remove issues from this list? Eg I don't think >>> https://github.com/qgis/QGIS/issues/58554 ("can't delete ESRI gdb >>> folders from browser") should block the release. >>> >> >> Actually thinking further, I'd argue that any issue which can be >> reproduced in 3.44 should NOT be eligible for being a blocker. >> > I also think the same. if it is in 3.44 it has nothing to do with being a > 4.4 blocker. > > Cheers > Marco > >> >> Nyall >> >> >>> >>> Nyall >>> >>> On Fri, 16 Oct 2026, 7:05?am Jorge Gustavo Rocha via QGIS-Developer, < >>> qgis-developer at lists.osgeo.org> wrote: >>> >>>> Hi all, >>>> >>>> We?ve created a QGIS 4.4 project on GitHub [1] to help us track, >>>> prioritise, and resolve the issues blocking the next LTR release. >>>> >>>> We?re starting with 136 open issues and 14 already in progress. Let?s >>>> focus our efforts on getting these issues resolved and the next LTR >>>> ready for release. >>>> >>>> Newly reported issues will be automatically added to the backlog if >>>> they >>>> match the following criteria: >>>> >>>> is:issue is:open label:Regression,"QGIS 4","LTR blocker","High Priority" >>>> >>>> How we?ll work together: >>>> >>>> Triage: Everyone is encouraged to review the issues. Once an issue >>>> has been triaged, move it to the Ready column and assign a priority: >>>> Critical, High, Medium, or Low. >>>> Development: Developers willing to contribute should pick issues >>>> from the Ready column. >>>> In progress: Once a PR is linked to an issue, it will move to the >>>> In progress column. >>>> Done: Once the PR is merged, the issue will be closed and moved to >>>> the Done column. >>>> >>>> Please use the project to help us coordinate our efforts, identify >>>> priorities, and keep track of progress. The more we can focus on this >>>> shared list, the sooner we can clear the blockers for the next LTR. >>>> >>>> Let?s get this done! >>>> >>>> Thanks for your help and contributions. >>>> >>>> Regards, >>>> >>>> Jorge/Giovanni/Andrea/Tim >>>> >>>> [1] https://github.com/orgs/qgis/projects/18 >>>> >>>> _______________________________________________ >>>> 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-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 >> > > > -- > Marco Bernasocchi > OPENGIS.ch CEO > QGIS.org Chair > OSGeo.org Board of Directors > > Find a meeting time on my calendar > ! > marco at opengis.ch > +41 (0)79 467 24 70 <+41794672470> > > > _______________________________________________ > 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 jef at norbit.de Fri Nov 6 02:51:51 2026 From: jef at norbit.de (=?utf-8?Q?J=C3=BCrgen_E=2E?= Fischer) Date: Fri, 6 Nov 2026 11:51:51 +0100 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: References: Message-ID: <20261106105151.hskargfix6jp6ab7@norbit.de> Hi Olivier, On Fri, 06. Nov 2026 at 11:05:36 +0100, Olivier Dalang via QGIS-Developer wrote: > Just a quick question for my understanding: from the published roadmap, I > thought that 4.4 was meant to replace 3.44 as the LTR only in march 2027, > and that before that, 4.4 was just a regular release. If so, wouldn't it be > enough to sort out those issues by then, so that latest release users can > already adopt 4.4 ? The branch is what gets long-time care and therefore it gets the ltr tag when it's branched off. That it doesn't replace the old LTR in the package repositories right away is just a technicallity. We build two branches - one feeds the LTR repos and one the regular repos - and while the new LTR is also the latest release it still feeds the regular repos, while the previous still feeds the LTR repos. As side effect it get some more time to mature as people can try the new LTR release, while the old LTR is still available (and even being maintained). > Also it would be great to have an idea (even if very vague) about how much > delay we're talking about, to help making deployment plans in this tricky > 3->4 transition time. Are talking about a few more days or could it be > months ? You mean how long it will take to fix or reclassify the blocking issues? J?rgen -- J?rgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstra?e 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden https://www.norbit.de QGIS release manager (PSC) Germany Matrix: @jef:osgeo.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From olivier.dalang at gmail.com Fri Nov 6 03:59:11 2026 From: olivier.dalang at gmail.com (Olivier Dalang) Date: Fri, 6 Nov 2026 12:59:11 +0100 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: <20261106105151.hskargfix6jp6ab7@norbit.de> References: <20261106105151.hskargfix6jp6ab7@norbit.de> Message-ID: Hello J?rgen, If I get it right, even if the 4.4.x branch was created today (including the LTR blocking issues), that would just feed the regular repos until march 2027, so not worse than today since 4.2 also has these issues. Then there would still be until march 2027 to fix these blocking issues and backport them to the branch so that they don't land in the LTR repos, no ? (sorry if I'm confused, here we're just discussing which version we target to roll out to our users, so I'd be happy to fully understand this :-) ) For the time frame, my question was about an estimate for the delay for 4.4.0 as LR (either with blocking issues fixed or reclassified). And if we can already foresee some delays for 4.4.4 as LTR, of course that would be great to know too (for instance if 4.4.0 ends up significantly delayed, would we also postpone the LTR so that it gets enough time to mature ?). Cheers ! Olivier On Fri, 6 Nov 2026 at 11:52, J?rgen E. Fischer via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > Hi Olivier, > > On Fri, 06. Nov 2026 at 11:05:36 +0100, Olivier Dalang via QGIS-Developer > wrote: > > Just a quick question for my understanding: from the published roadmap, I > > thought that 4.4 was meant to replace 3.44 as the LTR only in march 2027, > > and that before that, 4.4 was just a regular release. If so, wouldn't it > be > > enough to sort out those issues by then, so that latest release users can > > already adopt 4.4 ? > > The branch is what gets long-time care and therefore it gets the ltr tag > when > it's branched off. > > That it doesn't replace the old LTR in the package repositories right away > is > just a technicallity. We build two branches - one feeds the LTR repos and > one > the regular repos - and while the new LTR is also the latest release it > still > feeds the regular repos, while the previous still feeds the LTR repos. > > As side effect it get some more time to mature as people can try the new > LTR > release, while the old LTR is still available (and even being maintained). > > > Also it would be great to have an idea (even if very vague) about how > much > > delay we're talking about, to help making deployment plans in this tricky > > 3->4 transition time. Are talking about a few more days or could it be > > months ? > > You mean how long it will take to fix or reclassify the blocking issues? > > > J?rgen > > -- > J?rgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 > Dipl.-Inf. (FH) Rheinstra?e 13 Fax. +49-4931-918175-50 > Software Engineer D-26506 Norden > https://www.norbit.de > QGIS release manager (PSC) Germany Matrix: @jef: > osgeo.org > _______________________________________________ > 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 jef at norbit.de Fri Nov 6 05:20:22 2026 From: jef at norbit.de (=?utf-8?Q?J=C3=BCrgen_E=2E?= Fischer) Date: Fri, 6 Nov 2026 14:20:22 +0100 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: References: <20261106105151.hskargfix6jp6ab7@norbit.de> Message-ID: <20261106132022.r2kfbit5kl556ql3@norbit.de> Hi Olivier, On Fri, 06. Nov 2026 at 12:59:11 +0100, Olivier Dalang wrote: > If I get it right, even if the 4.4.x branch was created today (including > the LTR blocking issues), that would just feed the regular repos until > march 2027, so not worse than today since 4.2 also has these issues. Right. But my understanding was that we want to postpone the LTR release now until the blocking bugs are fixed. So either it's what I'm doing now or there wouldn't have been a reason to postpone anything as I believe March is still far away enough to fix the blockers - at least we don't known otherwise. J?rgen -- J?rgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstra?e 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden https://www.norbit.de QGIS release manager (PSC) Germany Matrix: @jef:osgeo.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Pflichtangaben URL: From romain.degoul at telespazio.com Tue Nov 10 07:19:23 2026 From: romain.degoul at telespazio.com (Degoul Romain) Date: Tue, 10 Nov 2026 15:19:23 +0000 Subject: [QGIS-Developer] =?windows-1252?q?ImageQualityToolset_plugin_=96?= =?windows-1252?q?_versions_1=2E1/1=2E2_not_approved_and_inaccessible_regi?= =?windows-1252?q?stered_email?= Message-ID: Hello, I am the maintainer of the QGIS plugin ImageQualityToolset (https://plugins.qgis.org/plugins/image_quality_toolset/), published under the account rdegoul. I apologise in advance if this is not the right contact for questions about the QGIS plugin repository (plugins.qgis.org). If so, could you please forward my request to the appropriate team, or let me know whom I should contact? I have two issues: 1. Rejected versions Version 1.0 (June 2026) was approved without any problem. However, the two new versions I uploaded on 3 November 2026 (1.1 and 1.2) were not approved: 1.1 shows as not approved with a warning flag, and 1.2 shows a red rejection icon. I have not received any explanation. Could you tell me why these versions were rejected and what I need to change so that a new version can be accepted? 2. Registered email address I cannot access The plugin is associated with the email address sen2like at telespazio.com, to which I do not have access. There is currently an email confirmation pending, but since the confirmation token is sent to this address, I cannot retrieve it and complete the process. This may also explain why I did not receive any notification about the rejection. Could you please update the contact email for the plugin to my own address, or tell me the procedure to do so? Thank you in advance for your help. Best regards, Romain Degoul Telespazio France ? Toulouse -------------- next part -------------- An HTML attachment was scrubbed... URL: From bas at rdgland.com Wed Nov 11 11:10:03 2026 From: bas at rdgland.com (Sebastian Gutwein) Date: Wed, 11 Nov 2026 14:10:03 -0500 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: <20261106132022.r2kfbit5kl556ql3@norbit.de> References: <20261106105151.hskargfix6jp6ab7@norbit.de> <20261106132022.r2kfbit5kl556ql3@norbit.de> Message-ID: I was also confused by the LTR timing. My undesrtanding now is: 1. 4.4.0 is an LTR, but it overlaps with the old 3.44 LTR until March. During that overlap, the LTR repositories will remain 3.44. 2. 4.4.0 will not be released until the regressions are cleared. 3. If the regressions are cleared before March, whatever 4.4.x release exists at that time will replace 3.44 in the LTR repositories. (assuming the QGIS core agrees of course) Currently I have my students using 4.2 because many of them have Macs and I think the experience is much better than 3.44. If a 4.4.0 were released with regresions I would have them switch because there are some new features that would benefit them now and they are already dealing with most of the 3.44 regressions in 4.2. Therefore, I would encourage the QGIS steering committee to release 4.4.0 with regressions and keep 3.44 in the LTR repositories and keep releasing reguarly scheduled point releases until the 4.4 regressions are cleared or 4.4.4 is released, whichever is later. This will get 4.4 into users hands where the new features can be used and issues can be raised before the LTR is replaced in the repositories. For what it is worth I always assumed that the LTR x.x.0 to x.x.3 releases were "LTR Release Candidates". Does it say "Release Candidate" on the splash screen or is that just for the x.x.0 release? Thanks -Bas On Fri, Nov 6, 2026 at 8:20?AM J?rgen E. Fischer via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > Hi Olivier, > > On Fri, 06. Nov 2026 at 12:59:11 +0100, Olivier Dalang wrote: > > If I get it right, even if the 4.4.x branch was created today (including > > the LTR blocking issues), that would just feed the regular repos until > > march 2027, so not worse than today since 4.2 also has these issues. > > Right. But my understanding was that we want to postpone the LTR release > now > until the blocking bugs are fixed. > > So either it's what I'm doing now or there wouldn't have been a reason to > postpone anything as I believe March is still far away enough to fix the > blockers - at least we don't known otherwise. > > > J?rgen > > -- > J?rgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 > Dipl.-Inf. (FH) Rheinstra > ?e 13 > Fax. +49-4931-918175-50 > Software Engineer D-26506 Norden > https://www.norbit.de > QGIS release manager (PSC) Germany Matrix: @jef: > osgeo.org > _______________________________________________ > 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 > -- ___________________________ Sebastian "Bas* " Gutwein *rhymes with Josh Regenerative Design Group 1 Chevalier Ave Greenfield, Ma 01301 Web: regenerativedesigngroup.com (631) 241-1018 *Look close, think big, make change. * -------------- 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-Developer] 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 uclaros at gmail.com Wed Nov 11 23:10:32 2026 From: uclaros at gmail.com (Stefanos Natsis) Date: Thu, 12 Nov 2026 09:10:32 +0200 Subject: [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 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 uclaros at gmail.com Wed Nov 11 23:59:18 2026 From: uclaros at gmail.com (Stefanos Natsis) Date: Thu, 12 Nov 2026 09:59:18 +0200 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: <20261106105151.hskargfix6jp6ab7@norbit.de> References: <20261106105151.hskargfix6jp6ab7@norbit.de> Message-ID: Hi J?rgen, On Fri, 6 Nov 2026 at 12:52, J?rgen E. Fischer via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > The branch is what gets long-time care and therefore it gets the ltr tag > when > it's branched off. > > That it doesn't replace the old LTR in the package repositories right away > is > just a technicallity. I humbly believe it's the other way round: The technicality here is the fact that the 4.4 branch will be tagged LTR when it's branched off. User's don't know (or care) about LTR branch, they know a version is LTR when they see a version number on the LTR column in the roadmap (4.4.4) and a download link for it. Obligatory XKCD https://xkcd.com/2501/ :D My expectation according to [1] was that the change to the schedule would be that if there are pending blockers by 2027-03-05 then the LTR column on the roadmap would become 3.44.20 instead of 4.4.4, potentially delaying the 4.6.0 release. [1] https://blog.qgis.org/2026/10/03/release-schedule-changes-for-next-qgis-ltr/ Cheers, Stefanos -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthias at opengis.ch Thu Nov 12 00:55:09 2026 From: matthias at opengis.ch (Matthias Kuhn) Date: Thu, 12 Nov 2026 09:55:09 +0100 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: References: <20261106105151.hskargfix6jp6ab7@norbit.de> Message-ID: Hi, I would also favor treating blockers as indicators for when 4.4 is ready to be officially labelled LTR and meanwhile release 4.4 as a regular release, just like Stefanos proposed. This would help us get more testing and potentially discover more blockers before a final release. The end users I am in touch with typically won't use nightlies or weeklies to test; they only start testing once a tagged release is out. One more note: according to the QGIS roadmap https://www.qgis.org/resources/roadmap/ a 3.44.16 (alongside the discussed 4.4.0) should be available but it seems this has also been delayed, probably as a side effect. We are currently holding back fixes for the current LTR and for the QGIS 4 release cycle. Kind regards Matthias On Thu, Nov 12, 2026 at 8:59?AM Stefanos Natsis via QGIS-Developer wrote: > > Hi J?rgen, > > On Fri, 6 Nov 2026 at 12:52, J?rgen E. Fischer via QGIS-Developer wrote: >> >> The branch is what gets long-time care and therefore it gets the ltr tag when >> it's branched off. >> >> That it doesn't replace the old LTR in the package repositories right away is >> just a technicallity. > > > I humbly believe it's the other way round: The technicality here is the fact that the 4.4 branch will be tagged LTR when it's branched off. > User's don't know (or care) about LTR branch, they know a version is LTR when they see a version number on the LTR column in the roadmap (4.4.4) and a download link for it. > Obligatory XKCD https://xkcd.com/2501/ :D > > My expectation according to [1] was that the change to the schedule would be that if there are pending blockers by 2027-03-05 then the LTR column on the roadmap would become 3.44.20 instead of 4.4.4, potentially delaying the 4.6.0 release. > > [1] https://blog.qgis.org/2026/10/03/release-schedule-changes-for-next-qgis-ltr/ > > Cheers, > Stefanos > _______________________________________________ > 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 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-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-Developer] [Qgis-voting-members] 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 administration at qgis.org Thu Nov 12 01:54:50 2026 From: administration at qgis.org (Marco Serusi) Date: Thu, 12 Nov 2026 10:54:50 +0100 Subject: [QGIS-Developer] [Qgis-voting-members] Community Voting Members Election Nov-Dec 2026: Schedule and Call for Nominations In-Reply-To: References: Message-ID: Hi Ismail, We are planning to do something similar to confirm we have, at the very least, the correct email address for everyone; however, I haven't had time to get started yet. We started with user groups because, looking at past elections, community voting members tended to vote regularly, while user groups had more issues. In this year's AGM, for example, 90.6% of community voting members voted, vs 67% of user groups (more stats like these coming soon; the AGM just closed). The challenge with Community Voting Members on the removal side is that while the PSC can approve/unapprove User Groups, it doesn't have a similar right for voting members, so even if we found unresponsive individuals, it wouldn't be technically possible to remove them. That being said, there will likely be a matter arising brought up in the 2027 AGM proposing a rule that if CVMs do not vote for X number of years and cannot be reached despite X number of attempts, they will be removed. This should help us keep the list clean and open up more spaces for active voting members. Hope it helps! On Thu, Nov 12, 2026 at 10:45?AM Ismail Sunni via Qgis-voting-members < qgis-voting-members at lists.osgeo.org> wrote: > 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 > _______________________________________________ > Qgis-voting-members mailing list > Qgis-voting-members at lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/qgis-voting-members > -- *Marco Serusi* *Administrative Assistant - QGIS* -------------- next part -------------- An HTML attachment was scrubbed... URL: From danas at specieshub.io Thu Nov 12 05:25:01 2026 From: danas at specieshub.io (Danas) Date: Thu, 12 Nov 2026 15:25:01 +0200 Subject: [QGIS-Developer] Plugin approval request: SpeciesHub (ID 6781) Message-ID: <1a1cfeee18d.753ad39914305.1684857043088654070@specieshub.io> Hello, Could a reviewer take a look at our plugin SpeciesHub (ID 6781, https://plugins.qgis.org/plugins/specieshub/ )? The review note on 0.1.2 (homepage should describe the plugin) is fixed in 0.1.3, uploaded on 4 November and marked done on the site; the security scan and Qt 6 check passed. The code is public at https://github.com/specieshub/specieshub-qgis . Please tell us if anything else is needed. Thank you, Danas Augutis? SpeciesHub -------------- next part -------------- An HTML attachment was scrubbed... URL: From jef at norbit.de Thu Nov 12 06:21:42 2026 From: jef at norbit.de (=?utf-8?Q?J=C3=BCrgen_E=2E?= Fischer) Date: Thu, 12 Nov 2026 15:21:42 +0100 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: References: <20261106105151.hskargfix6jp6ab7@norbit.de> Message-ID: <20261112142142.jhk4gmrspqy2mhfn@norbit.de> Hi Matthias, On Thu, 12. Nov 2026 at 09:55:09 +0100, Matthias Kuhn wrote: > I would also favor treating blockers as indicators for when 4.4 is > ready to be officially labelled LTR and meanwhile release 4.4 as a > regular release, just like Stefanos proposed. > This would help us get more testing and potentially discover more > blockers before a final release. The end users I am in touch with > typically won't use nightlies or weeklies to test; they only start > testing once a tagged release is out. The Debian/Ubuntu master nightlies are currently not working (because new wayland dependencies were added). And there's Nyalls ongoing work for the HTML support in master - for which PDF4Qt should be enabled, which also adds a couple of new dependencies. Debian/Ubuntu should be addressed in #68165. OSGeo4W up next. > One more note: according to the QGIS roadmap > https://www.qgis.org/resources/roadmap/ a 3.44.16 (alongside the discussed > 4.4.0) should be available but it seems this has also been delayed, probably > as a side effect. We are currently holding back fixes for the current LTR and > for the QGIS 4 release cycle. True. 3.44 could have been released alone. J?rgen -- J?rgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstra?e 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden https://www.norbit.de QGIS release manager Germany Matrix: @jef:osgeo.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From administration at qgis.org Thu Nov 12 06:56:04 2026 From: administration at qgis.org (Marco Serusi) Date: Thu, 12 Nov 2026 15:56:04 +0100 Subject: [QGIS-Developer] Plugin approval request: SpeciesHub (ID 6781) In-Reply-To: <1a1cfeee18d.753ad39914305.1684857043088654070@specieshub.io> References: <1a1cfeee18d.753ad39914305.1684857043088654070@specieshub.io> Message-ID: Hello Danas, Thank you for reaching out. Unfortunately, the workload faced by the volunteers who develop QGIS is very high at the moment, so reviews and approvals will take time. As I'm sure you know, QGIS is an open-source project run by volunteers who donate their free time to keep the project running, so the resources available are limited by their goodwill and other life commitments. If you'd like to help, there are many ways to contribute listed on our site that would be greatly appreciated by the community. Kind regards, On Thu, Nov 12, 2026 at 2:40?PM Danas via QGIS-Developer < qgis-developer at lists.osgeo.org> wrote: > Hello, > > Could a reviewer take a look at our plugin SpeciesHub (ID 6781, > https://plugins.qgis.org/plugins/specieshub/)? The review note on 0.1.2 > (homepage should describe the plugin) is fixed in 0.1.3, uploaded on 4 > November and marked done on the site; the security scan and Qt 6 check > passed. The code is public at > https://github.com/specieshub/specieshub-qgis. Please tell us if anything > else is needed. > > Thank you, > > *Danas Augutis* > > SpeciesHub > > > _______________________________________________ > 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 > -- *Marco Serusi* *Administrative Assistant - QGIS* -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthias at opengis.ch Thu Nov 12 08:07:05 2026 From: matthias at opengis.ch (Matthias Kuhn) Date: Thu, 12 Nov 2026 17:07:05 +0100 Subject: [QGIS-Developer] QGIS 4.4 - Coordinating efforts to unblock the next LTR In-Reply-To: <20261112142142.jhk4gmrspqy2mhfn@norbit.de> References: <20261106105151.hskargfix6jp6ab7@norbit.de> <20261112142142.jhk4gmrspqy2mhfn@norbit.de> Message-ID: Hi J?rgen, On Thu, Nov 12, 2026 at 3:22?PM J?rgen E. Fischer via QGIS-Developer wrote: > > Hi Matthias, > > On Thu, 12. Nov 2026 at 09:55:09 +0100, Matthias Kuhn wrote: > > I would also favor treating blockers as indicators for when 4.4 is > > ready to be officially labelled LTR and meanwhile release 4.4 as a > > regular release, just like Stefanos proposed. > > This would help us get more testing and potentially discover more > > blockers before a final release. The end users I am in touch with > > typically won't use nightlies or weeklies to test; they only start > > testing once a tagged release is out. > > The Debian/Ubuntu master nightlies are currently not working (because new > wayland dependencies were added). > > And there's Nyalls ongoing work for the HTML support in master - for which > PDF4Qt should be enabled, which also adds a couple of new dependencies. > > Debian/Ubuntu should be addressed in #68165. OSGeo4W up next. Thanks for taking care of all that! Do you consider a 4.4.0 release realistic once the OSGeo4W dependencies are sorted even though we might have a few remaining blockers? Bests Matthias 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-Developer] 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-Developer] 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 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-Developer] [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 niccolomarcom at gmail.com Mon Nov 16 08:54:29 2026 From: niccolomarcom at gmail.com (=?UTF-8?Q?Niccol=C3=B2_Marco?=) Date: Mon, 16 Nov 2026 17:54:29 +0100 Subject: [QGIS-Developer] =?utf-8?q?Request_for_=E2=80=98trusted_contribu?= =?utf-8?q?tor=E2=80=99_=28can=5Fapprove=29_status_on_the_QGIS_plug?= =?utf-8?q?in_repository?= Message-ID: Hello, I?d like to be considered for ?trusted contributor? status (the can_approve permission) on the QGIS plugin repository, so I can publish new versions of my plugins automatically once the automated security scan passes, rather than waiting for manual staff approval each time. I currently maintain three published plugins on plugins.qgis.org: - *Analisi territoriale* (territorial_suite) - 413 downloads, several approved versions (0.1.1, 0.2.0, 0.4.0), with 0.6.1 currently in the manual-approval queue (security scan and Qt6 check both passed). - *GeoCad UAV Toolkit* - 263 downloads, stable, latest approved version 2.2.5. - *Universal Earth Observation* (co-authored) - 366 downloads, stable, latest approved version 1.1.11. All three have a clean history on the repository: no version has ever been blocked by the security scan for critical issues. I?d appreciate being considered for auto-approval going forward. Thank you, Niccol? Marco Mancini -------------- next part -------------- An HTML attachment was scrubbed... URL: