@j0rge I am following correctly? Current Universal Blue Initiatives Summary:
Immediate priorities center on bolstering infrastructure security through comprehensive SBOM (Software Bill of Materials) generation, image signing, and automated repository scanning. Concurrently, intensive Fedora 42 (F42) testing is underway to address stability.
Strategically, Universal Blue is being positioned as a manufacturing process rather than a monolithic product, empowering customized image creation. Reflecting this, the Bluefin image will adopt a pure image mode for F42, moving away from local package layering, and will utilize the Anaconda installer for official ISOs. Enhanced upstream collaboration with Fedora teams is formalized through regular meetings, focusing on atomic desktop advancements and tracking initiatives like the proposed F43 removal of Fedora Flatpaks.
Key technical developments involve evaluating uupd as a potential default update mechanism, standardizing on Titanoboa for liveCD builds, and prototyping Dragonfly for peer-to-peer (p2p) LAN updates. Ensuring rebase helper integrity between CentOS and Fedora streams is also crucial. Access to dedicated ARM hardware aims to accelerate GDX development.
Overall efforts focus on refining tooling, improving security posture, ensuring a stable F42 release, and strengthening upstream alignment.