you can always start from main, basically starting point is essentially main without opinions
you can always start from main, basically starting point is essentially main without opinions
XI actually view that the startingpoint's point is so that you don't have to duplicate the effort. Since you set FROM as an uBlue image, you get everything included in that. Since the starting point is created for the sole purpose of customizing the uBlue images, it should be easy to just add a couple of packages.
C...
the furthest upstream Ublue image is Main
the furthest upstream Ublue image is Main
XIt serves essentially a completely different purpose for the end-user.
Xyes?
Bdefine end-user
CIf you set FROM as the furthest upstream Ublue image with the absolute minimum added to it
then you are setting it to Main. You are bypassing starting point entirely and using Main.
then you are setting it to Main. You are bypassing starting point entirely and using Main.
CThe only thing starting point could do to add less is use the upstream Red Hat image
Bbecuase for most ublue end users starting point wont even be a blip, for those that it will they will be tinkers for whom using it wont mean a thing of difference between using it or going and forking main
CWhich would just be using the Red Hat image instead of Ublue
Xsomebody just wanting to install fedora silverblue on their computer who wants to have ublues autoupdates / drivers and other tweaks
CThey rebase to Main, or the QoL downstream.
Band if you wanna go into that indepth tinkering you should think about going to upstream
Bmost such somebodies will go for main
Bor fork main and remove those few bits that they dont want, starting point makes no sense unless you are tinkerer but at that point you are likely to want to either fork main if you wanna go that indepth or go upstream in this case actual fedora silverblue and pull in ublue changes you like
XThey do, but ahh, then they learn a bit about containers, and want to add some of their own packages there, host a bit of their configuration inside the os container, maybe install and SDDM theme by including it in their container. Now they've got to create their own container image. What's better? An image made specifically for that purpose, or an image made for the purpose of including the common uBlue QoL tweaks being a template on the side.
Bthen they fork main and build on that
C? ^^^
That's not how inheritance works
That's not how inheritance works
Bmain is specifically built to build uppon
C^
XStarting point is not intended to be an image to consume, it shouldn't do anything. It's a starting point for somebody to create their own image.
CSo you want to specifically create the only un-bootable image by breaking the template so it is a better abstract template
Bmain serves the same pupose
Blets break down the architecture as it seems you dont understand it(sorry if im wrong)
Bon the top of it is upstream fedora image which is completly bare base image
MI think we could all take a beat here as many seem to be talking past each other
Bthen ublue makes it slightly opinionated ublue main image on top of which all other images are build uppon
XWell excuse me but I didn't know that before I made the starting point repository as both the graph that I made and everyone agreed to, the documentation, and my intuition said otherwise. I made a huge fucking mistake and now I'm stuck in a salty boredom-fueled conversation with people I try my best to respect.
XIt's not really an image, it's a template.
Bmain is a template
CAll Ublue images are image templates and vice versa afaik
MOkay. We’re stopping here
XI think I could go shove my face in a pile of snow rn. Read my arguments and respond to them, please don't just say
but main is a template too. That's not my point.MTo clarify. main is a template repo. @hermmm goal was to create a repo that is similar to main but for creating new ublue flavors. Both serve a purpose both are distinct. This isn’t a place to get heated we’re all here to build stuff
MIf conversations get heated we need to slow down and take a break
MWe can discuss the implications of if we need a new repo or not but for now I’m going to keep this channel on ice as I’m out and can not thumb type fast enough
BWhat im trying to say is that it makes little sense to use startingpoint repo when main is already a thing
M
I've removed slow down and re-enabled sending for this channel. I want to leave a signpost reminder - we're a very small (less than 100 people still!) but passionate bunch. Lets make sure we keep conversations civil in chat. If you find yourself getting frustrated or repeating yourself continuously, or find yourself getting upset it's an open source community project and taking a beat to reset is encouraged - nothing wrong coming back to a conversation in a few mins, hours, or even days.This project moves fast and we're going to make a series of changes that move in lots of different directions while we find the path forward. I know Jorge and I appreciate you all for coming in here and bringing your experiences and opinions - thank you all
M
Jcc @.jstone ^
Xhey uhh @j0rge i'm making & maintaining the https://github.com/ublue-os/images-website and i just did a few updates to make it a full uBlue frontpage
i was just bout to push to show yall the changes but i appear to not have write access to the repo that i made...
i was just bout to push to show yall the changes but i appear to not have write access to the repo that i made...
GitHub
Contribute to ublue-os/images-website development by creating an account on GitHub.
Jwhat's your github username?
Xid?
Xi'm the only person who's ever commited to that repo
JI need to add your permission explicitly
Jeinhr or something?
Xahh username, EinoHR
Jok you should be fine
Xi'll be changing that in a while though, is it username-based or account-based?
Jaccount based, it's per repo now instead of orgwide
Xdid you see my issue on the mkdocs website?
