From r.nijssen at terglobo.nl  Mon Apr  6 23:48:44 2026
From: r.nijssen at terglobo.nl (Raymond Nijssen)
Date: Tue, 7 Apr 2026 08:48:44 +0200
Subject: [Qgis-psc] Geospatial World Forum in Amsterdam
In-Reply-To: <CAB2Z92Df5m2-+QKQW=tEa2sjz=1bCgKuvYAVftDWua=WM4FVhg@mail.gmail.com>
References: <c62d093f-089d-41cb-aa87-e157de43945d@terglobo.nl>
 <CACGKw0ZDKKTWV6doGbXq3meB7KKPFcs+bO9=7YBUFBDrmA6fDw@mail.gmail.com>
 <CAB2Z92Df5m2-+QKQW=tEa2sjz=1bCgKuvYAVftDWua=WM4FVhg@mail.gmail.com>
Message-ID: <5268ba61-77c9-4719-aba1-2349d7da3f7a@terglobo.nl>

Hi, thanks for your replies. We will try to look into this next time.

Raymond



On 3/24/26 07:56, Andreas Neumann wrote:
> Hi all,
> 
> I like the option of a shared booth with other OSGeo projects - and QGIS 
> could certainly contribute to such a shared booth (both financially and 
> with people).
> 
> It would be great if the local QGIS user groups would take the 
> initiative if such an important event takes place in their country. 
> QGIS.ORG <http://QGIS.ORG> could then co-support the local user group.
> 
> As an example, in 2027 the international cartographic conference (ICC) 
> will take place in Warsaw ( https://icc2027.org/ <https://icc2027.org/ 
>  > ) and I asked the Polish QGIS user group to look into it organizing?a 
> boot there. They? have local contacts and are well connected, e.g. with 
> the local university that is the host of the conference. QGIS.ORG 
> <http://QGIS.ORG> can then potentially support them as well.
> 
> Greetings,
> Andreas
> 
> On Tue, 24 Mar 2026 at 00:34, Emma Hain via QGIS-PSC <qgis- 
> psc at lists.osgeo.org <mailto:qgis-psc at lists.osgeo.org>> wrote:
> 
>     I have often thought this was a good idea, however, the cost is a
>     lot, unless you can get a discounted price.
> 
>     An option could be for OSGeo to have a booth and then the
>     representatives from the respective software could man it.
> 
>     Sometimes the option may be cheaper to sponsor a social event.
> 
>     If a national government wanted to encourage the use of FOSS4G,
>     perhaps they could help with a grant?
> 
>     Kind regards
>     Em
> 
> 
>     On Mon, 23 Mar 2026 at 21:05, Raymond Nijssen via QGIS-PSC <qgis-
>     psc at lists.osgeo.org <mailto:qgis-psc at lists.osgeo.org>> wrote:
> 
>         Hi PSC,
> 
>         Today I bumped (a little late) into this announcement of the GWF in
>         Amsterdam (April 27 - May 1), having "Sovereignty" as a theme.
> 
>         https://geospatialworld.net/gwf/2026/index.php <https://
>         geospatialworld.net/gwf/2026/index.php>
> 
>         Has the PSC ever considered having a QGIS booth is such an
>         international
>         GIS conference? Or a shared booth with OSGeo maybe?
> 
>         As the Dutch QGIS user group, we could find volunteers to build
>         up and
>         run the booth, keeping cost a bit lower. However, the smallest
>         booth is
>         around 5000 euro for 3 days.
> 
>         floor plan:
>         https://service.rai.nl/INTERSHOP/web/WFS/RAI-raievents-Site/
>         en_US/Geospatial/EUR/ViewContent-Start?
>         PageletEntryPointID=pg_Floorplans <https://service.rai.nl/
>         INTERSHOP/web/WFS/RAI-raievents-Site/en_US/Geospatial/EUR/
>         ViewContent-Start?PageletEntryPointID=pg_Floorplans>
> 
>         This year we are too late I think, but I'd like to know if the
>         PSC is
>         interested in supporting this idea and making plans for upcoming
>         conferences around the world.
> 
>         Kind regards,
>         Raymond
> 
>         _______________________________________________
>         QGIS-PSC mailing list
>         QGIS-PSC at lists.osgeo.org <mailto:QGIS-PSC at lists.osgeo.org>
>         https://lists.osgeo.org/mailman/listinfo/qgis-psc <https://
>         lists.osgeo.org/mailman/listinfo/qgis-psc>
> 
>     _______________________________________________
>     QGIS-PSC mailing list
>     QGIS-PSC at lists.osgeo.org <mailto:QGIS-PSC at lists.osgeo.org>
>     https://lists.osgeo.org/mailman/listinfo/qgis-psc <https://
>     lists.osgeo.org/mailman/listinfo/qgis-psc>
> 
> 
> 
> -- 
> 
> --
> Andreas Neumann
> QGIS.ORG <http://QGIS.ORG> board member (treasurer)


