In #211 we came up with two potential approaches for improving the installer and live sessions (that ticket also includes goals for this initiative).
Since we've agreed that either of these approaches seems acceptable from a workstation perspective, the next step is to go over what would be required to implement each one, and then potentially reach out to relevant parties to discuss the proposals.
gnome-initial-setup
Mockups
Does the following sound right? Are there any steps that are particularly easy/difficult?
Both the double and triple session options would require the following changes:
In addition to the "both approaches" changes, the double session would require the following:
In addition to the "both approaches" changes, the triple session would require the following:
I know this is mostly focused on GNOME, but I think @appadeia would also be interested in this for KDE (as they are working on kiss as part of improving Fedora KDE in the same way).
kiss
From my own perspective, I think either the "double session" or "triple session" model makes sense. The "double session" model has the benefit of being more broadly reusable for other spins, while the "triple session" model provides a more "pure desktop" live environment experience.
The key functional difference between those approaches is that, in the double session, the user doesn't go through input source configuration before starting the full live session.
I think the advantage of the triple session approach is that it requires fewer anaconda changes.
I don't particularly like having this ticket sitting around not doing anything, but I'm not sure what to do with it. Maybe I should file an issue against anaconda with the details...
Metadata Update from @aday: - Issue tagged with: pending-action
Removing pending-action - unclear what role these design concepts have given Anaconda's move to Patternfly.
Metadata Update from @aday: - Issue untagged with: pending-action
Anaconda is being redesigned and I'm participating in discussions around that. I don't think we need this ticket any more.
Metadata Update from @aday: - Issue close_status updated to: Won't fix - Issue status updated to: Closed (was: Open)
My top ask would be to make sure the new design allows both language and keyboard layout selected to be disabled via the existing config file, so that we can move them to before the live session starts, rather than handling them later.
Log in to comment on this ticket.