Michael Brunton-Spall
Michael Brunton-Spall
The Slack instance has an acceptable use policy (Draft forthcoming from GDS) which confirms it's status under FOI, and what is or is not acceptable behaviour. When somebody joins, the...
The invite functionality could be triggered from a webpage, which asks for the users email address and if it matches the whitelist, then send the invite.
Inspired by https://github.com/18F/hubot-slack-github-issues#hubot-slack-github-issues When someone says something monumentally useful in the slack, adding the evergreen emoji as a reaction should cause the bot to take the text and.... put it...
If you say help to the bot, it enters help mode (https://github.com/bruntonspall/xgovslackbot/blob/master/app/slack_bot.js#L378) Once in help mode, you have to say "done" to get out of help mode, otherwise everything you...
We have two instances on cloudfoundary, production and sandbox. Currently the bot runs in the sandbox, for historical reasons. The ideal workflow should be: Pull requests should be deployed to...
The source is a bit of a mess. It could do with dividing into modules for things like users, rooms, welcome and so forth.
Some channels should be logged for FOI purposes. If the bot is invited to the channel, and logging is enabled, then log each statement into a daily log, and upload...
If someone has been idle for more than a specific time, say 3 months, then nag them to log back in, but if they don't, then disable their account.
2FA should probably be enabled for most staff. Using the slack API, work out who does not have 2FA enabled, and send them a message from the bot to encourage...
The domains are currently a fixed whitelist, changed on deploy. They could instead be stored in the database, and an admin page to allow editing of the domains without restarting...