edgi-govdata-archiving / edgi-hubot-halpy

Heroku-backed chatbot-friend who lives in EDGI Slack
https://edgi-hubot.herokuapp.com/
3 stars 0 forks source link

Create command to help estimate a fair quorum in channel #21

Closed patcon closed 5 years ago

patcon commented 7 years ago

It was raised on Slack that it's often difficult to know in a WG who and how many people are required to make a decision. I was wondering whether clarity might be provided by providing the folks making a decision with a rough estimate of quorum via a chatbot command. It might allow people to have some idea of who is active, and therefore who might have stake in conversation. It could theoretically be used something like this:

alice: @halpy quorum me
halpy: In the past 7 days, 4 people have been active in #this_channel (messages, reactions, typing):
       alice, bob, cindy, zach
alice: @halpy quorum me 1
halpy: In the past 1 day, 1 person has been active in #this_channel (messages, reactions, typing):
       alice

The Slack API offers a way to easily see the exact time when someone was last active on the whole of Slack. This would be dead simple to make use of, since it's already provided and tracked by slack. https://api.slack.com/methods/users.getPresence

Though it might be custom code (and therefore more effort), the chatbot could also be used to track last activity in a specific channel. I would need to double-check documentation for specifics, but this would at least work for in-channel emoji reactions, messages, and any typing action (regardless of sending or not). Notably missing is whether someone is reading (but not interacting in any way). For reading, we can only know that they logged into Slack at a specific time, but we have no info about what channels they read.

Anyhow, no pressure, just curious whether this might be useful in providing a sense of legitimacy in decision-making. (Particularly when people are following along and using emoji, but perhaps not speaking up.)

cc: @trinberg @ambergman @mayaad

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.