On Wed, 2019-07-24 at 15:29 +0200, Jiri Eischmann wrote: > Kamil Paral píše v St 24. 07. 2019 v 13:37 +0200: > > On Tue, Jul 23, 2019 at 7:44 PM Ben Cotton <bcotton@xxxxxxxxxx> > > wrote: > > > https://fedoraproject.org/wiki/Changes/Anaconda_Reclaim_Disk_Space > > > > > > The Manual Partitioning screen supports all actions of the Resize > > > Disk > > > Space dialog, so it doesn't make sense to have two user interfaces > > > with the same functionality. > > > > The manual partitioning screen is also much more complex and > > therefore more difficult to use. For the common use case of > > installing Fedora alongside Windows (where you need to shrink the > > Windows partition), the simple dialog is/was great. Linux novice > > users might not be able to accomplish that in the manual partitioning > > screen. > > > > Just my personal opinion, I'm not trying to convince you to revert > > your plan. > > I second Kamil here. I've introduced hundreds of people to Fedora and > "I've got Windows on the disk and need to reclaim space" is by far the > most common scenario among Fedora novices and instead of giving them a > simple dialog we're sending them to the manual setup which I as a Linux > user for 15 years have problems to get oriented in. > Is it really such engineering overhead to keep that dialog there? Yeah...this is specifically why this screen exists: to not be as scary as the full-on custom partitioning screen. Or, you know...either of the *two* full-on custom partitioning flows we have now. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx