Garrett LeSage

Here's how it would look like within Cockpit, using a PF4-like [full page editing pattern](https://www.patternfly.org/v4/components/inline-edit/design-guidelines/#full-page-edit) (but with the editing action in the top-right, consistent with the rest of our card...

I just realized that the list has to be more than just deployments if we're going to have the latest available there as well. Deployments are what's on the disk....

## Retrofit Since having the status makes sense... why not retrofit this into something that resembles the PackageKit software updates?  ## Editing source And editing the OSTree source would...

Finally looping back around to dialogs, as this is all so we can detangle the odd dialog. :laughing: ## Add repo  ## Edit repo 

I guess an error would go in the status area, unless it's contextual based on an action.  Regarding this error specifically: - Will updating still work with this...

Here's a higher def version I made in Penpot. - I've reordered things, in order of uniqueness and importance. - It now has headings, as it should. - I dropped...

Deployments and updates menu would have (at least) two items, clean up and reset:  Clean up action would have a modal with things to clean up, with non-interferring...

https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md#existing-work > Specifically as of today, this functionality is exposed in: > > - `rpm-ostree ex-container` > - `rpm-ostree rebase --experimental $containerref` HOWEVER, according to https://coreos.github.io/rpm-ostree/container/ it's even easier, perhaps?...

Jorge Castro made a video to demonstrate this yesterday: https://www.youtube.com/watch?v=X8h304Jp9N8

OK, I *think* all we'd need to support it in cockpit-ostree _right now_ is a toggle (off by default) to support `--experimental` during rebases. And then remember the experimental state...