It was agreed near the end of the Feb 19 meeting to define users and groups similar to legacy system for now and refine later. The following summarizes how the legacy system manages users and groups and how it assigns roles. I have suggested changes to the way roles are assigned to simplify things for now. The legacy system selectively assigns roles to groups (any roles can be assigned to a group). Users in a group are only able to be assigned the roles assigned to the group. For now, I suggest to ignore the group roles and simply allow any role to be assigned to any user.
Groups
Equivalent to “organizations” in legacy system
Legacy system selectively assigns roles to groups and only those roles are available to users in the group — suggest to ignore group roles and allow any role to be assigned to any user (easier to implement for now and more flexible)
Ignore legacy system’s “Point of Contact” users for each group/organization (point of contact users assign roles to users in that group) — allow only Register Manager role to assign roles to users
Ignore the legacy system’s “Administrator Group Membership” (administrator members create/manage users and groups) — allow only Register Manager role to create/manage all users and groups, and assign roles
Users
Use Git usernames for Paneron access
Users assigned to only one group
Users can only view proposals of users in their assigned group
Legacy system selectively assigns available group roles to users — suggest to ignore this and allow any role to be assigned to any user (easier to implement for now and more flexible)
Roles
Submitters — create/submit/unsubmit/delete/appeal their own group proposals
Control Body — view/return/reject/approve accepted proposals
Register Owner — view/return appealed proposals
Suggest to split the Control Body role into the following two separate roles to avoid inexperienced CB members accidentally approving/returning/rejecting proposals
Control Body Reviewer — view accepted proposals
Control Body Approver — view/return/reject/approve accepted proposals
User & Group Management
It was agreed near the end of the Feb 19 meeting to define users and groups similar to legacy system for now and refine later. The following summarizes how the legacy system manages users and groups and how it assigns roles. I have suggested changes to the way roles are assigned to simplify things for now. The legacy system selectively assigns roles to groups (any roles can be assigned to a group). Users in a group are only able to be assigned the roles assigned to the group. For now, I suggest to ignore the group roles and simply allow any role to be assigned to any user.