Standup bot with hubot ala tender
Create a room (or channel on IRC) for standup (existing one is okay) and invite hubot to the room if necessary.
First, you tell hubot who is a member for a particular team for the standup, using the
roles commands with "(who) is a (team) member".
Let's take "engineering" team for example.
miyagawa: hubot miyagawa is an engineering memberhubot: Ok, miyagawa is an engineering membermiyagawa: hubot john is an engineering memberhubot: Ok, john is an engineering membermiyagawa: hubot davidlee is an engineering memberhubot: Ok, davidlee is an engineering member
You can create as many teams as you want.
Note: This setup process hopefully won't be necessary in the future, when Hubot properly implements an API to get the list of online users in a room. So that everyone in a standup room == standup participants.
Hubot won't schedule the standup for you (yet), you have to start it by yourself when it's time.
miyagawa: hubot standup for engineeringhubot: Ok, let's start the standup: miyagawa, john, davidleehubot: john: your turn
Hubot remembers who should participate the standup, and will tell whose turn is the next. Tell what you did yesterday, will do today, anything blocked. and say "next" (or "done" or "that's it") when you're done.
john: Done some pretty nice hack yesterday.john: I will work on another cool stuff today.john: I'm not blockedjohn: hubot nexthubot: davidlee: your turn
When the user is offline or away for a second, tell hubot to skip the user.
miyagawa: hubot skip davidleehubot: Will skip davidleehubot: miyagawa: your turn
Once the last user is done, hubot will tell you how long the standup was.
miyagawa: I'm working on some nice stuff, and will continue doing so today.miyagawa: hubot nexthubot: All done! Standup was 5 minutes and 24 seconds.
This hubot script depends on
roles.coffee script. You're recommended to use
redis-brain.coffee to persist the team information.
In your project directory, run the following:
npm install hubot-standup --save
The bot can also post the standup archive to Yammer. You need to set a valid Yammer OAuth2 token to
HUBOT_STANDUP_YAMMER_TOKEN environment variable.
Here's how to get a valid Yammer OAuth2 token with the standard OAuth2 authorization flow.
See Yammer documentation for more details.
https://www.yammer.com/<DOMAIN>/client_applications/new. Leave the callback URLs empty
code=<CODE>query parameter in there, copy that.
Now set the token to
HUBOT_STANDUP_YAMMER_TOKEN and Hubot will ask which group ID the log should be posted to. Use the group ID 0 to turn off the feature for a group.