atom feed57 messages in org.xwiki.usersRe: [xwiki-users] [xwiki-devs] [Prop...
FromSent OnAttachments
Ecaterina ValicaMay 10, 2010 6:39 am 
Guillaume LerougeMay 10, 2010 7:01 am 
Ecaterina ValicaMay 10, 2010 7:07 am 
Thomas MortagneMay 10, 2010 8:21 am 
Ecaterina ValicaMay 13, 2010 1:57 am 
Ecaterina ValicaMay 18, 2010 2:03 am 
Guillaume LerougeMay 18, 2010 8:08 am 
Denis GervalleMay 18, 2010 8:29 am 
Ecaterina ValicaMay 19, 2010 3:23 am 
Ecaterina ValicaMay 19, 2010 3:39 am 
Denis GervalleMay 19, 2010 6:52 am 
Ecaterina ValicaMay 19, 2010 7:33 am 
Ecaterina ValicaMay 20, 2010 9:18 am 
Guillaume LerougeMay 20, 2010 9:21 am 
Ecaterina ValicaMay 21, 2010 10:51 am 
Alex BuseniusMay 21, 2010 11:42 am 
Ecaterina ValicaMay 21, 2010 10:57 pm 
Denis GervalleMay 22, 2010 1:31 am 
Ecaterina ValicaMay 26, 2010 6:48 am 
Ecaterina ValicaMay 27, 2010 12:57 am 
Denis GervalleMay 27, 2010 1:26 am 
Ecaterina ValicaMay 31, 2010 7:53 am 
Ecaterina ValicaMay 31, 2010 7:54 am 
Denis GervalleJun 1, 2010 12:03 am 
Ecaterina ValicaJun 1, 2010 3:54 am 
Ecaterina ValicaJun 3, 2010 9:09 am 
Denis GervalleJun 4, 2010 12:42 am 
Ecaterina ValicaJun 4, 2010 9:54 am 
Alex BuseniusJun 4, 2010 10:57 am 
Ecaterina ValicaJun 4, 2010 11:23 am 
Raluca StavroJun 4, 2010 11:33 am 
Raluca StavroJun 4, 2010 11:36 am 
Alex BuseniusJun 4, 2010 12:05 pm 
Denis GervalleJun 4, 2010 3:53 pm 
Ecaterina ValicaJun 7, 2010 1:22 am 
Ecaterina ValicaJun 7, 2010 1:50 am 
Denis GervalleJun 7, 2010 2:24 am 
Ecaterina ValicaJun 7, 2010 8:00 am 
19 later messages
Subject:Re: [xwiki-users] [xwiki-devs] [Proposal] Rights Management UI
From:Ecaterina Valica (
Date:May 20, 2010 9:18:03 am

A small variation for Version 3


- improved the display of inheritance of rights within a role description; - emphasize the display of "Inherited"|"Allow"|"Deny" by using color and icon representation.

For Rights version 4 I'll remove the concept of Role.

Thanks, Caty

On Wed, May 19, 2010 at 21:04, Denis Gervalle <> wrote:

On Wed, May 19, 2010 at 16:33, Ecaterina Valica <> wrote:

Hi Denis,

On Wed, May 19, 2010 at 16:52, Denis Gervalle <> wrote:

On Wed, May 19, 2010 at 12:39, Ecaterina Valica <> wrote:

On Tue, May 18, 2010 at 18:29, Denis Gervalle <> wrote:

On Tue, May 18, 2010 at 17:08, Guillaume Lerouge <



On Tue, May 18, 2010 at 11:03, Ecaterina Valica <



I've reviewed some of your feedback and added them to Rights



Proposal *VERSION 3*:

*Partial Prototype*

- Wiki Level:

*Desired Interaction*


Thanks, Caty

I like the separation between rights definition and rights affectation. Only

Nice indeed, but I do not understand how it could fits with current implementation.

downside -> inherited rights are displayed less clearly than




in version 2.

and I do not see any inherited information anymore.

For example, in Space Level http://localhost:8084/xwiki/bin/view/Improvements/Rights3Space the text in yellow represents the inherited users and inherited



upper level.

The text in black (evalica with Reviewer and the Reviewer



specified only for this level.

After the save the added "Reviewer" right is gonna look like this:


Thanks for these precision, I have better understand your idea. (Personally I have some difficulties with colors (partially color blind), so information based on colors is not always easy for me.)

So you're a great test candidate :). I also received a mail from Roman (he wanted icons to represent rights), so what I can do for you is to try a version with color + little icon to represent "Inherited"|"Allow"|"Deny". I will think about it.

I think that could be nice to have more visual than color information for inheritance. The way it was in proposal 2 was fine, since this was more intensity than color. And I will be pleased to be your candidate. Be careful that using icons for representing specific rights could add complexity when (later) components add new rights dynamically.

So, proposal 3 seems less interesting than proposal 2. I do not




solves based on previous comments either. Caty, could you explain further your goals with this proposal ?

I tried in proposal 3 to make it more easy to use. People told me



didn't understood the "Containing Spaces/Pages" so I've removed it. This proposal gives the users the possibility to create Roles that



semantically value to them and thus making the rights more easy to use.

This proposal accommodates the case: "Not sure it's scalable. In the future applications/components will be able to register new rights". Having the rights displayed vertically and only on Add, makes the UI more scalable, and in the code we could add as many rights as we would want. Also the spaces is now more economical having just "Allow"/"Deny" columns.

I completely agree that proposal 3 is clearer. The problem is that your samples and the structure of this proposal are really far from current implementation. Proposal 2 were fitting better but the samples where also not



remarks from Thomas about global wiki users should also be integrated.

About Thomas feedback, don't you like


So, I am puzzle by your goals here. Aren't we going too fast ? Since there is very poor documentation about the way XWiki rights



would be happy to improve that, but it will require some time), I have the impression that there is a important misunderstanding of how



effectively applied. So the design of a proper UI is not easy. I have also read the draft of Sergiu that aims to improve the documentation, but either I have not understand it or it does not describe current behavior.

So the question is for me, are we designing this UI to think about future possibilities or to replace the current UI ?

My purpose is "to make rights easy to use at last". IMO this means do whatever it takes to make them "easy to use" :) I try to base my proposal on existing code, but I never disregard new functionalities that I can add if this means the UI and experience is gonna be improved.

The only thing Rights version 3 is adding is the "Role" part, which is some kind of groups for rights. If the solution given is gonna be convincing enough to be use in the rights part (not yet .... but maybe some version of it) I'm sure there will be someone that is gonna want to implement it. Until then I will continue to prototype and find out how we can add all that functionality in one place.

Well, this precisely the grouping of right that is a big change. Currently, right are inherit individually, not as a group. Moreover, the inheritance is a little bit particular, since allowing a given right at lower level, will deny that same right for anybody else even if this right is allowed at a higher level. Said another way, once an allowance for a given right has been found and you are not part of it, you are denied. Of course, there is an exception to this rules regarding global admin rights, these ones are evaluated before and gets priority.

I would agree if you find this to be not the correct way of evaluating right, but this is the way it works since the beginning. There is also an option to evaluate rights based on a hierarchy of spaces, but this one is usually disabled. It will probably be revived when such hierarchy of space are bring back using the new reference model.

So, I am convinced that current right management is poor, but changing it will require important changes, and time.

Hope you get a better idea of my concerns. For detailled information on how rights are processed, you may want to have a look at This is really bare documentation of the code, but it tells the truths.

Denis, thanks for the extra info Caty

And yes... I need to focus more on the inheritance again.

Thanks, Caty


Thanks, Caty


Also, a drop-down might be better than an autosuggest when



right should be added to a role.