the bazzite testing branch has been baking for a week and the idea is they'll merge on friday
the bazzite testing branch has been baking for a week and the idea is they'll merge on friday
Hyeah and the motd can also utilize the libcolors.sh and libformatting.sh scripts so makes sense you wanted the just stuff first
R@j0rge Currently a hypothetical question - if I were to work on a cybersecurity spin of ublue (containing stuff like metasploit, burp suite, wireshark etc), would you be willing to accept that as an "official" ublue project?
Like animmutable image-based version of Kali Linux
Like an
JI'm kinda thinking pause on new images in the org and concentrating on some tech debt
Jand I kind of wish there were other orgs making images so it doesn't look like we're the only ones that can do this
Jlike, it's not looking like beyond is changing, still unsure about this kera thing (who's using it?), and we have cinnamon and another one that are out of band too
Jbazzifin were originally intended as hello worlds but kind of became "products"
RI'll probably move my images to their own dedicated org and start thinking of them as real projects sometime soon
JI thought about removing bluefin from the org but that's both bad and good.
Jand also this was supposed to be in Fedora for 38 so by now I think we were expecting there to be people doing this already
Jthen we had a long pause
Ti was thinking something similar when i posted the community image list on discourse. some of these images seem to be unmaintained or technically do not fit into our project
Ti know that's different than official
Tbut idk something i was thinking
Jwe never really got around to calling anything official
Tyea
FIdk if this fits your "security" goal, but secureblue exists:
https://github.com/secureblue/secureblue
So maybe you can help there too with your knowledge
https://github.com/secureblue/secureblue
So maybe you can help there too with your knowledge
Jwhat I for sure don't want to do is be the "come up with an idea and ublue will host it for you" because that's just running a SaaS and that's out of scope. Though we made an exception for like, working with an upstream, etc.
RYeah, this looks like a cool project, but it's more privacy focused, rather than the purple-team (attack/defend) focused image I'm looking to create.
FInterestingly, in their goal, it says security only
The following are not in scope for this project:
"Anything related to increasing "privacy", especially when at odds with improving security"
The following are not in scope for this project:
"Anything related to increasing "privacy", especially when at odds with improving security"
CStill a placeholder because the Kera developer is still refactoring it for contributions between freelance work and attempting to move from Turkey to Germany
NDo we know who maintains the other spins that we have? Like the ones with cinnamon? Are those upstream and we just build those?
Fsecureblue vs securepurple will be?
NLike the main images I know from upstream are Silverblue, Kinoite, Sericea, and CoreOS.
Jthe ones not in main are out of band
NBut I have seen on our full image list many more than that.
Joh and budgie will go away with the 38 cleanup because onyx did not exist at the time
NOh right Onyx as well.
FLxQT Ublue based image is worse than Fedora's Lazurite as an example
CLazurite is new
Jwe turned lxqt off
Fyes, just making an example on how unofficial images can be worse
Fespecially if they are not maintained
Jyeah, no one ever maintained that
NAhhh ok. That helps.
Jand some of them never need to be touched
Jlike cinnamon looks abandoned but it also only needs to be touched twice a year
NI see, so the supported ones would be in our build Ublue job on main.
Jthough latest tag seems out of date
NGitHub
OCI base images of Fedora with batteries included. Contribute to ublue-os/main development by creating an account on GitHub.
Tthats the one yeah
JJbut also no one is using it
Twe can have our own linux mint clone right here /s
NDo we think it might wise to cut down the amount of images we advertise if they are going unused / unsupported?
Jwe don't really advertise other than pointing people to the list
Jbut some of those are for sure worse than others
NRight, I just get concerned if we are pointing people to them and they have a bad experience, it reflects poorly on the project.
NJust food for thought, I don't think we need to make any immediate decisions around it.
JF38's EOL will force us to decide, so that won't be a problem until at least may
Jand for some of them you don't explicitly delete, we just don't bring forward. Like for Budgie we never brought it to 39, so it'll just get garbage collected