You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2015-11-03-november-wfh-slack.md
+15-14Lines changed: 15 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,33 +4,34 @@ title: Working From Home Slack Bot
4
4
author: Mike James
5
5
categories: [hacks,javascript,node, slack]
6
6
---
7
-
So back in June we had a hackday and produced an initial release of what we call WFH (working from home) bot (see [original post](/blog/hack-day-wfh-bot)). We have a remote working policy, so rather than having a long WFH email chain being sent individually everyday we've built a system to help. Slack is core to all internal chat communications and everyone uses it. It also provides a flexible API which makes it good place to interact with WFH.
7
+
Here at pebble{code} we have the freedom to work remotely. It's been a part of our culture from the early days. So back in June this year we had one of our hackdays and produced a service we call WFH (working from home) bot (see [original post](/blog/hack-day-wfh-bot)). The idea behind the hack day was to try out some new tech and solve some problems along the way. The bot helps prevent long email chains on who is working where. Slack is core to all internal chat communications.
8
8
9
-
The first version of WFH was private on Github, today we're releasing it as OpenSource. As we figured this might be useful to other people working remotely. This post documents the recent changes and features. Its here for you to play with and [host your own](https://github.com/pebblecode/wfh-api).
9
+
The first version of WFH was private, and today we're releasing it as OpenSource. As we figured this useful! So its here for you to play with and [host your own](https://github.com/pebblecode/wfh-api) under [MIT](http://opensource.org/licenses/mit-license.php).
10
+
11
+
###Architecture
12
+

10
13
11
14
###What's changed?
12
-
We've had a play around with the api and had some interations, we've also experimented with one version in Erlang. We've settled at the moment for a node.js version, as most of us devs here at pebble write JavaScript. But we're going to continue playing with Erlang as its an interesting platform.
15
+
We've had a play around with the api and had some interations, we've also experimented with one version in Erlang[here](https://github.com/pebblecode/wfh2_backend). We've settled at the moment for a Node.js version, as most of us devs here at pebble write JavaScript. But we're going to continue playing with Erlang as its an interesting platform.
13
16
14
17
#### Parameters
15
18
We now have parameters in the slash commands.
16
19
17
-
`default: (wfh,wfo)`
18
-
Allows you to change your default status. Say for example you change; to working from home by default and come to the office less frequently.
20
+
`default:wfh` or `default:wfo`
21
+
Allows you to change your default status. Say for example you change, to working from home by default and come to the office less frequently.
19
22
20
-
`message: I'm at a conference`
21
-
messages allow you to give some description.
23
+
`message: I'm at a conference` or `message: I wan't to sit in my pants all day and work from home`
We have InOffice, OutOfOffice, Sick and Holiday. All statuses last for a full working day. Say you want to set the status for your next day at work to another status you can do that after 8pm as we figured most people won't be updating their status for the current working day at 8pm.
25
30
26
-
27
-
###Architecture
28
-

29
-
30
31
###Integrations
31
32
The api has full CRUD functionality, see the docs for more details. So this is open for your own integrations. We've used this to integrate with [Tribe HR](https://github.com/pebblecode/tribehr-holiday-fetcher) and [send Emails at 10am](https://github.com/pebblecode/wfh-email-cron)
32
33
33
-
###We'd love to hear from you
34
-
Let us know what you do with WFH bot.
35
-
34
+

36
35
36
+
###We'd love to hear from you
37
+
We're pretty proud of our WFH bot, we can see various features being added over time. Its pretty simple to extend its a [hapi api](http://hapijs.com/). Do let us know what features you'll like to see with WFH bot.
0 commit comments