As more ublue-os images are added, it's becoming increasingly clear that we should reorganize our images to reduce duplication of work and increase sharing of commonly used packages and pat...
We could do that, I'd suggest we start with a branch for the changes. Alternatively, start a new repo and when ready archive this one with a new readme
I think we should steer the current base towards being the startingpoint image (as proposed in my graph). Strip it down, and make it a custom image starting point intended to be based on the -main, with more customizability in mind.
I think the easiest thing to do would be to create a ublue-os/mainublue-os/main repo so that we have a clean slate to play with, and ensure that cosign is set up
The scope should be A) one parameterized Containerfile for multiple Fedora releases and DEs B) limit the Containerfile defintion to essential rpm-ostree installs with QoL package inclusion/exclusion lists. This will give downstream maintainers a simple path for consuming images and ensuring that they're only adding features and not taking them out
I think anyone submitting package inclusion requests should be asking themselves if what they're requesting will be generally useful for everyone and won't benefit just one subset of users. If the feature is too specific, then it should instead exist in a downstream image