Create /api/groups endpoint #2
Labels
No Label
priority
high
priority
low
priority
medium
priority
very high
BUG
Feature
High Priority
Low Priority
Medium Priority
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: public/pyceo#2
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implement all of the /api/groups endpoints as specified in #1.
Make sure to implement the "auxiliary groups" feature which was present in the old ceo. For example, if someone is added to syscom, they should also get added to staff and adm (and possibly a few other groups). These auxiliary groups should be specified in the config file.
Additionally, if someone is added to syscom, they should be subscribed to several mailing lists (syscom, syscom-alerts, syscom-moderators). Same goes for exec, and possibly some other groups.
Removing someone from a group should undo the extra operations above - for example, if someone is removed from syscom, they should be removed from the auxiliary groups, and unsubscribed from the appropriate mailing lists.
Also, don't forget that creating a new club should create a new sudo role.
n4chung referenced this issue2023-01-01 17:30:08 -05:00