Anaconda Web UI requirement: Features for live session or installer #370

Closed
opened 2023-04-20 14:55:50 +00:00 by jkonecny · 2 comments

Based on these requirements https://pagure.io/fedora-workstation/issue/362#comment-847926:

  • Ability to connect Bluetooth input devices (likely through an assistant that is launched when no input is detected)
  • Ability to select the live session or installer (ideally in a way that is accessible and possible using Bluetooth input devices)
  • System status display while using the installer - at least to show the audio volume (for accessibility) and battery level

Our proposal:

These features are RFEs related to the net installation media or Live media with two environments (not implemented / proposed).

Our suggestion is to not follow these requirements for F39 or track them separately from Web UI proposal. First, these are not related to Web UI and second without the Live support of multiple environments (not planned yet) we have all this from the Live system already.

Questions:

  • Do Workstation SIG is fine with rejecting these requirements for F39 Web UI adoption proposal?
Based on these requirements https://pagure.io/fedora-workstation/issue/362#comment-847926: * Ability to connect Bluetooth input devices (likely through an assistant that is launched when no input is detected) * Ability to select the live session or installer (ideally in a way that is accessible and possible using Bluetooth input devices) * System status display while using the installer - at least to show the audio volume (for accessibility) and battery level **Our proposal:** These features are RFEs related to the net installation media or Live media with two environments (not implemented / proposed). Our suggestion is to not follow these requirements for F39 or track them separately from Web UI proposal. First, these are not related to Web UI and second without the Live support of multiple environments (not planned yet) we have all this from the Live system already. **Questions:** * Do Workstation SIG is fine with rejecting these requirements for F39 Web UI adoption proposal?
Owner

Yes, since you'll continue to run anaconda inside GNOME Shell there's no need to worry about these requirements. (These would be issues for a future standalone anaconda session.)

Yes, since you'll continue to run anaconda inside GNOME Shell there's no need to worry about these requirements. (These would be issues for a future standalone anaconda session.)
Owner

Metadata Update from @catanzaro:

  • Issue close_status updated to: Fixed
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @catanzaro**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
workstation/tickets#370
No description provided.