786110 - Using standup as an IRC status tool.

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P3)

Description

[Jacques Uber [:uberj]]

There is this tool called 'standup' (https://github.com/rlr/standup) which is a lot like teamstatus. Here is an example of what this site looks like http://standu.ps/.

The IRC portion of the app can be found here:
https://github.com/mythmon/standup-irc

I've figured out how to get the bot to connect to an IRC server with ssl enabled, have the bot register it's nick with nickserv, and join a channel using a channel key. If we are interested in using this tool we will need a home for the app. It needs:

 * A postgress database
 * A webserver

Where should we set this up?

Comment 1

[Shyam Mani [:fox2mike]]

Before we get ahead of ourselves, why are we doing this again? 

How is this any different from posting on Yammer? (which no one ever does)

Also, how many people have used the bot to tweet? (that's right, no one uses that either)

Let's not add on things we won't really use and focus on things we need :D

Comment 2

[Jake Maul [:jakem]]

(In reply to Shyam Mani [:fox2mike] from comment #1)
> Before we get ahead of ourselves, why are we doing this again? 
> 
> How is this any different from posting on Yammer? (which no one ever does)

The theory is that having the status update tool right in irc will invoke more thorough usage of it. A Yammer bot would potentially be an acceptable substitute... but as far as I know we don't have such a beast, and that necessarily excludes community from participation anyway, so it's perhaps not as good of a general solution.


> Also, how many people have used the bot to tweet? (that's right, no one uses
> that either)

I don't know what bot you're referring to... are you suggesting that we have a twitter bot and we should be using for team status updates? The only twitter thing I'm aware of is the @MozillaIT account, intended for outages and the like. That seems inappropriate here. We *do* make copious usage of some bots, so I don't think this should serve as an indictment against IRC bots in general.


> Let's not add on things we won't really use and focus on things we need :D

Sure, but I think we need a better way to communicate team status updates. This bug was filed by uberj, but in actuality it was something that WebOps asked for. We are basically offering to be the test subjects for the rest of IT. If it works well for us, others are invited to try it out too... but there's no sense in everyone spending time with it until it proves useful.

Comment 3

[Jake Maul [:jakem]]

Is there any further action to take here? The site is alive (http://opstat.us/, hosted in PHX1 by the looks of it) and the bot is posting to it.

Tentatively closing as completed, but please re-open if there's something I've overlooked (for instance, if something that's in use is temporary/testing and needs fleshed out better).

Comment 4

[Brandon Burton [:solarce]]

Since this is just using a local sqlite DB, we should make sure that's being backend up?

Comment 5

[Shyam Mani [:fox2mike]]

Bet the bot has a !backup ;)