[Qgis-psc] Blacksmith runners / macOS builds
Tim Sutton
tim at qgis.org
Tue Nov 10 08:47:32 PST 2026
Hi
For me I would be -1 to introduce 'ads' into the qgis/QGIS code base - we
have other spaces for that and we always tried to keep QGIS code base
'clean'. Why dont we just give them a sustaining membership and they get
all the visibility of other sustaining members? They will get better
exposure that way than in the readme too I think...
I will be happy to write up something for the blog and put it on the news
feed etc. We should get in the habit anyway of promoting our new sponsors
more (unless they want to remain incognito).
Regards
Tim
On Sat, Nov 7, 2026 at 3:50 PM Andreas Neumann via QGIS-PSC <
qgis-psc at lists.osgeo.org> wrote:
> Hi Matthias,
>
> I am fine with listing them with their logo in our readme or elsewhere -
> but they shouldn't be called "sponsors" but rather "in-kind donors" - we
> cannot have sponsors (for tax reasons).
>
> Andreas
>
> On 2026-11-06 14:41, Marco Bernasocchi via QGIS-PSC wrote:
> > Hey Matthias,
> > Number 2 was already discussed and we see no problem with that.
> >
> > We hadn't discussed 1 but i see no issue there either.
> >
> > Any other opinions from the psc?
> > Cheers
> >
> > Marco Bernasocchi
> >
> > QGIS.org Chair
> > OSGEO.org VP Europe
> > OPENGIS.ch CEO
> > http://berna.io
> >
> > On Fri, 6 Nov 2026, 09:38 Matthias Kuhn, <matthias at opengis.ch> wrote:
> >
> >> Dear PSC,
> >>
> >> Thanks a lot for the positive feedback. I'd like to start this as
> >> soon
> >> as possible, migrate a few workflows, and then write a blog post in
> >> a
> >> couple of weeks when we have results to present.
> >>
> >> They asked if also (cited):
> >>
> >> 1. we have a sponsor logo (attached) - would you be ok with placing
> >> it
> >> in your project README and image on your website?
> >> 2. would you be alright with us talking about our partnership on
> >> socials/blogs?
> >>
> >> I quickly checked how the others integrate the logo in the readme
> >> (e.g. celery): https://github.com/celery/celery#sponsors
> >>
> >> Sorry for the additional request; I forgot to include this in the
> >> original email.
> >> I hope that this can be confirmed quickly.
> >>
> >> Thanks a lot
> >> Matthias
> >>
> >> On Thu, Nov 5, 2026 at 12:14 PM Marco Bernasocchi <marco at qgis.org>
> >> wrote:
> >>>
> >>> Hey Matthias,
> >>> Sorry, it took a bit longer on my side.
> >>> we discussed this in the PSC and agree that we should go forward.
> >>> As soon as we finalise the test phase and the system proves it
> >> works, we can write the blog post for them.
> >>> Thanks a lot for taking care of this.
> >>>
> >>> Cheers
> >>> Marco
> >>>
> >>> On Fri, 9 Oct 2026 at 09:44, Régis Haubourg via QGIS-PSC
> >> <qgis-psc at lists.osgeo.org> wrote:
> >>>>
> >>>> Hi Matthias, thanks for pushing and testing this idea.
> >>>>
> >>>> In fact, listening at Jürgen yesterday in the conference, I
> >> realised that github runners are also a limiting factor for a
> >> OSGEO4W port to CI builds.
> >>>>
> >>>> As Blacksmith offers an open source partnership, I strongly
> >> support your proposal too as away to unlock our current github
> >> limitations fast and efficiently.
> >>>>
> >>>> As for long term plans to own a sovereign infrastructure,
> >> Blacksmith is a US based company, so it doesn't change this
> >> situation, but it would allow us to size more what kind of
> >> infrastructure we require.
> >>>>
> >>>> Best regards
> >>>> Régis
> >>>>
> >>>>
> >>>>
> >>>> On 09/10/2026 07:17, Alessandro Pasotti via QGIS-PSC
> >> <qgis-psc at lists.osgeo.org> wrote:
> >>>>> Hello Matthias,
> >>>>>
> >>>>> This looks a very good idea to me.
> >>>>>
> >>>>> Thank you for exploring this opportunity!
> >>>>>
> >>>>>
> >>>>> ---
> >>>>> Alessandro Pasotti
> >>>>> QCooperative: www.qcooperative.net [1]
> >> <https://www.qcooperative.net>
> >>>>> ItOpen: www.itopen.it [2] <http://www.itopen.it>
> >>>>>
> >>>>> Il ven 9 ott 2026, 07:07 Matthias Kuhn via QGIS-PSC <qgis-
> >>>>> psc at lists.osgeo.org <mailto:qgis-psc at lists.osgeo.org>> ha
> >> scritto:
> >>>>>
> >>>>> Hi Martin,
> >>>>>
> >>>>> Yes, running tests sounds reasonable too.
> >>>>> So far the build itself was taking too long and I didn't
> >> want to
> >>>>> increase this even more.
> >>>>>
> >>>>> Matthias
> >>>>>
> >>>>> On Thu, Oct 8, 2026, 22:45 Martin Dobias
> >> <wonder.sk at gmail.com
> >>>>> <mailto:wonder.sk at gmail.com>> wrote:
> >>>>>
> >>>>> Hi Matthias
> >>>>>
> >>>>> That all sounds good to me. And maybe we could also
> >> start to run
> >>>>> auto tests for mac plarform in CI? It seems quite a few
> >> are
> >>>>> broken on macOS, but we don't really know about that
> >> :-)
> >>>>>
> >>>>> Cheers
> >>>>> Martin
> >>>>>
> >>>>>
> >>>>> On Thu, Oct 8, 2026 at 1:59 PM Matthias Kuhn via
> >> QGIS-PSC <qgis-
> >>>>> psc at lists.osgeo.org <mailto:qgis-psc at lists.osgeo.org>>
> >> wrote:
> >>>>>
> >>>>> Dear PSC,
> >>>>>
> >>>>> We are currently producing macOS builds entirely
> >> within our
> >>>>> CI/CD pipelines (github workflows/actions). With
> >> this
> >>>>> approach, we can create dmg installer packages for
> >> currently
> >>>>> supported QGIS 3 and QGIS 4 versions for releases,
> >> pull
> >>>>> requests, and branch (latest) builds.
> >>>>>
> >>>>> For QGIS 4, one important component is currently
> >> missing: we
> >>>>> cannot build QtWebEngine (HTML rendering) because
> >> building
> >>>>> it takes over six hours (the maximum threshold for
> >>>>> workflows) on the (free-tier) github runners. This
> >>>>> limitation is significant, and several tickets
> >> request its
> >>>>> addition (for QGIS itself and for plugins like
> >> dataplotly).
> >>>>> We only need to rebuild this component when there's
> >> an
> >>>>> update, so it won't add time to every pipeline
> >> build.
> >>>>> However, we must ensure it builds once every few
> >> days.
> >>>>>
> >>>>> I recently was in touch with blacksmith <https://
> >>>>> www.blacksmith.sh/ [3]> which is an independent
> >> provider of
> >>>>> runners for github actions. They have very
> >> performant
> >>>>> runners, I was able to build QtWebEngine in less
> >> than 1.5
> >>>>> hours (compared to more than 6 hours on github).
> >> They would
> >>>>> allow us to use their infrastructure as part of
> >> their open-
> >>>>> source engagement and ask for a blog post in
> >> return.
> >>>>>
> >>>>> Blacksmith would also help us reduce CI time for
> >> other
> >>>>> workflows either by moving some workflows over to
> >> blacksmith
> >>>>> or by reducing the load on github actions cache.
> >> This would
> >>>>> significantly improve the developer experience.
> >>>>>
> >>>>> One remaining challenge will be providing mac
> >> packages for
> >>>>> Intel devices. Blacksmith does not offer this
> >> platform.
> >>>>> Apple stopped selling Intel macOS devices in
> >> mid-2023. Apple
> >>>>> will officially support Intel devices until 2028,
> >> after
> >>>>> which support will be reduced, ending entirely in
> >> 2030.
> >>>>> Offering QGIS 4 support for Intel devices would be
> >> nice, but
> >>>>> we would need to find another interim solution for
> >> the next
> >>>>> 2-4 years.
> >>>>>
> >>>>> I'd like to propose that we create an account with
> >>>>> blacksmith, install its github app and move the
> >> macOS arm64
> >>>>> workflow and potentially a few others over to
> >> blacksmith. If
> >>>>> this goes well and improves the situation, I'd like
> >> to write
> >>>>> a blog post about our experiences as part of this
> >> agreement.
> >>>>> This will improve the situation for macOS packages
> >> for arm64
> >>>>> (i.e. for all mac devices sold in the last 3 years
> >> and more
> >>>>> sold since 2020). For Intel, we would continue to
> >> build
> >>>>> packages but without QtWebEngine until we find a
> >> suitable
> >>>>> solution.
> >>>>>
> >>>>> Thanks a lot and best regards
> >>>>> Matthias
> >>>>>
> >>>>> --
> >>>>> <https://conference.qgis.org>
> >>>>>
> >>>>> *Matthias Kuhn* - Mr. Noproblemo
> >>>>>
> >>>>> CTO | Co-Founder
> >>>>>
> >>>>> email
> >>>>> matthias at opengis.ch <mailto:matthias at opengis.ch>
> >>>>> www
> >>>>> opengis.ch [4] <https://opengis.ch>
> >>>>>
> >>>>> linkedin
> >> <https://www.linkedin.com/company/opengisch/>
> >>>>> mastodon <https://fosstodon.org/@opengisch>
> >> github <https://
> >>>>> github.com/opengisch/ [5]>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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 [6]>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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 [6]>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> QGIS-PSC mailing list
> >>>>> QGIS-PSC at lists.osgeo.org
> >>>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
> >>>>>
> >>>> _______________________________________________
> >>>> QGIS-PSC mailing list
> >>>> QGIS-PSC at lists.osgeo.org
> >>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
> >>>
> >>>
> >>>
> >>> --
> >>> Marco Bernasocchi
> >>>
> >>> QGIS.org Chair
> >>> OSGEO.org VP Europe
> >>> OPENGIS.ch CEO
> >>> http://berna.io
> >
> >
> > Links:
> > ------
> > [1] http://www.qcooperative.net
> > [2] http://www.itopen.it
> > [3] http://www.blacksmith.sh/
> > [4] http://opengis.ch
> > [5] http://github.com/opengisch/
> > [6] http://lists.osgeo.org/mailman/listinfo/qgis-psc
> > _______________________________________________
> > QGIS-PSC mailing list
> > QGIS-PSC at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/qgis-psc
> _______________________________________________
> QGIS-PSC mailing list
> QGIS-PSC at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>
--
*Tim Sutton*
QGIS Project Steering Committee
tim at qgis.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20261110/cb0a1ac4/attachment-0001.htm>
More information about the QGIS-PSC
mailing list