Skip to content
This repository has been archived by the owner on Dec 26, 2022. It is now read-only.

Members specifications #32

Open
theofidry opened this issue May 17, 2015 · 4 comments
Open

Members specifications #32

theofidry opened this issue May 17, 2015 · 4 comments

Comments

@theofidry
Copy link
Member

Write down the specifications for the members management: here.

@theofidry
Copy link
Member Author

The features for the first version have been freezed. This tickets is reported to the next milestone for which more advanced features regarding the users will be provided.

@xNok
Copy link

xNok commented Aug 14, 2015

Why make a différence beetween Rôle and Type. User and Membre have the same rôle. Moreover we must had types : "membre du CA" and "Membre du bureau". It is a usefull entry to filter members.
After if you want to create an ACL you will manage right with Type (membre, intervenant, membre du CA, Membre du bureau) and not with Role.

@theofidry
Copy link
Member Author

Roles are ACL based, not types, meaning if you wish, you can have an admin role on a simple member or strip a "membre du CA" of all rights by giving him the simples role.

But you're right we could avoid the duplication and using only roles instead of adding type. But the question is: do we want to do it? Using roles instead of types implies two things:

  • we must have a hierarchy between each roles
  • in the front, we have to deal we system roles like ROLE_ALLOWED_SWITCH not to take them into account

The hierarchy part is not trivial as changing the hierarchy for adding a new role may be quite painful. For now it would not have much consequences as there is no ACL permissions set yet (almost). So we can do the change.

@theofidry
Copy link
Member Author

Another thing is, having roles and types allow us to add types on the fly without any problem and keeping the roles simple.

@flef your opinion?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants