Re: KDE Gear projects with failing CI (master + stable) (11 August 2026)

On Wednesday, 12 August 2026 21:36:04 Central European Summer Time Nate Graham 
wrote:
> On 8/12/26 1:20 PM, Ben Cooksley wrote:
> > Applications should be *strongly discouraged* from requiring anything
> > other than released Frameworks as it increases the barrier to
> > contributing to them from "install distro packages and build app XYZ" to
> > "install distro packages, build all frameworks and then build app XYZ"
> 
> It also breaks nightly Flatpak builds, since there's no nightly Flatpak
> runtime yet.

How many of those do we really have though, and how many of those actually 
need unreleased Frameworks and can't also support the previous release?

Cases like qrca or calindori that we just fixed had this not because they 
needed it but because it happened to be done that way for frameworks that 
aren't part of the runtime.

> Though if we had that, the app contribution docs for a drive-by
> contributor could be collapsed into "run this flatpak-builder command".
> For the past few months I've been building and testing changes to KDE
> apps by building them as Flatpaks, and it's actually been a really nice
> experience overall.

Absolutely! Throwing new app contributors needlessly down the kdesrc-build 
rabbit hole is not an ideal experience, we can do a lot better. See attached 
screenshot as a sneak peek on an Akademy talk demo that'll hopefully work, 
pushing this even further :)

Regards,
Volker

-----BEGIN PGP SIGNATURE-----

iHkEABECADkWIQQAnu3FVHA48KjZ07R/lszWTRLSRwUCan1ZVxsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMSwyLDIACgkQf5bM1k0S0kcTYgCfdrg0zJRKaLKCWYSLDhkA
UBKrQJYAnijRkeKAV3QdYEbk9ATFeqT8smGA
=NQHN
-----END PGP SIGNATURE-----