Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update iam workflow #8

Closed
4 tasks
christopherm99 opened this issue Jan 11, 2023 · 1 comment
Closed
4 tasks

Update iam workflow #8

christopherm99 opened this issue Jan 11, 2023 · 1 comment

Comments

@christopherm99
Copy link
Member

Ideally, I think it makes more sense to first verify users' email, to check they are a student, and then subsequently detect which team they are on, as the server grows. For instance, manually adding and removing users as they join various public events such as DataFests.

Thus setting up a system like ACM's verification, then team assignment workflow may make more sense. To this end, we could also require members to declare their name when calling the /iam command. Then, after being verified as a student, users can react to a message to request to join various teams.

  • /iam registers user nicknames (and users cannot modify their own names).
  • /iam is broken out into two separate tasks, one to verify users, and the other to enroll in a team.
  • MEE6 could be replaced for assigning users the DataLearn role.
  • In the future, users could even request to join other teams (ie. after an internal transfer) and after being approved by the corresponding team head, the Google Sheet would auto update.
@christopherm99
Copy link
Member Author

Closing this in favor of the solution in #16.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant