I just notices at the bottom of the user list there is note #4:
4. Users with privilege v inherit the combined privileges of developer,
anonymous, and nobody.
Well, 'v' is 'Developer' - so I'm thinking it wasn't really meant that
developers should inherit the privileges of developer. Probably this is a typo
and what was meant was this:
4. Users with privilege v inherit the combined privileges of reader, anonymous,
and nobody.
This would resolve one of my comments below.
RW
Ron Wilson, Engineering Project Lead
(o) 434.455.6453, (m) 434.851.1612, www.harris.com
HARRIS CORPORATION | RF Communications Division assuredcommunications(tm)
-Original Message-
From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-
boun...@lists.fossil-scm.org] On Behalf Of Ramon Ribó
Sent: Wednesday, October 20, 2010 10:29 AM
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] user capabilities - ui improvements?
Also, It is not clear for me the difference between:
a - Admin: Create and delete users
and
s - Setup/Super-user: Setup and configure this website
Is it really necessary to have these two separated options? They
really confuse my co-workers
and myself
Ramon Ribó
2010/10/20 Wilson, Ronald rwils...@harris.com
I'd like to make some observations of and suggestions for improving the
ui admin of users.
The User List screen is very clear; the notes with each capability as a
letter spelled out is very neat and usable. However, when you click on a
specific user, e.g. anonymous, the capabilities selection screen doesn't
show the letters anywhere and the list is in a different order from the
letters. Also, some capabilities are renamed, e.g. on the user list, 'h'
is for 'hyperlinks' whereas on the capabilities selection screen, I'm
pretty sure 'h' is for 'History'.
Also, the default capabilities seem to imply that 'developer' inherits
the capabilities of 'reader' (because the Password capability is not given
to developer by default). This could be explained in the special logins
section of the capabilities selection screen.
All of this makes user administration a little cumbersome. I suggest
that as a minimum, the capabilities selection screen should have the
letters next to the checkboxes in that correspond to the letters defined
on the user list screen.
One last thing - just a question. Capability 'b' or Attach controls
adding attachments to wiki or tickets. Does this depend on the
capabilities 'm' (append-wiki) or 'c' (append-tkt) or 'f' (new-wiki) or
'n' (new-tkt)? I'd like to allow anonymous users to add attachments to
tickets, but not wikis. Is that even possible?
RW
Ron Wilson, Engineering Project Lead
(o) 434.455.6453, (m) 434.851.1612, www.harris.com
HARRIS CORPORATION | RF Communications
Division
assuredcommunications(tm)
NOTICE: This e-mail transmission (and any of its attachments) may
contain confidential, proprietary and/or privileged information. The
sender intends this transmission only for the designated recipient(s). If
you are not a designated recipient (or authorized to receive for a
designated recipient), you are hereby notified that the disclosure,
copying, distribution or use of any of the information contained in this
transmission is strictly prohibited. If you have received this
transmission in error, please destroy this message, delete any copies
which may exist on your system and notify the sender immediately. Thank
you.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
