Hi everyone.
I'd like to start a discussion about making KDE/Kubuntu more user friendly, but first things first.
*The problem
Imagine an average Linux user. He/she (typically) has a laptop/tablet/phone and some sort of router with WiFi. So this is a home network - simple and convenient for most of home users. Next level would be some sort of file server/NAS box at home for content (music, family photos, videos) or for work (coding, book writing, etc.). With NAS/File Server or without it we have to share some content over the network. Now let's look from Kubuntu point of view. The Dolphin has the ability to browse the network and recognize most popular sharing protocols - SMB/CIFS, NFS, FTP, Apple's, via SSH and few more. At least from my own experience this functionality is so limited/unfinished from end user's perspective - I can browse my network shares, I can put as bookmarks in the left panel of Dolphin, but that happens with very different degree of success - i.e., I can see a NFS share but I cannot get in it (ACL is fine, I triple checked). The various issues with Samba shares.... All HOW-TOs say that I have to put an entry to fstab. OK, I did that for NFS share and all my problems have gone. Hurray!
But there is one question which still bothers me - why not to make this "fstab" step an integral part of browsing network in Dolphin ? Imagine, you came to the place in the network and you want it to be a permanent "bookmark" - you right-click on it and say "make it permanent mount" (or similar) which could lead to a dialog for options (i.e. auto/noauto, etc.) before saving it.
I understand that power users are able to make changes in the fstab first and then finish it elsewhere (i.e. Dolphin). But why not to make it easier ? Even professional linux users/admins would save time in such cases.
Imagine a user who just installed Kubuntu and wants Amarok play his/her music from NFS share on OpenMediaVault - it doesn't work even if you somehow managed to "bookmark" NFS in the Dolphin. Then that user spends few evenings searching for a solution, changing fstab, making mistakes and having to restore the fstab due to mistakes. Finally he/she gets a NFS share mounted/available under Devices in Dolphin. And finally Amarok recognizes mouthed share.
One good thing happens then - he/she learns something new . But the learning shouldn't be started this way if one wants it to be comprehensive and holistic. Of course, I might be missing something, some technical difficulties or perhaps IT architecture of Linux/KDE/Kubuntu doesn't support that.
The question
Is it worth to start feature request at KDE/Dolphin/Kubuntu developers ?
Regards
Artūras
I'd like to start a discussion about making KDE/Kubuntu more user friendly, but first things first.
*The problem
Imagine an average Linux user. He/she (typically) has a laptop/tablet/phone and some sort of router with WiFi. So this is a home network - simple and convenient for most of home users. Next level would be some sort of file server/NAS box at home for content (music, family photos, videos) or for work (coding, book writing, etc.). With NAS/File Server or without it we have to share some content over the network. Now let's look from Kubuntu point of view. The Dolphin has the ability to browse the network and recognize most popular sharing protocols - SMB/CIFS, NFS, FTP, Apple's, via SSH and few more. At least from my own experience this functionality is so limited/unfinished from end user's perspective - I can browse my network shares, I can put as bookmarks in the left panel of Dolphin, but that happens with very different degree of success - i.e., I can see a NFS share but I cannot get in it (ACL is fine, I triple checked). The various issues with Samba shares.... All HOW-TOs say that I have to put an entry to fstab. OK, I did that for NFS share and all my problems have gone. Hurray!
But there is one question which still bothers me - why not to make this "fstab" step an integral part of browsing network in Dolphin ? Imagine, you came to the place in the network and you want it to be a permanent "bookmark" - you right-click on it and say "make it permanent mount" (or similar) which could lead to a dialog for options (i.e. auto/noauto, etc.) before saving it.
I understand that power users are able to make changes in the fstab first and then finish it elsewhere (i.e. Dolphin). But why not to make it easier ? Even professional linux users/admins would save time in such cases.
Imagine a user who just installed Kubuntu and wants Amarok play his/her music from NFS share on OpenMediaVault - it doesn't work even if you somehow managed to "bookmark" NFS in the Dolphin. Then that user spends few evenings searching for a solution, changing fstab, making mistakes and having to restore the fstab due to mistakes. Finally he/she gets a NFS share mounted/available under Devices in Dolphin. And finally Amarok recognizes mouthed share.
One good thing happens then - he/she learns something new . But the learning shouldn't be started this way if one wants it to be comprehensive and holistic. Of course, I might be missing something, some technical difficulties or perhaps IT architecture of Linux/KDE/Kubuntu doesn't support that.
The question
Is it worth to start feature request at KDE/Dolphin/Kubuntu developers ?
Regards
Artūras
Comment