I am building a new "GroupRelationship" type called "GroupOwnership". Separating it from "uid"/"Author" field has many advantages.
Problem/Motivation
Using the "author" field of a group is challenging. It's hard to build things that include both the group author and it's members. Views are a totally different relationship structure. They have to be handled differently when displaying and when configuring permissions. It was difficult to add both to a View in a consistent way.
I am building a site using Group module. I want the entity to have a team, but I also want to be able to specify an "owner". I am building a site where content is like google docs or github repos: you can add people and specify an "owner", I want users to be able to "transfer ownership".
At first, I did this with a Role called "owner", but it didn't make sense in the roles field.
Proposed resolution
Add a new "Group Ownership" relationship type.
Remaining tasks
- GroupOwnership relation type
- GroupOwnershipPermissionProvider
- TBD
User interface changes
"Group Ownership" will appear as a possible relationship type, right alongside "Group Membership".
API changes
New GroupRelationType 'group_ownership'.
Data model changes
Does having a new GroupRelationType count?
Issue fork group-3632184
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments