NLinked it here:
N
NYeah, there is no guarantee of good internet and I was told in the speaker guide to have an offline form of my presentation.
Jexport a PDF from gdocs, no need to mangle it with libreoffice
NI'm so dumb. Yeah, I could've done that.
NI was also having issues embedding a video which I surprisingly had an easier time doing with libreoffice.
N@j0rge I might have some time this morning before I leave to reupload it as a Google presentation.
NIf that would be easier.
Jthe animations are what's going to slow you down
Nare you reviewing the Libreoffice one?
JI was
JI installed libreoffice for you, in case anyone ever doubts my dedication to this project
Nanimations definitely will, I do think that we have a lot of information on each slide regardless though.
Jyeah but you don't have to read each bullet to them
Jhikari's picture is brutally awesome
Jand yours makes me want to clean up my theater room lol
NXD
NI can do away with the animations if you think that will improve the speed of the presentation
NI still think the deck might be too long.
JI mean it's up to you
NI'm just having a hard time cutting anything without making it feel incomplete.
Jlike for the ones where it's like "things we need from fedora" you can just be like "here are all the things we're working on with fedora right now
Ntrue! that would be a better way to phrase that.
Jand the homebrew slide can be like 10 seconds, distro people won't care abou that
Jand the charts you don't have to explain, it just shows "we track this stuff", you don't need to go into the details on all of them other than they're going up
NI think you are right that we should remove the animations.
NWill get me to not read directly off the slides either.
Jright so for this one
J
Jjust cover the three main bullets, you don't need to read the little ones to them
J"One of our biggest benefits is the jank is in CI instead of the client, this leads to better UX"
J"We also like that all you need is podman, git, and a registry."
J"And we also think that speed is measured by developer efficiency."
Jnext slide.
Jthey'll read along as you hit each major point
N@j0rge do we have a more updated pulls chart?
NI see it only goes through 5-19
AWould be good to start collecting some info now that rechunk is getting used for some images. Might make, dare I say it, rpm-ostree bearable speedwise
AUnless you layer
NLocal layering will always slow things down, not sure we can do anything about that.
AYeah but right now updates take 5-20 minutes depending on download speed
AWithout layering
AHopefully bootc will help with that
JJif anyone asks about the slope it's because we trimmed the amount of images we make, so a bunch of our images have pull numbers that will never grow again
Jbut bazzite is still climbing heavily
Ahttps://github.com/hhd-dev/rechunk/issues/2 I also made this issue to track quirks
GitHub
Lets use this issue to track quirks inherent to booting an OCI image. Hopefully, when this issue closes it will be possible for someone to boot an image made with FROM fedora:40 First lets begin wi...
AHopefully colins bites and can help
Jsubbed
