Project permission/team member rabbit hole
We have a mashup of permission and membership which is very confusing, and prone to bugs. This was discovered as part of debugging #4222 (closed).
I'll outline what we know based on my chat with @DouweM and @jacobvosmaer:
- Groups can have multiple owners - as a project team membership role.
- Projects can have one owner, as an attribute on the project itself. Owners are not part of the project team membership.
- Group owners can be @ mentioned but project owners cannot.
- Projects also have a creator attribute
Questions:
- Why do we have both creator and owner for projects? I can't see a way to change project owner.
- Can we transition the project owner to a team member role? This would also open it up for multiple group owners. There are several permissions only available to project owners and it makes it difficult if there's no transparent way to see or change the owner.
- It seems the inability to @ mention a project owner is something that happened recently.
Actually, transitioning the project owner to a team member role would solve all the problems here. Are there any negatives?