Context
Currently, we have a duplication issue on on these two enums, which might confuse future contributors
What to do
- Unify both into an access.enums.CommitteeRole, which denotes the role of an user in that committe.
- Refactor tests to have the new proposed structure when needed
- Refactor session domain
Expected Behaviour
We expect an unified CommitteeRole, avoiding more future technical debt
Context
Currently, we have a duplication issue on on these two enums, which might confuse future contributors
What to do
Expected Behaviour
We expect an unified CommitteeRole, avoiding more future technical debt