Change: Anaconda WebUI Fedora Atomic #3666

New issue

Closed

opened 2026-08-03 13:18:52 +00:00 by amoloney · 9 comments

amoloney commented

2026-08-03 13:18:52 +00:00

Owner

Switch the installer used by Fedora Atomic ISO images from the legacy GTK-based Anaconda installer to the new WebUI installer.

This aligns the installation experience of Atomic media with Fedora Workstation, KDE and Fedora Live Spins.

Owners, do not implement this work until the FESCo vote has explicitly ended.
When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the FESCo ticket policy and the Changes policy for more information.
If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update.

REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.

Switch the installer used by Fedora Atomic ISO images from the legacy GTK-based Anaconda installer to the new WebUI installer. This aligns the installation experience of Atomic media with Fedora Workstation, KDE and Fedora Live Spins. * [Change proposal](https://fedoraproject.org/wiki/Changes/Anaconda_WebUI_Fedora_Atomic) * [devel post](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/JFOZV37W2PV6BOIRGCFAGMBFIA7WALZF/) * [Discourse discussion](https://discussion.fedoraproject.org/t/f45-change-proposal-anaconda-webui-fedora-atomic-self-contained/197421) * Owners: @siosm @supakeen @kkoukiou **Owners, do not implement this work until the FESCo vote has explicitly ended.** When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the [FESCo ticket policy](https://docs.fedoraproject.org/en-US/fesco/#_ticket_policy) and the [Changes policy](https://docs.fedoraproject.org/en-US/program_management/changes_policy/) for more information. If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update. **REMINDER**: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the [Fedora Devel](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/) mailing list.

amoloney added this to the Fedora Linux 45 milestone

2026-08-03 13:18:52 +00:00

amoloney added the

self contained change

label

2026-08-03 13:18:52 +00:00

gotmax23 commented

2026-08-03 14:43:59 +00:00

Owner

@siosm @supakeen @kkoukiou (I don't know if Forge automatically subscribes you to notifications, so @-mentioning y'all manually)

I think this should be re-classified as a system-wide Change and have the rest of Change proposal sections filed out. We can still approve an exception for a late system-wide Change submission if getting this into F45 is important, but anaconda is a critpath package which means this should be System-wide per policy:

System-wide changes involve system-wide defaults, critical path components, or other changes that are not eligible as self-contained changes.

--- https://docs.fedoraproject.org/en-US/operations/changes_policy/#_system_wide_changes (EDIT: copy-pasted wrong link)

@siosm @supakeen @kkoukiou (I don't know if Forge automatically subscribes you to notifications, so @-mentioning y'all manually) I think this should be re-classified as a system-wide Change and have the rest of Change proposal sections filed out. We can still approve an exception for a late system-wide Change submission if getting this into F45 is important, but anaconda is a critpath package which means this should be System-wide per policy: > System-wide changes involve system-wide defaults, critical path components, or other changes that are not eligible as self-contained changes. --- https://docs.fedoraproject.org/en-US/operations/changes_policy/#_system_wide_changes (**EDIT**: copy-pasted wrong link)

bookwar commented

2026-08-03 14:46:39 +00:00

There are no updates needed for this change from the Anaconda side. The functionality has been developed and is available in the codebase.

Thus, this change does not have significant impact on Anaconda or on any other non-Atomic deliverables using it.

It is about switching the configuration of the Atomic image to use the WebUI, not changing the installer component.

There are no updates needed for this change from the Anaconda side. The functionality has been developed and is available in the codebase. Thus, this change does not have significant impact on Anaconda or on any other non-Atomic deliverables using it. It is about switching the configuration of the Atomic image to use the WebUI, not changing the installer component.

supakeen commented

2026-08-03 15:11:07 +00:00

Owner

Note that it is possible to implement this as a self-contained change (change the definitions for only the Atomic installer to include anaconda-webui and firefox). The way it is written in the change proposal with the rich provides/requires it feels more like a system-wide change even if it only affects specific non-blocking artifacts.

Nothing in Anaconda itself changes here, only the packages installed in the Atomic installer ISO environment.

Note that it is *possible* to implement this as a self-contained change (change the definitions for only the Atomic installer to include anaconda-webui and firefox). The way it is written in the change proposal with the rich provides/requires it feels more like a system-wide change even *if* it only affects specific non-blocking artifacts. Nothing in Anaconda itself changes here, only the packages installed in the Atomic installer ISO environment.