/dolores-landingham-slack-bot

A Slack bot to welcome new 18F hires with the authority and compassion of Mrs. Landingham
  1. Ruby 73.9%
  2. HTML 12.5%
  3. CSS 7.5%
  4. JavaScript 5.2%
  5. Shell 0.9%
Ruby HTML CSS JavaScript Shell

Clone with HTTPS

Use Git or checkout with SVN using the web URL.

Open in Desktop Download ZIP
Find file
Switch branches/tags
Nothing to show
Latest commit 243248d Mar 10, 2017 @jmhooper jmhooper Don't create SentMessage records for test messages 
This commit adds an option to the MessageSender that tells the message it is sending is a test message. When this option is set to true, the message is sent, but a SentMessage record is not created.

This change allows users to receive onboarding messages after having been sent a test message for the given onboarding message. Prior to this commit, that did not happen because the logic to determine if an onboarding message should be sent to a user included a check for an existing onboarding message.

This commit also adds a feature spec to serve as a regression test to assure that users receive onboarding messages after receiving a test message for the given onboarding message.

Ref #250
Permalink
Failed to load latest commit information.
app Don't create SentMessage records for test messages Mar 10, 2017
bin Update deployer credentials for each space Feb 17, 2017
config Temporarily disable quarterly messages Oct 12, 2016
db Remove Employee uniqueness validation from SentMessage Mar 10, 2017
lib/tasks [Connects #72] Add nightly tasks to import new employees and update u… Jul 19, 2016
public Add Rails Sep 17, 2015
script Add ssh script for Cloud Foundry Jan 21, 2016
spec Don't create SentMessage records for test messages Mar 10, 2017
vendor/assets/javascripts redo style architecture Feb 19, 2016
.about.yml Closes #120: Add an .about.yml file Jan 6, 2016
.cfignore Added manifest file Sep 21, 2015
.codeclimate.yml Add rubocop and code climate Jun 24, 2016
.gitignore Improve performance of employee create action Mar 9, 2017
.rspec Add Rails Sep 17, 2015
.rubocop.yml Do not check for frozen string literal comment in files Jul 19, 2016
.ruby-version Update to Ruby 2.3.3 Feb 4, 2017
.sample.env Remove references to `AUTH_DOMAIN` env var Jul 27, 2016
.travis.yml Update deployer credentials for each space Feb 17, 2017
CONTRIBUTING.md Update CONTRIBUTING Feb 17, 2017
Gemfile Update to Ruby 2.3.3 Feb 4, 2017
Gemfile.lock Update webmock from 2.1.0 to 2.3.2 Mar 10, 2017
LICENSE.md Add license and contribution guides Sep 16, 2015
PULL_REQUEST_TEMPLATE.md Add pull request template Apr 30, 2016
Procfile Send delayed jobs Mar 8, 2017
README.md Update instructions for adding or editing messages Feb 3, 2017
Rakefile Use canonical acts-as-taggable repo Jul 19, 2016
Vagrantfile just enough to get vagrant up to work Aug 28, 2016
config.ru Add Rails Sep 17, 2015
manifest.yml Split out common configs for manifest Feb 17, 2017
manifest_base.yml Use internal ruby buildpack Feb 21, 2017
manifest_staging.yml Improve performance of employee create action Mar 9, 2017

README.md

Dolores Landingham Bot

Build Status Code Climate Dolores

This is a Slack bot that helps onboard new hires at 18F through scheduled Slack messages about topics relevant to 18F and GSA employees. Messages will be scheduled once per day and will trickle out to employees over the course of 60 days.

Mrs. Landingham will teach 18F employees about working in the federal government, how to set up travel, how to add their biographical information and pictures to our website, and other facts that will help them get acclimated to both 18F and the federal government.

Please file an issue if you have any questions about Mrs. Landingham.

The name of this bot is a friendly reference to the TV show The West Wing, where Mrs. Landingham is the fictional president's trusted secretary. This photo is from the show.

Usage instructions for 18F employees

To add new users

  1. Go https://dolores-app.18f.gov/
  2. Click https://dolores-app.18f.gov/employees/new
  3. Write their Slack username without the @ symbol
  4. Select the date that they started
  5. Select the time zone that they reside in
  6. Click https://dolores-app.18f.gov/employees to make sure they’re on the list

To add new messages

  1. Draft the message in this issue
  2. Admins can copy the message and paste it in the message body here: https://dolores-app.18f.gov/scheduled_messages/new
  3. Add a title to your message to be able to identify the message
  4. Add the number of days after an employee starts. (Add 1 to the last message in this Google Doc)
  5. Select a time that the message should be sent (the message will be sent at each employee's local time)
  6. Add tags to be able to surface the message

Installing and contributing

If you're interested in setting up a version of this bot or contributing to this one, our contribution guidelines explain how to set up and deploy this app, find potential tasks to work on, and submit pull requests.

Using Dolores

18F employees can view the scheduled messages that Dolores sends employees by visiting https://dolores-app.18f.gov/.

Any 18F employee with a Slack handle can add themselves as a Dolores Landingham message recipient here.

Only admin users can add and update scheduled messages. If you would like to add or update scheduled messages, please open an issue on this repo.

Admin users can add scheduled messages here.

Scheduled messages include a "day count" attribute. Messages to be sent on the day an employee starts have a day count of 0, messages to be sent the next day should have a day count of 1, and so on.

Questions?

If you have any questions about the Dolores Bot project and are internal to 18F, you can chat with us in the #bots Slack channel.

If you are not internal to 18F and have a question, we would be delighted to help. Please open a GitHub issue and we will get back to you as soon as we can.

Public domain

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication.

For more information, see license.