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

Configuration should allow for an ignore list of slack handles #7

Open
cpruitt opened this issue Sep 16, 2021 · 2 comments
Open

Configuration should allow for an ignore list of slack handles #7

cpruitt opened this issue Sep 16, 2021 · 2 comments
Assignees

Comments

@cpruitt
Copy link
Collaborator

cpruitt commented Sep 16, 2021

We might want to consider adding a per-channel ignore list for slack handles that exist in the channel but should not be part of the pairings. The use case here is someone who is acting as an administrator or facilitator who has reason to monitor questions in the channel but does not, personally, want to be part of the pairings.

From @tuxagon:

There are 2 ways I see this happening right now.

  1. We add a command that allows a person to set their user as invisible for a particular group
  2. We keep a list of specific people in the database that are always ignored for a particular group

I prefer (1) personally because it's not a hidden functionality.

I agree with the preference for #1. This feels like we're uncovering the need for a User model that can be looked up by slack ID.

@tuxagon
Copy link
Collaborator

tuxagon commented Jan 19, 2022

Related for some extra context #32

@tuxagon
Copy link
Collaborator

tuxagon commented Jan 19, 2022

I think we could potentially handle for the User model in a slightly different manner based on current usage.

Right now, we're using the slack user id as the in-db reference for a particular individual. That could end up being, at least conceptually

user_channel_visibilities
- slack_channel_id => string
- slack_user_id    => string
- visibility       => datatype to avoid being a boolean (hidden | visible | away)
- away_until       => date

The idea with away_until is that a date could be specified for when to become visible again during the matchmaking. The visible state would be more of a virtual/implicit state based on

  1. The absence of a record in the table
  2. A record's away_until being in the past

lsparlin added a commit that referenced this issue Jan 20, 2022
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

3 participants