As we presented to you we already have an idea for improvements for the current Web UI. This issue is about:
Enable users to select partitioning scheme (LVM, BTRFS, plain partitioning)
Our proposal:
We know that users have a strong preference about what technology will be used for the partitioning, we would like to introduce partitioning scheme selection to users. They can select what partitioning scheme they would like to have. However, we are not sure about the priority of this for the Fedora Workstation SIG.
Just a note, if we are going with the proposal of mountpoint assignment (https://pagure.io/fedora-workstation/issue/375) then we will provide users a way to change the partitioning (harder way).
Questions:
Could we please get this answered or proposed on a meeting?
Metadata Update from @catanzaro: - Issue tagged with: meeting-request
For desktops, I think it can be postponed to a later version. Most custom/manual partitioning users depend on system upgrade. Is it a hassle to have to install Fedora n-1, to have access to current manual partitioning UI, then upgrade to Fedora n? Sure. I think if we admit that it's both a little tedious and a necessary consequence of rollout due to resources - it's OK.
My take on this is similar to separate /home
So I don't see any need for this type of question on the guided path and would like any future addition of this be off the main path or even completely disabled for the Workstation installer.
Great point. Thanks for your opinions @otaylor and @chrismurphy .
Great summary, @otaylor - I agree with this.
We know that users have a strong preference about what technology will be used for the partitioning
I'm not entirely convinced by this statement and feel that it needs some scrutiny/nuance. Some users likely have preferences for particular partitioning schemes, but which users and what are their motivations and requirements?
Metadata Update from @catanzaro: - Issue untagged with: meeting-request
I think the working group agrees on the following:
(This is more or less what Owen said above.)
Metadata Update from @aday: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.