if i archive my repo, would that make the ublue-os version "upstream"?
if i archive my repo, would that make the ublue-os version "upstream"?
J@KyleGospo bootc did a 0.1 release, I mailed walters to ask if he plans on putting it in F39. I think we should add it to the base images.
JI am not sure what happens
Bme neither lol
Jbut we can look at disconnecting them, I think we'll be fine
Bfor the workflow it seems nicer to have them disconnected. then i can fork the ublue-os one and work on it like any other, from my fork on bobslept. if you know what i mean
Bbut for now it works
Jright
Bmaybe @turbwroan could test some images out, he has a framework right? We currently don't ship the just commands for kargs yet
Bbut they should be already set when you rebase on your framework 
Jyeah
JI think a custom.just in here just for frameworks is the way to go for now
Jor in config, not sure if device specific stuff should go there, but we can always move them there later.
Jworking in github on this wifi is a no op I'm just going to file them as issues.
Bi will copy the just command from bluefin-framework and ship it via custom.just like we do there
Bgood solution for now
Jindeed
J
Jbeautiful, they're already on the images page
Bsweet 
Jheh we're going to need to spend some time on that image generator to start sorting them better or something, haha.
Btrue that
B@j0rge can you ack the custom.just pr lol
Jon it
Bi've looked into delivering the backgrounds to silverblue the way bazzite does it. they are using copy based on $image_name but turns out all the other builds will fail because they have nothing to copy. that was a shame.
Bdelivering that stuff via rpm with a config repo could work but is quiet a lot of work
Jyeah ideally as people use them they'll just take ownership of fixing them up
Jthis is amazing, thank you!
Jwe should do a nice blog post later on, heh
Bthing is, they check in a run command to act on specific image. but inthere we cannot do a copy. what we can do is copy global to /tmp and copy it from there in run command. as /tmp is removed anyway it wont hurt other images.
Bbut not sure if that is "acceptable"
XThe docs is a non-issue since other README's are already pulled there, could reutilize the same codreApparently #
bluefin and #
bazzite README's are just exclusively hosted on the website and not pulled in dynamically. This isn't really an option for the modules since code and docs should be updated in the same PR. @j0rge @marcoceppi is there a way to dynamically pull in contents for the mkdocs site from a different github repository?XThere's the mkdocs include plugin which I believe we use for the image list, but that would require a github action that pulls in the bling repo to the codebase?
XOk, I could do a parse checkout in deploy.yml, but can't test that effectively because to deploy I'd need mkdocs insiders...
Jyeah you can do an include, look in the history of the images page it should be in there.
J{{ external_markdown('https://raw.githubusercontent.com/ublue-os/bluefin/main/README.md', '') }}
XThanks!
J@beekabop feel free to bypass the merge protection when you need to, no need to slow down if people aren't around
Bi would like to add silverblue specific stuff. but the only way i can do that now is moving image specific things to /tmp first and then copy it back via the run command. Would that be oke or is that a big nogo
Bthat way i can do a bazzite trick of using
run if silverblue copy and enable stufBthe
copy files/$base_name will faill if there is no dir for that base_name
G@hermmm I might add a folder to startingpoint for custom modules, and some docs on how to do it
XI am doing the thing rn so don't touch anything.
GThe fetching? Cool
XI'll keep the modules directory but just have a README with the "Making modules" section there
GAh
XEverything at the same time
XGitHub
Premade layers of bling to consume for your own images - ublue-os/bling
Xoops I updated readme withot changing the default commit message, palm hit enter when reaching for mouse
XOk we have the same PRs (https://github.com/ublue-os/startingpoint/pull/135 & https://github.com/ublue-os/website/pull/445) ready for the next round of reviews!!
Xtries to look at contributors list for ppl to ping @j0rge would you detach the startingpoint repo from being a fork of ublue-os/base please https://support.github.com/contact?tags=rr-forks&subject=Detach%20Fork&flow=detach_fork, need to be an org admin