The "developer" role is redundant; remove it
Bug #786842 reported by
Matt Giuca
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MUGLE |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Currently, there are two ways to tell if someone is a developer:
- They have the role "DEVELOPER", and/or
- They are a member of a devteam.
This is redundant. By definition, if you are in a devteam, you are a developer, and if you aren't, then you aren't. Therefore, we shouldn't have a separate database role for this.
Instead, in the User client class, add a derived field numDevTeams which shows the number of devteams this user is in. That can be used by the client UI for the same purpose as the current DEVELOPER role is used for (e.g., deciding whether to show "My Teams" and "My Games" links).
Revision history for this message
| Matt Giuca (mgiuca) wrote | #1 |
Revision history for this message
| Matt Giuca (mgiuca) wrote | #2 |
To post a comment you must log in.
The presence of the developer role is masking bug #786876. Even if we keep this role (for now), there should be no privileges that depend on DEVELOPER; they should all depend on either GUEST or ADMIN.