![](https://seccdn.libravatar.org/avatar/ed5b1491aa79201a8eaf93bf57193584.jpg?s=120&d=mm&r=g)
On 05/24/2012 05:25 AM, Andreas Jaeger wrote:
Let's start a new thread to look a bit more at different roles.
I saw these two proposals:
Stefan Seyfried proposed a machine use case:
Having a few "presets" with the most common use cases, best accompanied with a short description is still a good idea IMHO. Maybe stuff like:
* "Admin configured server": you need the root password for all changes
-> basically like in good old times before polkit and friends: you'll
need to "su -" and then use yast or whatever to change stuff.
* "User configured laptop": you are allowed to connect to WiFi networks,> connect printers and install package updates with your user account. For adding software repositories and installing additional software, you'll need the root passowrd.
* "third preset": I have no idea what a third preset could be
I think having this type of preset policy model may suffice. For everything else we'd provide the super flexible dialog dialog. I cannot not see where a role based model will provide a simple and quick at install time. The preset "access model" as described above can be a simple one click selection at install time, with the more detail settings dialog hanging of this dialog and activated by clicking on "Advanced Settings". I don't think we need to do any more than the combination of the two, i.e. preset "access model" + flexible select per function each user's allowed access. Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org