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.
Implement all of the /api/groups endpoints as specified in https://git.csclub.uwaterloo.ca/public/pyceo/issues/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.
merenber
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 issue 3 months ago