From nyall.dawson at gmail.com  Thu Apr  9 19:46:34 2026
From: nyall.dawson at gmail.com (Nyall Dawson)
Date: Fri, 10 Apr 2026 12:46:34 +1000
Subject: [Qgis-psc] Announcing QEP 420: Restore the print layout HTML item
 for QGIS 4
Message-ID: <CAB28Ashyskd+QsRxqfJM6sKiKNnKtDPrZvkr8+Jqu71kUga5JQ@mail.gmail.com>

An ongoing pain point for the QGIS project was QGIS 3.x's reliance on the
Qt Webkit library. This library has long been deprecated by the Qt
maintainers, and was finally completely removed in Qt 6.

A direct consequence of this is that functionality which relied on Qt
Webkit has been dropped in QGIS 4.0. This includes:

- The print layout HTML item
- The HTML annotation item

This project will resurrect the print layout HTML item. The underlying
low-level changes will also facilitate a potential replacement for the HTML
annotation item, but this is out-of-scope for the current project.

Note that the functionality required for the QGIS HTML item is also
required for some third-party QGIS plugins, such as the DataPlotly plugin.
These plugins are currently broken on QGIS 4.x as a result.

Please see full details of the proposal at
https://github.com/qgis/QGIS-Enhancement-Proposals/pull/377. Discussion and
comments welcome!

This QEP will be submitted as part of the QGIS.org grant program

Nyall
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20260410/fa344088/attachment.htm>

From dvdkon at konarici.cz  Mon Apr 13 11:30:09 2026
From: dvdkon at konarici.cz (=?UTF-8?B?RGF2aWQgS2/FiGHFmcOtaw==?=)
Date: Mon, 13 Apr 2026 20:30:09 +0200
Subject: [Qgis-psc] QEP 338 announcement: SIP incremental builds
Message-ID: <efde39e2-e349-41c2-9782-52e425dfe4b7@konarici.cz>

Hi all,
I've proposed a new QEP [1]. As part of the QGIS grant programme, I'd 
like to refactor async code in QGIS (mainly QgsChunkLoader) to use the 
new features introduced in Qt6 (QPromise and QFuture methods).

David Ko?a??k

[1]: https://github.com/qgis/QGIS-Enhancement-Proposals/pull/379

From johannes.kroeger at wheregroup.com  Thu Apr 23 05:58:59 2026
From: johannes.kroeger at wheregroup.com (=?UTF-8?Q?Johannes_Kr=C3=B6ger_=28WhereGroup=29?=)
Date: Thu, 23 Apr 2026 14:58:59 +0200
Subject: [Qgis-psc] Existing plugin versions should not be marked with
 "security issues"
Message-ID: <bda7c8c4-e7a0-4bcb-8e8c-e34da07a4826@wheregroup.com>

Hi,

the plugins repository now *publicly* denounces plugins when its 
security scan has flagged something.
I use the word "denounce" aggressively here because as a plugin 
developer it is not nice to have plugins *which do not actually have 
security issues* brandished insecure with a BIG RED WARNING, losing 
trust of their users.

The rules are not perfect and at least for plugins where I have insight 
the false positive rate is higher than the correct flags...
For example it flags any requests.get() call without a timeout. The 
worst that can happen is a hanging QGIS, big whoop...
It also flags hashes as secrets and I fail to see how this is helpful 
for plugins that are *already published and accessible*.

Please revert the public display of this badge for now. If it is planned 
to publicly flag existing plugin versions, give developers ample time to 
review, fix or dispute the findings.

Sorry for the aggressive tone but this was unexpected and is very 
unpleasant to deal with.
I do think that the scanning and potential blocking of new versions is a 
great feature (thank you for it!) but the retrospective scanning with 
public display without human validation is not.

Cheers, Hannes



From julien.moura at oslandia.com  Thu Apr 23 06:44:49 2026
From: julien.moura at oslandia.com (Julien Moura (Oslandia))
Date: Thu, 23 Apr 2026 15:44:49 +0200
Subject: [Qgis-psc] Ownership transfer of QGIS-plugin-CI to QGIS.org
In-Reply-To: <c234d25e-e0f7-47cd-a570-037b1c3616ea@gmx.at>
References: <CAMtsY+ZCfeTUmvVUgSywLHV=zw6TfO_+PeeELDnBRYixYymHvg@mail.gmail.com>
 <3935b6ca-e65e-432f-a405-ae067d39db66@gmail.com>
 <c234d25e-e0f7-47cd-a570-037b1c3616ea@gmx.at>
Message-ID: <1a4202c3-4ed0-4421-8b58-cc4f814669cb@oslandia.com>

Hi htere,

I've created an issue to track on this topic: 
https://github.com/opengisch/qgis-plugin-ci/issues/394

Should we wait for an official decision or additional votes? Should we 
proceed?

Note we're actively working on the version 3 which aims, among other 
things, to fully integrate with Qt6 ecosystem.

Regards,
Julien

