clay at claydoh.com
Sun Dec 30 17:58:19 UTC 2012
Alex Fiestas <afiestas at kde.org> wrote:
>On Saturday 29 December 2012 12:30:13 Scott Kitterman wrote:
>> I may be wrong, but I had always considered KDE to target both the
>> doesn't care much about computers and users that are more into them.
>> more advanced user is the reason that all of the customization
>Indeed customization is important, being able to manage groups from a
>so much since those users will not mind doing it from the CLI (and
>again it is
>something you hardly want to do).
>> While we should never enforce use of the GUI where it can be avoided,
>> should, IMO, also strive to enable people that don't like command
>> avoid it. When I say Linux to people one of their first reactions is
>> commonly that they don't want to have to open a shell and type lots
>> commands. The fact that I can honestly tell them that it's not
>> makes them much more comfortable with trying it out.
>For reaching this point (using the cli) in the case we are talking
>have yet to read a usecase that is not figurative or super cutting
>> Userconfig was developed as a kuser replacement. It was proposed to
>> it, but it never quite got to the top of the TODO list, so it's not
>> KDE SC.
>> As far as targets for your development efforts, I think the "About
>> module covers the basic case and you should try to encompass both
>> userconfig functionality in what you are doing. KDE SC already has
>> user management functions ("About Me" and kuser) and I don't think it
>> Of course, Rome wasn't built in a day and software isn't either, so
>> userconfig/kuser completely" may be a longer term goal, but I think
>> good one.
>> As far as the case for group related functions goes, I think it is
>> to be able to see a list of groups and membership in groups because
>> in group yyy" or "What users are listed as members of zzz" are
>> common troubleshooting/support questions. Personally, although I
>> edit /etc/group in vim on my servers, I use userconfig on Kubuntu
>> because it's harder to screw something up. Just because I can do it
>> hand, I prefer to take the safer route where I'm only
>> boxes and not editing directly.
>Can you tell me why are you messing with groups in your Kubuntu box? In
>server I can understand but in a desktop? Give me use cases !
>As a personal note, we (KDE) won't be able to move forward if we keep
>on our old user base of hardcore users, do you know what most sysadmins
>these days? Use osx. I wonder why.
>kubuntu-devel mailing list
>kubuntu-devel at lists.ubuntu.com
>Modify settings or unsubscribe at:
As a relatively "regular" user, I do have to agree for the most part. However, enough people use something like Virtualbox that needs some group editing. I may be wrong but I do not recall instructions there to do this using any method, just what group to add the user to. This is probably the only real life case where this is needed, but will make people howl when they discover that the gui tool is not there. Now I am one to try and figure out out but there are many who won't, will gripe loudly that Kubuntu sucks etc.
There are a fair number of people who do advanced things without using the advanced (cli) tools that this does need to be considered, perhaps.
Just my 1¢ though I am in agreement about a group administration gui not being needed by default.
Sent from my Android phone with K-9 Mail.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the kubuntu-devel