equinor / equinor/prisma-decision-api
[DRAFT] improve roles
- Dominant language
- C#
- Stars
- 3
- Forks
- 3
- Avg merge
- 2d 13m
- Merged PRs (30d)
- 27
Description
Roles should be improved. So far only roles towards DA/DQ are defined
- Decision Maker
- Facilitator
- (team) Member
Other roles could include (from https://github.com/equinor/prisma-decision-web/issues/640)
> In the current version, the facilitators have special role, in particular for being the only ones who can enter a project description.
In practice, the facilitator may not write anything in Prisma and the (new) role of scribe should be distinct. However, the role of scribe is not mutually exclusive as anyone in the team could be the scribe, this role even changing from session to session.
Roles towards the ownership of the data and project haven't been yet defined.
Contributor guide
Research direction
Start by reviewing the existing DA/DQ role definitions and the related discussion in equinor/prisma-decision-web#640. Clarify the proposed scribe role and how roles relate to data and project ownership before identifying the API entry points affected. The issue is complete only when the role model and its ownership rules are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100