Le 27/01/2026 ? 12:06, Anita Graser via QGIS-PSC a ?crit?:
> +1 from me. Thank you for the initiative.
> regards
> Anita
>
> _______________________________________________
> QGIS-PSC mailing list
> QGIS-PSC at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
-- 
Oslandia 
<https://oslandia.com/?utm_source=email&utm_campaign=signature_oslandia&utm_medium=email> 
- Livre blanc pour migrer/hybrider son SIG 
<https://oslandia.com/livre-blanc-migration-sig-opensource/?utm_source=email&utm_campaign=signature_oslandia&utm_medium=email>

From johannes.kroeger at wheregroup.com  Thu Apr 23 09:40:23 2026
From: johannes.kroeger at wheregroup.com (johannes.kroeger at wheregroup.com)
Date: Thu, 23 Apr 2026 18:40:23 +0200
Subject: [Qgis-psc] [QGIS-Developer] Existing plugin versions should not
 be marked with "security issues"
In-Reply-To: <CAMLC-sCBUVS7-+7T6NxXVqBOg8zx8FrxibsZK98_1epV7_+NzQ@mail.gmail.com>
References: <bda7c8c4-e7a0-4bcb-8e8c-e34da07a4826@wheregroup.com>
 <CAMLC-sCBUVS7-+7T6NxXVqBOg8zx8FrxibsZK98_1epV7_+NzQ@mail.gmail.com>
Message-ID: <c5434be1c1e1751e9a9babc156c6bbb4@wheregroup.com>

Hi Lova,

thanks for the super swift response and for removing the badge from 
public view. I agree that it is properly the best approach to only show 
it to the owners and staff.

If a public badge is planned, I would suggest a long introduction period 
during which plugin authors have time to check and update their plugins 
before a badge is shown.
Maybe it would be enough only show it for new uploads and leave the old 
versions unchecked and unlabeled as before.

All the best, Hannes

Am 2026-04-23 16:03, schrieb Lova Andriarimalala:
> Hi Johannes,
> 
> Thanks for raising this issue.
> 
> the plugins repository now *publicly* denounces plugins when its
>> security scan has flagged something.
>> I use the word "denounce" aggressively here because as a plugin
>> developer it is not nice to have plugins *which do not actually have
>> security issues* brandished insecure with a BIG RED WARNING, losing
>> trust of their users.
> 
> 
> Could we just hide the badge from public view and show it only for the
> plugin author/maintainer and, eventually, for staff/superusers? This
> feature was requested by Etienne (
> https://github.com/qgis/QGIS-Plugins-Website/issues/267), but I think
> making it publicly visible wasn't really part of the scope in this case 
> (so
> sorry for that). We could always show it in public view later when the
> checks reflect user cases.
> 
> The rules are not perfect and at least for plugins where I have insight
>> the false positive rate is higher than the correct flags...
>> For example it flags any requests.get() call without a timeout. The
>> worst that can happen is a hanging QGIS, big whoop...
>> It also flags hashes as secrets and I fail to see how this is helpful
>> for plugins that are *already published and accessible*.
> 
> 
> That's correct, and we are aware that there are some teething problems 
> with
> the ruleset. I would be great if you could please raise an issue at
> https://github.com/qgis/QGIS-Plugins-Website/issues about which case 
> you
> think should be addressed by the checks.
> Please also note that we have just published a blog article about the
> plugin checks implementation at
> https://blog.qgis.org/2026/04/23/plugin-repository-security-enhancements/.
> 
> Best regards,
> 
> Lova Andriarimalala
> 
> 
> *QGIS Full Stack Developer   *
> *T *: +27(0) 87 809 2702          *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.*
> 
> 
> On Thu, 23 Apr 2026 at 15:59, Johannes Kr?ger (WhereGroup) via
> QGIS-Developer <qgis-developer at lists.osgeo.org> wrote:
> 
>> Hi,
>> 
>> the plugins repository now *publicly* denounces plugins when its
>> security scan has flagged something.
>> I use the word "denounce" aggressively here because as a plugin
>> developer it is not nice to have plugins *which do not actually have
>> security issues* brandished insecure with a BIG RED WARNING, losing
>> trust of their users.
>> 
>> The rules are not perfect and at least for plugins where I have 
>> insight
>> the false positive rate is higher than the correct flags...
>> For example it flags any requests.get() call without a timeout. The
>> worst that can happen is a hanging QGIS, big whoop...
>> It also flags hashes as secrets and I fail to see how this is helpful
>> for plugins that are *already published and accessible*.
>> 
>> Please revert the public display of this badge for now. If it is 
>> planned
>> to publicly flag existing plugin versions, give developers ample time 
>> to
>> review, fix or dispute the findings.
>> 
>> Sorry for the aggressive tone but this was unexpected and is very
>> unpleasant to deal with.
>> I do think that the scanning and potential blocking of new versions is 
>> a
>> great feature (thank you for it!) but the retrospective scanning with
>> public display without human validation is not.
>> 
>> Cheers, Hannes
>> 
>> 
>> _______________________________________________
>> 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
>>